PRB: "Invalid Handle" Error with Delta

ID: Q130883

The information in this article applies to:

Microsoft Delta for Windows, version 1.0

NOTE: Some products mentioned in this article are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

SYMPTOMS

Sometimes, when checking in a file with Delta over a Novell network, "Invalid Handle" is returned, and Delta refuses to check in the file. The following error message is returned:

   error writing <server>\<master>\DIFF\<project name>\<filename>
   (invalid handle) retry?

Replying Yes yields the same message, and replying No yields this message:

   incomplete write to <server>\<master>\DIFF\<project name>\<filename>
   (invalid handle) retry?

Other project files appear unaffected by the error. Other files may be checked out and in without error. Commands that write to or read from the DIFF file (Remove File, Retrieve Previous Version, Delete Previous Version) elicit similar errors:

   error writing <server>\<master>\DIFF\<project name>\<filename>
   (file not found) retry?

   incomplete write to <server>\<master>\DIFF\<project name>\<filename>
   (invalid handle) retry?

RESOLUTION

Contact Novell and inquire as to what may cause the incomplete write. The error is generated by the server software and is ported from Delta's backgrounded MS-DOS session to the Delta output window. The error message text is identical when executing the commands from an MS-DOS prompt.

Resolution One

Load the associated difference file into a text editor such as Notepad or Write. Other editors may cause the diff archive to become corrupt. If the diff archive becomes corrupt, it must be restored from backup. Save the file and exit without making any changes to the file. (Do not use a 'smart' editor that requires that the file be modified before saving.) Attempt the Check In command again. This is believed to complete the write to the file, allowing the file to be checked in without error.

Resolution Two (if One fails)

Let MYPRG.C be the file containing the corrupted history.

1. Rename the history file, <server>\<master>\DIFF\<project name>\MYPRG.C,

   to <server>\<master>\DIFF\<project name>\MYPRG2.C. This saves the
   history for later use if necessary. Delta will no longer be able to
   retrieve version from the old diff archive, MYPRG2.C.

2. Check in the problem file. This creates a new history for the file. The

   file version is incremented, but the new history only contains the last
   change. Only the current file version and one previous version may be
   retrieved using Delta. Other previous versions must be rebuilt by hand
   using the old diff file, MYPRG2.C.

There is probably a switch on the server that must be turned on or off to dispose of the error permanently.

Additional query words:

Keywords          : kb3rdparty kbnetwork
Issue type        : kbprb