BizTalk Pipeline component – Unable to copy file “…\Pipeline Components\MyPipelineComponent.dll” to “bin\Debug\ MyPipelineComponent.dll”. The process cannot access the file “bin\Debug\ MyPipelineComponent.dll” because it is being used by another process

Posted: January 18, 2011  |  Categories: BizTalk Pipelines

When building BizTalk Project it gives the following error:

Unable to copy file “…\Pipeline Components\MyPipelineComponent.dll” to “bin\Debug\ MyPipelineComponent.dll”. The process cannot access the file “bin\Debug\ MyPipelineComponent.dll” because it is being used by another process

More details in MSDN Forum, Thread Title: custom pipeline error

In the past I posted an article regarding a similar problem:

Cause

  • Visual Studio has a lock on the file in order to show the pipeline components in the toolbox.

Or

  • Some BizTalk process is running BizTalk host and have a lock on the file

These two errors have basically the same solution, and to solve them, you can try two approaches:

Solution 1

  • Close Visual Studio and restart host instance to make sure the pipeline component DLL gets released.
  • And then deploy pipeline component.

Solution 2

  • Rename the file (it is much faster).
  • Restart host instance
  • Deploy pipeline component
  • And then delete old DLL’s
Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

7 thoughts on “BizTalk Pipeline component – Unable to copy file “…\Pipeline Components\MyPipelineComponent.dll” to “bin\Debug\ MyPipelineComponent.dll”. The process cannot access the file “bin\Debug\ MyPipelineComponent.dll” because it is being used by another process”

    1. I know your frustration. This error may be a little annoyed but it not exactly a BizTalk error. This type of error can happen even when developing C # projects.

      I’m developing BizTalk projects about 7 years and I just had this problem maybe 5 times 🙂

      1. Hi Sandro,
        I am getting this issue on the UAT environment, we are ending up by rebooting the server. Can you please advice if it can be resolve without Rebooting the server.
        Cheers!!!

        1. Hy Shadab,

          This problem may occur if:
          – Visual Studio has a lock on the file (you should close all VS windows) – but this option doesn’t apply to your situation
          – Some BizTalk process is running BizTalk host and have a lock on the file;
          – or if the process is associated with BizTalk Isolated host then the IIS AppPool has a lock on the file.

          So my advice is restart BizTalk Host Instances, restart IIS (or recycle the application pool), this should do the work… if this doesn’t work you may try at last option restart also SSO service.

  1. Hi,
    i had closed the admin console and closed all visual studio projects reset the IIS and restarted all the BizTalk services andSSO service too. opened once again my visual studio Biztalk project and trying to build my pipeline project.but, still facing with the same issue

  2. Hi,
    This is an old thread and me working with VS2012 do have the same problem. What is observed is that the orchestration projects keep locking the rest of the DLLs (schemas, map DLLs etc.,). I usually unload the orc project and clean the rest. Then reload the orc project and clean it again. That way I do not have to restart my VS. But I am looking for a more cleaner way.

Leave a Reply

Your email address will not be published. Required fields are marked *

BizTalk360
BizTalk Server

Over 500+ customers across
30+ countries depend on BizTalk360

Learn More
Serverless360
Azure

Manage and monitor serverless
components effortlessly

Learn More
Atomicscope
Business Users

Monitor your Business Activity in iPaaS
or Hybrid integration solutions

Learn More

Back to Top