Check the drive space on the host AP for this CP. Shrink uses extra space
and you may be running out.
I'm not certain but since the ICC session failed during the 'shrink' it may
have left the database locked causing the remaining sessions to fail.
I hate to be a killjoy but it's just these types of problems that cause me
to avoid 'automatic' scripts to handle my CP's. These are fragile databases
that can sometimes be easily corrupted. Everything has to go just right or
the synchronization between the running CP, its workfile, it's locks, and
CSA can be fowled.
-Original Message-
From: Stan Brown [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 02, 2000 7:29 AM
To: [EMAIL PROTECTED]
Subject: upload/shrink/checkpoint problems
I jsut deployed my new upload/shrink/checkpoint script on a new node,
and it failed during the run last night.
Can anyone give me some insight into what this failure means? Here is
the ouput of one station:
Starting upload/checkpoint...
Mon May 1 23:00:05 GMT 2000 --- upload and checkpoint CP0401
DONE 1 OPEN CP0401!: Mon May 1 23:00:06 2000
DONE 2 UPLOAD CP0401!: Mon May 1 23:04:53 2000
FAIL 3 SHRINK CP0401!: Mon May 1 23:06:53 2000 -15 ICCshrink
error: class=
-30 error= 0 text= ICCinit: CCshrink problem
FAIL 4 CHECKPOINT CP0401!: Mon May 1 23:06:53 2000 -15 ICCchkpt
error: clas
s= 20 error= 1 text= Session not in progress
FAIL 5 CLOSE CP0401!: Mon May 1 23:06:53 2000 -16 ICCclose error:
class= 20
error= 1 text= Session not in progress
DONE 6 EXIT CP0401!: Mon May 1 23:06:53 2000
I _think_ all the later errors are trigered by the shrink problem,
but I am not certain of this.
Any insight would be greatly appreciated.
--
Stan Brown [EMAIL PROTECTED]
843-745-3154
Charleston SC.
--
Windows 98: n.
useless extension to a minor patch release for 32-bit extensions and
a graphical shell for a 16-bit patch to an 8-bit operating system
originally coded for a 4-bit microprocessor, written by a 2-bit
company that can't stand for 1 bit of competition.
-
(c) 2000 Stan Brown. Redistribution via the Microsoft Network is
prohibited.
---
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with unsubscribe foxboro in the Subject. Or, send any mail to
[EMAIL PROTECTED]
