I turned on Single Sign on Service on MOSS 2007 Server. In my environment, I have medium server farm with 2 front-end web servers, App server, index server and cluster SQL backend. When I tried to configure single sign on, I got this error "The sql server specified is either invalid or is an unsupported version" Under the server name, I entered SQL Cluster name instead of the SQL Server name because my SQL server is set up as cluster. Have anyone sucessfully set up SSO on MOSS 2007? Thanks, Thusinh

I am getting this error as well. I have the environment as a server farm with one frontend server and one SQL backend server running SQL Server 2000 SP4. I will continue working on setting up SSO, explicitly setting up the required multiple user accounts, and seeing if this fixes the problem.

I also have this error. I have one frontend server and one sql 2005 backend server. Any fix?

Im also having this problem and cannot find an answer on the net. This thread has been open for a long time, still without a solution. Im running a three tier farm consisting of 1 Web front end server, 1 application server and 1 SQL 2005 server. I was led into setting up SSO when I tried to connect SharePoint Designer to my SQL database. I found that if your SQL database is NOT on the same server as SharePoint, you are required to use SSO. This is due to the single authentication hop restriction. If your SQL is on the same box as your SharePoint, there is only one authentication hop, thus connecting to SQL with SharePoint Designer is possible. I hope someone can offer some insight on the "The sql server specified is either invalid or is an unsupported version" error. Ive set the Microsoft Signle Sign on service to use the a domain account with SQL access, the administrative accounts on the SSO configuration page are also domain accounts with proper privileges. I checked the SQL server to insure that SQL browsing was enables along with the corresponding protocols such as TCP/IP.

I resolved this error by changing the SQL Server. It appears that MOSS installs 2 SQL Server instances (my farm is all on one server). One is called MICROSOFT##SSEE and the other is OFFICESERVERS. By SSO defaults toMICROSOFT##SSEE, but when I changed the instance to OFFICESERVERS I was able to create the SSO db.

I do not see a secondary instance of SQL when looking at SQL Management Studio. Im running SharePoint 2007 Enterprise Edition with SQL Server 2005 Enterprise Edition. Some additional history. A few months back I attempted to setup SSO with my SQL 2005 Server which failed. As a test, I tried pointing the SSO config to my SQL 2000 Server. The save was successful on the Manage Server Settings for Single Sign-On page. I did not continue and complete the SSO setup, because my goal was to get it to work with SQL 2005. Needless to say this project was set aside for a few weeks. Current Situation: Further investigation has led me down a path with still no solution. Ill walk you through the process. At the Manage Server Settings for Single Sign-On page, I received the The Sql Server specified is either invalid or is an unsupported version. error after clicking ok to execute the configuration of SSO. I went into the detailed SharePoint logs located at: c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS (On the SharePoint Web Server) and found the following entries. These entries appear every time I attempt to execute the SSO configuration as mentioned in step 1 above. I noted the line below MYDOMAINNAME\USERNAMEUSEDBYSSOSERVICE as this identified a permissions failure. SSOSRV.EXE (0x1558) 0x0940 SharePoint Portal Server SSO 0 High NetGetDCName failed SSOSRV.EXE (0x1558) 0x0940 SharePoint Portal Server SSO 0 High Error code is: -2147022443 SSOSRV.EXE (0x1558) 0x0940 SharePoint Portal Server SSO 0 High IsValidGlobalAccount() failed SSOSRV.EXE (0x1558) 0x0940 SharePoint Portal Server SSO 0 High Error code is: -2147022443 SSOSRV.EXE (0x1558) 0x0940 SharePoint Portal Server SSO 0 Critical User MYDOMAINNAME\USERNAMEUSEDBYSSOSERVICE failed to configure the single sign-on server. The error returned was 0x80070995. Verify this account has sufficient permissions and try again. w3wp.exe (0x0A1C) 0x149C SharePoint Portal Server SSO 0 Verbose RPC call to c_ConfigureSecretServer() failed w3wp.exe (0x0A1C) 0x149C SharePoint Portal Server SSO 0 Verbose Error code is: -2147022443 w3wp.exe (0x0A1C) 0x149C SharePoint Portal Server SSO 0 Verbose CSSOServiceClient::ConfigureSecretServer failed w3wp.exe (0x0A1C) 0x149C SharePoint Portal Server SSO 0 Verbose Error code is: -2147022443 I then checked the Windows Event Log on the SharePoint Web Server to find the below log: Event Type: Error Event Source: Office SharePoint Server Event Category: SSO Event ID: 6517 Date: 2/21/2008 Time: 9:55:12 AM User: N/A Computer: SHAREPOINTSERVER Description: User MYDOMAINNAME\USERNAMEUSEDBYSSOSERVICE failed to configure the single sign-on server. The error returned was 0x80070995. Verify this account has sufficient permissions and try again. I realized that this error was likely telling me that this account failed to successfully connect to the SQL Server to create the SSO database. The SQL Server event log displays Login failed for user: MYDOMAINNAME\USERNAMEUSEDBYSSOSERVICE. After doing a little research online, I made the following permission changes within SQL for the MYDOMAINNAME\USERNAMEUSEDBYSSOSERVICE account Added All SQL Server Roles to user User did not have a default database, set Master as default Set User Mapping permissions for the Config and tempbd to dbo. I reattempted step1 and received a new error within the web page. Single Sign-on error has occurred. Please contact an administrator. Details: Could not find domain controller for this domain At this point, I decided that rather then reconfiguring SSO to point at SQL 2005 rather than the SQL 2000 server, I might be able to remove the SQL 2000 Server from the farm. Unfortunately, this was unsuccessful due to dependencies. The message An object in the SharePoint administrative framework could not be deleted because other objects depend on it. appears when attempting to remove the SQL 2000 server from the farm. So, I cannot connect SSO to SQL 2005 or remove the preexisting SQL 2000 server from the farm. Suggestions?

I was having the same problem with a similar set-up. While checking the event log on the server I noticed that I was getting a kerberos error. I had been logged onto the server with a different account that I was using in the Single Sign-On Administrator Account. As soon as I logged onto the server with the same account as the Single Sign-On Administrator Account it worked like a charm. Hope this works for you. BDok

For me, the problem was the the application pool that Central Administration was running under was not a Domain user account (it was the local Administrator account). This seems to be causing problems when trying to communicate with SQL Server that is running on another computer.

Anyone got the problem solved so far?I have my MOSS installed in domain A, and my SQL Server 2005 database installed in domain B. I have created a SSO administrator account in domain B, but when i come to "Manage Single Sign-on Setting" page, i got this error"The Sql Server specified is either invalid or is an unsupported version.".Anyone have the same problem and got it solved? Please help!Nobody is perfect, I am nobody...

Hi BDok,When you said logged onto the server, which server did you mean? The server which running the central administration or database server?Nobody is perfect, I am nobody...

I managed to finally get the issue working in our environment. After using my administrative account to manage the SSO service unsucessfully, as had been described with the same event IDs and errors by others previously, I changed the sign in to the central admin siteto use the same domain user account that I have the SSO service running as and tried again. This timeitrecieved an error stating that the process could not access the SQL server specified.Upon the event log I found the following:Event ID: 5170Description: Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\SSO.mdf' because it already exists. Change the file path or the file name, and retry the operation.This was from an attempt to manually create the database previously and the mdf and log files had not been removed after deleting the database from the SQL server. I manually deleted the mdf and log files described and then tried the manage single sign on process again and then worked OK.

I met the same issue ,Who can tell me how to resolve it?

I am having the same issue as well with a test environment. I have a separate box with SQL Server 2005 and SharePoint 2007 Enterprise. I noticed that my SQL databases are located in my Microsoft Office Server\MSSQL\Data but I have no SSO.mdf. Because I am using an Active Directory to setup SharePoint, can I not use Single Sign On? Thanks if anyone and shed some light on this for me.

Before removing some user roles/rights on the SharePoint SQL server because of a Ethical Hack, my SharePoint SSO configuration for the NetBackup SharePoint GRT backup worked fine. After this change the GRT Backup didn't work anymore, and after trying to rebuild the SSO database I had the (same) error: The SQL server specified is either invalid or is an unsupported version Solution: Give the SharePoint service account sysadmin rights, this will allow the creation of the database, after which you can remove the rights again. I would like to bring the following to setup SSO to everyone’s attention: http://www.thorprojects.com/blog/archive/2008/08/02/moss-single-sign-on-setup-step-by-step.aspx Hope this helps!