This content has been marked as final. Show 5 replies
My guess is that this is the 'standard' CS4 - debug issue. You must have msvc 2005 sp1 installed for it to run. There have been a number of posts about this.
so i need the full msvc not just the runtime libraries... i'll try that.
Ok... I managed to run the server both debug and release via command line. The second error mentioned above went away after installing Visual C 2005 sp 1.
However, if I start the either server, debug or release, via the services window, I always get a "Error 1053: The service did not respond to the start or control request in a timely fashion" message. I tried modifying the timeout as mention in here: http://support.microsoft.com/kb/922918/en-us upto 90000 milliseconds, but still I get timeouts.
But if I make the service to automatically start at boot... it is successful but not a workable solution cause I can't manually start or restart the service.
Anybody experiencing the same thing? I'm on a WIndows 2008 Server.
Is this an issue of not going able to run BOTH debug and release services at the same time. Or it doesn't matter. You just mean that you couldn't manually start the service on either debug or release?
if it's the latter, please make sure you have .NET 2.0 framework or later installed. You'll need that to make IDS as service. You mentioned that the service can automatically start at boot. If you don't have .NET 2.0 framework, I think it will show as if it started, but not really.
Let us know if this helps.
No, I can both run debug and release at the same time, but this is only if I set the service to run automatically upon boot up. But if I want to restart or manually stop and start the server, then I get the error message posted earlier. Increasing the timeout does not help as I still get the same error.
Yes I do have .NET 3.0 installed via the adding it as a feature of the 2008 server. An the service is working properly cause I can send SOAP messages through it from a separate client. Its only when I restart or manually start the service that it causes the problem.