Odd happenings with CAUPDVSN.TXT


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Tom Fulton on October 03, 2006 at 09:22:44:

We upgraded Henry Calvin Fabrics to current versions of all Comet products. They are running on a Windows 2000 server. We installed
Comet as a service on the server so that it would be available for
C/A hosting on restarts. Monday we got a call that the Boston showroom could not connect. They were receiving an excp 2 on file
CAUPDVSN.TXT Their INI file has an entry for 'C' type directory
$(CATEMP) When I connected to their server there were only the QDIR
files in CATEMP. I created the text file and added 373 as a version.
I was then able to connect and Boston was also. This morning we got
a call that Boston was connected but the San Fran showroom was getting the excp 2. We connected up and found CAUPDVSN.TXT as a zero
byte file. We restarted Comet and the file is now there with 372 in
it. SF showroom has connected up. I'm not sure where to even start
with the questions. Monday morning was probably a startup of the server, so the file not being there has something to do with timing
or permissions? I don't believe the server was restarted overnight,
they do Veritas backup with open files option. So where did the 373
that I input yesterday go? Why did it show 372 on restart? I think
I'll remove it as a service for the time being. Tom.


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):






[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]