In the spirit of documenting all possible and imaginary errors, let’s address a classic one today: File transport does not have read/write privileges on the receive location DRIVE:\FOLDER NAME.
This happens more than you may think, and today, after finishing creating a backup port for testing a new process, while I was trying to enable the File receive location, I got the following errors:
File transport does not have read/write privileges for receive location “C:\BizTalkPorts\IN_POLLING\”.
Followed by other similar warning messages:
The Messaging Engine failed to add a receive location “POLLING_FILE” with URL “C:\BizTalkPorts\IN_POLLING\*.xml” to the adapter “FILE”. Reason: “File transport does not have read/write privileges for receive location “C:\BizTalkPorts\IN_POLLING\”. “.
The receive location “POLLING_FILE” with URL “C:\BizTalkPorts\IN_POLLING\*.xml” is shutting down. Details:”The Messaging Engine failed while notifying an adapter of its configuration. “.
📝 One-Minute Brief
A troubleshooting guide explaining why the BizTalk File Adapter fails with a read/write privileges error on a receive location and how to fix folder permissions for BizTalk host instance service accounts.
Cause
As I said before, this is a classic error; the reason is quite obvious, and the error message clearly identifies the origin of the problem.
The problem is that the user who is running the BizTalk Server host instance(s) doesn’t have read/write privileges in that specific folder.
Solution
To solve this problem, you need to grant read/write privileges to the user running the BizTalk Server Host Instance (in my case, BTSHostSrvc) on that specific folder. For that, you need to:
- From the file system, access to the folder in question, and then right-click on the folder and select the Properties option.
- If the attribute Read-only (only applies to files in folder) is enabled (selected), disable it (unselect).
- Then go to the Security tab, and then click the Edit… button, and then the Add… button.
- Search for the user that is running the BizTalk Server Host Instance and then click OK.
- For that specific user, give read and write access.
- In my case, because this was/is a BizTalk process folder, I gave Full control.
- Click OK and OK once again.
Once you give access to the user, this classic problem is going away… until the next time!
Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son.
Just thought I’d add that Read/Write actually isn’t enough for a Receive Location. Since the File Adapter removes the file after reading, it also needs “delete” permissions (found under “special permissions”). “Modify” is not enough either… only “full” or manually adding “delete” permissions will do. Don’t know how many times this has bitten me… 🙂
Thanks for a great resource Sandro, please keep it up!
Thanks Martin! You comment solved it for me. My admin was just giving read and write, but no special permissions, and that was not enough 🙂 Thanks!