Neil Thompson

BizTalk | .NET | SQL |

  Home  |   Contact  |   Syndication    |   Login
  15 Posts | 20 Stories | 56 Comments | 55 Trackbacks

News

Article Categories

Archives

Post Categories

Fav BizTalk Blogs

My team has answered the following problem many times, it seems to be a very common mistake. The problem is that the account that the biztalk host is running under (usually BtsInstanceHost) does not have enough permissions on the directories acting as the send/receive locations for the file adapter.  The fix is to grant the Biztalk host account “Full access“ to those folders (modify might not be enough for some strange reason)

I recommend having one directory (i.e. d:\BtsFileEndPoints) that contains all file send/recieve locations. That way you can configure the permissions once, and never have to worry about it again.

Event Type:       Error
Event Source:    BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID:           5644
Date:                <date>
Time:                <time>
User:                N/A
Computer:         <computer name>
Description:
The Messaging Engine failed to add a receive URL "ReceiveLoc1" to the adapter "FILE". Reason: "File transport does not have read/write privileges for receive location 'C:\PickUp\'. ".

  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati
posted on Monday, April 17, 2006 10:38 AM

Feedback

# re: File locations fail 2/19/2007 4:00 AM Rafik
Hi Neil, I am still getting this error though i have given full control access on the folder to the user which is associated with host instance. The folder is in local, i shared and gave permission to the host inst user. But i am testing this through remote access logged by a admin user. Help is appreciated.

Regards.

# re: File locations fail (More info) 2/19/2007 4:01 AM Rafik
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 7183
Date: 2/19/2007
Time: 12:55:51 PM
User: N/A
Computer: SERVER1
Description:
File transport does not have read/write privileges for receive location "\\server1\Filedrop\ReceiveRequest\".



# re: File locations fail 2/19/2007 8:57 AM nsthompson
Rafik

I can see from your error message that you are binding to the file location through the share, here are two fixes, each of which should work on their own.

1. Make sure that the SHARE permissions (as well as the file permissions) grant full access to the hostinstance account
2. OR you could bind to the file location locally (i.e. C:\FileDrop\ReceveRequest) just change this to point to your actual file.

Either of these should work if the info you have given me is correct.

If this works please let me know

# re: File locations fail 1/13/2010 11:43 PM Mikhail
Thx, full access solve the problem.

Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification: