[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1131
  • Last Modified:

MS CRM 3.0 install error "Cannot generate SSPI context" when connecting to SQL server

I am installing MS CRM 3.0 on an SBS 2003 SP1 server connecting to an SQL 2005 Standard server for the db and reporting service. I am getting an error listed in the checks area on the screen prior to allowing the install. The error is "Cannot Generate SSPI context". I believe the issue is being caused by my SQL server name or named instance of "XXXXX-SQL". I have read multiple SSPI articles attempting to solve the problem but nothing specific to CRM.

0
ND_2007
Asked:
ND_2007
  • 6
  • 4
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
It's not being caused by your SQL server name or named instance if you are installing the Small Business Edition of CRM because that version must be installed on a SBS 2003 Premium edition with SQL Server running on the same machine.

If you are installing the standard version of CRM, you cannot do so on an SBS.

Jeff
TechSoEasy


0
 
ND_2007Author Commented:
Thanks, I did not see anywhere in the requirements that it needed to be the premium version of SBS to install CRM. I did see either using SQL 2000 SP4 or SQL 2005 standard or enterprise.

To be dumb about the SBS server that was purchased and setup before I was employed here how do I tell if it is the premium or the standard edition?

Keith
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Perhaps you should review the CRM 3.0 SBE implementation guide?
http://download.microsoft.com/download/D/9/C/D9C50A36-8464-44BB-AC39-555C562C09B8/Implementing%20Microsoft%20CRM%20Small%20Business%20Edition.pdf

Also, don't be dumb about SBS... you need to fully understand SBS before working with one.  If you have a good amound of standard Server 2003 knowledge, you should certainly leave that at the door... SBS must be managed according to it's unique design.

The difference between SBS Standard and Premium is that Premium includes SQL Server and ISA Server.  If you have the Premium Technologies disk as part of your original media, then you have Premium.  

SBS 2003 SP1 Premium uses SQL Server 2000.  In order to ugrade to SQL 2005 you would need to upgrade SBS to R2.  

If you have Standard Edition, you need to upgrade to Premium.  The cost is really only the difference between the two versions so you don't lose anything.

See http://www.microsoft.com/windowsserver2003/sbs/howtobuy/pricing.mspx for the various SKUs.

Jeff
TechSoEasy
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
ND_2007Author Commented:
Thank you for the link. I was using the CRM 3.0 Implementation guide that had a specific section on SBS but not fully devoted to it.

In the implementation guide it states under the SQL selection that you can select the SQL server from a list of available SQL servers in the domain of which the SQL 2005 server I want to connect to is in the domain and available. So I do believe there is a login, name, permissions tcp issue with connecting to it.

I definitely understand the special attention needed for SBS but I was more saying where in SBS 2003 does it tell you if you have the premium edition or standard. This way I would know if the original installer just did not load the premium technologies disk or that we do not own it.

Keith
0
 
ND_2007Author Commented:
I found this post on A Freaky Microsoft Dynamics CRM Blog indicating I can setup the system in the fashion I am attempting to do with the SBS and SQL on separate machines (matches what the implementation guide indicates).

"Just a quick blog (copy and paste) about what is allowed regarding the installation of Microsoft Dynamics 3.0 Small Business Edition on a Small Business Server 2003.

   1.Microsoft CRM 3.0 SBE can be installed on a SBS 2003 Premium server (all in one box)
   2. Microsoft CRM 3.0 SBE can be installed on a SBS 2003 Standard server + SQL Server (all in one box)
   3.Microsoft CRM 3.0 SBE can be installed on a SBS 2003 server, with a standalone SQL server that is not part of the SBS server (however, this requires separate regular SQL license to be purchased)
   4.Microsoft CRM 3.0 SBE CANNOT be installed on a server that is NOT a SBS 2003 server
Hope this clarifies a lot of your questions on this specific topic."

0
 
ND_2007Author Commented:
A new development with this is that if I change the reporting services from connecting to an existing server for reporting to create a new server I get the same "Cannot generate SSPI context" that is under the SQL server check. If I use connect to existing it just gives me a warning about "trust for delegation" for the computer object.

HELP!!!

Keith
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
What kind of licensing do you have for this separate SQL 2005 Server?

Jeff
TechSoEasy
0
 
ND_2007Author Commented:
I believe It is for SQL server 2005 standard edition with 5 users. I am starting to get the feeling that it is something complex because I cannot find a solution for this particular problem anywhere on the net (blogs, forums, support sites etc.)

CRM 3.0 works with SQL 2005 workgroup edition right? I may purchase that and add it to my SBS since I don't have the premium version. Also does the workgroup edition come with reporting services?

thanks for the help!

Keith
0
 
ND_2007Author Commented:
Well I actually was able to get a grace case from Microsoft on the install since it was pre-sales for evaluation purposes. It turns out that the SPN needed to be added to the service owner. The setspn tool is in the Program Files/Support Tools folder. Through the command line we did an "setspn -L [username]" which gave us a list of the spn's. Using setspn -A we added the following 2 entries for the user:

MSSQLSvc/xxxxx.xxxxx.local
MSSQLSvc/xxxxx.xxxxxx.local:1433

After this the application installed fine with one exception that does not seem to be causing any issues except an error in my event viewer. I get the following message in the event viewer I have found the KB's in relation to the issue but have not successfully resolved it yet. I think it came about because we through trial and error added it to multiple accounts.

Source: KDC
Event: 11
There are multiple accounts with name MSSQLSvc/xxxxx.xxxxx.local:1433 of type DS_SERVICE_PRINCIPAL_NAME.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
0
 
ee_autoCommented:
Question PAQ'd, 500 points not refunded, and stored in the solution database.
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now