Skip to main content
Solved

Customization Package publishing error

  • November 10, 2022
  • 7 replies
  • 272 views

Forum|alt.badge.img+3

After unpublishing the customization package in one or multiple instances and again trying to re-publish, the system throws the below mentioned error exception:

System.IO.IOException: The process cannot access the file 'C:\Program Files\Acumatica ERP\Administrator\.vs\Administrator\FileContentIndex\write.lock' because it is being used by another process.

There isn’t any other customizations that have been published before.
Can anyone please guide us out the reason of this exception message.

Thank you.

Best answer by Harshita

Hello @Naveen Boga and @jinin I tried to publish the same package in a new instance, and the package was successfully published.

View original
Did this topic help you find an answer to your question?

7 replies

jinin
Pro I
Forum|alt.badge.img+11
  • Pro I
  • 702 replies
  • November 10, 2022

Hi @Harshita 

Can you unpublish all other packages if u already published them and then select the new package and publish once?


Forum|alt.badge.img+3
  • Author
  • Captain II
  • 317 replies
  • November 11, 2022
jinin wrote:

Hi @Harshita 

Can you unpublish all other packages if u already published them and then select the new package and publish once?

Hello @jinin thank you for the prompt reply. I did tried to unpublish all and then tried to publish the only required one but it throws the same exception.


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3410 replies
  • November 11, 2022

Hi, @Harshita  Are you getting the same issue when you try to publish the NEW EMPTY Package as well?


Forum|alt.badge.img+3
  • Author
  • Captain II
  • 317 replies
  • November 15, 2022
Naveen Boga wrote:

Hi, @Harshita  Are you getting the same issue when you try to publish the NEW EMPTY Package as well?

Thank you for your suggestion @Naveen Boga . The system didn’t raise any error while trying to publish an Empty Package. But when trying to publish any other non-empty pkg it throws the same exception error.


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3410 replies
  • November 15, 2022

Hi, @Harshita  Not sure about this issue. Please raise a support case with Acumatica on this error.


Forum|alt.badge.img+3
  • Author
  • Captain II
  • 317 replies
  • Answer
  • November 17, 2022

Hello @Naveen Boga and @jinin I tried to publish the same package in a new instance, and the package was successfully published.


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3410 replies
  • November 17, 2022

Yes, I thought the same hence I told you to try the publish the empty package. It seems some issue with the OLD instance.

 

Thanks for the sharing update.

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings