Tuesday, January 09, 2007

 

Happy New Year - Your Server Is Causing Errors Everywhere!

Okay - let's recound what I've done this year:
  1. Used the Control Panel/Services applet to change the SQL Server and SQL Agent service account passwords
  2. Nothing else
Let's look at aalllllllll the fun (and different!) error messages and experiences today so far:
  1. FallBack certificate initialization failed with error code: 4
  2. The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.
  3. When trying to connect to my SSIS packages using SSMS: Client unable to establish connection
    Encryption not supported on SQL Server. (MsDtsSrvr) [note: I can browse/open file-based packages just fine)
    1. Failed to retrieve data for this request was also seen
  4. When trying to retrieve SSIS package info from a job: The LoadFromSqlServerMethod has encountered an OLE DB error code 0x80004005 (Client unable to establish connection...)
  5. When trying to run SSIS package from job: Executed as user: .\Administrator. The package could not be loaded. The step failed.
  6. All SSIS packages report an error upon opening:
    1. The description for Event ID '1073819649' in Source 'SQLISPackage' cannot be found
    2. SSIS An OLE DB error has occurred. Error code: 0x80040E4D (which was the result of it failing to remember my passwords when I typed them in after the previous error, I guess. Once I set the security to DoNoSaveSensitive and then saved it back to default of SaveWithUserKey it worked lol).
    3. There were errors while the package was being loaded.
      The package might be corrupted.
      See the Error List for details.
    4. The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.
      1. Of course I only have a single (default) instance of SQL 2005 on my machine
Unfortunately, due to so many errors and my being in a race to resolve them, I may have mixed one or two together in the list above.

Anyway, I have resolved 80% of the errors above but I still cannot connect up to my SSIS packages stored in msdb nor can I execute any jobs :(

And you know what is perhaps the most annoying part about this? When I go to Google, type in any one of the error messages/codes above and then click on almost any of the Microsoft links returned, it tries to force me to LOG OUT or CREATE ACCOUNT - there is no login page/link! It's either that or it returns results that require me to login on a different site to view the answer/post. Time for a new search engine?

I think this all stemmed from my not using the SQL Configuration Manager to change the passwords (instead, I used the Control Panel/Administrative Tools Services MMC snap-in). I know that I should use the Config Mgr but I didn't for whatever reason!

Labels: , , , , , ,


AddThis Social Bookmark Button

# posted by Scott Whigham @ 8:58 AM
Comments:
Well, I resolved it... I installed SP2 Beta (they technically call it a "CTP" but we all know it's a Beta) and everything worked.

I suspect that it was something to do with the SQL Native Client and maybe it was corrupt. I don't know - everything else connected fine...

Anyway, my suggestion to anyone who experiences this problem is to (1) grab your SQL installation media and reinstall the SQL Native Client and reboot. If that doesn't work, (2) install/reinstall the latest service pack.

Good luck - hope this helps someone!
# posted by Blogger Scott Whigham : 2:02 PM
 
Post a Comment

Links to this post:

Create a Link



<< Home

This page is powered by Blogger. Isn't yours?