I have a problem using Show History on a single file. The client reports
"Operation Failed". The Server side log file has a little more info, but it is not very helpful...
7/24/2007 1:09:37 PM - 2: GetFileHistoryException: File or project not found
7/24/2007 1:09:37 PM - 7/24/2007 1:09:37 PM - Server Exception (400): OPERATION_FAILED
7/24/2007 1:09:37 PM - 2: Server Error: 400
I can obtain the history fine via VSS. It is only SOS that is failing. We have run Analyze repeatedly and it reports no problems. We're running SOS Server version V4.2, VSS 2005. Windows Server 2003.
Other files in the project have no problems with "SHOW HISTORY", although I have not tried every one.
Any help would be appreciated.
Thanks
Tim
Show History fails in SOS client, OK in VSS
Moderator: SourceGear
-
- Posts: 5
- Joined: Mon Feb 13, 2006 8:14 pm
Can you tell me the exact Automation Component Version you are using?
Usually that error is caused by some sort of VSS corruption: http://support.sourcegear.com/viewtopic.php?p=28257&
Even after running Analyze, there still can sometimes be corruptions that are just picked up by the automation component. It is far more sensitive than the VSS client (the VSS client does not use the automation component).
One thing that helps some people is to perform an archive and restore on the problem files. You can try it first with just restoring that file to a dummy repository to see what it will do and if that fixed it.
Usually that error is caused by some sort of VSS corruption: http://support.sourcegear.com/viewtopic.php?p=28257&
Even after running Analyze, there still can sometimes be corruptions that are just picked up by the automation component. It is far more sensitive than the VSS client (the VSS client does not use the automation component).
One thing that helps some people is to perform an archive and restore on the problem files. You can try it first with just restoring that file to a dummy repository to see what it will do and if that fixed it.
-
- Posts: 5
- Joined: Mon Feb 13, 2006 8:14 pm
There have been a few users reporting history problems problems with that automation component, but it's inconsistent right now. I would still suggest the archive/restore, and after that you could try a different automation component. We have 6.0c posted here: http://support.sourcegear.com/viewtopic.php?t=1348. 6.0d is also a good one if you have it.
-
- Posts: 5
- Joined: Mon Feb 13, 2006 8:14 pm
We're a bit hesitant to try the archive/restore on a single file, since we understand that it will cause any shared connections for that file to get lost. So it means a full archive/restore I suppose.
When you suggest using the 6.0c automation component (SSAPI.DLL) or the 6.0d version - do you mean remove the VSS2005 version and replace it with an earlier version?
Thanks
Tim.
When you suggest using the 6.0c automation component (SSAPI.DLL) or the 6.0d version - do you mean remove the VSS2005 version and replace it with an earlier version?
Thanks
Tim.