error logs

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

I have msas installed on a win200 server that has been
running ok for a while. Last Friday the "error" log file
grew to the 625mb of free space on the C drive. Obviously,
the file was to large to open but I was able to remove it
and eventually delete the error.txt file.

Has anyone seen this kind of activity?
 
I have msas installed on a win200 server that has been
running ok for a while. Last Friday the "error" log file
grew to the 625mb of free space on the C drive. Obviously,
the file was to large to open but I was able to remove it
and eventually delete the error.txt file.

Has anyone seen this kind of activity?
Click to expand...

Yes, few people reported this problem on the newsgroups here and the
solution you have found (to delete the error log) is the only available
now.
 
As Mikolaj says. This has been reported here a number of times, and I've
experienced the issue myself 3 times--in each case on a Windows 2000
servers.

My own advice would be that if watching this carefully isn't to your taste,
I'd recommend removing the current beta product from the server.

I've seen it go normally for weeks, and then take off and eat available disk
space. It will run to 4 gigs on an NTFS partition--and when it hits that
limits, it may show high CPU usage until the condition is cleared--i.e. stop
the processes and delete the file. Not pretty symptoms to see on a
production machine.
 
I am experiencing problems with an error log which grows
constantly and i am using XP.

The error message that is being written is as follows:-

91::ln 0:Object variable or With block variable not
set::gcasDtServ:modAgentsDataStore:SaveData::30/06/2005
22:19:39:XP:1.0.614

Exactly the same message wrote to the log file 39 times in
the 1 second i looked at. I have been having this problem
ever since I first installed about 4 months ago
 
Thanks--I have now found an XP machine with this issue--still have the same
recommendations, though. If you can't tolerate the possibility of this
fault--remove the beta.

I'm glad you also posted that this was with the new build. I'd seen one
post that this might have been fixed, and was looking for corroboration.
Looks like not!

--
 
Back
Top