Hello,
I'm getting the following error while selecting one of our repositories
Now the repository does hold 52000 files. (version history)
Could the amount of files be a problem ? (clients have no problem accessing it)
Vault: v3.1.5
OS: Windows 2000 SP4
SQL: 2000 SP3a
Admin tool crashes when clicking properties.
Moderator: SourceGear
What are the exact steps to reproduce -- select the repository name, then click "Properties?" Or something else?
What version of the .NET Framework is installed on the Admin Tool machine?
Is this a new problem? Did it work properly before?
How many repositories do you have?
Is this reproducible if the Admin tool is on a different machine?
Update: Just noticed the FailDBReader error. Is there anything in the Vault server log file that corresponds to the error? The log is sgvault.log and is in the %windir%\temp\sgvault directory on the server machine.
What version of the .NET Framework is installed on the Admin Tool machine?
Is this a new problem? Did it work properly before?
How many repositories do you have?
Is this reproducible if the Admin tool is on a different machine?
Update: Just noticed the FailDBReader error. Is there anything in the Vault server log file that corresponds to the error? The log is sgvault.log and is in the %windir%\temp\sgvault directory on the server machine.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Just select and click properties .. then it's busy for ~ 2 or 3 minutes then I get that error message.What are the exact steps to reproduce -- select the repository name, then click "Properties?" Or something else?
2 Different workstationsWhat version of the .NET Framework is installed on the Admin Tool machine?
v2.0.50727
And on the server.
v1.1.4322
Yes and Yes.Is this a new problem? Did it work properly before?
In total 45 repositoriesHow many repositories do you have?
Yesterday it was.Is this reproducible if the Admin tool is on a different machine?
But today it seems to function again. Clientside reboot seemed to fix it.
Nothing with Fail in the log for that day or in the sgvault.log.Update: Just noticed the FailDBReader error. Is there anything in the Vault server log file that corresponds to the error? The log is sgvault.log and is in the %windir%\temp\sgvault directory on the server machine.
I guess the universal administrators fix "the reboot" performed it's usual miracle. I am unable to reproduce it now.