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 John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CCM.LOG - Unable to access target machine for request

Status
Not open for further replies.

dgillings

IS-IT--Management
Sep 9, 2003
8
GB
This is an ongoing issue that I have with my site pushing out (or rather NOT pushing out clients) Any extra input would be greatly appreciated...



OK more information. I have been sifting through the log files and I have discovered this in the CCM.LOG:

======>Begin Processing request: "KMWXOJQU", machine name: "RDGSL022" SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
Waiting for change in directory "D:\SMS\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 2112 (0x0840)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> Attempting to connect to administrative share '\\RDGSL022\admin$' using account 'INGUKRDG\SMSServer_ING' SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> The 'best-shot' account has now succeeded 1 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> Connected to administrative share on machine RDGSL022 using account 'INGUKRDG\SMSServer_ING' SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> Attempting to make IPC connection to share <\\RDGSL022\IPC$> SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> Unable to obtain Access Token for machine name &quot;RDGSL022&quot;, error 5. SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
---> ERROR: Unable to access target machine for request: &quot;KMWXOJQU&quot;, machine name: &quot;RDGSL022&quot;, error code: 5 SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
STATMSG: ID=3014 SEV=W LEV=M SOURCE=&quot;SMS Server&quot; COMP=&quot;SMS_CLIENT_CONFIG_MANAGER&quot; SYS=RDGSSMS SITE=ING PID=1724 TID=1928 GMTDATE=Thu Dec 11 17:03:50.328 2003 ISTR0=&quot;RDGSL022&quot; ISTR1=&quot;&quot; ISTR2=&quot;&quot; ISTR3=&quot;&quot; ISTR4=&quot;&quot; ISTR5=&quot;&quot; ISTR6=&quot;&quot; ISTR7=&quot;&quot; ISTR8=&quot;&quot; ISTR9=&quot;&quot; NUMATTRS=0 SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
Retry request id for &quot;KMWXOJQU&quot; set to &quot;RDGSL022&quot; SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
Stored request &quot;RDGSL022&quot;, machine name &quot;RDGSL022&quot;, in queue &quot;Retry&quot;. SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)
<======End request: &quot;RDGSL022&quot;, machine name: &quot;RDGSL022&quot;. SMS_CLIENT_CONFIG_MANAGER 11/12/2003 17:03:50 1928 (0x0788)


Anyone have any idea why I have this message:

ERROR: Unable to access target machine for request: &quot;KMWXOJQU&quot;, machine name: &quot;RDGSL022&quot;, error code: 5

I have checked all permissions, and as far as I can see there is no issue with either the account accessing the computer, or the computer itself...?

IF only I could push advanced clients.. :(

Another issue I have discovered - which may help someone brainy out there to help me - is that even if I go through a manual install of an advanced client on a system, and it succeeds, then I do a discover - once again success, it doesn't report in the SMS console as an object with a client at all?

Starting to lose my hair
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top