|
Home > Archive > BizTalk Server Applications Integration > February 2004 > .Net AIC Submitting to Private Queue
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 |
.Net AIC Submitting to Private Queue
|
|
|
| Hello:
I have an AIC written in .Net. It implements
IBTSAppIntegration and ServicedComponent. The AIC is
supposed to submit a message to a private queue.
The AIC is signed with a strong name and I used regsvcs
to create a COM+ application. When I test the AIC
directly by calling the IBTSAppIntegration.ProcessMessage
on and instance of the AIC everything works fine and a
message is submitted in the private queue but when the
AIC is instantiated by a messaging port the message is
not submitted.
I know that the AIC is instantiated and is working up
until the last step of submitting the message because I
can see that it is performing other tasks.
Has anyone see this before? Are there any security
considerations? The COM+ app is a library and not a
server application so there is not identity to be set.
Thanks for your input.
Koka
| |
| Jan Eliasen 2004-02-08, 8:41 am |
| On Mon, 5 Jan 2004 07:24:07 -0800, "Koka"
<anonymous@discussions.microsoft.com> wrote:
Not knowing anything about MEssage Queuing, I guess that the user
running your AIC (COM+) does not have the rights to write to the
private queue?
Try control panel => Administrative Tools => Component Servies and
unfold until COM+-applications. Then rightclick on the appropriate
com+ application and change whoever is running it to someone who has
the correct rights. Or change the properties for the queue to allow
whoever is running the AIC to write to it.
>Hello:
>
>I have an AIC written in .Net. It implements
>IBTSAppIntegration and ServicedComponent. The AIC is
>supposed to submit a message to a private queue.
>
>The AIC is signed with a strong name and I used regsvcs
>to create a COM+ application. When I test the AIC
>directly by calling the IBTSAppIntegration.ProcessMessage
>on and instance of the AIC everything works fine and a
>message is submitted in the private queue but when the
>AIC is instantiated by a messaging port the message is
>not submitted.
>
>I know that the AIC is instantiated and is working up
>until the last step of submitting the message because I
>can see that it is performing other tasks.
>
>Has anyone see this before? Are there any security
>considerations? The COM+ app is a library and not a
>server application so there is not identity to be set.
>
>Thanks for your input.
>Koka
--
Jan Eliasen, representing himself and not the company he works for
| |
| Nick Malik 2004-02-08, 8:41 am |
| Hello Koka,
Jan is probably correct, you probably have Biztalk Messaging set to run
under the interactive user or the local system accounts, which may not have
the right to write to the queue.
I would add that you probably have another problem as well... It is quite
likely that MSMQ is raising an error and that your AIC is not catching it
and reporting it. Consider adding a mechanism to either write errors to a
file, a database, or the application log. Check out the
Microsoft.ApplicationBlocks.ExceptionManagement application block. I use it
in my AICs, and it works well.
HTH,
--- Nick
"Koka" <anonymous@discussions.microsoft.com> wrote in message
news:004501c3d39f$f5b9c840$a101280a@phx.gbl...
> Hello:
>
> I have an AIC written in .Net. It implements
> IBTSAppIntegration and ServicedComponent. The AIC is
> supposed to submit a message to a private queue.
>
> The AIC is signed with a strong name and I used regsvcs
> to create a COM+ application. When I test the AIC
> directly by calling the IBTSAppIntegration.ProcessMessage
> on and instance of the AIC everything works fine and a
> message is submitted in the private queue but when the
> AIC is instantiated by a messaging port the message is
> not submitted.
>
> I know that the AIC is instantiated and is working up
> until the last step of submitting the message because I
> can see that it is performing other tasks.
>
> Has anyone see this before? Are there any security
> considerations? The COM+ app is a library and not a
> server application so there is not identity to be set.
>
> Thanks for your input.
> Koka
>
|
|
|
|
|