EIAM Services dont start on fresh install - Revision history

Erik.johnson at 16:33, 30 March 2010

2010-03-30T16:33:51Z

Erik.johnson at 16:32, 30 March 2010

2010-03-30T16:32:33Z

Erik.johnson at 16:31, 30 March 2010

2010-03-30T16:31:31Z

Erik.johnson at 16:25, 30 March 2010

2010-03-30T16:25:21Z

Mitcr01 at 19:27, 23 August 2009

2009-08-23T19:27:55Z

Mitcr01 at 19:27, 23 August 2009

2009-08-23T19:27:41Z

Akhilkmathur: New page: '''EIAM does not start on install''' I had to install Service Desk, Service Catalog and Workflow on a very new image. I started with the install shield and went through the instructions a...

2009-08-21T18:41:06Z

New page: '''EIAM does not start on install''' I had to install Service Desk, Service Catalog and Workflow on a very new image. I started with the install shield and went through the instructions a...

New page

'''EIAM does not start on install'''

I had to install Service Desk, Service Catalog and Workflow on a very new image. I started with the install shield and went through the instructions and steps provided for a clean install of all this products. Though I did not recieve any error's while I was doing the install, I still could not get the EIAM services to start. <br>

When I looked at the services on the server, I could see the eTrust Directory services were stopped and would not start when I try manually or through command line. I was not getting enough help from the log's to narrow down the problem. <br>

Finally, not have anywhere to go, I uninstalled all the Unicenter products and rebooted the machine and tried to install again, but this time I was using another User ID logging into the server. [Note: The permissions on both the id's I used were exactly the same and were a part of Administrative Group on the local machine] <br>

'''This time, I was able to successfully install everything and also had the EIAM working, wondering what might be the issue...we noticed that when you install the CA products it does not like the user account to be all numbers....In our enviornment and in this particular case, our USER ID to login to the server are 9 digit numbers. EIAM does not like userid to be starting with a number...'''

The second time I installed the products again, I used a alpha-numeric userid and everything worked normal.

Thought I will share this with anyone who might have faced a similar issue.

Thanks <br>
AKM

@@ Line 21: / Line 21: @@
 I encountered a similar problem on our test server, and a full wipe and reinstall didn't fix it, nor did a database wipe. I think it may be hardware specific, because we are using an account with no numerals in it. Our problem was that EIAM was taking a very long time to load, and the Unicenter Service cannot start until this is done, but it does not intuitively know that it needs to wait so Services would have to be manually started each time. The only way I was able to reconcile this was to create Service dependencies so that the Unicenter Service will not try to start until the EIAM (eTrust) Services have. The settings for such a configuration get wiped out upon reboot, so I had to put it into a batch file and have it run as a scheduled task on Startup to ensure the process was followed.
-Here's the code from the batch file:<br>
+Here's the code from the batch file (Service dependencies separated by a '/' as per sc.exe syntax):<br>
 @echo off<br>
 c:\windows\system32\dllcache\sc.exe config pdm_daemon_manager depend= DXserver_iTechPoz-SERVER_HOSTNAME/DXserver_iTechPoz-SERVER_HOSTNAME-Router/ssld_iTechPoz-Server/dxadmind_master

@@ Line 21: / Line 21: @@
 I encountered a similar problem on our test server, and a full wipe and reinstall didn't fix it, nor did a database wipe. I think it may be hardware specific, because we are using an account with no numerals in it. Our problem was that EIAM was taking a very long time to load, and the Unicenter Service cannot start until this is done, but it does not intuitively know that it needs to wait so Services would have to be manually started each time. The only way I was able to reconcile this was to create Service dependencies so that the Unicenter Service will not try to start until the EIAM (eTrust) Services have. The settings for such a configuration get wiped out upon reboot, so I had to put it into a batch file and have it run as a scheduled task on Startup to ensure the process was followed.
-Here's the code from the batch file.
+Here's the code from the batch file:<br>
-@echo off
+@echo off<br>
 c:\windows\system32\dllcache\sc.exe config pdm_daemon_manager depend= DXserver_iTechPoz-SERVER_HOSTNAME/DXserver_iTechPoz-SERVER_HOSTNAME-Router/ssld_iTechPoz-Server/dxadmind_master

@@ Line 19: / Line 19: @@
 Update by Erik:
-I encountered this problem on our test server, and a full wipe and reinstall didn't fix it, nor did a database wipe. I think it may be hardware specific, because we are using an account with no numerals in it. The only way I was able to reconcile this was to create Service dependencies so that the Unicenter Service will not try to start until the EIAM (eTrust) Services have. The settings for such a configuration get wiped out upon reboot, so I had to put it into a batch file and have it run as a scheduled task on Startup to ensure the process was followed.
+I encountered a similar problem on our test server, and a full wipe and reinstall didn't fix it, nor did a database wipe. I think it may be hardware specific, because we are using an account with no numerals in it. Our problem was that EIAM was taking a very long time to load, and the Unicenter Service cannot start until this is done, but it does not intuitively know that it needs to wait so Services would have to be manually started each time. The only way I was able to reconcile this was to create Service dependencies so that the Unicenter Service will not try to start until the EIAM (eTrust) Services have. The settings for such a configuration get wiped out upon reboot, so I had to put it into a batch file and have it run as a scheduled task on Startup to ensure the process was followed.
 Here's the code from the batch file.
 @echo off
 c:\windows\system32\dllcache\sc.exe config pdm_daemon_manager depend= DXserver_iTechPoz-SERVER_HOSTNAME/DXserver_iTechPoz-SERVER_HOSTNAME-Router/ssld_iTechPoz-Server/dxadmind_master

← Older revision		Revision as of 16:25, 30 March 2010
Line 15:		Line 15:
	Thanks <br>		Thanks <br>
	AKM		AKM
		+
		+
		+	Update by Erik:
		+
		+	I encountered this problem on our test server, and a full wipe and reinstall didn't fix it, nor did a database wipe. I think it may be hardware specific, because we are using an account with no numerals in it. The only way I was able to reconcile this was to create Service dependencies so that the Unicenter Service will not try to start until the EIAM (eTrust) Services have. The settings for such a configuration get wiped out upon reboot, so I had to put it into a batch file and have it run as a scheduled task on Startup to ensure the process was followed.
		+
		+	Here's the code from the batch file.
		+	@echo off
		+	c:\windows\system32\dllcache\sc.exe config pdm_daemon_manager depend= DXserver_iTechPoz-SERVER_HOSTNAME/DXserver_iTechPoz-SERVER_HOSTNAME-Router/ssld_iTechPoz-Server/dxadmind_master

@@ Line 5: / Line 5: @@
 When I looked at the services on the server, I could see the eTrust Directory services were stopped and would not start when I try manually or through command line. I was not getting enough help from the log's to narrow down the problem. <br>
-Finally, not have anywhere to go, I uninstalled all the Unicenter products and rebooted the machine and tried to install again, but this time I was using another User ID logging into the server. [Note: The permissions on both the id's I used were exactly the same and were a part of Administrative Group on the local machine.
+Finally, not have anywhere to go, I uninstalled all the Unicenter products and rebooted the machine and tried to install again, but this time I was using another User ID logging into the server. [Note: The permissions on both the id's I used were exactly the same and were a part of Administrative Group on the local machine].
-'''This time, I was able to successfully install everything and also had the EIAM working, wondering what might be the issue...we noticed that when you install the CA products it does not like the user account to be all numbers. In our environment, and in this particular case, our USER ID to login to the server are 9 digit numbers. EIAM does not like userid to be starting with a number.'''
+'''This time, I was able to successfully install everything and also had the EIAM working, wondering what might be the issue...we noticed that when you install the CA products it does not like the user account to be all numbers. In our environment, and in this particular case, our USER ID to login to the server are 9 digit numbers. EIAM does not like userid to be starting with a number'''
 The second time I installed the products again, I used a alpha-numeric userid and everything worked normal.