PRB: Upgrading Beta to Final v6.0 Could Cause AV in SEM

Last reviewed: April 30, 1997
Article ID: Q134697

The information in this article applies to:

Microsoft SQL Server, version 6.0

SYMPTOMS

An access violation occurs when you exit from SQL Enterprise Manager (SEM). This problem occurs after you upgrade from a beta version to the released product of Microsoft SQL Server version 6.0. It does not occur if you upgrade from version 4.21a, or if it is a new installation of version 6.0.

CAUSE

The SQL Server version 6.0 Setup program installs the two files SQLOLE32.DLL and SQLOLE32.TLB in the <SQL PATH>\DLL directory, but it does not remove the SQL Server version 6.0 beta files from <SQL PATH>\BINN. Because the <SQL PATH>\BINN directory is first in the system path, SQL Enterprise Manager uses the beta files found here, which cause the problem.

WORKAROUND

Delete the files SQLOLE32.DLL and SQLOLE32.TLB from the SQL60\BINN directory.

Additional query words: sql6 AV SEM stack trace dump reinstall
Keywords : kbenv kbsetup SSrvEntMan SSrvInst
Version : 4.21 6.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.