P
protactinium
Guest
A few months ago we started hosting many of our websites on a Plesk server, and for the most part we've been quite happy with the results. One problem we are having though is with the data that is recorded in the IIS logs with DotNetNuke websites.
DNN websites are database driven and use dynamic URLs. On our old servers, these dynamic URLs are recorded correctly in the log files, whereas on our Plesk server, it is only recording entries for actual physical files (ie., default.aspx almost 100% of the time). The websites function perfectly fine, but it causes issues with our stats program as it is unable to read the relevant URLs.
Looking in IIS, the logging settings are set exactly the same as on our old servers, which leads me to believe that there is perhaps some kind of Plesk handler that is interfering with what is being recorded. See below for a screenshot of our IIS log settings.
I notice that the Directory is set to the \inetpub\logs\LogFiles, whereas they are actually being saved within each websites own statistics\logs folder, so this further indicates some interference from Plesk.
Any help or suggestions would be appreciated as we've been scratching our heads for a little while about what to do.
DNN websites are database driven and use dynamic URLs. On our old servers, these dynamic URLs are recorded correctly in the log files, whereas on our Plesk server, it is only recording entries for actual physical files (ie., default.aspx almost 100% of the time). The websites function perfectly fine, but it causes issues with our stats program as it is unable to read the relevant URLs.
Looking in IIS, the logging settings are set exactly the same as on our old servers, which leads me to believe that there is perhaps some kind of Plesk handler that is interfering with what is being recorded. See below for a screenshot of our IIS log settings.
I notice that the Directory is set to the \inetpub\logs\LogFiles, whereas they are actually being saved within each websites own statistics\logs folder, so this further indicates some interference from Plesk.
Any help or suggestions would be appreciated as we've been scratching our heads for a little while about what to do.