services logon

Question

SQL Server 2005 standard edtion on XP workstation SP3. This is a test environment for mirroring and I am trying to use a local admin account as the logon for the sql server service. If I try to do this through the configuration manager it gives this error when applied:

WMI Provider Error Cannot find object or property. [0x80092004]

once applied, if I try to start the service, I see this in the logs:

 Error: 15466, Severity: 16, State: 1.

An error occurred during decryption.

followed by:

Error: 17190, Severity: 16, State: 1.

FallBack certificate initialization failed with error code: 1.

Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.

Error: 17182, Severity: 16, State: 1.

TDSSNIClient initialization failed with error 0x80092004, status code 0x80.

Using the local system account or a domain admin account works fine.

I suspect it is permissions related but I am not sure what is wrong. 

Any help appreciated.

thanks

 

 

---

WWED

Answer 1

did you try with certificates ? here is more help  http://msdn.microsoft.com/en-us/library/ms191140.aspx

---

http://uk.linkedin.com/in/ramjaddu

Answer 2

Hi,

Does the SQL services and instance start when you use the local admin account? Have you see this - http://blogs.msdn.com/b/karthick_pk/archive/2011/03/05/initializing-the-fallback-certificate-failed-with-error-code-1-state-1-error-number-2146893788.aspx

It required that the user profile for the account be deleted and re-created.

---

Sean Massey | Consultant, iUNITE

Feel free to contact me through My Blog or Twitter.
Please click the Mark as Answer button if a post solves your problem!

Answer 3

The SQL services and instance will not start with local admin account as originally stated. Tried deleted and recreating the profile but still the same error

---

WWED

Answer 4

Hi,

I think you have encryption issue, you run your SQL server with account and then you change this account. The point is are you changed that account using SQL server configuration manger or something else.

 

I you change it with configuration manager SQL server will solve the encryption problems otherwise you face many difficulties.

I did not try this but if possible try to change the service account to the previous account if it work, then go to SQL Server configuration manger and change the service account from there (Only no place else).

 

check this link:

http://msdn.microsoft.com/en-us/library/bb934049.aspx

 

I hope this is helpful.

 

Elmozamil Elamir

MyBlog

---

Please Mark it as Answered if it answered your question
OR mark it as Helpful if it help you to solve your problem
Elmozamil Elamir Hamid
http://elmozamil.blogspot.com

Answer 5

Thanks for the suggestion but I made the logon change for the service from the configuration manager - I understand about the problems with doing that from the services.msc

Also, it is only the local admin account that does not work. If I use local system or domain admin it works fine.

 

 

 

---

WWED

Answer 6

@southside steve

Please check whether the local admin account is a member of sysadmin role.

---

Best Regards,
Peja

Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Answer 7

local admin has sysadmin role

 

thanks 

 

steve

---

WWED

Answer 8

Karthick has blogged about this in http://mssqlwiki.com/2012/04/19/sqlserver-initializing-the-fallback-certificate-failed-with-error-code-1-state-1-error-number-2146893802/

Thanks

Manish

Answer 9

to start database mirroring , sql server services should be started with the same service accounts,

starting a service with local admin account will not allow you to configure the database mirroring

http://sqlservr.blog.com/2011/12/29/database-mirroring-in-simple-steps/

---

Ramesh Babu Vavilla MCTS,MSBI

Answer 10

I'm sorry but I got lost somewhere in the middle of this thread, so please tell me if I missed the point:

If you want to configure DB mirroring the important point is that the user authorizing the mirroring endpoint on server 1 needs to be able to authenticate on server 2 as well and vice versa. Additionally those user need the Connect privilege on the endpoint on server 2. If you run the server using a local account this account will not be able to authenticate on the other server... You will need either a domain based account FOR THE ENDPOINT (! and only for that, not necessarily for the server itself...) or you need an account that authorizes with certificates.