PRB: 'Unable to Connect' Message with SEM Object Transfer

Last reviewed: April 9, 1997
Article ID: Q159232
The information in this article applies to:
  • Microsoft SQL Server version 6.5

SYMPTOMS

The Object Transfer methods exposed by the GUI interface in SQL Enterprise Manager (SEM) may report either of the following errors:

  • Unable to connect.

    -or-

  • The name 'My-Server' is not a valid object identifier, or not a valid format for this property or method.

The Transfer facility will generate all the necessary scripts from the source server, and it may report either of these errors when it attempts to connect to the destination server.

CAUSE

SEM uses the SQL-Distributed Management Objects (DMO) to perform the Transfer operations. The Transfer object contains the DestServer property. When an attempt is made to set the value of DestServer, it is validated. DestServer must be a valid SQL Server Identifier, or SEM will return the error. See SQL Server Books Online for specific details on what makes a valid SQL Server Identifier.

WORKAROUND

To work around this problem, use a valid SQL Server identifier for the name of your destination server. This can be facilitated by placing an Advanced Entry in the SQL Client Configuration Utility.


Additional query words:
Keywords : kbusage SSrvDMO SSrvEntMan
Version : 6.5
Platform : WINDOWS
Issue type : kbprb


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