AsiaTech: Microsoft APGC Internet Developer Support Team

We focus on various troubleshooting plan and solution on IIS web platform and distributed applications

How to troubleshoot the “Red Arrow” issue in Component Services (III)

How to troubleshoot the “Red Arrow” issue in Component Services (III)

  • Comments 2


This is an extra troubleshooting plan in additional to plan (I) and (II). Several days ago, I worked with one problematic Win2003 environment, there is no lucky after we go through all steps in plan (I) and (II). Although the COM+ clean reinstallation, registry keys permission, registration folder permission, and important services (COM+ Event System, COM+ System Application) are all okay, the "Red Arrow" icon still displayed in DCOMCNFG. And when expanding the "My Computer" node, the error always pup up:


"The server catalog version is not supported. The catalog is either newer or older than this application and a common version for communications does not exist."


After further investigation, figured out  that this is not caused by corrupted registration files in c:\windows\registration, but caused by registry keys corruption. We need to make sure below keys exist on the system first:















If any key missed please, register below DLLs  with regsvr32:

ole32.dll, oleaut32.dll, catsrv.dll, catsrvut.dll, comsvcs.dll

If still cannot generate them, please  try import they from a good machine:


Note: For keys under HKEY_LOCAL_MACHINE\Software\Classes\CLSID\,  there can be one random InprocServer32 value under in different system:


Please delete the InprocServer32 value after importing if they come from other system.


In my real case, customer system missed ProxyStubClsid and ProxyStubClsid32 under



After importing good keys from another good machine, the issue  finally got fixed.




Freist Li from APGC DSI Team





Leave a Comment
  • Please add 8 and 7 and type the answer here:
  • Post
  • Thank you, It's worked 100%

    I try to find and read many source no solution yet the problem still occur, your solution is very useful.

    Thanks again.

  • Absolutely spot on.

    After reading source after source with no solution, finally your solution worked perfectly.

    If you cannot resolve this issue with Windows Server 2008 R2 this one is a must.

    Thank you so much for your solution.

Page 1 of 1 (2 items)