RE: MP Install issue



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: SQL account rights
    ... Please advice what is the best, suitable rights rather than domain admin ... issues, such as a server that might have IIS running on the same machine, ... applicable to SQL 2000 environment, ... files, or backups, make sure that the service account has Full ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Express Fails with Hardware Error
    ... The LocalSystem account is a built-in account, ... which the SQL Service runs. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Minimum Hardware Requirement (Warning) ...
    (microsoft.public.sqlserver.setup)
  • RE: MP Install issue
    ... MPDB ERROR - CONNECTION PARAMETERS ... SQL Database Name: SMS_S01 ... with a trusted SQL Server connection. ...
    (microsoft.public.sms.setup)
  • Re: Distributed Query - Linked Servers?
    ... In the case of SQL style accounts, it doesn't seem very secure to me, because the password will be transmitted over the network. ... it should also be able to work by setting up a credential and proxy account on Server1. ... In this case it could work with NTLM authentication. ... we just need to verify that the 2 sql server instances are under sql server and windows authentication mode and the sql account you use has the permission on the 2 sql server instances. ...
    (microsoft.public.sqlserver.server)
  • Connection problem in Visual Studio 2008 C# with SQL Server 2008 Express
    ... I did manage to install VS08 with SQL ... Server 2008 Express, as I indicate in this post here: ... to make a new connection for a new programming project (so we're ... under the account of the application pool's identity while a WinForm ...
    (microsoft.public.sqlserver.setup)