To compound their gross mistake of not providing a public Release Candidate for SharePoint 2010, today I learned that Microsoft has made an even bigger mistake: skipping public beta and public Release Candidates for SQL Server 2008 R2. God help us all.
A few months back, I had to perform a partial rebuild of my MOSS 2007 SP1 environment. One of the steps was to build a new SSP using SharePoint Central Admin which in turn created a new SQL Server 2005 SP3 database for that new SSP. Everything has been working fine. The other day, I fired up SQL Server Management Studio and decided to explore the SQL Server Logs. Inside those logs I found endless occurrences of the following error message:
Login failed for user ‘mytestdomain\sqlserver’
The message was occurring every minute.
I searched the internet and found several references to various SQL Server Jobs that MOSS 2007 SP1 sets up under SQL Server Agent. One such job has a long title that ends with “DB_Job_DeleteExpiredSessions”. In my case, there were two of those jobs, one for the old, discontinued SSP and one for the new replacement SSP. When I right-clicked on the old job and chose View History, the same pattern of errors was visible that I had seen earlier in the SQL Server Logs. I disabled the scheduling of that job and the errors stopped.
Lesson learned: when you reconfigure your SharePoint SSP’s, don’t forget to check SQL Server Jobs associated with any SSP’s that you replaced or deleted to insure your SQL Server Logs aren’t filled with needless error messages about failed logins.
SharePoint depends on SQL Server 2005. Therefore, keeping SQL Server 2005 patched is something every developer should be aware of.
You may think putting Service Pack 3 (SP3) on is all you need to do to keep SQL Server 2005 up-to-date. Not true. To understand how/why Microsoft delivers fixes for SQL Server 2005, the support article that describes SQL Server Incremental Servicing Model is a “must read”, not just for DBA’s, but anybody who deals with SQL Server 2005, even indirectly (e.g., SharePoint administrator or SharePoint developer).
While I’m at it, visit The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released. In addition to information about the three releases of “post-SP3 cumulative update packages”, you’ll see the latest SQL Server 2005 internal numbering.
To see what version of SQL Server 2005 you are running, run the following query:
SET NOCOUNT ON;
SELECT serverproperty('Edition') [Edition],
WHEN 2 THEN 'Standard or Workgroup'
WHEN 3 THEN 'Enterprise, Enterprise Evaluation, or Developer'
WHEN 4 THEN 'Express, Express Edition with Advanced Services, or Windows Embedded SQL'
END [Engine Edition],
serverproperty('ProductVersion') [Product Version],
serverproperty('ProductLevel') [Product Level]
With just Service Pack 3 installed on my SharePoint development box, the output from the above command is:
Engine: Enterprise Edition
Engine Edition: Enterprise, Enterprise Evaluation, or Developer
Product Version: 9.00.4035.00
Product Level: SP3
The latest downloadable post-SP3 cumulative update package (#1) can be found here.