我如何解决“进程无法访问文件 .ISPAC,因为它正被另一个进程使用"?错误? [英] How do I work around the "The process cannot access the file .ISPAC because it is being used by another process" error?

查看:66
本文介绍了我如何解决“进程无法访问文件 .ISPAC,因为它正被另一个进程使用"?错误?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用 SSDT 和 Visual Studio 执行了一个 SSIS 包.当我尝试执行另一个程序包时,我收到一条错误消息:该进程无法访问文件 XXXX.ispac,因为它正被另一个进程使用".我试过重新启动,但这是背后的痛苦.我该如何解决这个错误?

I executed an SSIS package using SSDT and Visual Studio. When I try to execute another package I get an error saying "The process cannot access the file XXXX.ispac because it is being used by another process". I have tried rebooting but that is a pain in the behind. How can I work around this error?

推荐答案

您可以检查补丁级别.我在 2015 年发布的 SSDT 中更频繁地看到这种情况,但从那以后就不再经常咬我了.

You might check your patch level. I saw this much more frequently with the 2015 release of SSDT but hasn't bit me too often since then.

Sysinternals 有一个出色的工具,名为 Process Explorer.它是免费的,不需要安装,可帮助您查看计算机上发生的一切.在这种情况下,您希望找到在您的文件 (MyProject.ispac) 上有脏手指的进程,然后将其杀死.

Sysinternals has an excellent tool called Process Explorer. It's free, doesn't require an install and helps you see what all is happening on your computer. In this case, you want to find the process that has its grubby finger on your file (MyProject.ispac) and then kill it.

https://helpcenter.gsx.com/hc/en-us/articles/115015880627-How-to-Identify-which-Windows-Process-is-Locking-a-File-or-文件夹

另一种不需要运行 Process Explorer 的方法是将构建从开发更改为发布(然后再返回).

A different approach that doesn't require getting Process Explorer running is to change your build from Development to Release (and back again).

这篇关于我如何解决“进程无法访问文件 .ISPAC,因为它正被另一个进程使用"?错误?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆