MTS components registry entries were corrupted...

[CarlosArturo]

Hi,

I am creating and using a COM component that resides in MTS and that components registry entries were corrupted. The following message is shown by Event Viewer:

A server process failed during initialization. The most common cause is an invalid command line, which may indicate an inconsistent or corrupted catalog. This error caused the process to terminate. GetCLSIDsForPackage (Microsoft Transaction Server Internals Information: File: d:\viper\src\runtime\mtxex\cpackage.cpp, Line: 345)

I aready tried this:

1)In MTS
- Shut Down Server Process
- Stop MSDTC
2) Shut down the IIS Admin Service
3) Re Register COM DLL's
4) In MTS
- Refresh all components.
- Start MSDTC

Does anyone know a different solution?

I would appreciate any help...

Thanks,
Carlos

 

[nomi2000]

Yes it seems that you have done something with your components registrations but what you could do the following steps
1) Shut Down the IIS Admin Service
2) Re-Register the DLL’s either by compiling them or register using RegSvr32
3) Delete the Package which contains the COM DLL’s
4) Make a new “Empty Package” and Add the new compiled DLL’s into it
Run the application again see if it works…
What I see in some cases that Refreshing the components actually doesn’t refresh the components.
I hope it will help you
Regards
Nouman

 

[CarlosArturo]

Hi Nouman,

Unfortunately, it didn't work. Any other thought?

Thanks,
Carlos

 

[nomi2000]

Hi Carlos
oops okay carlso give me the environment plus how u r calling the compoents
mean r u using win2k server and win2k prof for clients? r u getting this error on server during design or run-time ?
have u checked whether the same error occurs for other server?
okay let me know
i hope it will help you
Regards
Nouman

 

[CarlosArturo]

Hi Nouman,

I am using WinNT 4 on the server as well as on the client machines.

I am getting the error on the server during run-time.

As for the others servers, yes I tested the components on a different server but they worked fine.

This is the Event Log info:

Event ID: 4131
Source: Transaction Server
Type: Error
Category: Executive


Please let me know if you need more details...

Thank you,
Carlos

 

[nomi2000]

It means that component services at that particular server are not behaving correctly hmmm but are the components running on different server have same WINNT 4 installed as the conflicting server, I mean does they have SERVICE PACK of WIN NT installed or SERVICE PACK of MTS?
As a last resort u could install Component Service (MTS) again on that server.
You see I honestly didn’t get this error for my MTS or COM+ life but still above are the hints which can help you in solving the prob.
Regards
Nouman

 

[CarlosArturo]

Hi Nouman,

The Web Administrator decided to reinstall the Web And the Transaction severs to fix this problem.

Fortunately everyrhing is working fine now.

Thanks for your help,
Carlos