January 23, 2013 at 2:14 pm
This lovely error happens frequently when I need to add articles to my transactional replication setup. After making the changes needed to the publication, I start the Snapshot Agent (needed to replicate the new articles/changes over) an error RANDOMLY occurs with the CLR – and as far as I know, the only way this will be fixed is to restart the MSSQL service on Production
Message: Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80004005. You need to restart SQL Server to use CLR integration features.
Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80004005. You need to restart SQL Server to use CLR integration features.
Command Text: if object_id('sys.sp_replcleanupccsprocs') < 0 exec sp_replcleanupccsprocs @publication
Parameters: @publication = MyDB
Found an article from MS that pertains specifically to the error (my situation is #3) and it basically says to reinstall the .NET Framework 2.0 - Just lovely...as this happens to frequently occur on our busiest, most critical production server :crazy:
My question is: Does anyone know any way around this or am I SOL?
EDIT: Also wanted to ask if anyone knows of potential pitfalls/areas of concern with reinstalling this older .Net platform
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
February 26, 2013 at 7:41 pm
In trying MS's adive (re-installing the 2.0 framework), it won't allow me to do that - it errors out stating it's required and cannot be uninstalled - any suggestions?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
May 14, 2013 at 10:03 am
I'm getting this same error. Did you manage to figure it out? I was thinking of trying the steps here tonight after hours:
http://support.microsoft.com/kb/306160
The Redneck DBA
May 14, 2013 at 2:22 pm
Nothing seems to work other than a complete reboot of the server (unfortunately), and it returns randomly...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
May 14, 2013 at 2:33 pm
Interesting. Reinstalling .Net didn't fix it, but a reboot did? We must have a different version of the error...we tried a reboot last night and it didn't make a difference.
The Redneck DBA
May 14, 2013 at 2:38 pm
If you see my prior post, it won't allow you to uninstall and reinstall the framework unless you completely remove SQL Server and it's components...so i didn't go that route. I can't 100% remember right now but I believe just restarting the MSSQL service may have done the trick
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
May 14, 2013 at 3:04 pm
What edition, version and build are you guys on?
SELECT SERVERPROPERTY('ProductVersion') AS ProductVersion,
SERVERPROPERTY('Edition') AS Edition,
SERVERPROPERTY('ProductLevel') AS ProductLevel;
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
May 14, 2013 at 8:16 pm
Gah! After looking at my situation more, it turned out that there was a synonym involved that was actually pointing to an entirely different server when that SP was called. After bouncing the SQL service on that server everything started working again. Sheesh.
The Redneck DBA
May 15, 2013 at 2:00 am
sql.hopper (5/15/2013)
....
reported as link spam
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
May 15, 2013 at 10:14 am
At our shop the versions where this error randomly occurs are:
ProductVersionEditionProductLevel
10.0.4000.0 Enterprise Edition (64-bit)SP2
ProductVersionEditionProductLevel
10.0.5500.0 Enterprise Edition (64-bit)SP3
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply