BUG: Signing a CAB File Fails When Project Is on Remote Drive

ID: Q197031

The information in this article applies to:

SYMPTOMS

When you open a Code-behind HTML project on a remote shared network directory and build it, the following error occurs:

   Failed to generate signature for Project1.CAB, because it does not
   exist.

CAUSE

This error occurs only on some system configurations. You get the same results regardless of whether or not you use a UNC path or if the shared network directory is mapped to a network drive.

RESOLUTION

Copy the project to your local drive to resolve the error message. You can also rename the shared network drive to an 8.3 filename to resolve the error.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

NOTE: These steps only reproduce the behavior under some system configurations.

1. Map your Z: drive to a shared network directory that has a long path

   name (for example, \\javadev1\OurProjects).

2. Open a Code-behind HTML project (for example, Z:\My Projects\Project1)
   on a remote shared network directory.

3. Build the project.

REFERENCES

For the latest Knowledge Base articles and other support information on Visual J++ and the SDK for Java, see the following page on the Microsoft Technical Support site:

   http://support.microsoft.com/support/visualj/ 
   http://support.microsoft.com/support/java/ 

(c) Microsoft Corporation 1998, All Rights Reserved. Contributions by Mohan Ananthakrishnan,Microsoft Corporation.

Additional query words:

Keywords          : kbVJ600bug 
Version           : WINDOWS:6.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbpending

Last Reviewed: December 9, 1998