Client Agent problem (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message


jrweiss -> Client Agent problem (5/8/2007 9:39:18 AM)

Hi,

I installed SCCM 2007 beta 2 successfully, all componenmts are green, it detects my environment via AD (workstations, etc.) and I am also able to install the client agent. But there is no info send back from the client to the server; the server does not see the client as installed in the collections.
The LocationServices.log file contains at the end what is listed after the end of this post. I added SMS_SLP and MP_LHO to WINS manually since I did not want to upgrade my AD schema. When I check IIS it does not contain a virtual directory named sms_slp.
Any idea or hint? Many thanks.

J.R.


---LocationService.log file --------------------------------------------------------------------
<![LOG[Assigning to site 'LHO']LOG]!><time="14:32:00.953+-60" date="05-08-2007" component="LocationServices" context="" type="1" thread="3668" file="lsad.cpp:3347">
<![LOG[LSVerifySiteVersion : Verifying Site Version for <LHO>]LOG]!><time="14:32:00.953+-60" date="05-08-2007" component="LocationServices" context="" type="1" thread="3668" file="lsad.cpp:5085">
<![LOG[LSGetSiteVersionFromAD : Failed to retrieve version for the site 'LHO' (0x80004005)]LOG]!><time="14:32:01.000+-60" date="05-08-2007" component="LocationServices" context="" type="3" thread="3668" file="lsad.cpp:4897">
<![LOG[LSGetSLPFromRegistry: Failed to get SLP from Registry (80004005)]LOG]!><time="14:32:01.000+-60" date="05-08-2007" component="LocationServices" context="" type="3" thread="3668" file="lsad.cpp:2482">
<![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="14:32:01.000+-60" date="05-08-2007" component="LocationServices" context="" type="1" thread="3668" file="lsad.cpp:2264">
<![LOG[[CCMHTTP] HTTP ERROR: URL=http://172.0.1.111/sms_slp/slp.dll?site&sc=LHO, Port=80, Protocol=http, SSLOptions=0, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE]LOG]!><time="14:32:01.046+-60" date="05-08-2007" component="LocationServices" context="" type="1" thread="3668" file="ccmhttperror.cpp:263">
<![LOG[Raising event:
instance of CCM_CcmHttp_Status
{
DateTime = "20070508133201.062000+000";
HostName = "172.0.1.111";
HRESULT = "0x8004027e";
ProcessID = 904;
StatusCode = 404;
ThreadID = 3668;
};
]LOG]!><time="14:32:01.062+-60" date="05-08-2007" component="LocationServices" context="" type="1" thread="3668" file="event.cpp:522">
<![LOG[LSGetSiteVersionFromSLP : No site version  returned from SLP for site <LHO>]LOG]!><time="14:32:01.062+-60" date="05-08-2007" component="LocationServices" context="" type="3" thread="3668" file="lsad.cpp:5052">
<![LOG[LSVerifySiteVersion: Failed to get Site Version from AD and SLP]LOG]!><time="14:32:01.062+-60" date="05-08-2007" component="LocationServices" context="" type="3" thread="3668" file="lsad.cpp:5147">
<![LOG[A Fallback Status Point has not been specified.  Message with STATEID='608' will not be sent.]LOG]!><time="14:32:01.062+-60" date="05-08-2007" component="LocationServices" context="" type="1" thread="3668" file="fspclientdeployassign.cpp:47">




ssimpson -> RE: Client Agent problem (5/8/2007 4:07:48 PM)

when you added the sms_slp, do you recall the command line? I tried it as per the notes in the "how to manually add configuration manager site info" but it rejects it saying it is incomplete information.
Thanks,
Sarah




jrweiss -> RE: Client Agent problem (5/9/2007 1:34:15 AM)

Hi Sarah,
yes, I followed the same MS article. It's:

netsh wins server
add name name=SMS_SLP endchar=1A rectype=0 ip={SmsServerIP}
add name name=MP_YourSiteCode endchar=1A rectype=0 ip={SmsServerIP}

Important are the curly brackets, otherwise it rejects the commands. "YourSiteCode" is the three chracater SMS site code.

Good Luck. It did not help me.
Regards, JR




carterd -> RE: Client Agent problem (10/2/2008 7:12:44 PM)

I know this is over a year old, but I was having the same problem with SCCM 2007 SP1.  Just thought I add that here, in case someone runs across this thread while searching for the answer.  It took me days to finally piece the information from different posts together to finally realize that I needed to install a SLP.

I finally installed the SLP (System Locator Point) component on my primary server and that solved the issue. 




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.21875