Tuesday, March 27, 2012

Error when starting SQL SERVER service

Hello all,
When i am starting SQL Server, I am getting an error saying "Encryption Error When starting SQL Server service.. on connecttionbopen.... " What could be the problem ?
Please help me with the steps..
Saiwhat are the log on properties of the sql server services on your server?
have u recently changed the password for the server?
or else try using some other protocol from client/server utility.|||hello Harshal,
Actually when i am logging in to the database using my regular user details i am getting this error. Infact i am not able to see the Properties of the SQL server from the Enterprise manager. When i right Click and select properties of the Service in E.M i am getting the same error.

I tried re-installing the SQL server in the same Directory.. But Still the problem hooks..

What should i do now ?

Sai|||RE:
...I tried re-installing the SQL server in the same Directory.. But Still the problem hooks..
Q1 What should i do now ?
Sai

A1 Much depends on the specific situation.

Some things to consider / investigate:

a If the server was previously functional; what environment changes may have been made prior to the server having the issue, i.e.(where any patches, development environments, upgrades, etc. applied)?

b If the server was previously functional; what was the nature of any activity performed prior to the server having the issue, e.g.(were there any peak / near peak resource utilization conditions present, where load tests, intrusion tests, etc., performed)?

{Somewhat similar issues on development machines may sometimes be traced to such things as corrupted / damaged registry keys and / or dlls. On occasion, the fix is relatively simple, but this is not always necessarily so.}

If inital efforts are unsucessful, and the time / resources to investigate in detail are not available, you may wish to consider completely reinstalling OS, MS Sql Server (from "scratch"). However, if the issue ultimately is caused by a misbehaving custom application or perhaps even failing hardware, it may well re-occur (until any underlying issues have been resolved).

No comments:

Post a Comment