SQL Server instance could not be contacted to verify permissions SCCM Sp1 and SQL 2008
Getting the SQL Server sysadmin rights error. Ive seen this and it doesn't help, http://social.technet.microsoft.com/forums/en-US/configmgrgeneral/thread/70539409-7c7d-48ee-9d13-2e8f0f37f955/ What Ive done: Ran the SQL service with a Domain Admin account, I set the SPN... SQL service account and Computer is part of local Admins Used the Provisioning tool Default instance Even tried running the SQL Agent service locally. Checked the PreReq.log and getting the following: <10-16-2009 07:58:58> Could not connect to SQL database. <10-16-2009 07:58:58> (SERVERNAME); SQL Server sysadmin rights; Error; Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance targeted for site database installation or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue. Environment: SQL server 2008 and Windows 2008 same computer AD, IP/DNS on a different server I don't think its a sysadmin permission issue but something with configmgr is not seeing the database. Any tips to verify the SQL connection/anything else I'm missing?
October 17th, 2009 2:34am
The SQL service account should not be an domain admin or even a local admin as a security best practice. The SQL Agent is not required for ConfigMgr. What SPN did you set and what syntax (exactly) did you use to set it? What account are you using to install? Is SQL on the same system you are trying to install ConfigMgr on? If not, did you make the computer account for the ConfigMgr system a local admin in the SQL server?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 17th, 2009 3:40am
I do think it is a sysadmin permission issue.In contrast to sql 2005, the built-in\administrators group is no longer a sysadmin in SQL 2008.In SQL server management studio, connect to the database engineNavigate to Security\loginsCreate a new loginType in the name of the Sccm primary site server as DomainName\Primarysiteservername$On the Server Roles tab grant the computer account sysadmin permissions.Now try again."Everyone is an expert at something"
Kim Oppalfens Configmgr expert for lack of any other expertise.
http://www.scug.be/blogs/sccm
October 19th, 2009 12:39pm
Its a lab environment so I wasn't too worried about the security. Sorry my mistake, I meant the SQL Service not the agent. I am installing with the SQL Account, also tried my domain admin account. SQL is on the same computer I gave the server local admin rights. setspn -A MSSQLSvc/<Servername.fqdn.com>:1433 <SQL Account> If I do a setspn -L I see it in there. The one thing I haven't tried is deleting the SPN and recreating it. I'll give that a try.
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2009 7:50pm
Hi I doubled check and made sure the SCCM primary site server name was in the sysadmin accounts.
October 19th, 2009 7:53pm
I ran the following SQL statement in SQL management Studio
select auth_scheme from sys.dm_exec_connections where session_id=@@spid
it is returning NTLM instead of KERBEROS. So I went back and re-checked the SPN, everything looked fine. So I used ADSI Edit to give SQL the rights to dynamically create SPN, just in case I was doing something wrong. (Per http://support.microsoft.com/kb/319723) Looks like the SPN is getting created automatically because I see this in the Application logs: The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/(server.fqdn.com):1433 ] for the SQL Server service. Doubled check with setspn -L.
Free Windows Admin Tool Kit Click here and download it now
October 20th, 2009 12:04am
If SQL is on the box you are installing ConfigMgr on, the SPN doesn't matter. As Kim points out, local admins are no longer added to sysadmins roles in SQL when installed on Server 2008. Thus, you need to make sure that the account you are installing with has sysadmin rights in SQL server as well as local admins in Windows. The server account has nothing to do with these and will play no part because SQL and ConfigMgr are on the same system.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
October 20th, 2009 1:26am
Hi I am checking the rights again: 1. SQL Studio 2. Security->logins 3. Verified the account is there. 4. Checked Server Roles and it is listed under Sysadmin 5. The same account is a local admin I thought that I had to add the configure SPN since I am not using Local Service for SQL Server. I have installed SCCM a few times before, though this is a new lab environment. I'm not sure what I am missing. I doomed myself, I told my boss that the install is pretty straightforward and I could have it done in an afternoon :)
Free Windows Admin Tool Kit Click here and download it now
October 20th, 2009 2:32am
SPNs are for kerberos authentication between systems/authorities, in this case, you're on the same system and thus already authenticated. Which account are your checking for permissions on? The one you are logged in with and trying to install ConfigMgr with? Is SQL server running? What version?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
October 20th, 2009 4:23am
I rebuilt the server and was able to install.Not sure what happened, thanks for the help!
Free Windows Admin Tool Kit Click here and download it now
October 22nd, 2009 2:13am