We have a .NET 2.0 based Windows Service that is part of our Product Suite and it is a Socket based file multi-threaded File storage service (DICOM server). That accepts data from multiple clients and then stores the files onto the Disk in a Catalog. The file sizes are anywhere from 1Kb to 20MB in size. The actual sockets are implemented by a third-party library that we create an instance of when we start the service. That Library does the actual task of receiving connections and receiving data and storing it. It is depended on couple of .NET assemblies. Our Service depends on - MS SQL Express 2005 SP3 (Makes entries for each file received) - Firewall is turned off - Defender is turned off - TCP-IP 4 based connectivity over a 1GB network card We have noted a behavior that we are unable to get a handle on. Every now and then (Week to 10 days etc), the service starts dropping files and/or fails to save the files to the hard-drive. So we get incomplete set of Files or corrupted files We tried the following - Restart the service. Does not really fix the problem but it does sometime give us extra time. But the Service woild fail neverthless even when restarted - We tried to capture detail logs and windows Event logs. Nothing was found that could point to the issue But if we switch/change the LOG-ON user for that service from one Administrator to Another then it works fine. We have created 2 local admin accounts. So switching the LOGON user actually makes the service work and then after a few days or a week or two it happens again Environment - Our service is installed within a corporate environment. But the Service itself runs on a desktop that is isolated from their Active Directory. So our Desktop is assigned a Static DHCP IP address but its not part of the Corporate Active Directory. Any suggestion as to whats going on here?

We have a .NET 2.0 based Windows Service that is part of our Product Suite and it is a Socket based file multi-threaded File storage service (DICOM server). That accepts data from multiple clients and then stores the files onto the Disk in a Catalog. The file sizes are anywhere from 1Kb to 20MB in size. The actual sockets are implemented by a third-party library that we create an instance of when we start the service. That Library does the actual task of receiving connections and receiving data and storing it. It is depended on couple of .NET assemblies. Our Service depends on - MS SQL Express 2005 SP3 (Makes entries for each file received) - Firewall is turned off - Defender is turned off - TCP-IP 4 based connectivity over a 1GB network card We have noted a behavior that we are unable to get a handle on. Every now and then (Week to 10 days etc), the service starts dropping files and/or fails to save the files to the hard-drive. So we get incomplete set of Files or corrupted files We tried the following - Restart the service. Does not really fix the problem but it does sometime give us extra time. But the Service woild fail neverthless even when restarted - We tried to capture detail logs and windows Event logs. Nothing was found that could point to the issue But if we switch/change the LOG-ON user for that service from one Administrator to Another then it works fine. We have created 2 local admin accounts. So switching the LOGON user actually makes the service work and then after a few days or a week or two it happens again Environment - Our service is installed within a corporate environment. But the Service itself runs on a desktop that is isolated from their Active Directory. So our Desktop is assigned a Static DHCP IP address but its not part of the Corporate Active Directory. Any suggestion as to whats going on here? Any suggestions or solution from the Bright MVPs on the forum. It will greatly help alleviate the issue and make my life easier.

Just make sure that you are not running out of desktop heap. How to use DHeapMon.exe to troubleshoot Desktop Heap issues http://blogs.msdn.com/b/alejacma/archive/2008/07/29/how-to-use-dheapmon-exe-to-troubleshoot-desktop-heap-issues.aspx Also try checking the "allow service to interact with desktop" box in the service properties, resart the service and observe if it recurs in the same time frame. Desktop Heap Overview http://blogs.msdn.com/b/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx Check the eventlog for any errors around that time. Sumesh P - Microsoft Online Community Support