|
Home > Archive > BizTalk Server Applications Integration > February 2004 > AIC Problems with BizTalk server
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 |
AIC Problems with BizTalk server
|
|
| newsgroup user 2004-02-08, 8:42 am |
| I am writing a custom AIC for connecting my third part application to BizTalk. I tried two scenarios:
a. Create AIC using VB 6 and deploy it on 2002
b. Create AIC using VB .Net and deploy it again on 2002
But with every install of my new component the server stops responding and gets stuck. Even the stop and restart BizTalk server option doe snot work. When I restart the system, it complains that some DLL is not responding and then when I forcefully restar
t it works.
Do I need to restart server everyime? I have installed SP 1 and still having the same issues. Has anyone saw this problem? What is the resolution.
Regards
Aj
| |
| Nick Malik 2004-02-08, 8:42 am |
| stop using install scripts.
The biztalk components that you are referencing get uninstalled when you
uninstall your app.
To install your .NET component, copy the files to the Biztalk system,
register the com components that you are providing, and (if you are doing a
preprocessor) add the registration key to the registry.
That's it.
uninstall means unregistering the com components and dropping the registry
key.
I used to get the same problem continuously, to the point where Biztalk
would not work with an AIC at all unless I reinstalled SP1 (which
reregisters everything). I solved the problem by avoiding installation
programs.
Also, use VB.NET over VB6. The .net components are freethreaded, which
allows Biztalk to operate a maximum speed. VB6 is apartment threaded, which
makes Biztalk run apartment threaded as well, dropping your performance
dramatically.
Good luck,
--- Nick
Biztalk Bum
"Aj" <anonymous@discussions.microsoft.com> wrote in message
news:F08900B2-66B7-4C2E-96C0-52E3F32CC9B6@microsoft.com...
> I am writing a custom AIC for connecting my third part application to
BizTalk. I tried two scenarios:
> a. Create AIC using VB 6 and deploy it on 2002
> b. Create AIC using VB .Net and deploy it again on 2002
>
> But with every install of my new component the server stops responding and
gets stuck. Even the stop and restart BizTalk server option doe snot work.
When I restart the system, it complains that some DLL is not responding and
then when I forcefully restart it works.
>
> Do I need to restart server everyime? I have installed SP 1 and still
having the same issues. Has anyone saw this problem? What is the resolution.
>
> Regards
>
> Aj
| |
| Nick Malik 2004-02-08, 8:42 am |
| And one more bit of advice,
When you install or uninstall an AIC, you have to stop a series of services
before the operation, and then restart them after.
Stop MSMQ, IIS admin, W3SVC, XLANG, and Biztalk Messaging Manager
do your install
Then restart everything.
I don't remember the specific order, but when you issue the NET STOP
commands, it will tell you what needs what.
HTH,
--- Nick
"Aj" <anonymous@discussions.microsoft.com> wrote in message
news:F08900B2-66B7-4C2E-96C0-52E3F32CC9B6@microsoft.com...
> I am writing a custom AIC for connecting my third part application to
BizTalk. I tried two scenarios:
> a. Create AIC using VB 6 and deploy it on 2002
> b. Create AIC using VB .Net and deploy it again on 2002
>
> But with every install of my new component the server stops responding and
gets stuck. Even the stop and restart BizTalk server option doe snot work.
When I restart the system, it complains that some DLL is not responding and
then when I forcefully restart it works.
>
> Do I need to restart server everyime? I have installed SP 1 and still
having the same issues. Has anyone saw this problem? What is the resolution.
>
> Regards
>
> Aj
| |
| richard 2004-02-08, 8:42 am |
| Hi Nick,
There is a resolution for the problem you're seeing when creating Setup
projects for biztalk components.
For some reason visual studio sets the Register property of any interop
components identified as dependencies in a setup project in a to "vsdrfCOM"
by default. This causes the components to be registered with COM, which is
not necessary.
This results in the ClassIds for the biztalk interfaces in libraries such as
cisapi.tlb and BTSInterchange lib pointing to the .net CCW Interop
assemblies rather than the original libraries that ship with biztalk.
As a result, when the custom application is uninstalled, the CCW interop
libraries are removed which breaks biztalk as all the classids now point to
..net assemblies that have now been removed.
The solution is to change the configuration of the setup project so that the
interop type libs, dlls, etc are not registered for COM interop when they
are installed. This can be done from within visual studio by viewing the
properties for each of the "Detected Dependancies" of your setup project and
changing the value of the "Register" property to "vsdraDoNotRegister".
hope this helps
richard
"Nick Malik" <nickmalik@hotmail.nospam.com> wrote in message
news:CrCQb.115266$nt4.465504@attbi_s51...
> stop using install scripts.
>
> The biztalk components that you are referencing get uninstalled when you
> uninstall your app.
>
> To install your .NET component, copy the files to the Biztalk system,
> register the com components that you are providing, and (if you are doing
a
> preprocessor) add the registration key to the registry.
>
> That's it.
>
> uninstall means unregistering the com components and dropping the registry
> key.
>
> I used to get the same problem continuously, to the point where Biztalk
> would not work with an AIC at all unless I reinstalled SP1 (which
> reregisters everything). I solved the problem by avoiding installation
> programs.
>
> Also, use VB.NET over VB6. The .net components are freethreaded, which
> allows Biztalk to operate a maximum speed. VB6 is apartment threaded,
which
> makes Biztalk run apartment threaded as well, dropping your performance
> dramatically.
>
> Good luck,
> --- Nick
> Biztalk Bum
>
>
> "Aj" <anonymous@discussions.microsoft.com> wrote in message
> news:F08900B2-66B7-4C2E-96C0-52E3F32CC9B6@microsoft.com...
> BizTalk. I tried two scenarios:
and[color=blue]
> gets stuck. Even the stop and restart BizTalk server option doe snot work.
> When I restart the system, it complains that some DLL is not responding
and
> then when I forcefully restart it works.
> having the same issues. Has anyone saw this problem? What is the
resolution.
>
>
| |
| Sameer.Surve@ilg.com 2004-02-08, 8:42 am |
| I have encountered similar issues before.
Also start and restart COM+ service listed below:
1. BizTalk Server Interchange Application
2. XLANG Scheduler
This can be automated using a VB script listed below:
****************************************
**********************
Option Explicit
const XLANG_APPNAME = "XLANG Scheduler"
const BTS_INTERCHANGE_APPNAME = "BizTalk Server Interchange Application"
Dim catalog
Set catalog = CreateObject("COMAdmin.COMAdminCatalog")
catalog.ShutdownApplication XLANG_APPNAME
catalog.ShutdownApplication BTS_INTERCHANGE_APPNAME
WScript.Echo "BizTalk COM+ applications shut down successfully."
****************************************
*******************************
"Nick Malik" <nickmalik@hotmail.nospam.com> wrote in message news:<fjHQb.113974$5V2.564987@attbi_s53>...[color=blue]
> And one more bit of advice,
>
> When you install or uninstall an AIC, you have to stop a series of services
> before the operation, and then restart them after.
>
> Stop MSMQ, IIS admin, W3SVC, XLANG, and Biztalk Messaging Manager
>
> do your install
>
> Then restart everything.
>
> I don't remember the specific order, but when you issue the NET STOP
> commands, it will tell you what needs what.
>
> HTH,
> --- Nick
>
> "Aj" <anonymous@discussions.microsoft.com> wrote in message
> news:F08900B2-66B7-4C2E-96C0-52E3F32CC9B6@microsoft.com...
> BizTalk. I tried two scenarios:
> gets stuck. Even the stop and restart BizTalk server option doe snot work.
> When I restart the system, it complains that some DLL is not responding and
> then when I forcefully restart it works.
> having the same issues. Has anyone saw this problem? What is the resolution.
| |
| Nick Malik 2004-02-08, 8:42 am |
| Thank you Richard,
That was the best explaination I've ever seen for this issue, and I
appreciate you letting me know about the solution.
Thanks
-- Nick
"richard" <reply@tonewsgroup.com> wrote in message
news:OxibiXM5DHA.2736@TK2MSFTNGP09.phx.gbl...
> Hi Nick,
>
> There is a resolution for the problem you're seeing when creating Setup
> projects for biztalk components.
>
> For some reason visual studio sets the Register property of any interop
> components identified as dependencies in a setup project in a to
"vsdrfCOM"
> by default. This causes the components to be registered with COM, which is
> not necessary.
>
> This results in the ClassIds for the biztalk interfaces in libraries such
as
> cisapi.tlb and BTSInterchange lib pointing to the .net CCW Interop
> assemblies rather than the original libraries that ship with biztalk.
>
> As a result, when the custom application is uninstalled, the CCW interop
> libraries are removed which breaks biztalk as all the classids now point
to
> .net assemblies that have now been removed.
>
> The solution is to change the configuration of the setup project so that
the
> interop type libs, dlls, etc are not registered for COM interop when they
> are installed. This can be done from within visual studio by viewing the
> properties for each of the "Detected Dependancies" of your setup project
and
> changing the value of the "Register" property to "vsdraDoNotRegister".
>
> hope this helps
> richard
>
>
>
> "Nick Malik" <nickmalik@hotmail.nospam.com> wrote in message
> news:CrCQb.115266$nt4.465504@attbi_s51...
doing[color=blue]
> a
registry[color=blue]
> which
> and
work.[color=blue]
> and
> resolution.
>
>
|
|
|
|
|