|
Author Topic:   TMLogScan poll
KiLlEr
Member
posted March 04, 2004 03:37 PM            
KV is having trouble runing LogSCan under 98se, I'm wondering what OS is everyone else using LogScan on. Please post the OS that you are using to run LogSCan on.

I'm running it on XP Pro Service Pack 2

IP:

BamZipPow
Member
posted March 04, 2004 08:34 PM            
Win98se, Win2000 Pro SP4, WinXP Pro SP1/2...

[This message has been edited by BamZipPow (edited March 04, 2004).]

IP:

=DNX= Matrix
Member
posted March 04, 2004 09:30 PM            
XP Pro (corporate) Build 2600

IP:

BamZipPow
Member
posted March 04, 2004 10:42 PM            
Exactly what kind of problems is he having?

More info is required, please...

IP:

CyberCannon
Member
posted March 05, 2004 12:53 AM            
NEED INPUT, NEEEEEEED INPUT...

------------------
An Irish Blessing
May the road rise to meet you.
May the wind be always at your back.
May the sun shine warm upon your face.
The rains fall soft upon your fields and,
Until we meet again.
May God hold you in the palm of His hand.

CC

IP:

Blue n Gold Sue
Member
posted March 05, 2004 02:13 AM            
Win2K pro, sp2

IP:

kv
Member
posted March 05, 2004 07:41 AM            
I used to be able to run logscan, but now I get "file is empty" errors when logscan tries to update.

IP:

Robo Jaws
Member
posted March 05, 2004 07:54 AM            
W2k pro Sp4.

I have just had to re-install logscan as I was geting 2gigs of logfiles per day
each file was growing by 1med per day and logs where being generated every few mins.

after the re-install Ive got 1 logfile of 730K in 3days

so maybe a uninstall and reinsatll of logsacan will do the trick

[This message has been edited by Robo Jaws (edited March 05, 2004).]

IP:

KiLlEr
Member
posted March 05, 2004 10:56 AM            
KV's trouble is that TM's dedicated.log file is locked while TM is running. He can't even open the logfile with notepad. Something on his system is preventing shared access to files opened as shared write (which is what TM opens the log files as) which is causing logscan to barf.

IP: