SOS 3.5 Unknown error(0x8004d83c)

Takoca · Post by **Takoca** » Fri Feb 01, 2008 8:50 am

Hello!

We are use SOS 3.5 , Win2k3 R2, VSS 6.0. During the last one year it was working perfectly but today our user report me they are cannot list a folder in the file structure. The acces of that folder and files from the local lan over VS S client is working withot any problem.
I found this in the SOS log:

Code: Select all

Fri Feb 01 15:17:29 GMT+01:00 2008 - 84.**.2*.1*.dclient.hispeed.ch(84.**.2*.1*) - End Get File List Operation: $/ver800/SOURCE
Fri Feb 01 15:17:45 GMT+01:00 2008 - 84.**.2*.1*.dclient.hispeed.ch(84.**.2*.1*) - Begin Get File List Operation: $/ver800/Documentation
Fri Feb 01 15:17:45 GMT+01:00 2008 - 84.**.2*.1*.dclient.hispeed.ch(84.**.2*.1*) - Getting version information
Fri Feb 01 15:17:45 GMT+01:00 2008 - 84.**.2*.1*.dclient.hispeed.ch(84.**.2*.1*) - Unknown error(0x8004d83c)
Fri Feb 01 15:18:14 GMT+01:00 2008 - 84.**.2*.1*.dclient.hispeed.ch(84.**.2*.1*) - Begin Get File List Operation: $/ver800
Fri Feb 01 15:18:14 GMT+01:00 2008 - 84.**.2*.1*.dclient.hispeed.ch(84.**.2*.1*) - End Get File List Operation: $/ver800

The folder was deleted and re added to the project. But nothing.
Later the clients report that they are cannot connect to the server (log in just hanging) After the SOS service restart it was solved.

Our internet connections is good. On the server the log is clear. (no disk error etc.). Everything looks like working good on the internal network.

So what can I doing?? Where do I need find the problem and soulions??
Pls help!

lbauer · Post by **lbauer** » Fri Feb 01, 2008 9:36 am

There may be some corruption in your VSS database. The first thing I would suggest is to run Analyze:

http://support.sourcegear.com/viewtopic.php?t=50

Takoca · Post by **Takoca** » Mon Feb 04, 2008 2:39 am

lbauer wrote:There may be some corruption in your VSS database. The first thing I would suggest is to run Analyze:

http://support.sourcegear.com/viewtopic.php?t=50

Thanks for your answer!

Yes, there was an database error. In that folder one of the files was corrupt, after we delete and re add it the problem was solved.

(the VS built in analyzer doesent find the problem....)