RE: connection problems in secondary site and SQL server

It's been a while since I had Win2k... I recall there was something w/ win2k
servers where you had to add machine accounts using a different computer.

Do you have a Windows 2003 server anywhere in your environment? Or I think
you can do this also from XP. Anyway, when logged in to the 2003 server or
XP as an account with rights to the Win2k Server, the one with the
SMS_SiteSystemToSQLConnection_<sitecode >, right-click "My Computer", Manage.

Highlight "Computer Management (local)", and right-click, connect to another
computer.
Type in the Windows 2000 server name.
Now, go to Local Users and Groups, Groups; and double-clik the
SMS_SiteSystemToSQLConnection_<sitecode > group.
Click Add...,
(here's the important bit): then Object Types... and check on "Computers"
Now type in the secondary site server name, OK, Ok, OK...

Hope this helps!
--
Standarize. Simplify. Automate.


"cyb165er" wrote:

Sherry. No work when i do owner this group in the database.

I see that the secondary site server name no appear in the
SMS_SiteSystemToSQLConnection_<sitecode > group in me primary server.
And, i can't add this account to this group. The system (win2ksp4) no permit
to me add computer account to this group.
I think that is the source of the problem.

Please, how i can resolve it?

thanks in advanced
Cyber


"Sherry Kissinger [MVP-SMS]" wrote:

http://www.myitforum.com/forums/Site-Status:__SMS_MP_CONTROL_MANAGER/m_136270/tm.htm

Check mchung's entry (the last one) in that thread. Hope that helps!

--
Standarize. Simplify. Automate.


"cyb165er" wrote:

hi:
I spend some days with problems in me proxy MP.
When i do the http verificartion show error.

Finally i can see this error in Status Message Viewer. Error 5420.

I have one primary and one secondary site. Standard security, primary and
secondary use the same SQL database. In me primary alla run fine, not in
seconcary, for this problems in MP.

SQL use SQL and Windows autentication. I use SMSService account to
comunicate between sites and add this account to
SMS_SiteSystemToSQLConnection_<sitecode > group

please i can appreciate if any share the correct use of account in SMS system

Any another idea to find the problem?

I appreciate the time to read and help me.

Thanks in advanced
cyber






SMS Management Point encountered an error when connecting to its Database
SMS on SQL Server My_Primary_SMS_Server. The OLEDB error code was 0x80004005.

Possible cause: The SQL server site system is turned off, not connected to
the network, or not functioning properly.
Solution: Verify that the SQL server site system is turned on, connected to
the network, and functioning properly.

Possible cause: SMS Management Point does not have sufficient access rights
to the SQL server site system.
Solution: Verify that the SQL server is properly configured to allow
Management Point access. If using a standard SQL security account, verify
that the SQL Server is configured to allow standard SQL Security; or
configure the Management Point to use an NT integrated security account, with
appropriate access. If using integrated security, verify the account used
by the MP to connect to the SQL server is a member of the
SMS_SiteSystemToSQLConnection_<sitecode > group on the SQL server, that the
account is not locked out, and that the account password is not expired. (In
standard security, the default account is SMS_SQL_RX_<sitecode>.)

Possible cause: Network problems are preventing SMS Management Point from
properly accessing the SQL server.
Solution: Investigate and correct any problems with your network.

Possible cause: The Management Point having problems is at a secondary site,
and SQL access account being used was recently reset by the parent site.
Solution: This can automatically repair itself after one hour , as long as
the account in use is not locked out. Check that the account in use is not
locked out. Instead of waiting an hour, you can stop and start the
SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration.

Possible cause: The SQL server Service Principal Names (SPNs) are not
registered correctly in Active Directory
Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.
.

Relevant Pages

  • Re: Compromise?
    ... Yes, if you don't provide a password on your SA account, anybody able to run ... and connect now has complete control over your SQL Server. ... Server has. ...
    (microsoft.public.sqlserver.security)
  • Re: Windows Auth to SQL Server from ATL Web Service not working...
    ... account I'm logged on as. ... SQL on a different box from my web service in an Atl Server web ... impersonation token is not passed on to the SQL Server. ... Event Category: Account Logon ...
    (microsoft.public.vc.atl)
  • Re: Discussing 3 different strategies for deleting from multiple tables
    ... I will be using SQL Server but I am riding on top of a third party ... FYI, Account contains around 20K ... >>> This results in one parameterized query followed by two more trips to ...
    (microsoft.public.data.ado)
  • Re: Site Code Not Discovered.
    ... I receive the following when trying to reinstall the Management Point. ... The IIS IWAM account has expired, been disabled, or has ... DHCP Setup - are the clients looking at a specific DHCP Server ... outide of the SMS boundaries, even though it is dishing out SMS ...
    (microsoft.public.sms.admin)
  • RE: MP Install issue
    ... Will setting the SPN on the domain account fix the communication issue ... >> MPDB ERROR - CONNECTION PARAMETERS ... >> with a trusted SQL Server connection. ...
    (microsoft.public.sms.setup)