CREATE BLOG dbo.SqlServer

For two weeks in a row, Windows Update has told me that I need to patch my SQL Server 2005 SP2 installation - with a lower build number than I currently have! I have build 3159 (click here for an explanation of the SP2 silliness) and yet Windows Update tells me that I should let it install build 3150. When it popped up two weeks ago, I told it to not install and to not notify me again of this patch but, hey! Whaddayaknow? It popped up again today asking me to install it. I think that, since it was Tuesday, it felt the need to do *something*...

Oh hell - just as I started trying to find the link to 3159, i noticed that a new hotfix is out dated two days ago: build 3161. It is really annoying at how they have been forced to throw out so many hotfixes post-SP2. Oh well - do you think they've learned their lesson so that we won't have this problem again? No? Me either... We went through this with Service Pack 2 for SQL Server 2000 as well you may remember if you've been around SQL Server for more than a few years.

Anyway, back on topic...

Here's a few helpful links to help you wade through the myriad of hotfixes and keep up-to-date:

• Aaron Bertrand has a comprehensive list going of all the hotfixes here
• SQL Server 2005 Service Pack 2 (SP2) Re-release and post fixes explained

Labels: sql, sql server, sql server 2005, sql server 2005 sp2

Want to download the latest CTP of SQL Server 2008 (nee SQL Server "Katmai")? I just did :)

If you want to download this first beta of SQL 2008, check it out here: https://connect.microsoft.com/SQLServer/content/content.aspx?ContentID=5395

It takes a good deal of logic problem solving to figure out this website but, once you do, you're in!

Labels: sql, sql server, sql server 2008

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: dts, integration services, sql, sql 2005, sql server, sql server 2005, ssis