Below are the responses to your questions...
I have had no other reports of issues accessing the database other than history on some files.--You can use that database normally in every other way except for retrieving a history?
We have 3 databases. The first, main database which is where the issues are reported. A second database is used for holding specifications and test results (in lieu of a Document Management System), the 3rd was a temporary database we used for .NET development while we researched setting up Team Foundation Server.--How many VSS databases do you have?
The issue only seems to be present in our main database which is by far the biggest. The only issues I know about are particular binary files. I have had no reports of issues with source code (text) files.--Is this issue only present on some of them? And, if so, is it the entire database or with just some files?
Yes, I regularly run Analyze and Fix on our database as a part of the backup procedure.--Have you run an analyze on your database (more information on that earlier in this thread)?
Yes, no problems are found either with VSS Explorer V6 or 2005--Can you get a file history with VSS?
It is only users accessing the database using Source Offsite. I have a license to access from home and it fails remotely. I have also generated an IKY file to access internally while in the office to verify the SOS Service is running and SOS has the same issue.--Only remote users had an issue, or was it internal and remote?