Reply to thread

Message

<blockquote data-quote="Big_Kev" data-source="post: 209406" data-attributes="member: 52102">Hi risu,Is there anything showing in the log file? You need to look at it immediately after the problem occurs to see if there was an issue during the initial connection, and at what stage it occurred.The web server starts up and tries to listen on the port specified - that could be the issue. Or when the initial connection is made to the database engine, though this is a client connection and is much less likely to cause a socket error...Hopefully the log might throw some more light on it.Regards,KevEDIT: During an update, the service is stopped first and re-started afterwards using direct calls to the services manager, so it is definitely stopped and started cleanly. If you are using vista, you should be able to select a startup option for the web server of delayed automatic (or automatic delayed - I can't remember which it is). This might give any dependencies a chance to start up first.</blockquote>

[QUOTE="Big_Kev, post: 209406, member: 52102"] Hi risu, Is there anything showing in the log file? You need to look at it immediately after the problem occurs to see if there was an issue during the initial connection, and at what stage it occurred. The web server starts up and tries to listen on the port specified - that could be the issue. Or when the initial connection is made to the database engine, though this is a client connection and is much less likely to cause a socket error... Hopefully the log might throw some more light on it. Regards, Kev EDIT: During an update, the service is stopped first and re-started afterwards using direct calls to the services manager, so it is definitely stopped and started cleanly. If you are using vista, you should be able to select a startup option for the web server of delayed automatic (or automatic delayed - I can't remember which it is). This might give any dependencies a chance to start up first. [/QUOTE]

Verification