PCM and PGC Cannot Connect to Servers With Long Names

 Last reviewed: April 22, 1997
Article ID: Q126643

The information in this article applies to:
  • Microsoft Systems Management Server version 1.0

SYMPTOMS

When Package Command Manager (PCM) or Program Group Control (PGC) attempt to connect to some logon servers, they error messages indicating that they were unable to complete their configurations appear. Other servers work properly. PCM indicates that it was unable to find a server. PGC indicates that it could not complete updating the client; the SMSLOG.TXT shows that Error 20 occurred. Any connections to servers than contain 12 characters or less work correctly. When you run the /DEBUG switch or watch a network trace of the transaction, you see that the programs appear to be connecting to the server properly.

CAUSE

The applications are attempting to connect to a logon server with more than 12 characters in it's server name.

WORKAROUND

To work around this problem, use 12 or fewer characters for the server name.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 1.0. This problem was corrected in Systems Management Server version 1.1.

Additional query words: sms prodsms
Keywords : kbbug1.00 kbfix1.10 kbother nt16ap nt32ap smspcm smspgc
Version : 1.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 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.