RE: MP Install issue



Will setting the SPN on the domain account fix the communication issue
between the secondary and primary?
--
Justin Harter
::BLOG:: http://spaces.msn.com/members/jharter


"Justin Harter" wrote:

> Where in the installation are you talking about specifying the account rather
> than integrated. In the secondary site installation, it has a page that
> refers to SMS Security, which is Advanced security or Standard (advanced is
> usually recommended). Is this what you are talking about?
>
> I definitely think that you are on the right track as far as the sites not
> being able to communicate with the database, but I'm unsure still as to how
> to fix it (changing the SQL Service account to local system really isn't an
> option for me).
>
> --
> Justin Harter
> ::BLOG:: http://spaces.msn.com/members/jharter
>
>
> "BrianG" wrote:
>
> > OK.. I got it working.. however the resolution leads to another question..
> >
> > Digging further I've pulled up the following info out of the
> > SMS_CCM\Logs\MP***.log files
> >
> > From MPRetry.log :
> >
> > MPDB ERROR - CONNECTION PARAMETERS
> > SQL Server Name : servername
> > SQL Database Name : SMS_S01
> > Integrated Auth : True
> >
> > MPDB ERROR - EXTENDED INFORMATION
> > MPDB Method : Init()
> > MPDB Method HRESULT : 0x80004005
> > Error Description : Login failed for user '(null)'. Reason: Not associated
> > with a trusted SQL Server connection.
> > OLEDB IID : {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}
> > ProgID : Microsoft OLE DB Provider for SQL Server
> >
> > MPDB ERROR - INFORMATION FROM DRIVER
> > SQL Server Name : servername
> > Native Error no. : 18452
> > Error State : 1
> > Class (Severity) : 14
> >
> >
> > From MPPolicy.log
> >
> > MPDB ERROR - CONNECTION PARAMETERS
> > SQL Server Name : servername
> > SQL Database Name : SMS_S01
> > Integrated Auth : True
> >
> > MPDB ERROR - EXTENDED INFORMATION
> > MPDB Method : Init()
> > MPDB Method HRESULT : 0x80004005
> > Error Description : [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does
> > not exist or access denied.
> > OLEDB IID : {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}
> > ProgID : Microsoft OLE DB Provider for SQL Server
> >
> > MPDB ERROR - INFORMATION FROM DRIVER
> > Native Error no. : 17
> > Error State : 1
> > Class (Severity) : 16
> >
> >
> >
> > OK.. this tells me SQL connection problems.. thats at least better that
> > "Internal Server Error".. sheesh...
> >
> >
> > I have verified the following :
> > The computer account for the Remote server is in these groups on the Primary
> > Site server/SQL server. Local Administrators,
> > SMS_SiteSystemToSiteServerConnection_S01, SMS_SiteSystemToSQLConnection_S01,
> > SMS_SiteToSiteConnection_S01
> >
> > The SMS_SiteSystemToSQLConnection_S01 Group is permitted access to the SQL
> > Database
> >
> >
> > Now... as everyone does once they are thouroughly frustrated after 3 days
> > of fighting.. i started making changes without tracking them.. so.. one of
> > the things i did eventually fixed it.. I'm going back and trying to
> > re-tracking my steps as i write this..
> >
> >
> > Looking at the statement "Integrated Auth : TRUE" something (finally..)
> > clicked.. SQL Service is starting with a Domain Service Account... Easiest
> > thing to do at this point for testing was to change the SQL Service to start
> > as Local System.. Rebooted Primary Server, then Secondary... and wouldn't you
> > know it.... It started working..
> >
> > Changed it back.. it broke again..
> >
> > So i guess when instaling the secondary site.. if your SQL Serivce is
> > starting with a domain account, you need to specify that account, not
> > Integrated...
> >
> > This leads to my next question.. for future knowledge.. How do I change the
> > SQL Auth type/SQL Server Account on a secondary site after it is installed?
> > (without re-installing the site....)
> >
> >
> > My head hurts....
> >
> >
.



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: MP Install issue
    ... Where in the installation are you talking about specifying the account rather ... > MPDB ERROR - CONNECTION PARAMETERS ... > SQL Server Name: servername ... > with a trusted SQL Server connection. ...
    (microsoft.public.sms.setup)
  • RE: connection problems in secondary site and SQL server
    ... Do you have a Windows 2003 server anywhere in your environment? ... i can't add this account to this group. ... SMS Management Point encountered an error when connecting to its Database ... SMS on SQL Server My_Primary_SMS_Server. ...
    (microsoft.public.sms.admin)