Visual-SourceSafe 错误 - 无法完成文件写入
我们使用 Nant 来自动化构建。一切都工作正常，直到大约一周前，降雨导致我们停电，构建服务器必须重新启动。现在，每当我们尝试构建时，我们都会收到以下错误：
<internalerror>
<type>System.Runtime.InteropServices.COMException</type>
<message><![CDATA[SourceSafe was unable to finish writing a file. Check your available disk space, and ask the administrator to analyze your SourceSafe database.]]></message>
<stacktrace><![CDATA[ at SourceSafeTypeLib.VSSItemClass.Get(String& Local, Int32 iFlags)
at NAnt.Contrib.Tasks.SourceSafe.GetTask.ExecuteTask()]]></stacktrace>
</internalerror>
我们在 VSS 数据库上运行分析实用程序，构建服务器上似乎有足够的空间，但运气不佳。有什么想法吗？我不知所措。
We use Nant to automate our builds. Everything was working fine until about a week ago when the rains caused our power to go out and the build server had to be re-booted. Now, we get the following error whenever we attempt a build:
<internalerror>
<type>System.Runtime.InteropServices.COMException</type>
<message><![CDATA[SourceSafe was unable to finish writing a file. Check your available disk space, and ask the administrator to analyze your SourceSafe database.]]></message>
<stacktrace><![CDATA[ at SourceSafeTypeLib.VSSItemClass.Get(String& Local, Int32 iFlags)
at NAnt.Contrib.Tasks.SourceSafe.GetTask.ExecuteTask()]]></stacktrace>
</internalerror>
We ran the Analyze utility on the VSS database and there appears to be plenty of room on the build server, but no luck. Any ideas? I'm at a loss.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我的问题是当前文件是空的...我对其写了一条评论，一切正常
My problem was that the current file was empty... I wrote a comment on it and everything worked ok
好的，这是决议。事实证明，不知何故，构建脚本中引用的 app.config 文件版本已损坏（实际上是所有以前的版本），这导致了 VSSGet 错误。将版本更新到当前版本修复了错误。
Ok, here is the resolution. It turns out that somehow, the version of an app.config file that was referenced in the build script was corrupted (all the previous versions, actually), which caused the VSSGet error. Updating the version to the current version fixed the errror.
当我尝试使用 VSS2SVN 将源安全数据库迁移到 Subversion 时，遇到了此问题。
此错误与消息相关
Source Safe 工具analyze.exe 可能会报告该情况。
如果您查看文件的历史记录并尝试获取比analyze.exe 报告的版本更旧的版本，则会显示此问题的消息。
Microsoft 针对由 XML 文件切换 BOM 包含导致的情况提供了修补程序 KB927887，但我没有尝试应用它。
另请参阅消息：SourceSafe 无法完成文件写入
I had this issue when I tried to migrate a Source Safe database to Subversion, using VSS2SVN.
This error is related to the message
that may be reported by the Source Safe tool analyze.exe.
If you look into the history of the file and try to Get a version that is older than the one reported by analyze.exe, the message of this question is shown.
Microsoft provided hotfix KB927887 for cases where this was caused by XML files toggling BOM inclusion, but I did not try to apply it.
See also Message: SourceSafe was unable to finish writing a file