This project has moved and is read-only. For the latest updates, please go here.


Performing EndTypeChangeRequest for resource type "System.BizTalk:BizTalkAssembly".EXEC : error : Access to the path is denied.


I've been deploying this project for years but the last few releases I've been getting the above error. Sometimes it's after Gacing the Schema assembly but usually after Gacing the Maps assembly. Yesterday on my dev server it succeeded after the 3rd Redeploy. After 10 redeploy attempts on my QA server I gave up. I created an msi from the Admin console on my dev box with just the Map and Orchestration dll's and imported it successfully on the QA box. I used the bindings file that was generated during the failed BDF installation. I've attached the BDF Results files from the successful installation on the dev box and the last failed redeployment from the QA box. I didn't see how to attach multiple files so I combined them into 1 with the failure on top. Thanks.

file attachments

Closed Feb 15 at 6:58 PM by tfabraham
This is something for Microsoft Support since it's generated by BTSTask.exe.


tfabraham wrote Feb 14 at 5:09 PM

In this case, the error is from BizTalk's BTSTask.exe, not from the Deployment Framework:

BTSTask.exe AddResource -Type:BizTalkAssembly -Source:"..\xxx.Payroll.Tax.Maps.dll" -ApplicationName:"xxx.Payroll.Tax" -Options:GacOnAdd,GacOnImport,GacOnInstall

As a result, I'd expect BizTalk Admin to generate the same sort of error. You might find more information about this on the BizTalk MSDN/TechNet forums.

Did you ever find a resolution?

wrote Feb 14 at 5:10 PM

johnamuller wrote Feb 15 at 1:05 PM

No. My workaround is to create an msi from the Admin console on my Dev server, containing the dll's that weren't installed (Maps and Orchestrations). When we did the release it failed on the DR servers, so I imported the missing dll's and bindings from the Admin console, but the BDF install worked in Prod.

tfabraham wrote Feb 15 at 4:45 PM

Such an odd issue. I've seen it before, and you're not alone by any means. Seems like people rarely, if ever, find a cause because it always seems to affect only specific computers.

One person determined that a virus scanner was the cause, and got their admins to add scan exclusions on the folders that BizTalk touches. That was mentioned in another thread here.

There are mentions of similar issues on StackOverflow and blogs too.

You could use Process Monitor to trace what's happening when BTSTask.exe runs, and try to catch the Access Denied error to see what file or directory is involved. That's probably your best bet to find the root cause.

Are you OK if I close this issue? This is a BizTalk/Microsoft Support issue, not BTDF.


johnamuller wrote Feb 15 at 5:44 PM

I'll look at those links. Thanks for your time and a great application. You can close this.

wrote Feb 15 at 6:58 PM