Strange changes to permissions when changes made to logging files

[Ghost]

I anyone else aware (or heard of) strange changes being made to login permissions after changes have been made to the logging files? (It may be unrelated, but we also recently applied the latest service pack 4 patch about 4 days ago).

 

[Kyperion]

You applied Service pack 4 for NT or the NT4 option pack that upgrades to IIS4.

 

[Ghost]

We are running NT4 and had already loaded Service pack 4 to it. The patch we just applied a few days ago (we were told) was to fix a security hole and also (supposedly) fix a bug in the logging functions.... We got the patch out on

http://www.ntsecurity.net.

Was this a reasonable thing to do?

 

[Kyperion]

NT4 service pack 4 is still in beta, and because of that I have not messed with it on any of our production machines. I ma not sure what effects it will have on the IIS sub-system, but I would try uninstallingthe beta SP and revert to SP3 and see if that clears your logging problem.<br>
<br>
Other then that you can try running the NT Option pack install again and hit the add/remove button. This will allow you to go into the set-up options and make sure that the logging components were in fact installed.<br>

 

[Ghost]

Strangely enough the solution was to simply reasign the virtual to a different IP address and then reasign it again back to the original one. This must have reset the logging or something because the site came back up when I did this. So the hotfix for the logging routine definitely screwed something up. It also cause my CPU to get bogged down which was corrected when I reaplied the patch.