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 in BizTalk
Tags: , , ,

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 to 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 get released.
  • And then deploy pipeline component.

SOLUTION 2

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

Tags: BizTalk | Pipeline | Deploy | Errors and Warnings, Causes and Solutions

Comments
  1. roundel1900 says:

    This is ridiculous. How are you supposed to develop applications like this?

    • 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🙂

      • Shadab Anwer says:

        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!!!

      • 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.

  2. David M. says:

    Thank you so much, renaming the files at least makes this slightly less annoying🙂

  3. Bala says:

    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

  4. Praveen Behara says:

    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

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s