Im doing Fresh Installation of sdm 17.0 with latest release (patch 17.1). But it got failed at 'Configuring CA Service Desk Manager' step. as shown in screenshot2
then i click ok and finish the setup. and run the COnfigure but still it fails at last step. as below.
The error i can see in stdlog is below....cannot connect to domsrvr...what could be issue?
When there's an error about the domsrvr being unable to connect, there's typically other errors associated to it. I think a full review of the logs are going to be necessary here. You may want to open a Support case if nothing obvious is displayed in the logs for you to see.
Following up on that thought, La-Qa, the installation log may also give us more insight into why the configuration failed initially. According to your screenshot, it's located under C:\Users\SERVIC~1\AppData\Local\Temp\casm\install.log (so the user folder for your ServiceDesk user, most likely). If you're not sure what the log is indicating, or you'd like us to assist in the analysis, please open a case and upload both the install.log and your whole log folder for us to examine.
Dear Joh & Alex
Thanks for your .. Ijust noticed that after failing at last step....the sdm services in services.msc is showing starting status...and after few minutes it changed to 'started'. And now i can login into servicedesk.
i didnt face this type of behaviour since im working on sdm implementation....what could be this issue??
i did again reconfigure to check this issue and agian same thing happened..it failed at last step ..but after few min services started successfully.
if i restart the sdm service from services.msc ..then it not starts...it gives error...sdm services started n then stop...
what could be issue??
also i i checked pdm_status command..4 services not running...wt is related to?? still sdm is accessible
Check out the knowledge article to see whether it helps: When installing CMDB R12.1 on windows 2008, the error, "Task failed (Start CA Service Desk service(s) in db admin mode.). Continue?" occurs during the configuration.
Already i applied this but not worked
Please let us know if you are continuing to run into difficulties with your 17.1 installation. If needed, we can review you logging and application behaviours in a support case.
To answer one of your earlier questions, the ehc_nxd, filter_nxd and ehwrter, all have to do with the older NSM integration, which is no longer in use. These processes can be safely ignored. The pdm_intrvlog_nxd process is Interval Logging, which is only a concern if you have consciously turned it on in SDM and are using it per Support instructions to review your install for any process deficiencies.
I just noticed that your installation was done under the E: \.Is 8dot3name enabled on the E: \.One way to see if the "Service Desk Manager" directory has activated its short name, you run the dir / x command in an MS-DOS window. (see screenshot)
If you cant find (SERVIC~1) the short name is not activated.
Service Desk needs short name when it tries to execute some script. If 8dot3name is not activated, you will have problems without stopping.
- What I suggest you do is uninstall Service Desk in full, - You also erase all CA directories. - You open an MS-DOS prompt as administrator. - You execute the command: fsutil 8dot3name set E: 0
After you re-install Service Desk from the beginning and inform us during the installation.
I had exactly the same problem, Microsoft does not auto-enable the generation of short names on the disk.
Something else to check... We had a similar issue and it turned out to be the fact that we had 2x network cards (NIC's) on the server. We had to apply a patch to Service Desk to sort it out.
Jon_Israel is a Pro on these matters, any advice to them Jon?