brorich Posted November 11, 2003 Report Share Posted November 11, 2003 We just purchased MultiServer 6.5 Windows along with all of the agents. We are not on a Windows Domain, but have a SQL server that we need to back up the databases on. When i first installed the software for testing things, i plugged in the sa username/password and all was good. I guess that after closing, restarting or some other function, this password was not remembered. When i try to login using this password again in the immediate backup screen, it says it cant authenticate. I tried releasing the license, and readding, but nothing I do works. I called Dantz support and the only suggestion was to release/renew the license and check my security preferences. ALl of these settings are identical to before, but i cant get Retrospect to connect to SQL now. Any ideas. Link to comment Share on other sites More sharing options...
Mayoff Posted November 11, 2003 Report Share Posted November 11, 2003 Which version of 6.5 are you using? Does the operations log display a specific error message? If you install Retrospect local to the SQL server, does the same problem happen? Link to comment Share on other sites More sharing options...
brorich Posted November 11, 2003 Author Report Share Posted November 11, 2003 We are using 6.5 Multi-Server for Windows. Log simply says that no source volumes have been located. I havent tried installing to the SQL server and dont really want to as it should work like it is. We bought a dedicated server specifically for backing up our network. Link to comment Share on other sites More sharing options...
Mayoff Posted November 11, 2003 Report Share Posted November 11, 2003 The exact version can be found in "about Retrospect" under the Help. It would be 6.5.XXX Link to comment Share on other sites More sharing options...
brorich Posted November 11, 2003 Author Report Share Posted November 11, 2003 Exact version is 6.5.336 Link to comment Share on other sites More sharing options...
Mayoff Posted November 11, 2003 Report Share Posted November 11, 2003 This may be a situation where we need to capture an advanced log while the error reproduces so we can have an engineer take a look to help identify what is going on. A 2nd call to tech support maybe the next step so we can capture some advanced logging. Link to comment Share on other sites More sharing options...
brorich Posted November 12, 2003 Author Report Share Posted November 12, 2003 OK, thanks for the info. I will call them today and see what we can dig up. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.