|
|
You're in the
sql server reporting services
group:DataBase Problem
sql server reporting services:
error logs located in C:\Program Files\Microsoft SQL Server\MSSQL.#\Reporting Services\LogFiles and see if there is any more detailed information in there. ------------------------------------- Chris Alton, Microsoft Corp. SQL Server Developer Support Engineer This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- [quoted text, click to view] > From: "Berger" <prodevteam@gmx.net>
> Subject: DataBase Problem > Date: Thu, 4 Oct 2007 13:31:32 +0200 > > Hello > > I have a problem with a Report Server installation. > The report server database is on another computer than the report server > frontend. > On the frontend Server SqlServer Service Pack2 was installed last night. > Now I can´t connect to the ReportServer Database. > How can I fix this problem, without creating a new Database? > I have tried to refresh the database but I get an error > > > thanx for any help > > regards > > Björn > > >
Hello
I have a problem with a Report Server installation. The report server database is on another computer than the report server frontend. On the frontend Server SqlServer Service Pack2 was installed last night. Now I can´t connect to the ReportServer Database. How can I fix this problem, without creating a new Database? I have tried to refresh the database but I get an error thanx for any help regards Björn
If the front end IIS Server does not have SP2 applied then it will not
connect to a SP2 backend ReportServer database. They both need to be at the same SP level. To check this do the following: 1. open up the "Reporting Services Configuration Tool" and go to the "Database Setup" section. 2. Click "Connect" and connect to the backend database server you are using. 3. Make sure the credentials are specified correctly for the database connection. 4. Click the "Apply" Button. If you get an error saying "Expected version C.0.8.43 but found C.0.8.54' or something similar that means that your versions are out of sync and you need to upgrade one or the other. ------------------------------------- Chris Alton, Microsoft Corp. SQL Server Developer Support Engineer This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- [quoted text, click to view] > From: "Berger" <prodevteam@gmx.net> http://www.eventid.net/display.asp?eventid=107&eventno=7858&source=Report%20> References: <O8KOeonBIHA.324@TK2MSFTNGP04.phx.gbl> <zjJvLkoBIHA.4648@TK2MSFTNGHUB02.phx.gbl> > Subject: Re: DataBase Problem > Date: Thu, 4 Oct 2007 16:58:34 +0200 > Hello > I´ve got the following error in windows eventlog: > Server&phase=1 [quoted text, click to view] >
> Can´t paste from Windows because it´s german ;) > > In the log directory I´ve found an error that the sqlaccount can´t login at > the database. > > I also have read an article that descripes that the wmi provider changed in > SP2. > The database was sp2 but the reporting service frontend wasn´t sp2. > So I believe it´s because SP2 was installed on the reporting service > frontend > > regards > > Björn > > "Chris Alton [MSFT]" <calton@online.microsoft.com> schrieb im Newsbeitrag > news:zjJvLkoBIHA.4648@TK2MSFTNGHUB02.phx.gbl... > > Can you post the error you are getting? Also, check the Reporting Services > > error logs located in C:\Program Files\Microsoft SQL > > Server\MSSQL.#\Reporting Services\LogFiles and see if there is any more > > detailed information in there. > > > > ------------------------------------- > > Chris Alton, Microsoft Corp. > > SQL Server Developer Support Engineer > > This posting is provided "AS IS" with no warranties, and confers no > > rights. > > -------------------- > >> From: "Berger" <prodevteam@gmx.net> > >> Subject: DataBase Problem > >> Date: Thu, 4 Oct 2007 13:31:32 +0200 > >> > >> Hello > >> > >> I have a problem with a Report Server installation. > >> The report server database is on another computer than the report server > >> frontend. > >> On the frontend Server SqlServer Service Pack2 was installed last night. > >> Now I can´t connect to the ReportServer Database. > >> How can I fix this problem, without creating a new Database? > >> I have tried to refresh the database but I get an error > >> > >> > >> thanx for any help > >> > >> regards > >> > >> Björn > >> > >> > >> > > > > >
Hello
I´ve got the following error in windows eventlog: http://www.eventid.net/display.asp?eventid=107&eventno=7858&source=Report%20Server&phase=1 Can´t paste from Windows because it´s german ;) In the log directory I´ve found an error that the sqlaccount can´t login at the database. I also have read an article that descripes that the wmi provider changed in SP2. The database was sp2 but the reporting service frontend wasn´t sp2. So I believe it´s because SP2 was installed on the reporting service frontend regards Björn "Chris Alton [MSFT]" <calton@online.microsoft.com> schrieb im Newsbeitrag news:zjJvLkoBIHA.4648@TK2MSFTNGHUB02.phx.gbl... [quoted text, click to view] > Can you post the error you are getting? Also, check the Reporting Services > error logs located in C:\Program Files\Microsoft SQL > Server\MSSQL.#\Reporting Services\LogFiles and see if there is any more > detailed information in there. > > ------------------------------------- > Chris Alton, Microsoft Corp. > SQL Server Developer Support Engineer > This posting is provided "AS IS" with no warranties, and confers no > rights. > -------------------- >> From: "Berger" <prodevteam@gmx.net> >> Subject: DataBase Problem >> Date: Thu, 4 Oct 2007 13:31:32 +0200 >> >> Hello >> >> I have a problem with a Report Server installation. >> The report server database is on another computer than the report server >> frontend. >> On the frontend Server SqlServer Service Pack2 was installed last night. >> Now I can´t connect to the ReportServer Database. >> How can I fix this problem, without creating a new Database? >> I have tried to refresh the database but I get an error >> >> >> thanx for any help >> >> regards >> >> Björn >> >> >> >
Hey Chris
Thank´s for your answer. If I do this I´ve got the question if I wish to update the databse. I say Yes and got an error in the SqlScript. The error is from type System.Data.SqlClient.SqlException. The error text: in sysdatabases no entry was found for "my Reporting Database". The Version of my reporting database is C.0.8.40 thanks Björn "Chris Alton [MSFT]" <calton@online.microsoft.com> schrieb im Newsbeitrag news:oVm8MbqBIHA.240@TK2MSFTNGHUB02.phx.gbl... [quoted text, click to view] > If the front end IIS Server does not have SP2 applied then it will not > connect to a SP2 backend ReportServer database. They both need to be at > the > same SP level. > > To check this do the following: > 1. open up the "Reporting Services Configuration Tool" and go to the > "Database Setup" section. > 2. Click "Connect" and connect to the backend database server you are > using. > 3. Make sure the credentials are specified correctly for the database > connection. > 4. Click the "Apply" Button. > If you get an error saying "Expected version C.0.8.43 but found C.0.8.54' > or something similar that means that your versions are out of sync and you > need to upgrade one or the other. > > > ------------------------------------- > Chris Alton, Microsoft Corp. > SQL Server Developer Support Engineer > This posting is provided "AS IS" with no warranties, and confers no > rights. > -------------------- >> From: "Berger" <prodevteam@gmx.net> >> References: <O8KOeonBIHA.324@TK2MSFTNGP04.phx.gbl> > <zjJvLkoBIHA.4648@TK2MSFTNGHUB02.phx.gbl> >> Subject: Re: DataBase Problem >> Date: Thu, 4 Oct 2007 16:58:34 +0200 >> Hello >> I´ve got the following error in windows eventlog: >> > http://www.eventid.net/display.asp?eventid=107&eventno=7858&source=Report%20 > Server&phase=1 >> >> Can´t paste from Windows because it´s german ;) >> >> In the log directory I´ve found an error that the sqlaccount can´t login > at >> the database. >> >> I also have read an article that descripes that the wmi provider changed > in >> SP2. >> The database was sp2 but the reporting service frontend wasn´t sp2. >> So I believe it´s because SP2 was installed on the reporting service >> frontend >> >> regards >> >> Björn >> >> "Chris Alton [MSFT]" <calton@online.microsoft.com> schrieb im Newsbeitrag >> news:zjJvLkoBIHA.4648@TK2MSFTNGHUB02.phx.gbl... >> > Can you post the error you are getting? Also, check the Reporting > Services >> > error logs located in C:\Program Files\Microsoft SQL >> > Server\MSSQL.#\Reporting Services\LogFiles and see if there is any more >> > detailed information in there. >> > >> > ------------------------------------- >> > Chris Alton, Microsoft Corp. >> > SQL Server Developer Support Engineer >> > This posting is provided "AS IS" with no warranties, and confers no >> > rights. >> > -------------------- >> >> From: "Berger" <prodevteam@gmx.net> >> >> Subject: DataBase Problem >> >> Date: Thu, 4 Oct 2007 13:31:32 +0200 >> >> >> >> Hello >> >> >> >> I have a problem with a Report Server installation. >> >> The report server database is on another computer than the report > server >> >> frontend. >> >> On the frontend Server SqlServer Service Pack2 was installed last > night. >> >> Now I can´t connect to the ReportServer Database. >> >> How can I fix this problem, without creating a new Database? >> >> I have tried to refresh the database but I get an error >> >> >> >> >> >> thanx for any help >> >> >> >> regards >> >> >> >> Björn >> >> >> >> >> >> >> > >> >> >> >
Is "My Reporting Database" really your database name? If so you've run into
a bug with the create/upgrade script. If your database name has spaces in it the script doesn't put [] around the database name for some reason so it blows off. Follow these steps to generate a script: 1. Open the Reporting Services Configuration Tool 2. Click the "Database Setup" link on the left side. 3. Click the "Script" button. 4. In the window that opens select either "New Database Script" or "Upgrade Database Script" on the left hand side. 5. If you are creating a new database follow these steps: a. Enter the name of the database you would like to create in the box. (The default is ReportServer) b. Select the language in the second drop down box. c. Specify the location where you want to save the created script. (this defaults to the current users "My Documents" folder) d. Click "OK". 6. If you are creating an "Upgrade" database script follow these steps: a. Type in the name of the Reporting Services database that you want to upgrade in the first box. b. Select the version of the database you are upgrading from in the second drop down box. c. Select the save file location in the 3rd drop down box. (this defaults to the current users "My Documents" folder) d. Click "OK". 7. Go to the "My Documents" folder. 8. Open the created script file in the file editor of your choice. 9. You should see a line in the script that looks similar to this: USE ReportServer[ReportServer] (This can vary depending on the name of your ReportServer database) 10. Do a find and replace on the following: Find: USE ReportServer[ Replace USE [ 11. Replace all instances of this in the script. 12. Save the file. 13. Execute this script in a Query Window on the database where you want to perform the operation. If that is not your issue then make sure you hit "Connect" first and then select the existing database in the drop down. If it is in the drop down then the databases exists on the server. ------------------------------------- Chris Alton, Microsoft Corp. SQL Server Developer Support Engineer This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- [quoted text, click to view] > From: "Berger" <prodevteam@gmx.net> <zjJvLkoBIHA.4648@TK2MSFTNGHUB02.phx.gbl> > References: <O8KOeonBIHA.324@TK2MSFTNGP04.phx.gbl> <uPLCLcpBIHA.5980@TK2MSFTNGP04.phx.gbl> <oVm8MbqBIHA.240@TK2MSFTNGHUB02.phx.gbl> [quoted text, click to view] > Subject: Re: DataBase Problem
> Date: Fri, 5 Oct 2007 11:52:27 +0200 > > Hey Chris > > Thank´s for your answer. > > If I do this I´ve got the question if I wish to update the databse. > I say Yes and got an error in the SqlScript. > The error is from type System.Data.SqlClient.SqlException. > The error text: in sysdatabases no entry was found for "my Reporting > Database". > The Version of my reporting database is C.0.8.40 > > thanks > > Björn > > > "Chris Alton [MSFT]" <calton@online.microsoft.com> schrieb im Newsbeitrag > news:oVm8MbqBIHA.240@TK2MSFTNGHUB02.phx.gbl... > > If the front end IIS Server does not have SP2 applied then it will not > > connect to a SP2 backend ReportServer database. They both need to be at > > the > > same SP level. > > > > To check this do the following: > > 1. open up the "Reporting Services Configuration Tool" and go to the > > "Database Setup" section. > > 2. Click "Connect" and connect to the backend database server you are > > using. > > 3. Make sure the credentials are specified correctly for the database > > connection. > > 4. Click the "Apply" Button. > > If you get an error saying "Expected version C.0.8.43 but found C.0.8.54' > > or something similar that means that your versions are out of sync and you > > need to upgrade one or the other. > > > > > > ------------------------------------- > > Chris Alton, Microsoft Corp. > > SQL Server Developer Support Engineer > > This posting is provided "AS IS" with no warranties, and confers no > > rights.
Hey Chris
The script doesn´t work :( Now I have tried to create a new report database. I think I have a problem with the wmi provider. In R.S. Configuration Tool I´ve got an error when I want to change to the menu "Initialization" the error text is something like: Error while changing scope. The reason can be an error while calling WMI properties. Details: Reportserver can´t connect to database In windows eventviewer I´ve got the error 107 again. Any ideas? regards Björn "Chris Alton [MSFT]" <calton@online.microsoft.com> schrieb im Newsbeitrag news:NLAHUa1BIHA.240@TK2MSFTNGHUB02.phx.gbl... [quoted text, click to view] > Is "My Reporting Database" really your database name? If so you've run > into > a bug with the create/upgrade script. > > If your database name has spaces in it the script doesn't put [] around > the > database name for some reason so it blows off. > > Follow these steps to generate a script: > 1. Open the Reporting Services Configuration Tool > 2. Click the "Database Setup" link on the left side. > 3. Click the "Script" button. > 4. In the window that opens select either "New Database Script" or > "Upgrade > Database Script" on the left hand side. > 5. If you are creating a new database follow these steps: > a. Enter the name of the database you would like to create in the box. > (The default is ReportServer) > b. Select the language in the second drop down box. > c. Specify the location where you want to save the created script. (this > defaults to the current users "My Documents" folder) > d. Click "OK". > 6. If you are creating an "Upgrade" database script follow these steps: > a. Type in the name of the Reporting Services database that you want to > upgrade in the first box. > b. Select the version of the database you are upgrading from in the > second drop down box. > c. Select the save file location in the 3rd drop down box. (this > defaults to the current users "My Documents" folder) > d. Click "OK". > 7. Go to the "My Documents" folder. > 8. Open the created script file in the file editor of your choice. > 9. You should see a line in the script that looks similar to this: USE > ReportServer[ReportServer] (This can vary depending on the name of your > ReportServer database) > 10. Do a find and replace on the following: > Find: USE ReportServer[ > Replace USE [ > 11. Replace all instances of this in the script. > 12. Save the file. > 13. Execute this script in a Query Window on the database where you want > to > perform the operation. > > If that is not your issue then make sure you hit "Connect" first and then > select the existing database in the drop down. If it is in the drop down > then the databases exists on the server. > ------------------------------------- > Chris Alton, Microsoft Corp. > SQL Server Developer Support Engineer > This posting is provided "AS IS" with no warranties, and confers no > rights. > -------------------- >> From: "Berger" <prodevteam@gmx.net> >> References: <O8KOeonBIHA.324@TK2MSFTNGP04.phx.gbl> > <zjJvLkoBIHA.4648@TK2MSFTNGHUB02.phx.gbl> > <uPLCLcpBIHA.5980@TK2MSFTNGP04.phx.gbl> > <oVm8MbqBIHA.240@TK2MSFTNGHUB02.phx.gbl> >> Subject: Re: DataBase Problem >> Date: Fri, 5 Oct 2007 11:52:27 +0200 >> >> Hey Chris >> >> Thank´s for your answer. >> >> If I do this I´ve got the question if I wish to update the databse. >> I say Yes and got an error in the SqlScript. >> The error is from type System.Data.SqlClient.SqlException. >> The error text: in sysdatabases no entry was found for "my Reporting >> Database". >> The Version of my reporting database is C.0.8.40 >> >> thanks >> >> Björn >> >> >> "Chris Alton [MSFT]" <calton@online.microsoft.com> schrieb im Newsbeitrag >> news:oVm8MbqBIHA.240@TK2MSFTNGHUB02.phx.gbl... >> > If the front end IIS Server does not have SP2 applied then it will not >> > connect to a SP2 backend ReportServer database. They both need to be at >> > the >> > same SP level. >> > >> > To check this do the following: >> > 1. open up the "Reporting Services Configuration Tool" and go to the >> > "Database Setup" section. >> > 2. Click "Connect" and connect to the backend database server you are >> > using. >> > 3. Make sure the credentials are specified correctly for the database >> > connection. >> > 4. Click the "Apply" Button. >> > If you get an error saying "Expected version C.0.8.43 but found > C.0.8.54' >> > or something similar that means that your versions are out of sync and > you >> > need to upgrade one or the other. >> > >> > >> > ------------------------------------- >> > Chris Alton, Microsoft Corp. >> > SQL Server Developer Support Engineer >> > This posting is provided "AS IS" with no warranties, and confers no >> > rights. >
You'll need to repair your database connection before you can finish the
initialization piece. Get the script to work and then you should be able to get your database connection functional. To finish the installation for SRS you shouldn't need to go to the Initialization portion of the config tool. Also, if the script failed what was the error when it failed? ------------------------------------- Chris Alton, Microsoft Corp. SQL Server Developer Support Engineer This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- [quoted text, click to view] > From: "Berger" <prodevteam@gmx.net>
> > Hey Chris > > The script doesn´t work :( > Now I have tried to create a new report database. > I think I have a problem with the wmi provider. > In R.S. Configuration Tool I´ve got an error when I want to change to the > menu "Initialization" > > the error text is something like: Error while changing scope. The reason can > be an error while calling WMI properties. Details: Reportserver can´t > connect to database > > In windows eventviewer I´ve got the error 107 again. > > Any ideas? > regards > > Björn > > "Chris Alton [MSFT]" <calton@online.microsoft.com> schrieb im Newsbeitrag > news:NLAHUa1BIHA.240@TK2MSFTNGHUB02.phx.gbl... > > Is "My Reporting Database" really your database name? If so you've run > > into > > a bug with the create/upgrade script. > > > > If your database name has spaces in it the script doesn't put [] around > > the > > database name for some reason so it blows off. > > > > Follow these steps to generate a script: > > 1. Open the Reporting Services Configuration Tool > > 2. Click the "Database Setup" link on the left side. > > 3. Click the "Script" button. > > 4. In the window that opens select either "New Database Script" or > > "Upgrade > > Database Script" on the left hand side. > > 5. If you are creating a new database follow these steps: > > a. Enter the name of the database you would like to create in the box. > > (The default is ReportServer) > > b. Select the language in the second drop down box. > > c. Specify the location where you want to save the created script. (this > > defaults to the current users "My Documents" folder) > > d. Click "OK". > > 6. If you are creating an "Upgrade" database script follow these steps: > > a. Type in the name of the Reporting Services database that you want to > > upgrade in the first box. > > b. Select the version of the database you are upgrading from in the > > second drop down box. > > c. Select the save file location in the 3rd drop down box. (this > > defaults to the current users "My Documents" folder) > > d. Click "OK". > > 7. Go to the "My Documents" folder. > > 8. Open the created script file in the file editor of your choice. > > 9. You should see a line in the script that looks similar to this: USE > > ReportServer[ReportServer] (This can vary depending on the name of your > > ReportServer database) > > 10. Do a find and replace on the following: > > Find: USE ReportServer[ > > Replace USE [ > > 11. Replace all instances of this in the script. > > 12. Save the file. > > 13. Execute this script in a Query Window on the database where you want > > to > > perform the operation. > > > > If that is not your issue then make sure you hit "Connect" first and then > > select the existing database in the drop down. If it is in the drop down > > then the databases exists on the server. > > ------------------------------------- > > Chris Alton, Microsoft Corp. > > SQL Server Developer Support Engineer > > This posting is provided "AS IS" with no warranties, and confers no > > rights. > > -------------------- > >> From: "Berger" <prodevteam@gmx.net> > >> References: <O8KOeonBIHA.324@TK2MSFTNGP04.phx.gbl> > > <zjJvLkoBIHA.4648@TK2MSFTNGHUB02.phx.gbl> > > <uPLCLcpBIHA.5980@TK2MSFTNGP04.phx.gbl> > > <oVm8MbqBIHA.240@TK2MSFTNGHUB02.phx.gbl> > >> Subject: Re: DataBase Problem > >> Date: Fri, 5 Oct 2007 11:52:27 +0200 > >> > >> Hey Chris > >> > >> Thank´s for your answer. > >> > >> If I do this I´ve got the question if I wish to update the databse. > >> I say Yes and got an error in the SqlScript. > >> The error is from type System.Data.SqlClient.SqlException. > >> The error text: in sysdatabases no entry was found for "my Reporting > >> Database". > >> The Version of my reporting database is C.0.8.40 > >> > >> thanks > >> > >> Björn > >> > >> > >> "Chris Alton [MSFT]" <calton@online.microsoft.com> schrieb im Newsbeitrag > >> news:oVm8MbqBIHA.240@TK2MSFTNGHUB02.phx.gbl... > >> > If the front end IIS Server does not have SP2 applied then it will not > >> > connect to a SP2 backend ReportServer database. They both need to be at > >> > the > >> > same SP level. > >> > > >> > To check this do the following: > >> > 1. open up the "Reporting Services Configuration Tool" and go to the > >> > "Database Setup" section. > >> > 2. Click "Connect" and connect to the backend database server you are > >> > using. > >> > 3. Make sure the credentials are specified correctly for the database > >> > connection. > >> > 4. Click the "Apply" Button. > >> > If you get an error saying "Expected version C.0.8.43 but found > > C.0.8.54' > >> > or something similar that means that your versions are out of sync and > > you > >> > need to upgrade one or the other. > >> > > >> > > >> > ------------------------------------- > >> > Chris Alton, Microsoft Corp. > >> > SQL Server Developer Support Engineer > >> > This posting is provided "AS IS" with no warranties, and confers no > >> > rights. > > > > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |