On Thu, 26 Mar 1998, Paul J. Sala wrote:

> 
> I have an application that runs on my Windows NT 4.0 server. 
> Each night the application retrieves a file out of afs
> and then updates a DB. Then it retrieves another file from afs
> and updates another DB.
> 
> After installing patch 7, things broke. The 1st file is retrieved
> and the DB updates. But when the application attempts to retrieve the
> 2nd file from afs, it fails.
> 
> The error message is:
>  File is not accessible. The remote server has been
>  paused or is in the process of being started.
> 
> This error message may not be valid because, I know the remote
> server is neither paused or being started, as I can access
> the file from other NT clients.
> 
> Any one seen anything like this or know what the problem is.
> 
> Thanks...........Paul
> ---------------------------------------------------------------
> Paul J. Sala                ||  Email: [EMAIL PROTECTED]
> IBM Microelectronics        ||  Phone: (802) 769-8823
> 
> 
> 
> 

   We found quite a few bugs in Patch 7 - file open operations from within
   certain applications broke, how AFS treated ".." was broken (it could
   cause xcopy to go into a recursive loop), etc.

   We found & reported all of these 1 day after Patch 7 came out and Transarc
   sent us a few test Patch 8 builds a few days later that included fixes for
   these problems.

   After we reported some new problems/issues with that build of Patch 8,
   and tesing a few more of the test/debugging builds of Patch 8
   Transarc said they'd be releasing Patch 8 soon - like
   next week.

   I'd either back out Patch 7 and wait for Patch 8 to come out.  As I 
   understand it, we weren't the only site to report problems and there were
   a few other sites that actually helped test Patch 8 as well, so this
   one should be good.

    --Craig

Craig Huckabee                          E-Mail : [EMAIL PROTECTED]
Computer Systems Lab, Computer Sciences Department                      
University of Wisconsin-Madison
http://www.cs.wisc.edu/~huck/

Reply via email to