|
Home > Archive > BizTalk Server Applications Integration > February 2004 > BizTalk Type Libraries Issues
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BizTalk Type Libraries Issues
|
|
|
| Hello
I want to develop and compile AIC code on my machine
which does not have BizTalk installed. I have copied
BTSCompLib type lib and generated DLL for it. Now I can
compile the code. But when I deploy the AIC DLL on the
production BizTalk machine it fails.
What do I do? Is there any specific way in which I need
to setup my development environment to develop and
compile and AIC code?
Regards
Aj
| |
| Nick Malik 2004-02-08, 8:41 am |
| You say that when you deploy it on the BTS machine, it fails. Could you
provide specifics of this failure? You may simply have problems with the
manner in which you are deploying it.
What language did you write you AIC in?
--- Nick
"Aj" <aj_mr@hotmail.com> wrote in message
news:078501c3d3c3$262de010$a001280a@phx.gbl...
> Hello
>
> I want to develop and compile AIC code on my machine
> which does not have BizTalk installed. I have copied
> BTSCompLib type lib and generated DLL for it. Now I can
> compile the code. But when I deploy the AIC DLL on the
> production BizTalk machine it fails.
>
> What do I do? Is there any specific way in which I need
> to setup my development environment to develop and
> compile and AIC code?
>
> Regards
>
> Aj
| |
| Aj M R 2004-02-08, 8:41 am |
| Hi Nick
Thanks for replying back. I compile the AIC component on
developer machine, then I deploy it/register it on
BizTalk server. It is when I deploy and try to initialize
it, when it gives me an error saying that the reference
is invalid? Think its reference path of BTSCompLib which
is different on developer machine?
My developer machine has those TLB installed under
c:\temp\
Let me see if I can get a detailed message to you.
Thanks again.
Regards
Aj
>-----Original Message-----
>You say that when you deploy it on the BTS machine, it
fails. Could you
>provide specifics of this failure? You may simply have
problems with the
>manner in which you are deploying it.
>
>What language did you write you AIC in?
>
>--- Nick
>
>"Aj" <aj_mr@hotmail.com> wrote in message
>news:078501c3d3c3$262de010$a001280a@phx.gbl...
>
>
>.
>
| |
|
| Also, I have written AIC in VB.Net and BizTalk is 2002.
Aj
>-----Original Message-----
>You say that when you deploy it on the BTS machine, it
fails. Could you
>provide specifics of this failure? You may simply have
problems with the
>manner in which you are deploying it.
>
>What language did you write you AIC in?
>
>--- Nick
>
>"Aj" <aj_mr@hotmail.com> wrote in message
>news:078501c3d3c3$262de010$a001280a@phx.gbl...
>
>
>.
>
| |
| Suneeti 2004-02-08, 8:41 am |
| Hi Nick,
This is with reference to message earlier message posted.
I am providing with the actual steps that are followed and
the error specific that we get:
I have created a VB.NET AIC component by implementing the
IBTSAppIntegration interface. Once the AIC code is written
we are adding reference to BTSComponentsLib.dll file. This
file has been created by running the Visual Studio
tool 'tlbimp' on the btscomplib.tlb type library provided
with BizTalk Server 2002.
After adding a reference to this file and other Dlls that
the AIC refer we compile and build the DLL. The Dll is
built sucessfully
But when I deploy this AIC dll on the production machine
which has BizTalk Server 2002 installed on it, it fails.
The steps that we have followed on the production machine
are :
1. The AIC project folder with the bin folder is copied on
the production machine.
2. The AIC DLL is then registered on the production
machine with the "regasm /tlb " tool option, which
registers the DLL correctly with a message 'Types
registered sucessfully'.
3. Then this component is added as a COM+ component by
adding the AIC .tlb file generated as a result of step 2
above. Doing this lists out the AIC as a primary transport
AIC while configuring the port.
4. Then through BizTalk Messaging Manager we start with
configuring Messaging Ports.
5. While configuring messaging port and assigning the
Primary transport we can just see the VB.NET AIC fine, but
when i click on the Finish button I am getting an error :
The messaging port cannot be saved.
Error 0xC0C0128E: Either the syntax of this address is
incorrect for the Application Integration Component
transport type property, or the
component is not registered, or else the component is not
a valid AIC component.
Is there any specific point that I am missing out for .NET
AIC registration on the production machine?
Regards,
Suneeti
>-----Original Message-----
>You say that when you deploy it on the BTS machine, it
fails. Could you
>provide specifics of this failure? You may simply have
problems with the
>manner in which you are deploying it.
>
>What language did you write you AIC in?
>
>--- Nick
>
>"Aj" <aj_mr@hotmail.com> wrote in message
>news:078501c3d3c3$262de010$a001280a@phx.gbl...
>
>
>.
>
| |
| Suneeti 2004-02-08, 8:41 am |
| Hi Nick,
This is with respect the earlier message error
details.Below mentioned are the actual steps that we have
carried out and the error that we are getting with its
details:
I have created a VB.NET AIC component by implementing the
IBTSAppIntegration interface. Once the AIC code is written
we are adding reference to BTSComponentsLib.dll file. This
file has been created by running the Visual Studio
tool 'tlbimp' on the btscomplib.tlb type library provided
with BizTalk Server 2002.
After adding a reference to this file and other Dlls that
the AIC refer we compile and build the DLL. The Dll is
built sucessfully.
But when I deploy this AIC dll on the production machine
which has BizTalk Server 2002 installed on it, it fails.
The steps that we have followed on the production machine
are :
1. The AIC project folder with the bin folder is copied on
the production machine.
2. The AIC DLL is then registered on the production
machine with the "regasm /tlb " tool option, which
registers the DLL correctly with a message 'Types
registered sucessfully'.
3. Then this component is added as a COM+ component by
adding the AIC .tlb file generated as a result of step 2
above. Doing this lists out the AIC as a primary transport
AIC while configuring the port.
4. Then through BizTalk Messaging Manager we start with
configuring Messaging Ports.
5. While configuring messaging port and assigning the
Primary transport we can just see the VB.NET AIC fine, but
when i click on the Finish button I am getting an error :
The messaging port cannot be saved.
Error 0xC0C0128E: Either the syntax of this address is
incorrect for the Application Integration Component
transport type property, or the
component is not registered, or else the component is not
a valid AIC component.
Is there any specific point that I am missing out for .NET
AIC registration?
Regards,
Suneeti
>-----Original Message-----
>Also, I have written AIC in VB.Net and BizTalk is 2002.
>Aj
>fails. Could you
>problems with the
>.
>
| |
| Nick Malik 2004-02-08, 8:41 am |
| Hello Suneeti,
I haven't tried to develop AIC components without the benefit of having
Biztalk actually installed on the development machine, so I'm not able to
reproduce your problem (I am not affiliated with Microsoft... I don't have
their resources). Are you aware that the cost of a developer's edition is
only $500? To be honest, you may be able to install the 120 day trial and
have it work just fine for what you are doing.
I did a little digging and found another thread from December on another
forum, where the following suggestion was made:
>-------------
The solution for this problem is to register your component and
then go into the Component Services tool, select your COM+ object and
view the Security Tab in the properties window. Uncheck
the "Enforce Access Checks" option and then hit 'OK'. This
should solve your problem and make it possible for you to use the AIC.
------------<
If the suggestion above does work for you, you should add the following
attribute to your AssemblyInfo file.
[assembly: ApplicationAccessControl(false)]
(sorry for the C# format)
Another suggestion I have: have you tried to install the Biztalk Toolkit for
..NET? If not, I'd recommend that you try it. I have not attempted to
install this free download sdk on a machine that did not have BTS on it, so
I do not know if it will have a problem.
Note: if you do decide to install the Biztalk Toolkit for .NET, you need to
do a few extra steps after installing it to make it work with .NET Framework
1.1. Let me know if you want to follow this course, and I will post the
extra steps.
--- Nick
"Suneeti" <suneeti@hotmail.com> wrote in message
news:03d101c3d8de$4ee07ca0$a301280a@phx.gbl...[color=blue]
> Hi Nick,
>
> This is with respect the earlier message error
> details.Below mentioned are the actual steps that we have
> carried out and the error that we are getting with its
> details:
>
> I have created a VB.NET AIC component by implementing the
> IBTSAppIntegration interface. Once the AIC code is written
> we are adding reference to BTSComponentsLib.dll file. This
> file has been created by running the Visual Studio
> tool 'tlbimp' on the btscomplib.tlb type library provided
> with BizTalk Server 2002.
> After adding a reference to this file and other Dlls that
> the AIC refer we compile and build the DLL. The Dll is
> built sucessfully.
> But when I deploy this AIC dll on the production machine
> which has BizTalk Server 2002 installed on it, it fails.
>
> The steps that we have followed on the production machine
> are :
>
> 1. The AIC project folder with the bin folder is copied on
> the production machine.
> 2. The AIC DLL is then registered on the production
> machine with the "regasm /tlb " tool option, which
> registers the DLL correctly with a message 'Types
> registered sucessfully'.
> 3. Then this component is added as a COM+ component by
> adding the AIC .tlb file generated as a result of step 2
> above. Doing this lists out the AIC as a primary transport
> AIC while configuring the port.
> 4. Then through BizTalk Messaging Manager we start with
> configuring Messaging Ports.
> 5. While configuring messaging port and assigning the
> Primary transport we can just see the VB.NET AIC fine, but
> when i click on the Finish button I am getting an error :
>
> The messaging port cannot be saved.
>
> Error 0xC0C0128E: Either the syntax of this address is
> incorrect for the Application Integration Component
> transport type property, or the
> component is not registered, or else the component is not
> a valid AIC component.
>
> Is there any specific point that I am missing out for .NET
> AIC registration?
>
> Regards,
> Suneeti
>
| |
| Suneeti 2004-02-08, 8:41 am |
| Hello Nick.
Thanks first of all for your reply. As per your suggestion
I tried the first approach suggested by you but that
didnot help.
Hence have downloaded the BizTalk Toolkit for .NET to
install it on the machine which does not have BizTalk
installed on it. However you have mentioned that I need to
perform some extra steps in order to get that working
with .NET v 1.1 . Can you please post those steps that
need to be performed.
- Suneeti
>-----Original Message-----
>Hello Suneeti,
>
>I haven't tried to develop AIC components without the
benefit of having
>Biztalk actually installed on the development machine, so
I'm not able to
>reproduce your problem (I am not affiliated with
Microsoft... I don't have
>their resources). Are you aware that the cost of a
developer's edition is
>only $500? To be honest, you may be able to install the
120 day trial and
>have it work just fine for what you are doing.
>
>I did a little digging and found another thread from
December on another
>forum, where the following suggestion was made:
>The solution for this problem is to register your
component and
>then go into the Component Services tool, select your
COM+ object and
>view the Security Tab in the properties window. Uncheck
>the "Enforce Access Checks" option and then hit 'OK'. This
>should solve your problem and make it possible for you to
use the AIC.
>------------<
>
>If the suggestion above does work for you, you should add
the following
>attribute to your AssemblyInfo file.
>[assembly: ApplicationAccessControl(false)]
>(sorry for the C# format)
>
>Another suggestion I have: have you tried to install the
Biztalk Toolkit for
>..NET? If not, I'd recommend that you try it. I have
not attempted to
>install this free download sdk on a machine that did not
have BTS on it, so
>I do not know if it will have a problem.
>
>Note: if you do decide to install the Biztalk Toolkit
for .NET, you need to
>do a few extra steps after installing it to make it work
with .NET Framework
>1.1. Let me know if you want to follow this course, and
I will post the
>extra steps.
>
>--- Nick
>
>"Suneeti" <suneeti@hotmail.com> wrote in message
>news:03d101c3d8de$4ee07ca0$a301280a@phx.gbl...
have[color=blue]
the[color=blue]
written[color=blue]
This[color=blue]
provided[color=blue]
that[color=blue]
machine[color=blue]
on[color=blue]
transport[color=blue]
but[color=blue]
error :[color=blue]
not[color=blue]
for .NET[color=blue]
have[color=blue]
can[color=blue]
the[color=blue]
need[color=blue]
>
>
>.
>
| |
| Nick Malik 2004-02-08, 8:41 am |
| I have these extensively documented at my desk. I'm doing this from
memory...
Basically, you install the toolkit as you'd expect. Then you change
directories to /Program Files/Microsoft Biztalk for .NET Toolkit
If you were using framework 1.0, you'd type: "setup" at the command line and
a .CMD script would register the components in the GAC.
To make this work on machines that did not have the SDK, the toolkit comes
with TWO copies of GACUTIL from the 1.0 framework.
This is what prevents it from working on the 1.1 framework.
You have to do three things:
1) Install the .NET Framework SDK on the same machine. (It's a developer
machine... you need regsvcs and gacutil and some others).
2) edit the CMD script before you run it. Change the directory (I think it
is the third line of the file) where the Framework is installed.
3) before you run the script, scan through the subdirectories under
"/Program Files/Biztalk .NET Toolkit" and find the two extra copies of
GACUTIL. Rename them from .EXE to .SAV or delete them altogether. They are
obstacles.
Now, run the cmd script. This will install the components needed for the
framework to work.
This will give you the ability to write your AIC, and in fact, you get some
really good examples of AICs in both VB.NET and C#.
Hope this helps,
--- Nick
"Suneeti" <anonymous@discussions.microsoft.com> wrote in message
news:085801c3d9c7$a4917020$a601280a@phx.gbl...[color=blue]
> Hello Nick.
>
> Thanks first of all for your reply. As per your suggestion
> I tried the first approach suggested by you but that
> didnot help.
> Hence have downloaded the BizTalk Toolkit for .NET to
> install it on the machine which does not have BizTalk
> installed on it. However you have mentioned that I need to
> perform some extra steps in order to get that working
> with .NET v 1.1 . Can you please post those steps that
> need to be performed.
>
> - Suneeti
>
> benefit of having
> I'm not able to
> Microsoft... I don't have
> developer's edition is
> 120 day trial and
> December on another
> component and
> COM+ object and
> use the AIC.
> the following
> Biztalk Toolkit for
> not attempted to
> have BTS on it, so
> for .NET, you need to
> with .NET Framework
> I will post the
> have
> the
> written
> This
> provided
> that
> machine
> on
> transport
> but
> error :
> not
> for .NET
> have
> can
> the
> need
|
|
|
|
|