Wednesday, March 7, 2012

Error in initialization of the report service

I installed the evaluation version of SQL Server 2005 to my Windows XP machine. Everything has worked well. Now I have problem. I installed the reporting service to test the web reporting.

In the Report service configuration manager I get three errors:

The Web Services Identity indicator is red and pushing Apply button gives the error:ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 8007056B

Pushing Initialization button gives the message: There was an error while switching panels. The most likely cause is an error retriewing WMI properties. the exeception details are: An error occured when attempting to connect to the report server remote procedure call (RPC) end point. Verify that the Report Server Windows service is running and then try the operation. Execption 800706B3.

Server Status Indicator is also red. Pushing the Start Button gives the following message: System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed. at System.ServiceProcess. ServiceController. WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout) at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)

Has anyone an idea what I should do ?

thankfully

Matti

Maybe could be a permissions problem. You should take a look at the Report Server logs to see if you see anything helpful. Make sure you are configuring locally and you are administrator on the machine. You should also make sure that the ReportServer service is running.|||

Thanks for help Brian !

The usefull things I made:

1. Created ReportService database using Report Service Configuration

2. Edited my personal account to Web Service Account in rsreportserver.config

3. Used rsconfig utility to encrypt the connection and account information

4. Edited my personal account to <processModel userName=" " >

etc.

There were many things which were not easy to find, but now the system works.

Matti

|||

Hi there,

I have the same problem as you.

Isn't there a different way to solve this?

What is the reason this problem occurs?

Cheers,

Carsten

|||

Did you manage to figure this one out? Really struggling with this...

Just to re-cap -

When using the Reporting services configuration manager - I get the same problem - clicking on "Report Server virtual directory" or "Web Service Identity" just comes up with the error message "...Object reference not set to an instance of an object"

Please help!!

Thanks

Wicky

|||

Hi Brian

I can't seem to get around this problem.

I'm running Windows Server 2003 so the default setup was for Report Server Windows service was to run under Network Service.

Whatever I do when clicking on the "Web Service Identity" option or "Report Server Virtual Directory" option I get the above mentioned error message about "Object reference not set to an instance of an object".

Wicky (again!)

|||

I am also getting message like "There was an error while switching panels. The most likely cause is an error retrieving WMI properties. The Exception details are : An internal error occurred on the report server.See the error log for more details. ( rsInternalError) "

while initializing report server.

please help.

neeraj kaushik

|||

Hi All,

I am getting the following error in reporting services configuration. Could someone please help out.

1) The status of report server is running but initilized found to be No.

2) The report server virtual directory and report manager virtual directory is in Green.

There was an error while switching panels. The most likely cause is an error retrieving WMI properties. The Exception details are : An internal error occurred on the report server.See the error log for more details. ( rsInternalError) "

Could someone please give pointers where in the problem is occuring asap.

Thanks so much,

Kushal

|||i am facing the same problem as well. I am running SQL Server 2005 under Windows Server 2003.

1) Report Manager Virtual Directory is grey.

2) When i click on the Web Service Identity, error msg as below:

"There was an error while switching panels. The most likely cause is an error retrieving WMI properties. The Exception details are : An internal error occurred on the report server.See the error log for more details. ( rsInternalError) "

My http://localhost/ReportServer is verified running. But my http://localhost/Reports cannot be accessed where there is error of "Page not Found 404".

I try to locate Reports or Report Manager under MS SQL Server folder but nth to be found.

Any help is much more appreciated.
|||I've got this problem as well.

I noticed in a previous post that the administrator privilege on the machine is advised to launch the reporting service configuration tool.

Is that true ? On my development server the tool works fine but I have the problem on the production. I'm not administrator of any of the two.

Thanks,

Galic
|||

Hi,

For people who received the exception message:

" An internal error occurred on the report server.See the error log for more details. ( rsInternalError) "

could you, please, take a look in the Reporting Services windows service log file and see what is logged there?

This log file lives in this directory:

%Program Files%\Microsoft SQL Server\MSSQL.X\Reporting Services\LogFiles

and its name looks like this:

ReportServerService__<timestamp>.log

Also what version and edition of Reporting Services are you running?

Mihaela

|||Probable Cause, in short:

The Reporting Services Configuration Manager must be the one creating the database. Do not use an existing database this causes all sorts of problems. Also, if you conduct a service pack or upgrade before Reporting Services is completely set up, Initialisation might produce that

Probable Solution:

In any case, when this problem occurs, it is best to drop the database, (reboot if any Service packs were installed in-between) and use the wizard (Reporting Services Configuration Manager) in the Database Setup screen, to create the db again.

PS: A similar error occurs when credentials are insuffient or incorrect. Domain controllers make matters more complex. Try different logins in Database Setup. eg: YOURSERVER\Adminuser

No comments:

Post a Comment