This article describes a problem that occurs after you install Microsoft Visual Studio 6 Service Pack 6 (SP6) or Microsoft Visual Studio .NET 2003. Database diagrams appear to be blank when you open them. This problem occurs because incorrect .dll files are installed in Visual Studio 6 SP6 and in Visual Studio .NET 2003. You must reinstall the Visual Studio 6 SP5 version of those files to resolve the problem.
When you open a Microsoft SQL Server database diagram, the diagram appears to be blank and contains no content. However, you receive no error message.
This problem occurs after you install Visual Studio 6
SP6 or Visual Studio .NET 2003.
This problem occurs because some incorrect .dll files are included in Visual Studio 6 SP6 and in Visual
Studio .NET 2003. These files include .dll files that are typically located in the
C:\Program Files\Common Files\Microsoft Shared\MSDesigners98
To resolve this problem, replace all files in the MSDesigners98 folder by using the files in the same folder in Visual Studio 6 SP6. To do this, follow these steps:
- Download Visual Studio 6 SP6.
following file is available for download from the Microsoft Download
Download the Vs6sp5vb.exe package now.
Collapse this imageExpand this image
Release Date: February 21, 2001
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
How to obtain Microsoft support files from online services
- In the File Download dialog box, click
- In the Save As dialog box, click
Desktop in the left pane, and then click
- On the desktop, double-click Vs6sp5vb.exe to
extract the file.
- In the Open File dialog box, click
- Type the location where you want to save
the extracted files, and then click OK. For
example, type C:\Vs6sp5, and then click
OK. If the folder that you specify does not exist, click
Yes to create the folder.
- Expand files to the C:\Program Files\Common
Files\Microsoft Shared\MSDesigners98 folder. To do this, follow these steps:
- Click Start, click
Run, type cmd, and then click OK.
change the directory to the folder where you extracted the .cab files in step
6, type the following command, and then press ENTER:
cd c:\Vs6sp6Note Replace c:\Vs6sp6 with the path that you used in step 6.
expand the files from the .cab file to the appropriate folder, type the following command, and then press ENTER:
expand Vs6sp6b2.cab -F:msdesign*.dll C:\Program Files\Common Files\Microsoft Shared\MSDesigners98
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed in the "Applies to" section.
Any database diagrams that you created in Visual Studio 6 SP6 or in Visual Studio .NET 2003 will still work after you install the Visual Studio 6 SP5 .dll files.
Steps to reproduce the behavior
- Install any version of Microsoft SQL Server 2000.
- In SQL Enterprise Manager, create a new database diagram that is named DD1, and then save the diagram.
- Install the original release version of Visual Studio 6.
- In SQL Enterprise Manager, create a new database diagram that is named DD2, and then save the diagram.
- Install Visual Studio 6 SP5.
- In SQL Enterprise Manager, create a new database diagram that is named DD3, and then save the diagram.
Notice that all three database diagrams can be modified at
- Install Visual Studio 6 SP6 or Visual Studio
- Try to modify the database diagrams that you created in
steps 1 through 6.
Notice that the diagrams appear to be blank.
Article ID: 902245 - Last Review: January 17, 2015 - Revision: 1.4
- Microsoft Visual Studio .NET 2003 Professional Edition
- Microsoft Visual Studio .NET 2003 Enterprise Architect
- Microsoft Visual Studio .NET 2003 Enterprise Developer
- Microsoft Visual Studio 6.0 Service Pack 6
|kbnosurvey kbarchive kbvs2005swept kbvs2005doesnotapply kbfix kbtshoot kbbug KB902245|