|
When an
XP client joins our domain running SMS (2.0 SP4), the client gets installed,
packages start getting installed, etc. Everything installs correctly but after a
few days (I have never been able to figure out exactly how long), if you go to
the SMS status screen on an XP client, all items except "SMS
Client Base Components" and
"Windows Management"
show up as "Repair
pending".
I know I should look in the logs but as y'all know, there are what seems like
nine million to look in. A couple of weird things I saw:
ccim32.log
Component "Hardware
Inventory Agent" needs to be verified $$<CCIM32><Sun Feb 23 13:29:06.312
2003><thread=1708 (0x6AC)>
Client core file version (from cliver.exe) is 2.00.1493.4105 $$<CCIM32><Sun Feb
23 13:29:06.328 2003><thread=1708 (0x6AC)>
Trying to open IPC connection with APM... $$<CCIM32><Sun Feb 23 13:29:06.359
2003><thread=1708 (0x6AC)>
ERROR: Unable to establish a connection with APM - The system cannot find the
file specified.~~ $$<CCIM32><Sun Feb 23 13:31:08.359 2003><thread=1708 (0x6AC)>
Warning - Could not process optional component command; retry on next cycle...
$$<CCIM32><Sun Feb 23 13:31:08.359 2003><thread=1708 (0x6AC)>
CLISVC.LOG
Using token account
handle 1b4~
$$<C:\WINDOWS\MS\SMS\CORE\BIN\CLISVCL.EXE><Sun Feb 23 13:29:06.000
2003><thread=1584 (0x630)>
***ERROR: Unable to launch "C:\WINDOWS\MS\SMS\clicomp\apa\Bin\smsapm32.exe
" - Error : 1314 $$<C:\WINDOWS\MS\SMS\CORE\BIN\CLISVCL.EXE><Sun Feb 23
13:29:06.109 2003><thread=1584 (0x630)>
*** SMS Available Programs Manager - Error launching (#0x3EB)
$$<C:\WINDOWS\MS\SMS\CORE\BIN\CLISVCL.EXE><Sun Feb 23 13:29:06.125
2003><thread=1584 (0x630)>
!!!WARNING: Problem starting App (1003). Doing App Verify.
$$<C:\WINDOWS\MS\SMS\CORE\BIN\CLISVCL.EXE><Sun Feb 23 13:29:06.125
2003><thread=1584 (0x630)>
SMSMon32.Log
IPC UI : Now attempting
to create an IPC connection.~ $$<MON><Sun Feb 23 11:03:54.957 2003><thread=2308
(0x904)>
IPC UI : Failed to create an IPC connection.~ $$<MON><Sun Feb 23 11:03:54.957
2003><thread=2308 (0x904)>
IPC UI : Waiting 5000 msec before attempting to connect again.~
$$<MON><Sun Feb 23 11:03:54.957 2003><thread=2308 (0x904)>
Can anyone shed some light on this?
From the microsoft.public.sms.setup newsgroup
The only time Microsoft have seen this is when there is an XP setup policy
or configuration that is changing permissions. Check that out and take a
look at the SMS Security Essentials white paper as it outlines the
permissions you need and should help you find the problem:
http://www.microsoft.com/smserver/techinfo/deployment/20/deploysms/secessentials.asp
|
