Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unable to convert path into a NAL path - The parameter is incorrect

Status
Not open for further replies.

Depdiver

MIS
Sep 11, 2003
11
US
I am beginning to deploy clients I am getting the following errors on XP machines. Any idea what it means? I have googled this error message and tried Microsoft's knowledge base and I can not find anything. Please help.

Dep

======= Logging initialized for module &quot;C:\WINDOWS\sms_temp\CCMBtLdr.exe&quot; ======= $$<C:\WINDOWS\sms_temp\CCMBtLdr.exe><Fri Oct 10 10:49:04.221 2003><thread=1604 (0x644)>
ERROR: Unable to convert server path &quot;C:\WINDOWS\sms_temp\caplist.ini&quot;, NAL Type &quot;LOCAL&quot; into a NAL path - The parameter is incorrect.~~ $$<C:\WINDOWS\sms_temp\CCMBtLdr.exe><Fri Oct 10 10:49:04.241 2003><thread=1604 (0x644)>
Error locating CAP (2147942487) $$<C:\WINDOWS\sms_temp\CCMBtLdr.exe><Fri Oct 10 10:49:04.241 2003><thread=1604 (0x644)>
Could not spawn CCMBoot.exe - 2147942487 $$<C:\WINDOWS\sms_temp\CCMBtLdr.exe><Fri Oct 10 10:49:04.241 2003><thread=1604 (0x644)>
** Service Thread is ending ** $$<C:\WINDOWS\sms_temp\CCMBtLdr.exe><Fri Oct 10 10:49:04.241 2003><thread=1604 (0x644)>
 
I have exactly the same set of errors. It appears that I cannot install any new SMS Clients. After searching for weeks on Technet, Internet etc. I still cannot resolve the problem

I have tried the usual things of uninstalling the client. Making sure the Server and Workstation Service are running.

Created extra SMS Client accounts for installation, made sure File and Print was enabled.

All I get is the Systems Management Icon in the control Panel - List the details of the client on the General Tab, the Sites Tab just has the Site listed (no update Time) and there are no components installed.

My SMS Server details are as follows

Windows 2000 SP4
SQL Server 2000
SMS2 SP5

If anyone has any ideas - I would be very appreciaitive

cheers
 
I broke down and called microsoft on this. The tech asked me to send him my ccim32.log file from a machine. He told me to check 2 things. 1. SMSclient_??? account. ignore what the documentation says. This account, or any account you have in your client connection account, must have full control to all folders on the CAP share. 2. This one is a pain, check each winXP machine's registry HKLM\software\Micorosft\SMS and HKLM\software\microsoft\NAL. Delete these keys. You may need to take ownership of some of the sub keys before deleteing. then import in the HKLM\software\microsoft\NAL key from a working machine. then re-install the client. I've done this on about 700 machines so far and I'm actually finally getting my deployment back on schedule.

Hope this helps,
Dep
 
I asked Microsoft about this (that was the reason I originally called). This hot fix is included in SP5 which I am running. But there is a problem that sometimes, and in my case, the permissions are so messed up that the owner of the registry keys doesn't exist, so the hotfix is unable to take ownership and can not fix the keys. Even logging onto the machine as the local administrator will not allow you to delete the keys without first taking ownership. Maybe it will work for the rest of you, but my case it did not. If you are running SP5 you have the hotfix, if you are still having the problem then welcome to my world.

Dep :)
 
Funny as we are running SP5 and never had this trouble before and we were told by Microsoft's PSS that this Hotfix is NOT included in SP5 but will be in SP6......
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top