Microsoft KB Archive/288883

= SMS: Error Message: No Server Path Specified =

Article ID: 288883

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition
 * Microsoft Systems Management Server 2.0 Service Pack 1
 * Microsoft Systems Management Server 2.0 Service Pack 2

-



This article was previously published under Q288883



SYMPTOMS
When you use the Systems Management Server (SMS) script file (Smsls.bat) to install the SMS-based client components, the workstation may not successfully install the components, and an error message may be logged in the Wn_logon.log file:

=
Logging initialized for module

&quot;C:\Windows\Ms\Sms\Core\Bin\Boot32wn.exe&quot; =======

SmsclientPath (from &quot;C:\Temp&quot;) is &quot;&quot;

SmstempClientPath (from &quot;C:\Temp&quot;) is &quot;&quot;

ERROR: No server path specified.



CAUSE
This behavior can occur when there is an extra space after the Set Temp variable in the Autoexec.bat file. You can verify this extra space if you review the Wn_logon.log file and the following entry has been logged:

Wrote &quot;SmsserverPath=\\Usnycns01\Smslogon&quot; into file &quot;C:\Temp \Smsboot1.ini&quot;, iRet = 1



WORKAROUND
To work around this behavior, remove the extra space after the &quot;Set Temp=C:\Temp&quot; line in the Autoexec.bat file, restart the workstation, and then log on with an account that runs the Smsls.bat logon script.



MORE INFORMATION
If the Smsman.exe program is run from the logon point, you may observe the following entry in the Wnmanual.log file:

ERROR: Load of DLL CliEx32.dll failed (C:\Windows\Ms\Sms\Core\Bin\Cliex32.dll), 1157

ERROR: Initializing CliEx failed error code 1157

NOTE: The 1157 error may also be caused by a corrupted Clicore.exe program on the logon point.

Additional query words: prodsms

Keywords: kbclient kbconfig kbinterop kbprb kbsetup kbupgrade KB288883

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.