The actual translated file path is -
\\co2adsaxfile01\DisplayYieldLogs\AvailsLogs\CO2ADSAXAMWEB01\AvailsRequestLog.log. So this should not be a problem given what I understood from reading the link you provided regarding special characters.
We are basically logging the requests to a web method into that file. That web method is part of the SOAP-based ASP.NET web service running on IIS 7 (IIS 7 is configured to be running in compatibility mode of IIS 6).
The service is hosted on a single app-pool on any particular web server. The app-pool is restarted every 20 minutes. Hence there may be a few seconds during which IIS will be killing the old app-pool and starting a new one. Every web service instance (running
on the different web servers) will write to its own log file (the machine name is used in the folder path, e.g. CO2ADSAXAMWEB01). Hence across the servers, there should not be any lock contention.
From your statements, it looks like unless there is some sort of lock contention, the GUID should not appear as a prefix to the filename. Is there any recommended way to debug this locking problem ? By design, the contention should not happen in our code.
I am wondering what I should do to fix this.
The interval of midnight is a good suggestion. I will get can changed immediately.