BUG: Problem Connecting to an Unnamed Server with Sqlmaint.exe

ID: Q160237

The information in this article applies to:

Microsoft SQL Server version 6.5

BUG #: 1278 (Windows: 6.50)

SYMPTOMS

When you create a SQL Maintenance Wizard task (which uses the Sqlmaint.exe utility) to connect to an unnamed server, the Sqlmaint.exe utility will end with an unhandled access violation (AV). The executable file will either stop or open the default debugger.

This problem generally occurs on computers that are not valid SQL Server identifiers. For example, "MY-SERVER" is invalid because the dash (-) is not a valid SQL Server identifier symbol. Thus, no entry is placed in the sysservers table.

WORKAROUND

Use sp_addserver to add an entry for the local server. For example, instead of "MY-SERVER," you can use "MY_SERVER." Once you have added the local server entry, you will need to stop and restart SQL Server for the change to take effect.

You can verify the change with the following command:

select @@SERVERNAME

If the command returns (NULL), the server still has an invalid name.

STATUS

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

Keywords : kbenv kbnetwork kbtool SSrvGen kbbug6.50
Version : 6.5
Platform : WINDOWS
Issue type :