RE: connection problems in secondary site and SQL server

I'm probably miles off, but check your Secondary site servers Proxy
Management Point MP_RETRY.LOG and MP_GETAUTH.log files.

I wonder if it is full of Database connection errors? If so you could try
changing from TCP\IP to Named Pipes ...

There are some steps on doing this on the following KB article:

http://support.microsoft.com/kb/832109

--

Rob - Windows Management User Group

www.wmug.co.uk





"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

  • Security context issue (weird behavior)
    ... The SQL Server is setup to use mix mode authentication. ... The users have a domain account. ... To log in to the SQL server I use an ADO connection. ... I tried to view the pages from another machine with the anonymous access ...
    (microsoft.public.data.ado)
  • Re: SQL Connection String using Domain Account
    ... Web.Config but now have the problem that the web site will not run under ... you can have a username/password set up in sql server - but this would ... The DBA has given me a Domain user account with rights to ... I am unable to get a connection to the database. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Passthrough authenication w/ SQL trusted connection
    ... separate connection will be used for each security context (each user ... account will have it's own pool). ... if you are using a Windows 2000 Domain, ... backend SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: SQL Server on XP Home Network
    ... There is an "sa" account under the Security>Logins area. ... Does that coorelate to a SQL Server login? ... I tried setting up the connection to use that SQL Server ...
    (microsoft.public.sqlserver.setup)
  • Re: Login failed for user (null)
    ... SSPI security assumes that the user credentials are known to the SQL Server. ... Setup a login account matching your credentials and give the account rights ... > When I created my connection in the Data Adapter Configuration wizard, ...
    (microsoft.public.dotnet.framework.adonet)