|
Home > Archive > BizTalk Server > December 2004 > Messaging Engine receive error
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 |
Messaging Engine receive error
|
|
| Rudolf 2004-12-28, 2:46 am |
| I have set up a file receive function in a proof of concept environment that
is suppose to pick up plain flat text files. The account under which the
'BizTalk Server Application Service' service run has full read/write
permissions on the file share the files must be picked up. However, we still
receive the following errors:
The Messaging Engine failed to add a receive URL "POCTestReceiveLocation" to
the adapter "FILE". Reason: "File transport does not have read/write
privileges for receive location '\\odcfileshareqa\QA\Data\BizTalk\receiv
e\'.
".
We have checked that both share level and ntfs level permissions are
correct. The file share is on another machine. The BizTalk 2004 setup is a
dual machine setup both running under the same domain service account.
What else can we check that might cause the error?
Thanks
| |
| Rudolf 2004-12-28, 7:49 am |
| Just an update,
We change the permissions on the share to give 'Full' rights oppose to only
read/write and that seems to work. This however is not 1st price for the
network admins that like giving only absolute minimum permisions required.
Rudolf
"Rudolf" wrote:
> I have set up a file receive function in a proof of concept environment that
> is suppose to pick up plain flat text files. The account under which the
> 'BizTalk Server Application Service' service run has full read/write
> permissions on the file share the files must be picked up. However, we still
> receive the following errors:
>
> The Messaging Engine failed to add a receive URL "POCTestReceiveLocation" to
> the adapter "FILE". Reason: "File transport does not have read/write
> privileges for receive location '\\odcfileshareqa\QA\Data\BizTalk\receiv
e'.
> ".
>
> We have checked that both share level and ntfs level permissions are
> correct. The file share is on another machine. The BizTalk 2004 setup is a
> dual machine setup both running under the same domain service account.
>
> What else can we check that might cause the error?
>
> Thanks
| |
| Matt Milner 2004-12-28, 5:49 pm |
| Biztalk needs to be able to read/write and delete from that directory. I'm
not 100% on the permissions that it requires from an NTFS or share
perspective, but generally giving full permissions is what solves the
problems. You can try to play around with the permissions a little to not
give it full writes, but with what it needs, it'll be pretty close anyway.
Matt
"Rudolf" <Rudolf@discussions.microsoft.com> wrote in message
news:750B56CD-18FA-4267-8087-0F2F99917D2B@microsoft.com...[vbcol=seagreen]
> Just an update,
>
> We change the permissions on the share to give 'Full' rights oppose to
> only
> read/write and that seems to work. This however is not 1st price for the
> network admins that like giving only absolute minimum permisions required.
>
> Rudolf
>
> "Rudolf" wrote:
>
| |
| Rudolf 2004-12-29, 7:49 am |
| Thanks
"Matt Milner" wrote:
> Biztalk needs to be able to read/write and delete from that directory. I'm
> not 100% on the permissions that it requires from an NTFS or share
> perspective, but generally giving full permissions is what solves the
> problems. You can try to play around with the permissions a little to not
> give it full writes, but with what it needs, it'll be pretty close anyway.
>
> Matt
>
>
> "Rudolf" <Rudolf@discussions.microsoft.com> wrote in message
> news:750B56CD-18FA-4267-8087-0F2F99917D2B@microsoft.com...
>
>
>
|
|
|
|
|