Select the product you need help with

FIX: You may receive a "'VsRptDesigner Package' has failed to load properly" error when you open Visual Studio .NET 2003 with a mandatory roaming profile

Article ID: 830968 - View products that this article applies to.

SYMPTOMS

When you start Microsoft Visual Studio .NET 2003 to create Crystal Reports, you may receive an error message if the following conditions are true:

You do not have administrative permissions on the computer.
You use the mandatory roaming profile.

The error message is similar to the following:

Package 'VsRptDesigner Package' has failed to load properly ( GUID = {A9D2......} ). Please contact package vendor for assistance. Would you like to disable loading this package in the future? You may use 'devenv /resetskippkgs' to re-enable package loading. Application restart is recommended, due to possible environment corruption.

Back to the top | Give Feedback

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio .NET service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   22-Oct-2003  09:31  7.10.3295.0        45,056  Cmddef.dll       
   22-Oct-2003  09:31  7.10.3295.0        86,016  Dbgurt.exe       
   22-Oct-2003  09:31  7.10.3295.0        49,152  Dbgurtmnu.dll    
   22-Oct-2003  12:24  7.10.3295.0       217,088  Devenv.exe       
   22-Oct-2003  09:31  7.10.3295.0       118,784  Dexplore.exe     
   22-Oct-2003  09:31  7.10.3295.0        81,920  Msdnmnu.dll      
   22-Oct-2003  12:44  7.10.3295.0        45,056  Msenvmnu.dll     
   22-Oct-2003  12:24  7.10.3295.0       258,048  Vbaenv.exe       
   22-Oct-2003  12:48  7.10.3295.0        45,056  Vbamnu.dll

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

Back to the top | Give Feedback

MORE INFORMATION

Steps to reproduce the behavior

Open Visual Studio .NET 2003 by using a roaming profile:
1. Create a roaming profile on a domain server that stores the Ntuser.dat file in the user's root directory on the server.
2. On a computer that has Visual Studio .NET 2003 installed, log on to the domain that you created in step a as a roaming user.
3. Verify that Visual Studio .NET 2003 starts without any errors.
Open Visual Studio .NET 2003 by using a mandatory roaming profile:
1. Log off the computer, and then change the file name of the Ntuser.dat file for this user to Ntuser.man to make it a mandatory roaming profile.
2. Restart the computer, and then log on to the domain as the same user.
3. Open Visual Studio .NET 2003. Note that you receive the error message that is mentioned in the "Symptoms" section, and you cannot use Crystal Reports.

Back to the top | Give Feedback