PRB: Service Pack Setup May Fail If Probe Login or User Deleted

 Last reviewed: June 5, 1997
Article ID: Q169603
The information in this article applies to:
  • Microsoft SQL Server, version 6.5

SYMPTOMS

The SQL Server service pack Setup program may fail if the 'probe' user has been removed from the master database or if the 'probe' login does not exist. The failure message is: 

   Setup initialization could not be successfully completed.
   ISQL.EXE could not be executed.  Please check the relevant .OUT file.
In the Instrepl.out file, you will find the following output: 

   Adding logins and users for replication.

   Msg 4604, Level 16, State 1, Server XYZ, Line 1
   There is no such user probe.

CAUSE

The Instrepl.sql script attempts to grant permissions to execute a replication stored procedure. If the probe user does not exist, this GRANT fails, causing the service pack Setup to fail as well.

WORKAROUND

To work around this problem, add the probe login and user to the master database, using the following process: 

   use master
   go
   exec sp_addlogin probe, NULL, master
   exec sp_adduser probe
   go
From ISQL/w, open the Procsyst.sql script in the Mssql\Install directory and run this stored procedure. This will grant other permissions to the probe that are necessary for using Performance Monitor.

Keywords : kbenv kbsetup SSrvAdmin SSrvInst SSrvISQL
Version : 6.5
Platform : winnt
Issue type : kbprb
Resolution Type : kbworkaround

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: June 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.