August 4, 2006 at 9:23 am
Hi,
I am trying to create a maintenance plan throught the UI of the Mangement Studio - SQL 2005 Standard Edition. I get the following error and have not found a useful solution. We have SSIS installed.
--
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued and failed.
Any help would be greatly appreciated.
Thanks
KR
August 7, 2006 at 8:00 am
This was removed by the editor as SPAM
August 7, 2006 at 9:12 am
it may be a problem with the surface config - I seem to remember I had to allow something to enable maint plans - probably the SSIS service ?
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
November 13, 2006 at 12:21 pm
No the ssis seems to be enabled and running. I did not see an options specifically concerning maintenance plans
Thanks
KR
November 14, 2006 at 3:53 am
Hi,
i just have the thame problem and found this solution that works for me:
1. Go to C:\Documents and Settings\"sql startup account"\Application
Data\Microsoft\Crypto\RSA\S-1-5-21......
(where "sql startup account" should be the name of your startup account
for sql server")
2 Backup and then delete any files in the S-1-5-21etcetc folder. (but
don't delete the folder)
3. Restart SQL Server.
Hope that helps
MB
November 14, 2006 at 5:08 am
It looks like Cerificate issues.
Can you please check SQLError Logs and see if there are some errors related to certificate or Encryption?
Steps provided by Michael will work if above is true.
November 14, 2006 at 8:42 am
Hi,
Both of you have put me on the right track it seems like - I did find the missing certification in the error log. Here is the curious thing - I do not find the Crypto folder in our sql startup account folder. The only place the crypto is found is in the server admin's folder. What does it mean?
Thanks
KR
November 15, 2006 at 6:16 am
Did some one change startup account?
November 15, 2006 at 9:06 am
The start up account is the same as it has always been. However, the ssis uses the built in network service account. I did not set this up, so I don't know why the different account for ssis, only that it is the default account used during installation.
Thanks
KR
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply