Erland Sommarskog (7/29/2013)
The log you posted, disagrees with the output you posted from "SELECT @@version":Microsoft SQL Server 2005 - 9.00.5069.00 (Intel X86) Aug 22 2012 16:01:52 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
The log file you posted is something else:
2013-07-29 07:59:04.53 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
Maybe that's a local Express instance running on your local machine. (And to which you have not applied any service packs!).
I was of course interesting in the errorlog for the SQL Server where you have problem with running the CLR.
Oops, of course. I wasn't thinking and grabbed the log file off my laptop...
Here's the first 5 mins of the current log file on my server:
2013-07-14 05:50:55.54 Server Microsoft SQL Server 2005 - 9.00.5069.00 (Intel X86)
Aug 22 2012 16:01:52
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2013-07-14 05:50:55.62 Server (c) 2005 Microsoft Corporation.
2013-07-14 05:50:55.65 Server All rights reserved.
2013-07-14 05:50:55.67 Server Server process ID is 2936.
2013-07-14 05:50:55.70 Server Authentication mode is MIXED.
2013-07-14 05:50:55.71 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2013-07-14 05:50:55.78 Server This instance of SQL Server last reported using a process ID of 2940 at 7/14/2013 5:47:19 AM (local) 7/14/2013 9:47:19 AM (UTC). This is an informational message only; no user action is required.
2013-07-14 05:50:55.82 Server Registry startup parameters:
2013-07-14 05:50:55.84 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2013-07-14 05:50:55.85 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2013-07-14 05:50:55.85 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2013-07-14 05:50:56.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-07-14 05:50:56.65 Server Detected 16 CPUs. This is an informational message; no user action is required.
2013-07-14 05:50:58.01 Server Address Windowing Extensions is enabled. This is an informational message only; no user action is required.
If this is happening to any CLR module, maybe your DBA should try restarting SQL Server?
Indeed. We've restarted the server, but it doesn't fix the problem. Everything looks good, besides the fact that we can't use or install CLR functions.