You are hereHow To: Fix "The report server database is an invalid version" Error
How To: Fix "The report server database is an invalid version" Error
Recently, I decided to go through my work computer's event log to see if I was racking up any errors and found one error repeated quite frequently -
Source: Report Server Windows
Event ID: 117
Description: The report server database is an invalid version.
Event ID: 117
Description: The report server database is an invalid version.
Now, I have Microsoft's SQL Server 2005 installed on my work machine for development purposes and the error seems to be directly related to the Reporting Services functionality. After looking at the help for this error in the Help files, Microsoft's web site and even a few search engine searches, I couldn't find the full answer anywhere. However, I finally fixed the error and here's how to do it.
Reporting Services Configuration Manager
- Open up the "Reporting Services Configuration Manager" by going to Start -> Programs ->Microsoft SQL Server 2005 -> Configuration Tools -> Reporting Services Configuration.
- On the left hand side, click on "Database Setup". (there should be a red "x" to the left of Database Setup.
- Choose the appropriate Server Name.
- For the Database Name, click "New" and do not use the default name "ReportServer" since it's possible a .MDF file was already created with this name. I used "ReportServer2".
- Make sure to choose the "Credentials Type" and enter the account information for a user who has create database permissions.
- Click "Upgrade". Make sure you get all green check marks (even a warning message means the process probably didn't complete properly).
- Click "Apply" at the bottom.
You should now be good to go and no longer receive this error in your Event Log.
Your step 4 fixed my problem.
My problem is when I configure report server,
my database version is missing and it was not able to initialize.
After I use ReportServer2. It worked.
Does that mean after the configuration, I can connect to report service through sql server 2005 management studio?
http://www.ncoachoutlet.com/ coach outlet coach outlet online usa
http://www.smichaelkorsoutlet.com/ michael kors outlet usa michael kors purses
http://www.new-michaelkorspurses.com/ michael kors purses outlet online
http://www.mk-michaelkoroutlett.com/ michael kors outlet stpre
http://www.guccishoeoutletfactory.net/ gucci shoes outlet online
http://www.northfacenoutletonline.net/ north face jackets outlet online
http://www.monstervheadphones.com/ monster beats outlet online
http://www.coach-storesonline2013.net/ coach outlet store online
Glad my post could help.
Correct, you will then see the database in Management Studio and you should be able to do whatever it is you need to do now that you resolved the issue.
Wonderful Artical..it is working fine
Thanks for your post. I am not a SQL Server aficionado and don't want to make matters worse. When I click the drop-down for Server Name, the name of the physical server is there. Also (Local)BKUPEXEC,(Local)KAV_CS_ADMIN_KIT,(Local)SQLEXPRESS and other (Local) entries. Which "server" should I select?
I get this error, but following your instructions it complains about a virtual directory. I created one but the red mark will not go and I still get the error. I have disabled reporting services and will use an alternative like Crystal. MS Reporting Service - the usual ms rubbish that sort of doesn't sort of work-ish!
What exactly does the error say about the virtual directory? Is your IIS setup properly? That's probably the source of your problem - your Reporting Services is not configured properly to work with IIS on that machine. Coincidentally, this is why SQL 2008 is a much better solution because it avoids issues just like this.
Good luck finding a solution.
I had the same problem. It complained about the Virtual Directory not being setup.
I set one up and it still complained. I scratched my head, restarted the service and the application, but no change. The red cross remained there and the settings would show "not set".
Then I hit refresh (top left of the application UI) and the icon when from red cross to green tick and I could set it up again.
also note that you won't see a list of databases unless you manually connect to the database server (seems obvious but most other applications autofill the list...)
you should be able to confirm whether the ReportServer DB already exists by perusing the list.