service needs to be started about 3-4 times a day

[seiadmin]

we have 2 users connecting to SOS, the VSS DB is located on another server.

SOS version 4.2
no cryptography
VSS 6.0d
windows 2003 sp2
using port 80
sos is in the dmz
firewall allows port 80 in the dmz with no restrictions

the other server also runs VSS6.0d

about 3 - 4 times a day I have to restart because the other 2 users can no longer connect

when I look at the logs this is what I see

user ip: is the users we allow to connect
sos ip: my sos server


4/3/2007 8:27:53 AM - Connection accepted from user IP:4565 on local address sos ip:80, session id is 1.
4/3/2007 8:35:55 AM - Connection accepted from user IP:4578 on local address sos ip:80, session id is 2.
4/3/2007 12:18:57 PM - Connection accepted from user IP:3947 on local address sos ip:80, session id is 3.
4/3/2007 12:32:11 PM - 3: Exception: An existing connection was forcibly closed by the remote host
4/3/2007 12:43:45 PM - Connection accepted from 209.172.11.6:37443 on local address sos ip:80, session id is 4.
4/3/2007 12:43:45 PM - 4/3/2007 12:43:45 PM - Server Exception (407): [GET /a1b2 - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:45 PM - 4: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:45 PM - Connection accepted from 209.172.11.6:37522 on local address sos ip:80, session id is 5.
4/3/2007 12:43:45 PM - 4/3/2007 12:43:45 PM - Server Exception (407): [GET /adxm - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:45 PM - 5: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:46 PM - Connection accepted from 209.172.11.6:37558 on local address sos ip:80, session id is 6.
4/3/2007 12:43:46 PM - 4/3/2007 12:43:46 PM - Server Exception (407): [GET /adse - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:46 PM - 6: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:46 PM - Connection accepted from 209.172.11.6:37594 on local address sos ip:80, session id is 7.
4/3/2007 12:43:46 PM - 4/3/2007 12:43:46 PM - Server Exception (407): [GET /phpA - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:46 PM - 7: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:46 PM - Connection accepted from 209.172.11.6:37628 on local address sos ip:80, session id is 8.
4/3/2007 12:43:46 PM - 4/3/2007 12:43:46 PM - Server Exception (407): [GET /phpa - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:46 PM - 8: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:46 PM - Connection accepted from 209.172.11.6:37668 on local address sos ip:80, session id is 9.
4/3/2007 12:43:46 PM - 4/3/2007 12:43:46 PM - Server Exception (407): [GET /phpa - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:46 PM - 9: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:47 PM - Connection accepted from 209.172.11.6:37701 on local address sos ip:80, session id is 10.
4/3/2007 12:43:47 PM - 4/3/2007 12:43:47 PM - Server Exception (407): [GET /Ads/ - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:47 PM - 10: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:47 PM - Connection accepted from 209.172.11.6:37797 on local address sos ip:80, session id is 11.
4/3/2007 12:43:47 PM - 4/3/2007 12:43:47 PM - Server Exception (407): [GET /ads/ - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:47 PM - 11: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:47 PM - Connection accepted from 209.172.11.6:37839 on local address sos ip:80, session id is 12.
4/3/2007 12:43:47 PM - 4/3/2007 12:43:47 PM - Server Exception (407): [GET /xmlr - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:47 PM - 12: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:48 PM - Connection accepted from 209.172.11.6:37876 on local address sos ip:80, session id is 13.
4/3/2007 12:43:48 PM - 4/3/2007 12:43:48 PM - Server Exception (407): [GET /xmlr - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:48 PM - 13: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:48 PM - Connection accepted from 209.172.11.6:37926 on local address sos ip:80, session id is 14.
4/3/2007 12:43:48 PM - 4/3/2007 12:43:48 PM - Server Exception (407): [GET /xmls - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:48 PM - 14: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:48 PM - Connection accepted from 209.172.11.6:37965 on local address sos ip:80, session id is 15.
4/3/2007 12:43:48 PM - 4/3/2007 12:43:48 PM - Server Exception (407): [GET /blog - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:48 PM - 15: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:48 PM - Connection accepted from 209.172.11.6:38001 on local address sos ip:80, session id is 16.
4/3/2007 12:43:48 PM - 4/3/2007 12:43:48 PM - Server Exception (407): [GET /drup - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:48 PM - 16: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 12:43:48 PM - Connection accepted from 209.172.11.6:38040 on local address sos ip:80, session id is 17.
4/3/2007 12:43:48 PM - 4/3/2007 12:43:48 PM - Server Exception (407): [GET /comm - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/3/2007 12:43:48 PM - 17: Exception processing messages: UNRECOGNIZED_MESSAGE
4/3/2007 1:13:42 PM - Connection accepted from user IP:1914 on local address sos ip:80, session id is 18.
4/3/2007 1:17:40 PM - Connection accepted from user IP:1918 on local address sos ip:80, session id is 19.
4/3/2007 1:21:58 PM - Connection accepted from user IP:1924 on local address sos ip:80, session id is 20.
4/3/2007 1:26:11 PM - Connection accepted from user IP:1927 on local address sos ip:80, session id is 21.
4/3/2007 1:31:58 PM - Stopping the service.
4/3/2007 1:31:58 PM - Exception in Listen(): System.Net.Sockets.SocketException: A blocking operation was interrupted by a call to WSACancelBlockingCall
at System.Net.Sockets.Socket.Accept()
at System.Net.Sockets.TcpListener.AcceptSocket()
at ClassicService.Listener.Listen()

[lbauer]

There might be a couple of things going on:

1 -- If you have the VSS 6.0d automation component, version ending in 98.48, then you may be experiencing a concurrency crash:

http://support.sourcegear.com/viewtopic.php?t=10

2 -- This error message means the SOS Server is getting messages it doesn't understand:

4/3/2007 12:43:46 PM - 9: Exception processing messages: UNRECOGNIZED_MESSAGE

Since you're using port 80 for SOS, the SOS Server is probably getting hit with a lot of random HTTP traffic, since 80 is the default for IIS. This can de-stabilize the SOS Server. Try using a different port.