February 26, 2007 at 2:36 pm
Hi,
I am getting an error - Ole Db 0x80004005(client unable to establish connection) while enumerating packages when I try to create maintenance plans when the startup account for sql is not in the local admin group.
I have checked all the windows permissions according to the kb article in the microsoft website and it does seem to have all the necessary rights.
Thanks for the help in advance
KR
February 27, 2007 at 3:16 pm
Can you please check SQL Error Logs and see if there is some error related to Certificate?
FallBack certificate initialization failed with error code: 4.
OR
Warning:Encryption is not available, could not find a valid certificate to load
Let me know if above it true
February 27, 2007 at 3:59 pm
Yes, I do find both of those errors in the error logs -
except the error number is 1.
Fallback certificate initialization failed with error code: 4
Warning: encryption is not available, could not find a valid certificate to load.
I also find a error regarding the server unable to find a certificate to start a secure ssl connection. I got the ssl cert not existing message during installation, but it said that this mean that secure reporting was not possible. Is this the cause for the failure of maintenance plans too?
Thanks
KR
February 27, 2007 at 4:33 pm
1. Create a new account and change the SQL Server startup account to the new account. Do NOT change the SQL Server services startup account if it is a local account.
2. Delete the file in folder C:\Documents and Settings\<SQL Server startup account>\Application Data\Microsoft\Crypto\RSA\S-1-5-21-963106725-2405722570-177647575-1023 .The last part (S-1-5-21-963106725-2405722570-177647575-1023) may be different for every account.
Then restart SQL Server services to take effect.
Let me know if that works
February 27, 2007 at 4:39 pm
There is not crypto folder for the sql startup account - In fact it is not in any other folder except in the user who installed the sql server?
Thanks
KR
February 27, 2007 at 4:41 pm
What is the startup account of SQL Server?
Domain account OR LocalSystem
February 27, 2007 at 4:51 pm
Domain User - This has now happend to three of our test installations - one install and two upgrades. None of them created the crypto folder for the startup account and gave us the same error while creating maintenance plans.
I also want to say that I really appreciate your prompt replies.
Thanks again
KR
February 27, 2007 at 5:12 pm
Did you change the startup account after installation by any chance?
1. Please change the account to some other domain account (which is part of local admin group)
2. Change back the account to previous account
Make sure that this is done by SQL Server Configuration Manager (Not services)
Also Try below.....
1. On the SQL Server computer, create a Microsoft Management Console (MMC) snap-in
for the Certificates tool. To do this, follow these steps:
a. Click "Start", click "Run", type "mmc" (without the quotation marks) in the
"Open" box, and then click "OK".
b. On the "File" menu, click "Add/Remove Snap-in".
c. Click "Add", click "Certificates", click "Add", click "Computer account",
click "Next", click "Finish", click "Close", and then click "OK".
February 27, 2007 at 6:06 pm
I will try that and let you know
Thanks
KR
February 28, 2007 at 9:57 am
Ok, did the change on startup accounts, that did not help. I do see a certificate under computer account/personal.
From what I have observed so far, with the fact that this has happened on 3 installations (so no changing of the startup account involved), and the fact that once I give local admin rights to the startup account, it fixes the issue - it seems that it is not a question of an existence of the certificate, but a rights issue - As a local admin the account has the rights it needs to establish the connection and create a plan, but not otherwise.
Thanks
KR
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply