I am recently unable to push the SMS 2003 advanced client to new Windows XP SP3 clients. The server ccm.log has the following entries:
 
---> Connected to administrative share on machine computer_name using account 'installation_account' SMS_CLIENT_CONFIG_MANAGER 3/22/2012 12:15:14 PM 14484 (0x3894)
---> Attempting to make IPC connection to share <\\computer_name\IPC$> SMS_CLIENT_CONFIG_MANAGER 3/22/2012 12:15:14 PM 14484 (0x3894)
---> Unable to obtain Access Token/Lock for machine name "computer_name", error 5. SMS_CLIENT_CONFIG_MANAGER 3/22/2012 12:15:14 PM 14484 (0x3894)
---> ERROR: Unable to access target machine for request: "computer_name", machine name: "computer_name", error code: 5 SMS_CLIENT_CONFIG_MANAGER 3/22/2012 12:15:14 PM 14484 (0x3894)

I have substituted computer_name for the actual computer_name and installation_account for the actual installation account name.
Server operating system is Windows 2003 SP2
Database is SQL Server 2000 Runtime (8.00.194)
The installation account is a member of the local administrators group on the client.
There are no network connectivity problems.
The client name resolves correctly.
Windows Firewall is disabled on the client.
The Remote Registry service on the client is started.
The Server service on the client is started.
File and Printer Sharing for Microsoft Networks is installed on the client.
 
The client has Sophos Antivirus installed and I have disabled the Firewall for testing. I have dozens of other clients similarly configured that are running SMS fine. However, we have made a number of changes in our environment and I'm not able to correlate these changes to the inability to install clients.

Any help resolving this issue is appreciated.

• Edited by DEEDE Thursday, March 22, 2012 11:57 PM

 
---> Unable to obtain Access Token/Lock for machine name "computer_name", error 5. SMS_CLIENT_CONFIG_MANAGER 3/22/2012 12:15:14 PM 14484 (0x3894)

Hi,

This the KB for that error http://support.microsoft.com/kb/886139

Hi Bechir,

Thank you for the link. However, that article applies to "This symptom occurs if you try to install the SMS 2003 Advanced client on a computer that has the SMS 2.0 client or the SMS 2003 Legacy client already installed." I am installing on computers with a fresh OS install. They have never had SMS installed.

I do appreciate your help and any other suggestions are welcome.

Regards, Denise

Im cleaning up old posts, did you figure this out yet? IF so what was the solution?

Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.