My CA-Dataminder machine was running smoothly. But for some requirements I change the hostname of my CA server.
after this CA admin console can't connecting. plz check attachment for the error details.
Is there any official person responsible for users answers.>?
The communities site is monitored, but there is no official person responsible to answer the question in a specific time frame. For quicker response, I suggest opening an official support case.
Heh heh heh.... Don't do that. Do a complete reinstall or revert back to the old hostname. If you want to try and fix this without reinstalling be prepared to up the log levels and spend many hours troubleshooting (you'll also may need to work with undocumented registry keys).
If the CMS database is not local, and you want to take a stab at it, comb through the registry (both 32 and 64 bit) and change any references from the old CMS to the new CMS. Then locate your startup.properties file and change that too. In the database, update the CMS hostname in the WgnMachine table. Reboot. Cross your fingers and hope for the best. If you get the Admin Console to load, you'll have to add your new CMS hostname to the list of CMS's. If you want to go this route its worth a shot, but highly unlikely that it will work. Good luck.
Edit 2: You should also be looking at the system and activity logs. They can be found in %wgndatadir%\logs.
As Beeks has alluded towards hostnames are a focal point for machine identification. This avoids issues whereby IP changes could impact upon machine accessibility. With this in mind changing a hostname is not something to do lightly and reverting to the original hostname or a re-install are the most advisable courses of action.
However, these are general comments and observations. I would reiterate the recommendation from sprro04 that to address your issue, it may be prudent to progress the matter via an official support case.
Snr Support Engineer.
zabeehullah as Beeks come up with most appropriate answer to your issue, it's better to reinstall the setup rather to fight with unforeseen issues if you lay hands on OS registry . I guess you are doing all this in "test environment" and by reinstalling the setup, you'll remember the lesson that 'not to play with DLP in production environment'
Wgninfra is failing to start because the MachineName in the WgnMachine table and WgnWellknownString view doesn't match the hostname, but there is significantly more to this. Even if you did change the MachineName, there's the whole replication issue to consider.
You would need to re-parent all the downstream machines to the "new" CMS.
It's a good point though.
There needs to be an "Official" documented and supported way to:
a) Change the CMS name.
b) Clone a production CMS.
For a clone, you would also need to remove any references to "Child" machines from the clone, otherwise the clone CMS would attempt to connect to its previous children.
I would definitely concur - re-install...
Retrieving data ...