Insufficent Permission on Receive Location
Luca Boni
The Messaging Engine failed to add a receive URL
"ChiocciolatoToXML_ReceiveLocation_SFERACARTA" to the adapter "FILE".
Reason: "File transport does not have read/write privileges for receive
location '\\TelXX\cambi\broker\dati\PTPOSTEL\ptunix\backup\'. ".
...in the path of the receive location the biztalk user service have Modify
permission. i tried to give FullControl to biztalk user service and the
receive location work properly!!!!
What is the optimal configuration ?
Tanks
____________________________________________
Luca Boni ( luca...@credemtel.it )
CREDEMTEL S.p.A. - Gruppo CREDEM
Via R. Livatino 9, 42100 Reggio Emilia (RE), ITALY
Tel. (+39) 0522 271540, Fax (+39) 0522 926414
Questa posta elettronica contiene informazioni di carattere confidenziale
rivolte esclusivamente al destinatario sopraindicato.
E' vietato l'uso, la diffusione, distribuzione o riproduzione da parte di
ogni altra persona. Nel caso aveste ricevuto questa
posta elettronica per errore, siete pregati di segnalarlo immediatamente al
mittente e distruggere quanto ricevuto senza farne copia.
Le informazioni contenute in questa posta elettronica che non si riferissero
alle attivita' specifiche di CREDEMTEL SPA devono
essere intese come non autorizzate e non approvate da parte della Societa'.
Qualsivoglia utilizzo non autorizzato del contenuto
di questo messaggio costituisce violazione dell'obbligo di non prendere
cognizione della corrispondenza tra altri soggetti,
salvo piu' grave illecito, ed espone il responsabile alle relative
conseguenze civili e penali.
Paw Pedersen
delete the file after receiveing it.
"Luca Boni" <lu...@credemtel.it> wrote in message
news:uZV06Bka...@TK2MSFTNGP10.phx.gbl...
Adrian Hamza[MSFT]
the directory where the file receive location picks up messages
It does NOT have to be Full Control since that implies permission to edit
the permission settings. Install latest documentation and SDK and search
for FILE permissions. Here's what I found:
"It is recommended that you set strong discretionary access control lists
(DACL) in the receive locations drop directories. For example, you must set
read, write, delete files, and delete subfolders and files permissions to
the directory where the file receive location picks up messages from, so
that only authorized users can drop messages in this location. "
"Microsoft BizTalk Server 2004 - Troubleshooting the File Adapter
See Also
File Adapter
This topic lists problems and their causes that you may encounter when
using the File adapter.
Receive Location is Disabled
The File receive adapter disables the receive location if any of following
occur:
The File receive adapter cannot access the receive location on the file
system or network share because the specified path does not exist. For a
network share, the File receive adapter disables the receive location after
all retry attempts have been exhausted.
The File receive adapter cannot access the receive location on the file
system or network share because it does not have read-write permission for
that location. For a network share, the File receive adapter disables the
receive location after all retry attempts have been exhausted.
Files with names longer than 256 characters are encountered in the receive
location.
Files Are Not Being Read
The File receive adapter does not read a file from the receive location if
any of the following conditions apply:
The file is read-only.
The file has a system attribute.
The File receive adapter does not have permissions to read and write to the
file.
When the File receive adapter encounters such a file, it logs an error in
the event log and leaves the file in the receive location.
Messages Are Not Being Sent
The File send adapter fails to send a message if any of the following
occurs:
The File send adapter cannot access the directory that files are sent from
on the file system or network share because the specified path does not
exist.
The File send adapter cannot write to a file in the destination location on
the file system or network share because it does not have write permissions
for that file or for that location.
The File send adapter cannot write to the file specified because it is
read-only or is a system file (for example, has a system file attribute).
If a message failed to be written to a file, the File send adapter reports
an error in the event log and submits a message to the MessageBox database
to perform following operations (in the order listed):
Deliver the message to the File send adapter later, so it can retry the
write operation.
Deliver the message to the backup adapter.
Route the message to the suspended queue.
Sending files to locations that require a user name and password
Problem: You need to drop files to a location that requires a user name and
password.
Cause: The File adapter does not support setting user names and passwords
in its configuration properties.
Resolution: Map a network drive to the location used by the Send port,
specify the user and password, and then use that network drive in the Send
port address.
Sending a file using the File adapter is very slow
Problem: The File adapter is very slow when sending messages.
Cause: The Allow cache on write property is set to False by default.
Resolution: Change the Allow cache on write property to True (check the
box). For more information about the Allow cache on write property, see
Configuring a File Send Port By Using BizTalk Explorer.
See Also
File Adapter
----------------------------------------------------------------------------
---
To download updated BizTalk Server 2004 Help from www.microsoft.com, go to
http://go.microsoft.com/fwlink/?linkid=20616.
Copyright © 2004 Microsoft Corporation.
All rights reserved."
--------------------
>>From: "Paw Pedersen" <ne...@paws.dk>
>>References: <uZV06Bka...@TK2MSFTNGP10.phx.gbl>
>>Subject: Re: Insufficent Permission on Receive Location
>>Date: Thu, 15 Jul 2004 10:06:20 +0200
>>Lines: 49
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.3790.181
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181
>>Message-ID: <uAHnTLka...@TK2MSFTNGP09.phx.gbl>
>>Newsgroups: microsoft.public.biztalk.general
>>NNTP-Posting-Host: cpe.atm2-0-7184.0x535a1b9a.vjnxx1.customer.tele.dk
83.90.27.154
>>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
>>Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:17333
>>X-Tomcat-NG: microsoft.public.biztalk.general
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team