October 17, 2007 at 2:27 pm
I am configuring a new SQL Server 2005 Standard Edition server. When I started setting this up last week, we were using a drive directory for the default database location (server properties, database settings of SQL Server) that was subsequently changed. Whenever I attempt to configure the Reporting Services to add a ReportServer database, it attempts to locate the database in the original drive location, which is no longer valid, rather than the current location which is now shown in the default database location in the server properties for Database Settings. How can I get the database setup in Reporting Services to reflect a valid directory location for ReportServer?
Pam
October 17, 2007 at 7:24 pm
The default database location only determines where SQL Server will attempt to locate new databases. It'll attempt to locate databases it knows about in the location where the files were originally unless you do something like detach the database, move the files, and then re-attach the database or swap out files by creating new files, moving objects to them, etc.
Did you just move the database files for ReportServer and restart the SQL Server?
K. Brian Kelley
@kbriankelley
October 17, 2007 at 8:33 pm
No databases were moved. I had installed Reporting Services on my server before I realized that the file directory specified in the default database location was invalid. Obviously, the ReportServer database creation failed because it could not find the path. When I changed the default database location and tried to create the ReportServer, it retained the original invalid location for the file and there was no way I could change it.
Eventually, I had to do a re-install of SQL Server 2005 because after applying SP2, the SQL Server services would not start. The re-install solved both problems.
Pam
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply