Hello, have ISA 2006 running on Server 2003 with rapidly growing text file called wsISA.txt being saved to C:\temp which deletes on reboot. Last reboot file had grown to over 46 GB & starting to cause space issues. Can't find anything on net - any suggestions?
I can not open the file at this time since it has grown to large. It is currently over 50GB in size. You also can not delete or rename the file since it is locked.
I was told that the file looks like it reset to 0 when you reboot but I have not been able to confirm since the server currently has over 1000 users on it and I can not reboot it.
I checked the web and was not able to find anything on the file except some one asking the same question. I am not sure but it looks like the problem started after the latest update for ISA was installed.
you might review a part of the text file by using the type command in a command prompt. I wouldn't try opening it with notepad or wordpad
_____________________________
Marcel Netherlands
MCTS, MCITP (SA,EA) MCP, MCSA:Security, MCSE:Security, CCNA, CCSA, CCSE, CCSE+ No matter how secure, there is always the human factor. http://www.phetios.com/
Posts: 271
Joined: 5.May2001
From: Redmond, WA
Status: offline
quote:
ORIGINAL: SteveMoffat
In 10 years of ISA I have never seen a wsisa.txt file. What 3rd party applications/filters do you have installed on the ISA box?
"wsisa.txt", huh? Who wants to take the bet that it's related to a WebSense plug-in? Yano; "ws", "WebSense"? use process explorer to see who owns it. if you see fwsrv (or perhaps "wspsrv"), then it's a plug-in. ISA don do dat.
I have already went down the road. This server does have Web Sense installed but it looks like the wspsrv is the process that locked the file. I am going to reboot the server tonight and see if that clears the file.
Rebooted the server last night. The file did reset back to 0 but then started filling again. When I opened the file it look like a Firewall Log. I went in and checked the firewall logging settings and it is set to write the logs to the D drive. I checked it and it is logging to the D drive so I am not sure why it is also using this log in the C temp folder.
Have you checked Jim Harrisons advice? Might worth trying to disable websense. I haven't websense over here so I can't review it for you.
_____________________________
Marcel Netherlands
MCTS, MCITP (SA,EA) MCP, MCSA:Security, MCSE:Security, CCNA, CCSA, CCSE, CCSE+ No matter how secure, there is always the human factor. http://www.phetios.com/
I took your advice and look at it as a Web Sense issue. It turns out that the WSISA.txt is the debug log for Web Sense. The Web Sense admin had been working on an issue with Web Sense and turn on their debug logging and forgot to turn it off.