开发者

Visual-SourceSafe error - unable to finish writing a file

开发者 https://www.devze.com 2023-04-05 19:20 出处:网络
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 err

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 Sour开发者_如何转开发ceSafeTypeLib.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.


My problem was that the current file was empty... I wrote a comment on it and everything worked ok


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.


I had this issue when I tried to migrate a Source Safe database to Subversion, using VSS2SVN.

This error is related to the message

There is a diff chain size mismatch in file '' (bdaaaaaa) at version (versions earlier than that version can no longer be retrieved from the database).

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

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号