RE: MP Install issue
- From: BrianG <BrianG@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 27 Jan 2006 07:21:01 -0800
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....
.
- Follow-Ups:
- RE: MP Install issue
- From: Justin Harter
- RE: MP Install issue
- Prev by Date: Re: SMS client installation failures
- Next by Date: RE: MP Install issue
- Previous by thread: Re: SMS client installation failures
- Next by thread: RE: MP Install issue
- Index(es):
Relevant Pages
|
