PCM and PGC Fail to Execute Package from Servers with Long Name

 Last reviewed: April 23, 1997
Article ID: Q128456

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

SYMPTOMS

There are two symptoms:

  • When you use a Windows 3.1 client to execute a package which requires utilities from the MSTEST directory and the logon server has a server name greater than 11 characters, the client receives the following error: 

          Unable to connect. <errcode> - \\server\share. 2 -
      <followed by the actual universal naming convention (UNC) path used.>

    If you execute a package that does not require UNC access to the server, the symptom does not occur.

  • When you run the Program Group Control (PGC) that normally produces the shared application group, the following error appears: 

          No server could be found for application

These symptoms usually on computers running Windows 3.1 in a NetWare environment where logon servers can have names up to 47 characters in length.

These symptoms do not occur on clients running Windows for Workgroups 3.11.

CAUSE

Windows 3.1 KRNL386.EXE does not allow UNC paths with large server names.

STATUS

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

Additional query words: prodsms sms
Keywords : kbbug1.10 kbfix1.20 kbnetwork smspcm smspgc
Version : 1.1
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 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.