SMS Client Errors

Goto the SMS Home Page
This page details problems and issues relating to the SMS Client.

#$#$#$#$#$ ERROR: The Client Service is not authorised to run this application! (5)

Contributed By: Cliff Hobbs [MVP SMS] and Chenna Reddy
 If you’re seeing the above error in your CLISVC.LOG file then you might want to check out this article…  [Go to article]
 

Boot32wn Process Locks up on Windows 9x Clients

I am having the Boot32wn process locking up (process not responding and machine locked until end task) on Windows 9x machines.

This problem is caused by a corrupt 'Copylog.tcf' file as detailed Microsoft Knowledge Base Article 264976 'Client Computer Is Slow to Respond After Running the Boot32wn.exe Tool'.
 

"Cannot find the file SMSRUN32 (or one of its components.)"

If after upgrading some of your clients your users starts getting the above error it could be down to a Profile problem as explained in this article... [Go to article]
 

'CCMBtLDR.exe - Entry Point Not Found' Window appearing on Client

Re-applying the relevant SMS Service Pack could be the fix if you're seeing these errors... [Go to article]
 

Clients Unable to Access a CAP After SMS Server Rebuilt

So you've rebuilt your SMS Site Server identically to the way it was before but now your Clients are saying they can't locate the CAP.  What do you do?  Well start by looking at your Client Connection Accounts... [Go to article]
 

'Could not access Client Access Points - Exitting' Error in CCIM32.LOG

Check the permissions on your 'CAP_Sitecode' share if you're seeing this error... [Go to article]
 

'Couldn't find file in the FILE SOURCE section of logon_point\config\CopyLog.tcf~'

If you're seeing the above error message in 'WNMANUAL.LOG' while trying to install clients then it's time to give SMS a helping hand... [Go to article]
 

'Error - cannot find c:\winnt\ms\sms\core\bin\launch32.exe' On Logon

A rogue Registry key can give the above error when some users login... [Go to article]
 

'ERROR: Unable to establish a connection with APM' Error in CCIM32.LOG

I'm seeing the following error in 'ccim32.log':

'ERROR: Unable to establish a connection with APM - the filename, directory name, or volume label syntax is incorrect'

This problem can be caused when a site is upgraded to SP2 and the CAPs have upgraded but the Logon Points haven't. As a result new clients logging on won't install until the Logon Points have been updated. The client will try to install itself every hour and if it can't you will see the line as detailed above. Once the Logon Point(s) have upgrade the client should install correctly.

Additionally this problem can be caused if there are virus-fixed files residing on the CAP as detailed Optional Components not Installing on Windows 2000 Clients
 

Extra Large TMP Files in "TEMP" Directory or "MS\SMS\CORE\BIN"

Contributed By: Cliff Hobbs [MVP SMS]
 Seeing extra large TMP files in your "TEMP" or "MS\SMS\Core\Bin" directories? Well here's the answer.  [Go to article]
 

'Failed to connect to <machine_name>\admin$ using account <domain>\SMSService (1909)'

Has anyone ever seen the following error message in the 'CCM.LOG' file? I get NT Workstations discovered, but not installed properly and found this error today.

Failed to connect to \\SMSTEST2\admin$ using account IFTCMSTR\SMSService (1909)
ERROR: Unable to connect to remote registry for machine name "SMSTEST2", error 53.
ERROR: Unable to access target machine for request: "SMSTEST2.IFTCMSTR", machine name: "SMSTEST2", error code: 53"

Error 1909 means your SMS Service account is locked out.

Error 53 is an access denied message which means SMS couldn't access the admin$ share on the machine. If there is no admin$ share on an NT box, then SMS will never be able to install on it. It uses that share to get connectivity and install the client software. If the admin$ share is missing use one of the following methods to create it:

  1. Through Server Manager
  2. net share admin$
  3. Start the Server service
  4. Run 'fixacls.exe' from the Resource Kit.

Messages about Virtual Mouse, Keyboard and Mirror drivers not being digitally signed displayed on Clients

Contributed By: Wally Mead [MS]
If when you're installing new clients you're seeing messages about the Virtual Mouse, Keyboard and Mirror drivers not being digitally signed this could be why... [Go to article]
 

"NAL GetAccessible path operation failed - 2147942405" in WNMANUAL.LOG

Anyone seen the following error in "WNMANUAL.LOG"?

 "ASSIGNMENT *************************************** $$<CliEx32.dll><Thu Oct 12 9:19:51.448 2000 GMT Standard Time><thread=486 (0x1E6)>
Server NAL path for assignment is MSWNET:\\SWDADC001\SMSLOGON\
$$<CliEx32.dll><Thu Oct 12 9:19:51.448 2000 GMT Standard Time><thread=486 (0x1E6)>
Converting NAL path MSWNET:\\SWDADC001\SMSLOGON\ to raw path using
GetAccessiblePath $$<CliEx32.dll><Thu Oct 12 9:19:51.448 2000 GMT Standard Time><thread=486 (0x1E6)>
NAL GetAccessible path operation failed - 2147942405 $$<CliEx32.dll><Thu Oct 12 9:19:51.495 2000 GMT Standard Time><thread=486 (0x1E6)>
Attempting to use logon server path \\gents01\SMSLOGON\ for assignment
$$<CliEx32.dll><Wed Oct 11 16:53:55.650 2000 GMT Standard Time><thread=502 (0x1F6)>
CCliEx::DoSMSLogonAssignment returning 2147942405 $$<CliEx32.dll><Wed Oct 11 16:53:55.665 2000 GMT Standard Time><thread=502 (0x1F6)>
Finished CliEx processing. $$<H:\x86.bin\00000409\SMSMan.exe><Wed Oct 11 16:53:55.665 2000 GMT Standard Time><thread=502 (0x1F6)>
CBootMan::CleanUp $$<H:\x86.bin\00000409\SMSMan.exe><Wed Oct 11 16:53:55.665 2000 GMT Standard Time><thread=502 (0x1F6)>"

Contributed By: Cliff Hobbs [MVP SMS]
 This is another one of those generic errors which can have a multitude of meanings.

Almost every time I've seen the 'Get accessible path' message it's pointed to a problem with the client accessing a CAP. Check your 'SMSClient_Sitecode' account to make sure it's not locked out. It's also possible the password is incorrect on the local client.

Here's a suggestion for figuring some of these problems out:

  1. Convert the large number to hex (Windows Calculator can do this for you). In this case, '2147942405' converts to '80070005'.
     

  2. If the beginning 4 octets are '8007' the next four are a network error. Convert the next four back to decimal. In this case, that would be '5'.
     

  3. At a command prompt, type 'NET HELPMSG 5' where '5' is the number you got from step 2. Figure out how that error could happen.
     

  4. If the error doesn't start with '8007', look it up in the Microsoft KnowledgeBase.

In this case, error '5' is 'Access denied'. Check that the client has access to the 'SMSLOGON' share on the server. I believe that's the account it is using to try to access that share when running 'SMSMAN'.

With regards to error '5' This particular problem seems to always be permission related, be it Registry permissions, CAP permissions, etc.

I've recently discovered that this error can be reported when SMS doesn't have access to the 'HKLM\Software\Microsoft\NAL' and 'SMS' keys. Try deleting the 'NAL' and 'SMS' keys and then re-installing the client.

As far as CAPs go, this problem can occur if the permissions on the CAPs weren't changed when SP2 was deployed as everything seems to drop in without any problems once the correct permissions are applied. It looks as though any clients going through their verification cycle or new clients installing as SP2 are having problems accessing the CAPs which still have SP1 permissions.

The message is, if you haven't re-permissioned your CAPs since upgrading to SP2, do it sooner rather than later (the permissions for SP2 are shown below in case anyone needs them).
 

 

Permissions (Windows NT)

Share or directory name

Administrators

Guests

Users

Everyone

CAP_<sitecode> (share)

N/A

N/A

N/A

Full

CAP_<sitecode>

Full

RX

RX

N/A

CCR.box

Full

RWX

RWX

N/A

Clicomp.box

Full

RX

RX

N/A

Clidata.box

Full

RX

RX

N/A

Clifiles.box

Full

RX

RX

N/A

DDR.box

Full

RWX

RWX

N/A

Inventory.box

Full

RWX

RWX

N/A

Offerinf.box

Full

RX

RX

N/A

Pkginfo.box

Full

RX

RX

N/A

Sinv.box

Full

RWX

RWX

N/A

Statmsgs.box

Full

RWX

RWX

N/A

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


 

'SETSMSSRV.EXE - Unable to locate DLL'

A dialog box with the above error message is displayed on a client belonging to a Site Server where 'SETSMSSRV' has been used to control which CAP a client uses. On login the following message is displayed:

'The dynamic link library CLILOG.DLL could not be found in the specified path C:\WINNT\MS\SMS\CORE\BIN;C:\WINNT\SYSTEM32;C:\WINNT\SYSTEM....'

This problem is caused by the 'HKEY_LOCAL_MACHINE\Software\Microsoft\NAL' Registry key not being present. Add this key and grant the 'Users' and 'Power Users' groups Full Control access to this key to cure this problem.
 

"Site XXX is at a lower version (2.00.1493.4170) - it will be skipped for assignment"

Contributed By: Jeff LeBlanc [MSFT]
 If you’ve got problems with your clients complaining that they can’t upgrade to a later version of SMS after you’ve applied a Service Pack and compver.ini seems to be the culprit here’s some advice... [Go to article]
 

SMS Client performs a CHKDSK every time it boots

We have a problem on one of our sites with NT4 clients only. Every time a PC boots a chkdsk is performed.

This problem is documented in 235771 'BUG: Rchelp.Sys Can Cause CHKDSK to Run Continuously' which details changing the startup value of the "RCHELP" service from "1" (System), to "2" (Automatic).
 

'smsboot1.exe is not a valid Windows NT application' Error on NT clients

I came in this morning and a bunch of our NT workstation users were getting 'smsboot1.exe is not a valid windows NT application'. After doing some checking, on a lot of our logon points the 'smsboot1.exe' had a size of 0kb. So I found a logon point with a good copy threw it on the PDC and then told the Senior Site to update. Now we are working again. Has anyone else seen this before, or know what might have caused it?

I've not seen that specifically, but it does sound like one of the following possibilities:

  1. During an update, the Logon Point lost the network connection, corrupting the file. The 0kb file is a good indicator.
     
  2. Your PDC rebooted during the night due to an exception error during an update. Check your Event logs to see if the server was restarted.
     
  3. One of the workstations crashed during a logon session.
     
  4. Virus.

'Unable to open the service control manager to install the SMS Client Service and CCIM'

If you're seeing the above error then don't worry as help is at hand... [Go to article]
 

'Warning - could not find a site CAP with uplevel version of component' error in CCIM32.LOG

Don't worry if you're seeing the above error message in your CCIM32.LOG as this article offers some help and advice... [Go to article]
 

'Warning: Unable to check assignment for site '<site_code>' - #2147942453' in CCIM32.LOG

This is another error you might see in your CCIM32.LOG, but here's some help to fix it... [Go to article]
 

What is Error 8?

Contributed By: Cliff Hobbs [MVP SMS]
 Seeing an "error=8" message and wondering what it means?..  [Go to article]
 

WinMgmt Critical Error

The reason you could be seeing these errors is a problem with WMI so here's how to re-install WMI... [Go to article]
 

WinMgmt has performed an illegal operation

If your Windows 9.x clients are experiencing this problem then the version of DCOM and WMI they're using could be the problem... [Go to article]
 

Wuser32 GPFs and nVIDIA

If you're getting GPFs in Wuser32 caused by nVIDIA then here's how to stop pulling your hair out... [Go to article]
 

Wuser32 GPFs in COEXIST.DLL on bootup on Compaq EN 733s running Windows 95

Seeing WUser32 GPF's in 'COEXIST.DLL' at bootup? Well this could be why... [Go to article]
 
© FAQShop.com 2003 - 2008

Goto the SMS Home Page

 Email the Author