Solved

SMS 2003, Automatic site code discovery was unsuccessful

Posted on 2009-05-19
4
1,702 Views
Last Modified: 2013-11-21
A previos IT person before me here attempted to implement SMS 2003 but never had it working properly. I could not get his existing install working properly either, so i removed SMS, IIS, and SQL from the server and started from scratch.

I chose not to extend the AD Schema, as I do not have permission (not sure if it was already extended in the past). I installed the advanced client on a new test client by running client.msi from the SMS server CIFS share. During the install I put in the site code for the new SMS server. After the install, I checked in the Systems Managment in control panel it it did not show a site on the Advanced tab. I tried the discover button and got the message "Automatic site code discovery was unsuccessful". Before i uninstalled and reinstalled, clients were able to use the discover button.

If I manually enter our site code, it will accept it and I can receive packages. I have one SMS server that is configured for all roles (MP, SLP, DP, CAP, RP, Component Server, Site Server, SQL Server).

In the code snipplet below are the entries from the ClientLocation.log and  LocationServices.log

ClientLocation.log:
 
<![LOG[Setting Assigned Site]LOG]!><time="12:19:25.019+240" date="05-19-2009" component="ClientLocation" context="" type="1" thread="4080" file="smsclientclass.cpp:380">
<![LOG[The site code 'ENA ' is invalid]LOG]!><time="12:19:25.019+240" date="05-19-2009" component="ClientLocation" context="" type="3" thread="4080" file="smsclientclass.cpp:390">
<![LOG[Getting Assigned Site]LOG]!><time="12:19:57.942+240" date="05-19-2009" component="ClientLocation" context="" type="1" thread="3212" file="smsclientclass.cpp:874">
<![LOG[Autodiscover Site]LOG]!><time="12:19:59.836+240" date="05-19-2009" component="ClientLocation" context="" type="1" thread="3212" file="smsclientclass.cpp:1139">
<![LOG[Getting Assigned Site]LOG]!><time="13:09:37.526+240" date="05-19-2009" component="ClientLocation" context="" type="1" thread="2004" file="smsclientclass.cpp:874">
<![LOG[Autodiscover Site]LOG]!><time="13:09:41.635+240" date="05-19-2009" component="ClientLocation" context="" type="1" thread="2004" file="smsclientclass.cpp:1139">
 
 
 
LocationServices.log:
<![LOG[Assigning to site 'ENA ']LOG]!><time="12:19:24.957+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsad.cpp:2333">
<![LOG[Sitecode 'ENA ' is invalid, client will not be assigned.]LOG]!><time="12:19:25.019+240" date="05-19-2009" component="LocationServices" context="" type="2" thread="4080" file="lsad.cpp:2350">
<![LOG[Attempting to retrieve proxy MP from AD]LOG]!><time="12:19:25.050+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsproxymp.cpp:860">
<![LOG[Current AD site of machine is US-Novi]LOG]!><time="12:19:25.388+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsad.cpp:195">
<![LOG[Current AD site of machine is US-Novi]LOG]!><time="12:19:25.696+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsad.cpp:195">
<![LOG[Attempting to retrieve local MP from AD]LOG]!><time="12:19:25.804+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsad.cpp:2542">
<![LOG[Current AD site of machine is US-Novi]LOG]!><time="12:19:25.850+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsad.cpp:195">
<![LOG[Executing Task LSRefreshDefaultMPTask]LOG]!><time="12:19:27.112+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="scheduledcleanupendpoint.cpp:125">
<![LOG[Attempting to retrieve proxy MP from AD]LOG]!><time="12:19:27.235+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsproxymp.cpp:860">
<![LOG[Current AD site of machine is US-Novi]LOG]!><time="12:19:27.328+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsad.cpp:195">
<![LOG[Current AD site of machine is US-Novi]LOG]!><time="12:19:27.420+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsad.cpp:195">
<![LOG[Attempting to retrieve local MP from AD]LOG]!><time="12:19:27.589+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsad.cpp:2542">
<![LOG[Current AD site of machine is US-Novi]LOG]!><time="12:19:27.682+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="4080" file="lsad.cpp:195">
<![LOG[Current AD site of machine is US-Novi]LOG]!><time="12:19:59.897+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="3212" file="lsad.cpp:195">
<![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="12:20:00.082+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="3212" file="lsad.cpp:1901">
<![LOG[Failed to resolve IP address from WINS]LOG]!><time="12:20:09.009+240" date="05-19-2009" component="LocationServices" context="" type="3" thread="3212" file="lswins.cpp:323">
<![LOG[LSGetSLP : Failed to resolve SLP from WINS, is it published]LOG]!><time="12:20:09.009+240" date="05-19-2009" component="LocationServices" context="" type="3" thread="3212" file="lsad.cpp:1915">
<![LOG[LSGetAssignedSiteFromSLP : Unable to get the list of SLPs]LOG]!><time="12:20:09.009+240" date="05-19-2009" component="LocationServices" context="" type="3" thread="3212" file="lsad.cpp:1734">
<![LOG[Current AD site of machine is US-Novi]LOG]!><time="13:09:41.698+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="2004" file="lsad.cpp:195">
<![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="13:09:42.010+240" date="05-19-2009" component="LocationServices" context="" type="1" thread="2004" file="lsad.cpp:1901">
<![LOG[Failed to resolve IP address from WINS]LOG]!><time="13:09:51.010+240" date="05-19-2009" component="LocationServices" context="" type="3" thread="2004" file="lswins.cpp:323">
<![LOG[LSGetSLP : Failed to resolve SLP from WINS, is it published]LOG]!><time="13:09:51.010+240" date="05-19-2009" component="LocationServices" context="" type="3" thread="2004" file="lsad.cpp:1915">
<![LOG[LSGetAssignedSiteFromSLP : Unable to get the list of SLPs]LOG]!><time="13:09:51.010+240" date="05-19-2009" component="LocationServices" context="" type="3" thread="2004" file="lsad.cpp:1734">

Open in new window

0
Comment
Question by:bradl3y
  • 2
  • 2
4 Comments
 
LVL 15

Expert Comment

by:HayesJupe
ID: 24428802
so if you havent extended AD, you must use WINS,  lmhosts or specify the fqdn during client install.
0
 
LVL 6

Author Comment

by:bradl3y
ID: 24431255
By using ADSI Edit I granted permission for the SMS computer account to access the "CN=System Management" container. This seems to have allowed the clients to discover the site.
0
 
LVL 15

Accepted Solution

by:
HayesJupe earned 500 total points
ID: 24436736
so you have extended the AD, you just previously hadnt granted the correct permissions.... solved your own issue, good to see.
and you dont need to use adsiedit, just use AD users and computers and put it in advanced mode.
0
 
LVL 6

Author Closing Comment

by:bradl3y
ID: 31583132
Thanks, it seems the schema has been extended in the past, i just didn't realize it.
0

Featured Post

Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The environment that this is running in is SCCM 2007 R2 running on a Windows 2008 R2 server. The PXE Distribution point is running on its own Windows 2008 R2 box. This is what Event viewer showed after trying to start the WDS service:  An erro…
Problem Description: Actually I found the below issue with some customers after migration from SMS 2003 to SCCM 2007 and epically if they change site code, some clients may appear in the console with old site code, plus old sites still appearing …

832 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question