May 28, 2009 at 5:46 pm
Hi All,
I am facing problems in installing SQL 2005 Enterprise Edition. I tried two methods
1) First i install SQL 2000 Enterprise Edition on a Server and restored my databases successfully. Also i restored 100 DTS packages in SQL 2000 and installed SP4 for SQL 2000.every thing goes smoothly.
I have to upgrade SQL 2000 to SQL 2005 enterprise Edition. When i ran the setup and select upgrade option . I dont need Analysis Server, Reporting Server and rest of tools.
Just want to upgrade the instance to SQL 2005.
When setup came down to SQL Server Database Services the error comes up . The error says
" SQL Server setup couldnot connect to the database service for server configuration. the error was: [Microsoft][SQL Native Client]SSL provider: The clilent and server cannot communicate, because they do not possess a common algorithm.
Refer to server logs and setup logs for more information. for details on how to view setup logs, see "How to view setup Log Files" in SQL Server Books online. "
i click on retry button but it didnt work so i cancel it and SQL 2005 finished unsuccessfully. no Studio nothing gets installed.
This was first approach. Second Method that i adopted is
2) I uninstall everything from server related to SQL 2005. Reboot the server . and run fresh setup of 2005 enterprise Edition. Selected default instance and default configuration and choose local system account for restarting the service.
Again when the setup reaches configuring SQL Server Database Services the same error comes and setup finished unsuccessfull. Again nothing gets installed.
I havent faced this error before even i build couple of others servers in the same approach.
Please can someone help me in getting this error resolved?
I'll be greatful .
Thanks in Advance.
May 28, 2009 at 8:22 pm
Hello,
It’s not an error message that I have experienced myself, but there are a couple of threads around that suggest it can be caused by having the “FIPS compliant algorithms enabled”.
You could check if it is enabled on your Server, and if so disable it and try once more.
You can access the setting via: Administrative Tools, Local Security Policy, Local Policies, Security Options, System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply