Friday, February 24, 2012

Error trying to open Reporting Configuration Tool

I just installed SQL Server 2005 Express Edition and reporting services (followed the video tutorial). Whenever I try to open the Reporting Configuration Tool, it gives me the following error:

SQL Server 2005 Reporting Configuration Tool has encountered a problem and needs to close. We are sorry for the inconvience.

My only options are to Debug or Close.

I'm not sure why I am getting this error. Can anyone help?

Thanks,

Amanda

mandercruso wrote:

I just installed SQL Server 2005 Express Edition and reporting services (followed the video tutorial). Whenever I try to open the Reporting Configuration Tool, it gives me the following error:

SQL Server 2005 Reporting Configuration Tool has encountered a problem and needs to close. We are sorry for the inconvience.

My only options are to Debug or Close.

I'm not sure why I am getting this error. Can anyone help?

Thanks,

Amanda

I would recommend reinstalling the reporting services components of SQL.

|||

thanks. how can I just reinstall that component? I've uninstalled and reinstalled SQL Server 2005 Express thinking that would solve the problem, but it didn't....|||

Hmmm...If reinstalling the whole kit and kabudle didn't solve it then I would doubt that reinstalling just that component would.

It almost sounds like an operating system conflict. What does it do when you click debug?

|||

it gives me the following error:

an unhandled exception ('System.ComponentModel.Win32Exception') occurred in RSConfigTool.exe [7680].

Then it gives me the possible debuggers to choose from

|||Have you applied SP1 or SP2?

|||

Just downloaded SP2 with Advanced Options. Not sure if it matters but I have SQL Server 2000 on my machine... Visual Studio 2003 and 2005...

|||OK so you have yet to install SP2? Let us know if you still get the error after installing it.

|||

No, I meant, that's what I have originally downloaded and installed.

|||

bump... still having this problem. Does anyone know what's wrong?

No comments:

Post a Comment