This content has been marked as final. Show 2 replies
Would seem like an environment problem.
Windows services are started in a threaded manner. Thus if if service A depends on service B then service A might be started before B. That is normally solved with a dependency list as part of the service (part of the install.)
Other than that maybe a permissions problem whch impacts how soon something is ready to be used.