I use the Microsoft Enterprise 5 logging unit. When testing locally, all sliding flat files are created correctly and database logging in my local instance of SQL logs is as expected. The problem is when I publish my applications in a test environment. Here, when something strange happens: log files are created with strange GUID-like names. They ultimately roll, but it is very strange, and this often happens. Nor is Databse logging recorded. I could not find anything related to this problem on the Internet. I suspect authentication problems when configuring application pools and folders in IIS, but not sure. Does anyone have this problem? Here are my configuration settings:
<add name="Rolling Flat File Trace Listener" type="Microsoft.Practices.EnterpriseLibrary.Logging.TraceListeners.RollingFlatFileTraceListener, Microsoft.Practices.EnterpriseLibrary.Logging, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" listenerDataType="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.RollingFlatFileTraceListenerData, Microsoft.Practices.EnterpriseLibrary.Logging, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" fileName="D:\logs\MobileApps\rolling.log" formatter="Text Formatter" rollFileExistsBehavior="Increment" rollInterval="Hour" timeStampPattern="yyyy-MM-dd-hh" />
Files get type names
deb7f413-6cb3-44ac-900e-02883856e82bRolling.log rolling.2012-01-19-09.log
source share