SQL Distributed Transaction fired by a COM+ not working

If you have some COM+ object that connects to SQL Server and opens a transaction, sometimes it stops working at all, you may be facing a COM+ Corrupted Database, to “repair” this database you must follow the following steps:

 

  1. Find the file %WinDir%\System32\Clbcatq.dll and rename it to ~Clbcatq.dll
  2. Reboot the computer in Recovery Mode.
  3. Open the Registry and delete the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3.
  4. Find in the %WinDir% directory and look for a subdirectory named Registration. Delete Registration folder.
  5. Reboot the machine normally.
  6. Open Control Panel | Add/Remove Programs | Add/Remove Windows Components.
  7. Click Next to reinstall COM+.
  8. Now your transactions should work

 

Regards,

 

Ing. Eduardo Castro Martínez, PhD – Microsoft SQL Server MVP

http://mswindowscr.org

http://comunidadwindows.org

Costa Rica

Technorati Tags: SQL Server

LiveJournal Tags: SQL Server

del.icio.us Tags: SQL Server

http://ecastrom.blogspot.com

http://ecastrom.wordpress.com

http://ecastrom.spaces.live.com

http://universosql.blogspot.com

http://todosobresql.blogspot.com

http://todosobresqlserver.wordpress.com

http://mswindowscr.org/blogs/sql/default.aspx

http://citicr.org/blogs/noticias/default.aspx

http://sqlserverpedia.blogspot.com/




Note: Cross posted from Eduardo Castro.

Permalink

Comments

Popular posts from this blog

Desempeño de SQL Server 2008 R2 y Max Worker Threads

Cómo identificar consultas más pesadas en SQL Server

SQL Server La longitud de los datos LOB (2200100) que se van a replicar excede el máximo configurado 65536.