BUG: SQL Admin Reports SQL Monitor Not Started

 Last reviewed: April 29, 1997
Article ID: Q118386

The information in this article applies to: 

  - Microsoft SQL Server Programmer's Toolkit, version 4.2
BUG# 10074 (4.21)

SYMPTOMS

You may see the message: 

   The SQL Server Monitor is not started on this server
if you attempt to manipulate scheduled events (for example, Add Event, Drop Event, Start/Stop Backup Engine or Clear Events) within SQL Administrator after logging into SQL Server using the TCP/IP network library DBMSSOCN or DBMSSOC3. When SQL Monitor is checked, however (with either NET START or the SQL Server Service Manager), it is found to be running.

As stated in the Release Notes, new values were added to the registry that enhance SQL Administrator's ability to communicate with SQL Monitor. Some of these new values are listed in the registry under the following Hive\Key listing for the Windows NT version of SQL Administrator, 

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SQLServer\Client\Monitor
and under the following section in the Windows WIN.INI file, 

   [SQLMONITOR].
These areas provide templates that SQL Administrator can use to parse the original connect string in order to build a new connect string that can be used to login to SQL Monitor.

The templates provided for the DBMSSOCN and DBMSSOC3 network libraries do not work when used by SQL Administrator to connect to SQL Server via TCP/IP. The templates for the Name Pipes connection, IPX/SPX connection, and local pipe connection all work as expected.

WORKAROUND

SQL Administrator will successfully make its required connections to SQL Monitor if you place an explicit connection string in the appropriate area in the Windows NT Registry or Windows WIN.INI file.

The following are examples for entering a Windows NT Registry and Windows WIN.INI entry for a Server called TSETSE:

Windows NT

  1. Start the REGEDT32.EXE program.

  2. Open the HKEY_LOCAL_MACHINE window.

  3. Open folders in the following sequence: SOFTWARE, Microsoft, SQLServer, Client, Monitor.

  4. From the Edit menu, select Add Value.

  5. Add "TSETSE" in the Value Name line edit box, then click OK. (In this case, the Data Type can be REG_SZ)

  6. Enter the Connection String in the line edit, which would be the following:

    DBMSSOCN,223.111.495.1,1434

    (NOTE: The port number is one more than the default. If you are not sure what the port number is for SQL Monitor, look under: 

            HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SQLServer\SQLMonitor
        \Parameters\ListenOn)

  7. Click OK.

  8. Exit the REGEDT32.EXE program.

Windows

  1. Start SYSEDIT or use a text editor to open the WIN.INI file.

  2. Under the [SQLMONITOR] group add the following:

    TSETSE=DBMSSOC3,223.111.495.1,1434

  3. Save your changes.

  4. Exit SYSEDIT or your text editor.

STATUS

Microsoft has confirmed this to be a problem in SQL Server Administrator version 4.21. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: sql windows nt regedit
Keywords : kbbug4.21 kbinterop kbtool SSrvAdmin SSrvMon
Version : 4.21
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 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.