Windows Services required for TDM Portal
search cancel

Windows Services required for TDM Portal

book

Article ID: 231579

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

Experiencing TDM Portal service failures. The portal service fails with "The CA Test Data Manager Portal service failed to start due to the following error:  The account name is invalid or does not exist, or the password is invalid for the account name specified.

Servers are restarted every night at 11PM EST. This error pops up almost every other day. A manual start of the service works fine. 

Microsoft has said that this may be due to network latency or some windows services not starting before the Portal service. 

Need to know all the mandated Windows services that are required for the Portal service to start successfully.

Environment

Release : 4.9

Component : TDM Web Portal

Resolution

As per development team review, we don't have a list of dependent services otherwise we would made a dependency from them. But what Microsoft means is DNS, LDAP, domain and similar services. You can try changing startup type from Automatic to Automatic (delayed).

https://superuser.com/questions/285653/what-does-delayed-start-do-in-startup-type-for-a-windows-service

  • A service marked as Automatic (Delayed Start) will start shortly after all other services designated as Automatic have been started. In my experience, this means that they are started 1-2 minutes after the computer boots.
  • The setting is most useful in lessening the "mad rush" for resources when a machine boots.
  • Note that when you have 20 services all being started at the same time, each will start up slower as it competes with the others for slices of the machine's precious resources (CPU/RAM/Disk/Network). That is, each service takes longer to become available!
  • If you have a few services that are critical, then you may want to set those few to Automatic and set as many of the others as you can to Automatic (Delayed Start). This will ensure that the critical services get the most resources early and become available sooner, while the non-critical services start a bit later (which by definition is ok).