jallensls Posted November 3, 2005 Report Share Posted November 3, 2005 I am running Retrospect 7.0 Multiserver with the value package on my Windows 2003 Server running SQL Server 2000. All products have the latest patches/service packs. I cannot get Retrospect to show the SQL container. In the licensing tab, I see that I have 0 SQL license in use, and 1 available. SQL was installed prior to Retrospect, so it's not a re-boot issue (it's been rebooted many times since both were installed). Does anything ned to be done to activate/use the SQL license? Any help would be appreciated. Link to comment Share on other sites More sharing options...
natew Posted November 4, 2005 Report Share Posted November 4, 2005 Hi SQL doesn't show at all in the configure->volumes screen in Retrospect? Do you have the latest version (7.0.326) of Retrospect installed? Was Retrospect installed with Admin priveleges? You need to... Thanks Nate Link to comment Share on other sites More sharing options...
jallensls Posted November 4, 2005 Author Report Share Posted November 4, 2005 Yes...I have the latest version. It was installed with admin priviliges. It does not show at all in the configure volumes..just my local hard drives, network places, backup clients and source groups. Retrospect just completely does not see/show it. Link to comment Share on other sites More sharing options...
jallensls Posted November 4, 2005 Author Report Share Posted November 4, 2005 more info....I have another perfectly working SQL server (Win 2000 server in this case, with SQL 2000 and the latest Retrospect). I installed the retrospect CLIENT on both servers just to see what they can see about each other. My problem server (Server A) CAN indeed see the SQL container on the client server (server , so it's not a licensing issue - the SQL agent seems to be installed and working. Also, server B sees server A as a client, but DOES NOT show a SQL container. So for whatever reason Retrospect cannot/does not see the SQL server instance on server A either locally or as a client. Is there something with Windows Server 2003 (the only variable) that is prohibiting Retrospect from recognizing the SQL instance? Some sort of port/authentication/security issue?? Link to comment Share on other sites More sharing options...
natew Posted November 8, 2005 Report Share Posted November 8, 2005 Hi It wouldn't be a security problem. Retrospect connects to the database the same way it would any other computer. I suspect the database is either not registered somewhere or that there are some strange permissions at play that prevent Retrospect from seeing the DB. Type CTRL + ALT + P + P in Retrospect and set trees and volumes logging to "7" Then Restart Retrospect and open the configure volumes window. Then set logging back to 3 and restart Retrospect. Your Retrospect log will have a bunch of debug information in it. Do you see any errors about SQL? Thanks Nate Link to comment Share on other sites More sharing options...
jallensls Posted November 8, 2005 Author Report Share Posted November 8, 2005 Fortunately this was a new install and there was no SQL data imported yet, so I just uninstalled and the re-installed SQl and now it sees it. Link to comment Share on other sites More sharing options...
nembot Posted November 16, 2005 Report Share Posted November 16, 2005 Hi, What was then the issue? Hadn't you installed Retrospect as yet the first time? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.