Monday, February 27, 2012

Help - can't create or edit a Maintenance Plan

I noticed the following after changing the password for the SQL 2005 Service
Accounts.
- I could not longer edit or create Maintenance Plans.
- error returned 0x80004005 (Client unable to establish connection)
In the SQL error log I found
Server Microsoft SQL Server 2005 - 9.00.1399.06 (X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
.
.
Server FallBack certificate initialization failed with error code: 1.
Server Warning:Encryption is not available, could not find a valid
certificate to load.
.
.
Logon The prelogin packet used to open the connection is structurally
invalid; the connection has been closed. Please contact the vendor of the
client library. [CLIENT: <local machine>]
Logon Error: 17828, Severity: 20, State: 3.
*** Note that SQL is running on
Windows Server 2003 R2 Standard x64 edition Service Pack 1
It is also a domain controller.
Any ideas?
ThanksHi,
I was having this exact same problem, here is what resolved this issue
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.
HTH.
BobT732 wrote:
> I noticed the following after changing the password for the SQL 2005 Service
> Accounts.
> - I could not longer edit or create Maintenance Plans.
> - error returned 0x80004005 (Client unable to establish connection)
> In the SQL error log I found
> Server Microsoft SQL Server 2005 - 9.00.1399.06 (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
> .
> .
> Server FallBack certificate initialization failed with error code: 1.
> Server Warning:Encryption is not available, could not find a valid
> certificate to load.
> .
> .
> Logon The prelogin packet used to open the connection is structurally
> invalid; the connection has been closed. Please contact the vendor of the
> client library. [CLIENT: <local machine>]
> Logon Error: 17828, Severity: 20, State: 3.
>
> *** Note that SQL is running on
> Windows Server 2003 R2 Standard x64 edition Service Pack 1
> It is also a domain controller.
> Any ideas?
> Thanks|||Yes that did it!
Thank You Very Much
"teefer22@.hotmail.com" wrote:
> Hi,
> I was having this exact same problem, here is what resolved this issue
> 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.
> HTH.
>
> BobT732 wrote:
> > I noticed the following after changing the password for the SQL 2005 Service
> > Accounts.
> >
> > - I could not longer edit or create Maintenance Plans.
> > - error returned 0x80004005 (Client unable to establish connection)
> > In the SQL error log I found
> > Server Microsoft SQL Server 2005 - 9.00.1399.06 (X64)
> > Oct 14 2005 00:35:21
> > Copyright (c) 1988-2005 Microsoft Corporation
> > Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
> > .
> > .
> > Server FallBack certificate initialization failed with error code: 1.
> > Server Warning:Encryption is not available, could not find a valid
> > certificate to load.
> > .
> > .
> > Logon The prelogin packet used to open the connection is structurally
> > invalid; the connection has been closed. Please contact the vendor of the
> > client library. [CLIENT: <local machine>]
> > Logon Error: 17828, Severity: 20, State: 3.
> >
> >
> > *** Note that SQL is running on
> > Windows Server 2003 R2 Standard x64 edition Service Pack 1
> >
> > It is also a domain controller.
> >
> > Any ideas?
> >
> > Thanks
>

No comments:

Post a Comment