Management Point cannot connect to SQL database/server
We have an SCCM 2007 R2 SP2 mixed mode environment with clustered SQL servers so SQL db is on a separate server. Our SCCM servers are 2008 64 bit as are our SQL servers. SQL is SQL 2005. In our mpcontrol.log we are seeing these errors constantly: *** *** Unknown SQL Error! SMS_MP_CONTROL_MANAGER 9/29/2010 12:14:09 PM 2652 (0x0A5C) *** Failed to connect to the SQL Server. SMS_MP_CONTROL_MANAGER 9/29/2010 12:14:09 PM 2652 (0x0A5C) Failed to get connection to the configured SQL database. SMS_MP_CONTROL_MANAGER 9/29/2010 12:14:09 PM 2652 (0x0A5C) Failed to connect to the configured SQL database. SMS_MP_CONTROL_MANAGER 9/29/2010 12:14:09 PM 2652 (0x0A5C) Failed to get the current CLR Enabled configuration setting for the configured SQL Server hosting the database. SMS_MP_CONTROL_MANAGER 9/29/2010 12:14:09 PM 2652 (0x0A5C) Completed periodic tasks. SMS_MP_CONTROL_MANAGER 9/29/2010 12:14:09 PM 2652 (0x0A5C) Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 9/29/2010 12:19:09 PM 2652 (0x0A5C) Http test request failed, status code is 500, 'Internal Server Error'. SMS_MP_CONTROL_MANAGER 9/29/2010 12:19:09 PM 2652 (0x0A5C) Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 9/29/2010 12:19:09 PM 2652 (0x0A5C) Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 9/29/2010 12:24:09 PM 2652 (0x0A5C) Http test request failed, status code is 500, 'Internal Server Error'. SMS_MP_CONTROL_MANAGER 9/29/2010 12:24:09 PM 2652 (0x0A5C) Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 9/29/2010 12:24:09 PM 2652 (0x0A5C) Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 9/29/2010 12:29:09 PM 2652 (0x0A5C) Http test request failed, status code is 500, 'Internal Server Error'. SMS_MP_CONTROL_MANAGER 9/29/2010 12:29:09 PM 2652 (0x0A5C) Here is a section of the mp_GetAuth.log: CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 MPDB ERROR – CONNECTION PARAMETERSSQL Server Name: PRDMSSQL02\LSSQL Database Name: SMS_002 MPDB ERROR - CONNECTION PARAMETERS SQL Server Name : PRDMSSQL02\LS SQL Database Name : SMS_002 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 I have verified in SQL that named pipes and TCP/IP are enabled. I've also verified that the SPN is set and is correct. The MP server is also in the local admins group on the SQL servers. Port 80 is being used for client requests. I don't see any errors on the SQL server. How can I determine what account is being used to connect to the SQL server? Or is it even getting to that point? Thanks,
September 29th, 2010 8:33pm

"SQL Server does not exist or access denied." By default, the server account of the system is used to access the database. Thus, this account must be a local admin on the DB server and must be a SysAdm in the DB itself. Is this a new installation? If not, what changed? Is the MP Server account a local admin on the SQL Server using a group membership or directly? Are you connecting to the virtual name of the SQL Server or the name of one of the cluster nodes? Is the MP Server account a local admin on both physical server nodes?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2010 9:28pm

The MP server account is in the local admins group on both physical server nodes via group membership. We are connecting to the virtual name of the SQL server (PRDMSSQL02) In the SQL Server management studio, the MP server has the role smsdbrole_MP. Under login properties, the server role is "public". These have not been changed. This isn't a new installation. We had a single SQL server and are trying to "test" using a SQL cluster. That is when these issues started. thanks!
September 29th, 2010 9:55pm

When did you create the security group containing the MP server account? Has the MP been rebooted since being added to this group? What version of Windows is the cluster? If Windows 2003, is Kerberos enabled on the SQL resource group? If so, have you verified that an account for the virtual SQL resource was created in AD? What do your SPNs look like?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2010 11:44pm

The security group containing the MP server account was created when we initially installed the SCCM environment. The MP was added to the group at that time (about 6 months ago...) The MP server (along with all the SCCM servers have been rebooted multiple times. The SQL server cluster is Windows 2008. the virtual SQL server is in AD as well. Our SQL admin has said that the SPNs are correct and that we are using the SQL servers for other applications/systems with no issues. Here's another clip from the mpcontrol.log: *** [08001][17][Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. SMS_MP_CONTROL_MANAGER 9/30/2010 7:29:13 AM 2652 (0x0A5C) *** [01000][67][Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). SMS_MP_CONTROL_MANAGER 9/30/2010 7:29:13 AM 2652 (0x0A5C) *** Failed to connect to the SQL Server. SMS_MP_CONTROL_MANAGER 9/30/2010 7:29:13 AM 2652 (0x0A5C) Failed to get connection to the configured SQL database. SMS_MP_CONTROL_MANAGER 9/30/2010 7:29:13 AM 2652 (0x0A5C) Failed to connect to the configured SQL database. SMS_MP_CONTROL_MANAGER 9/30/2010 7:29:13 AM 2652 (0x0A5C) Failed to get the current CLR Enabled configuration setting for the configured SQL Server hosting the database. SMS_MP_CONTROL_MANAGER 9/30/2010 7:29:13 AM 2652 (0x0A5C) Do we have to have an ODBC connection to the SQL server now that it's clustered? How can I tell what account is being used to log into the SQL server? Thanks!
September 30th, 2010 3:32pm

Also, when I use the commands http://mpservername/sms_mp/.sms_aut?mplist - I do not get any info back. I do get the 500 Internal Server error. However, when I issue the command http://mpservername/sms_mp/.sms_aut?mpcert, I am able to see the certificate/long string..... thanks
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2010 5:01pm

A 500 is expected if you are having DB connectivity errors. ConfigMgr always uses an ODBC connection to SQL Server. The account of the server hosting the MP is used to log into the DB. Just because the DBA says its correct, doesn't mean it is. Check the SPN and Kerberos on the virtual resource group. What port is the the SQL instance listening on? Is there a host based firewall enabled on the SQL server or the MP? Have you reviewed the security log on the SQL Server?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
September 30th, 2010 5:14pm

I've checked the SPN on the server and it is set to the virtual name: PRDMSSQL02 I don't see anything in the log on the SQL server that references the MP server. I do see connections in the log on the SQL server from the site server as well as the PXE server. The MP account domain\sccmmp01$ is an admin on the SQL servers. I'll check the port and firewall as well as the ODBC connection. thanks again!
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2010 5:58pm

well, the only way we could find to correct this issue is to move the SQL db back to a non-clustered server. Once we did that and restarted the site server, everything works fine. Has anyone gotten SCCM to work in a SQL clustered environment? If so, were there any other configuration issues that needed to be done? It appears that our issue may have been "name resolution" related, but we couldn't find out where it was failing.
October 4th, 2010 7:07pm

I've done it in production multiple times for multiple customers without issue. There is nothing special, its a SQL DB and the clients have no idea that it is hosted on a cluster. You say you think it might be name resolution issue? Why do you think this? Can you ping the virtual resource name from the MP itself?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2010 8:10pm

Yes, we can ping the virtual name from the MP server. We have verified DNS settings, IP settings, ports, the SPN's, firewall settings, ODBC connection - all to no avail. Going back to these errors in the log: *** Failed to connect to the SQL Server. SMS_MP_CONTROL_MANAGER 9/29/2010 12:14:09 PM 2652 (0x0A5C) Failed to get connection to the configured SQL database. SMS_MP_CONTROL_MANAGER 9/29/2010 12:14:09 PM 2652 (0x0A5C) Failed to connect to the configured SQL database. SMS_MP_CONTROL_MANAGER 9/29/2010 12:14:09 PM 2652 (0x0A5C) Failed to get the current CLR Enabled configuration setting for the configured SQL Server hosting the database. SMS_MP_CONTROL_MANAGER 9/29 I can't determine what account is attempting to connect to the SQL server. We've run realtime monitoring tools, but the MP doesn't seem to want to connect to the SQL server for whatever reason (name resolution?). Unfortunately, since we've moved back to a single server, I don't have any of the prior logs torefer back to.
October 4th, 2010 9:17pm

It's probably time to open a case with CSS because either you missed something (probably not anything obvious) or you hit a true bug (yes they exist). In either case, it will take more dedicated troubleshooting and help that can be offered here on the forums.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2010 10:36pm

FYI - I had this exact problem and found it was a name resolution problem. My DB server was on a resource domain and the MP server didn't have its domain name in the suffix search list. So everything worked nicely when resolving the FQDN, but when the DB connection is establisted it uses the netbios name which failed: Registered connection type for SQL Server 'SCCMDB' and database 'SCCMDB, 1433\SMS_001'. Hope this helps. Matt. mattlog.net
November 7th, 2010 6:20pm

FYI - I had this exact problem and found it was a name resolution problem. My DB server was on a resource domain and the MP server didn't have its domain name in the suffix search list. So everything worked nicely when resolving the FQDN, but when the DB connection is establisted it uses the netbios name which failed: Registered connection type for SQL Server 'SCCMDB' and database 'SCCMDB, 1433\SMS_001'. Hope this helps. Matt. mattlog.net
Free Windows Admin Tool Kit Click here and download it now
November 7th, 2010 6:20pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics