ADSM-L

Error ANS4007E on restore using 3.1.05 Win95 32-bit client

1998-08-31 22:50:07
Subject: Error ANS4007E on restore using 3.1.05 Win95 32-bit client
From: Pete Tanenhaus <tanenhau AT US.IBM DOT COM>
Date: Mon, 31 Aug 1998 22:50:07 -0400
I believe that there may be a bug restoring from older filespaces which have
not been migrated
to the new UNC naming convention introduced in ptf 5.

Filespace names are automatically converted to the new UNC naming convention
when accessed for
backup for the first time by the level 5 client.

The old filespace name is, however, left intact during restore.

I'm guessing that the problem you are seeing occurs because the restore is
being done before the filespace name
has been migrated to the new naming convention.

Once the filespace name has been migrated to the new naming convention the
problem should go away.

Can you try backing up a file up to this filespace and then try the restore
again ?

Thanks .....

Pete Tanenhaus, ADSM NT Client Development
---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 08/31/98
1/98
09:48 PM ---------------------------


ADSM-L AT VM.MARIST DOT EDU on 08/31/98 07:46:41 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Error ANS4007E on restore using 3.1.05 Win95 32-bit client


I receive the following error message (names changed to protect the
innocent) when using the new 3.1.05 Win95 32-bit client to restore a
single directory backed up by the 3.1.05 client.  However, the directory
does indeed get created and all the data seems to come back.

08/31/1998 18:13:12 CreateDirectory(): Win32 RC=5 .
08/31/1998 18:13:12 ANS4007E Error processing '\\mynode\c$\mydir':
access to the object is denied

When I use the new 3.1.05 client to restore the same directory from a
backup taken by the previous client (3.1.03), I do not receive any error
messages.

Can anyone explain the meaning of the *apparent* error message?



<Prev in Thread] Current Thread [Next in Thread>