Subj : WCSTATS
To   : All
From : RICK SPILMAN
Date : Thu Jan 31 2019 19:16:51

Date: Sat, 31 Mar 2001 08:09:00 -0400
From: RICK SPILMAN
To: CECIL BRIDGEWATER
Subject: WCSTATS
Newsgroups: win.server.wcreports
Message-ID: <986045960.37.986018489@winserver.com>
References:  <986018489.37.0@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 53

CB>Anyone out there using WCreports on win 2000 PRO?  Everything works with
CB>the exception of the STATS program. I get a error WCSTAT.exe has
CB>generated errors will be closed by windows.  This occurs when it
CB>attempts to access user 1.

CB>WCReports Bluebar version 5.02 Build 446
CB>Winserver 5.4.449.1


CB>A graphic server program appears to be loaded and requires me to use
CB>task manager to shut it down.

CB>Graphics server 4 for Windows 32 bit Version 4.05 Dec 11, 1995.

CB>The last thing that WCstat reports is Creating AVerage USER information


Hello Cecil.  I am glad you mentioned this.  I am using the same
wcReports since that is the last release of any updates to it as far as
major revisions.  I have the latest update to WINServer - 5.4.449.4
which was released earlier this month.

The Graphic Server you mention will stay open until it is closed
apparently manually or supposedly by the program that calls it.
However, since the stats generation is erring out, it never gets the
call to close from wcReports.

I am using Windows 2000 Server rather than the Pro version you mention
above.  For the past two weeks, my stats program
has been erring on the 'Activity 1' log processing.  That seems to be
the only place that it errors on me.  If I remove 'Activity.1' from the
directory, everything else works fine.  I thought that possibly last
week there was some garbage in that file and that is why all of a sudden
it had a problem.  However, it ran again last evening (runs on Friday
evening for Weekly Stats) and it errored again.  This week it said it
had a problem with "Call Number 16".  I removed call number 16 from the
file and reran.  It still said it had a problem with call number 16 so I
removed the whole file and it ran on through on the next attempt.

Now this does not help solve your problem, but maybe it makes you feel
better that someone else is seeing some strange occurrence similar to
yours.  I have not had time to track it much to see if there is anything
that I can tell about the problem.  If I get a chance, I will try to
look harder into it as I just thought last weekends run was a one time
occurrence.

Rick




                                
--- Platinum Xpress/Win/WINServer v3.1
 * Origin: Prison Board BBS Mesquite Tx  //telnet.RDFIG.NET www. (1:124/5013)

.