Re: sms 2003 installation finish but Site Status is empty

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi

First: remember that you need to modify the local administrator group on the
SQL server, not on the SMS box.

I think the errors you enclosed are pretty normal in smssetup.log. They are
logged when the setup tries to create shortcuts on the start menu, but I
never seen that shortcuts are actually missing or invalid when those errors
are logged.

Since you say that SMS Services are running under LocalSystem your site must
be in advanced security.

The MP troubleshooting guide contains some info about how to check that the
MP has access to the DB, but you should be able to use that for the site
server as well. Take a look at the "To verify that the management point
computer account has adequate credentials" section in this document:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/maintain/managepoint/management_point_2.mspx
and do the check using osql and check the SPN as well (the section below).

/Rune


"Eric Lau" <EricLau@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2ED0CA6F-34A6-4B15-B763-3FE07A2F2234@xxxxxxxxxxxxxxxx
> Yes, I am pretty sure that is the problem of accessing SQL.
> SMS services are running under Local System even I logged in with an
> Domain
> Admin Account. I am running Advanced Security and the Machine Name is in
> the
> Local Administrator Group.
> By looking at the smssetup.log, I got these errors:
> <01-17-2006 12:38:17> Couldn't reload group, DDE error =4009
> <01-17-2006 12:38:18> Couldn't reload group, DDE error =4009
> <01-17-2006 12:38:19> Couldn't reload group, DDE error =4009
> <01-17-2006 12:38:20> Couldn't reload group, DDE error =4009
> <01-17-2006 12:38:21> Couldn't reload group, DDE error =4009
> <01-17-2006 12:38:22> Couldn't reload group, DDE error =4009
> <01-17-2006 12:38:23> Couldn't reload group, DDE error =4009
> <01-17-2006 12:38:24> Couldn't reload group, DDE error =4009
> <01-17-2006 12:38:25> Couldn't reload group, DDE error =4009
> <01-17-2006 12:38:26> Couldn't reload group, DDE error =4009
> Thanks.
>
> Eric
>
>
> "Rune Norberg" wrote:
>
>> The smssetup.log snippet seems fine, but you have an access denied in the
>> sitecomp.log. From what I can see it seems like you have problem
>> accessing
>> your SQL server from the SMS server. Ensure that the SMS service account
>> have admin rights on the SQL server if you are running SMS in standard
>> security, or that the computer account from the SMS server is added to
>> the
>> local admin group on the SQL server if you are running in advanced
>> security.
>>
>> /Rune
>>
>> "Eric Lau" <EricLau@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:76499192-B6F0-4443-9470-11D7E1E6F1AA@xxxxxxxxxxxxxxxx
>> >I installed SMS 2003 on a Windows 2003 sp1 server with SQL 2000 sp3a on
>> >a
>> > different Windows 2003 sp1 box. The setup is finished but I got some
>> > errors
>> > from the setup logs. Here are some of them:
>> >
>> > <01-15-2006 11:32:26> Starting evaluation process.
>> > <01-15-2006 11:32:27> Enough free disk space.
>> > <01-15-2006 11:32:27> Checking domain for advanced security, PDC for
>> > domain
>> > SC is \\DC00
>> > <01-15-2006 11:32:27> Registering connects for SQLSRV00, , master
>> > <01-15-2006 11:32:27> Registered the types
>> > <01-15-2006 11:32:27> Running test query.
>> > <01-15-2006 11:32:27> Sql version is 8.0, 8.00.760.
>> > <01-15-2006 11:32:35> Verified machine account by installing service
>> > SMS_ACCOUNT_TEST_SERVICE
>> > <01-15-2006 11:32:35> Modifying Active Directory Schema - with SMS
>> > extensions.
>> > <01-15-2006 11:32:35> DS
>> > Root:CN=Schema,CN=Configuration,DC=SC,DC=ESILICON,DC=com
>> > <01-15-2006 11:32:35> Attribute cn=MS-SMS-Site-Code already exists.
>> > <01-15-2006 11:32:35> Attribute cn=mS-SMS-Assignment-Site-Code already
>> > exists.
>> > <01-15-2006 11:32:35> Attribute cn=MS-SMS-Site-Boundaries already
>> > exists.
>> > <01-15-2006 11:32:35> Attribute cn=MS-SMS-Roaming-Boundaries already
>> > exists.
>> > <01-15-2006 11:32:35> Attribute cn=MS-SMS-Default-MP already exists.
>> > <01-15-2006 11:32:35> Attribute cn=mS-SMS-Device-Management-Point
>> > already
>> > exists.
>> > <01-15-2006 11:32:35> Attribute cn=MS-SMS-MP-Name already exists.
>> > <01-15-2006 11:32:35> Attribute cn=MS-SMS-MP-Address already exists.
>> > <01-15-2006 11:32:35> Attribute cn=MS-SMS-Ranged-IP-Low already exists.
>> > <01-15-2006 11:32:35> Attribute cn=MS-SMS-Ranged-IP-High already
>> > exists.
>> > <01-15-2006 11:32:35> Class cn=MS-SMS-Management-Point already exists.
>> > <01-15-2006 11:32:35> Class cn=MS-SMS-Server-Locator-Point already
>> > exists.
>> > <01-15-2006 11:32:35> Class cn=MS-SMS-Site already exists.
>> > <01-15-2006 11:32:35> Class cn=MS-SMS-Roaming-Boundary-Range already
>> > exists.
>> > <01-15-2006 11:32:35> Created action thread, thread id = 3784
>> > <01-15-2006 11:32:36> Stopping service SMS_SITE_COMPONENT_MANAGER
>> > <01-15-2006 11:32:36> Service SMS_SITE_COMPONENT_MANAGER is not
>> > installed,
>> > skip it.
>> > <01-15-2006 11:32:36> Stopping service SMS_SQL_MONITOR
>> > <01-15-2006 11:32:36> Service SMS_SQL_MONITOR is not installed, skip
>> > it.
>> > <01-15-2006 11:32:36> Stopping service SMS_EXECUTIVE
>> > <01-15-2006 11:32:36> Service SMS_EXECUTIVE is not installed, skip it.
>> > <01-15-2006 11:32:36> Stopping service SMS_SERVER_BOOTSTRAP_SMS00
>> > <01-15-2006 11:32:36> Service SMS_SERVER_BOOTSTRAP_SMS00 is not
>> > installed,
>> > skip it.
>> > <01-15-2006 11:32:36> Stopping service SMS_HIERARCHY_MANAGER
>> > <01-15-2006 11:32:36> Service SMS_HIERARCHY_MANAGER is not installed,
>> > skip
>> > it.
>> > <01-15-2006 11:32:36> Stopping service SMS_INVENTORY_AGENT_NT
>> > <01-15-2006 11:32:36> Service SMS_INVENTORY_AGENT_NT is not installed,
>> > skip
>> > it.
>> > <01-15-2006 11:32:36> Stopping service SMS_CLIENT_CONFIG_MANAGER
>> > <01-15-2006 11:32:36> Service SMS_CLIENT_CONFIG_MANAGER is not
>> > installed,
>> > skip it.
>> > <01-15-2006 11:32:36> Stopping service SMS_SITE_CONFIG_MANAGER
>> > <01-15-2006 11:32:36> Service SMS_SITE_CONFIG_MANAGER is not installed,
>> > skip
>> > it.
>> > <01-15-2006 11:32:36> Stopping service SMS Remote Control Agent
>> > <01-15-2006 11:32:36> Service SMS Remote Control Agent is not
>> > installed,
>> > skip it.
>> > <01-15-2006 11:32:36> Stopping service LICSVR_SERVICE
>> > <01-15-2006 11:32:36> Service LICSVR_SERVICE is not installed, skip it.
>> > <01-15-2006 11:32:39> Starting InstallDatabase()
>> > <01-15-2006 11:32:39> Registering connects for SQLSRV00, , SMS_SUV
>> > <01-15-2006 11:32:39> Registered the types
>> > <01-15-2006 11:32:39> SQL Checkpoint 3
>> > <01-15-2006 11:32:39> Registering connects for SQLSRV00, , SMS_SUV
>> > <01-15-2006 11:32:39> Registered the types
>> >
>> > In sitecomp.log, I got this error:
>> > ERROR: NAL failed to access NAL path "MSWNET:\\SQLSRV00\admin$\",
>> > probably
>> > because the machine is down, the network is down, or the Site System
>> > Connection Accounts are misconfigured. NAL
>> > INetworkObject::IsAccessible()
>> > returned 0x80070005: The operation completed
>> > successfully.SMS_SITE_COMPONENT_MANAGER 1/17/2006 12:23:24 PM 3516
>> > (0x0DBC)
>> >
>> > Server reinstallation failed and will be retried in the next polling
>> > cycle. SMS_SITE_COMPONENT_MANAGER 1/17/2006 12:23:24 PM 3516 (0x0DBC)
>> >
>> >
>> >
>> > Under the System Status -> Site Status -> Site Name, it is empty.
>> > I think it should have 20+ services running here. It is completely
>> > empty.
>> > The schema has no problem of extending.
>> > SMS server is the local administrator of the SQL server.
>> > I am suspecting that the problem is talking to the SQL server but no
>> > idea
>> > to
>> > continue.
>> > Any help is appreciated.
>>
>>
>>


.

Relevant Pages

  • RE: Management Point not available
    ... > configured the Default Web Site within IIS 6 to use port 8080. ... Manually restart the SMS Agent Host service on the MP. ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Re: Failed to get a SQL Server connection
    ... remote SQL Server device. ... check that you have installed the SMS SQL database on the default ... Use the output to verify that the account is enabled, ... SMS Site Component Manager failed to reinstall this component on this site ...
    (microsoft.public.sms.setup)
  • Http verification .sms_aut (port 80) failed
    ... I noticed I couldn't get SMS reports to work.... ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Re: Http verification .sms_aut (port 80) failed
    ... I noticed I couldn't get SMS reports to work.... ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ... SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration. ...
    (microsoft.public.sms.admin)
  • Re: SMS Component errors after installing SP2
    ... MVP Windows Server System - SMS ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ... is used to publish fully qualified host names in Active Directory. ...
    (microsoft.public.sms.setup)