Problem trying to restore repositories
Moderator: SourceGear
Problem trying to restore repositories
I keep getting the following error message when using the Admin tool to restore the vault database:
"Database restore failed. Please see the server log for specific details."
Now I assume that the log being referred to is the log for SQL Server 2000? Looking at this there is no mention of a database restore failing.
I have tried to make sure that there are no SQL connections to sgvault before attempting the restore, however the Admin tool itself establishes a connection.
Also a question - Is it possible to select an individual repository to restore?
Thanks
Christian
"Database restore failed. Please see the server log for specific details."
Now I assume that the log being referred to is the log for SQL Server 2000? Looking at this there is no mention of a database restore failing.
I have tried to make sure that there are no SQL connections to sgvault before attempting the restore, however the Admin tool itself establishes a connection.
Also a question - Is it possible to select an individual repository to restore?
Thanks
Christian
In the Admin Tool, look at the Server Options tab. You should see Path to log file.christian wrote:I looked for a file in the Vault server directory that looked to be a log file (eg log.txt, vault.log) but no luck - what is the name and location of this log file?
OR
Examine Vault Server's vault.config file. You'll find an XML element for LogFilePath
By default the path is %windir%\temp\sgvault\sgvault.log
Yeschristian wrote:Can I use Enterprise manager to also perform a restore?
Jeff Clausius
SourceGear
SourceGear
Is this what you're referring to...
<appSettings>
<add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='false'; Server=(local); Database=sgvault; Integrated Security='true'" />
</appSettings>
or ...
<sessionState mode="InProc" stateConnectionString="tcpip=xxx.x.x.x:xxxxx" sqlConnectionString="data source=xxx.x.x.x;user id=sa;password=" cookieless="false" timeout="4320" />
<appSettings>
<add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='false'; Server=(local); Database=sgvault; Integrated Security='true'" />
</appSettings>
or ...
<sessionState mode="InProc" stateConnectionString="tcpip=xxx.x.x.x:xxxxx" sqlConnectionString="data source=xxx.x.x.x;user id=sa;password=" cookieless="false" timeout="4320" />
I believe that is the problem.
The Admin Tool is going to get the connect string from this file to attempt to connect to the database for database backup. Unfortunately, the Admin Tool is geared to only do backups from a connection string configured for SQL Server authentication. Hence the failure.
Two options here:
1) Reinstall the server, but using SQL Authentication for the database connection.
2) Run backups from within SQL Server itself.
The Admin Tool is going to get the connect string from this file to attempt to connect to the database for database backup. Unfortunately, the Admin Tool is geared to only do backups from a connection string configured for SQL Server authentication. Hence the failure.
Two options here:
1) Reinstall the server, but using SQL Authentication for the database connection.
2) Run backups from within SQL Server itself.
Jeff Clausius
SourceGear
SourceGear
Yes, however, in most cases, the problem is the user configured to connect to the database does not necessarily have backup rights, and configuring this requires more changes to SQL Server logins.
Regardless, we do have a feature request for this. I've added your name to the list.
Regardless, we do have a feature request for this. I've added your name to the list.
Jeff Clausius
SourceGear
SourceGear