BizTalk Server Applications Integration - AIC won't register in Production machine

Author

AIC won't register in Production machine

James Lange

2005-01-28, 5:49 pm

Hi

I've recently done some maintenance work on an AIC for BT 2002 written in C#
(.NET 1.1)

While testing it I registered the component with COM+ using regsvcs and all
went well.

I've now moved the same code to the production machine along with the
BTSComponentsLib.dll

When I run the regsvcs command utility I get error relating to my component
not extending ServicedComponents (which it does) and a generate type libaray
exception.

When I try again moving the component to the dev machine, it registers
without a problem.

Can anyone point me to if the problem is with the .NET framework or any
other suggestions would be helpful

Thanks in advance

Tomas Restrepo \(MVP\)

2005-01-28, 8:46 pm

James,

> I've recently done some maintenance work on an AIC for BT 2002 written in
C#
> (.NET 1.1)
>
> While testing it I registered the component with COM+ using regsvcs and
all
> went well.
>
> I've now moved the same code to the production machine along with the
> BTSComponentsLib.dll
>
> When I run the regsvcs command utility I get error relating to my
component
> not extending ServicedComponents (which it does) and a generate type
libaray
> exception.
>
> When I try again moving the component to the dev machine, it registers
> without a problem.
>
> Can anyone point me to if the problem is with the .NET framework or any
> other suggestions would be helpful

Sounds like the server has a different .net framework version (possibly
1.0?)

--
Tomas Restrepo
tomasr@mvps.org

James Lange

2005-01-31, 5:53 pm

Hi Tomas

The server as well as the development machine are running both versions of
the framework. 1.0 and 1.1.

The reason is:

The first messaging deployment used AIC's and pipelines that were writting
for .NET 1.0. Some of these, due to maintenance now run on 1.1. This
particular one was original written for 1.0 and is now being upgraded to 1.1
(along with other upgrades). I can confirm that I did use the version of
regsvcs that was installed in the 1.1 version folder...

Is there anything mentioned above that could help narrow down the problem?
Would repairing the installation of 1.1 help?

Many thanks

James

"Tomas Restrepo (MVP)" wrote:

> James,
>
> C#
> all
> component
> libaray
>
> Sounds like the server has a different .net framework version (possibly
> 1.0?)
>
> --
> Tomas Restrepo
> tomasr@mvps.org
>
>
>

Tomas Restrepo \(MVP\)

2005-01-31, 8:49 pm

Hi James,

> The server as well as the development machine are running both versions of
> the framework. 1.0 and 1.1.
>
> The reason is:
>
> The first messaging deployment used AIC's and pipelines that were writting
> for .NET 1.0. Some of these, due to maintenance now run on 1.1. This
> particular one was original written for 1.0 and is now being upgraded to
1.1
> (along with other upgrades). I can confirm that I did use the version of
> regsvcs that was installed in the 1.1 version folder...
>
> Is there anything mentioned above that could help narrow down the problem?
> Would repairing the installation of 1.1 help?

When you say the component you're registering is now being upgraded to 1.1,
I presume you mean you actually recompiled it using VS.NET 2003, right? If
so, no reason why it should fail registration at all.

I've seen this error happen plenty of times, and it could always be
attributed to somehow ending up registering it with the incorrect
regsvcs.exe version. If that doesn't work, then I'd try creating an MSI with
a custom action to register the component... that might work better...

--
Tomas Restrepo
tomasr@mvps.org

James Lange

2005-02-01, 5:59 pm

Hi

I tried the Installer... this also failed. Here is what I've tried recently
since my last post:

Assigned new GUID to the Application and Class. This failed.
Tested various command switches to try register.

The latest error I'm getting is that it is unable to install the type
library. What I've done now which seems to work is register it with Regasm,
then import an already registered component into the COM+ application.

However, I'm still curious to know why the proper method didn't want to
work...

Thanks for the help...

James

"Tomas Restrepo (MVP)" wrote:

> Hi James,
>
> 1.1
>
> When you say the component you're registering is now being upgraded to 1.1,
> I presume you mean you actually recompiled it using VS.NET 2003, right? If
> so, no reason why it should fail registration at all.
>
> I've seen this error happen plenty of times, and it could always be
> attributed to somehow ending up registering it with the incorrect
> regsvcs.exe version. If that doesn't work, then I'd try creating an MSI with
> a custom action to register the component... that might work better...
>
> --
> Tomas Restrepo
> tomasr@mvps.org
>
>
>

Tomas Restrepo \(MVP\)

2005-02-02, 2:50 am

Hi James,

> I tried the Installer... this also failed. Here is what I've tried
recently
> since my last post:
>
> Assigned new GUID to the Application and Class. This failed.
> Tested various command switches to try register.
>
> The latest error I'm getting is that it is unable to install the type
> library. What I've done now which seems to work is register it with
Regasm,
> then import an already registered component into the COM+ application.
>
> However, I'm still curious to know why the proper method didn't want to
> work...

Funky... I just saw this same problem today with the registration of the
TLB. FWIW, I was able to get past my problems by running regasm on
System.EnterpriseServices.dll again. Might work for you...

--
Tomas Restrepo
tomasr@mvps.org

James Lange

2005-02-02, 2:50 am

Cool...

Thanks for all the assistance with this.

Regards

James

"Tomas Restrepo (MVP)" wrote:

> Hi James,
>
> recently
> Regasm,
>
> Funky... I just saw this same problem today with the registration of the
> TLB. FWIW, I was able to get past my problems by running regasm on
> System.EnterpriseServices.dll again. Might work for you...
>
> --
> Tomas Restrepo
> tomasr@mvps.org
>
>
>