Thursday, April 05, 2007

 

No end to my SP2 troubles

Whew - this has been a challenging last 30 days as I've tried and tried to just get SP2 to work in various environments without generic and generally not-helping-thank-you-though error messages. I love the new features in SP2 particularly the ability to create and use Custom Reports, but today I've had about four hours of SQL Hell lol. One problem was that I installed Reporting Services onto an already-SP2 machine. I then applied SP2a then patched to 3152 - all good, right?

After that, my RSConfigTool.exe (a.k.a., the Report Services Configuration Manager/Tool/Utility) doesn't work lol. When I launch it, it lets me connect to SSRS but immediately throws one of the "Unhandled Exception has occurred in your application. If you click continue..." popups that we get when we are in development and haven't implemented an exception handler.... ahem....

Here's the error thrown:
System.Management.ManagementException was unhandled
Message="Not found "
Source="System.Windows.Forms"
StackTrace:
at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at System.Windows.Forms.Control.Invoke(Delegate method)
at ReportServicesConfigUI.ConfigurationManager.Panel_ConfigurationChanged(Object sender, EventArgs e)
at ReportServicesConfigUI.Panels.ConfigurationPanel.OnConfigurationChanged(EventArgs e)
at ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String connectionString, String server, String database, ConfigurationCredentialsType credsType, String account, String password, Boolean upgrade, String dbVersion)
at ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(Object state)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
Likely it's too generic to offer anything but I put it up here just in case someone else has seen this :(

Another error that I've gotten in the RSConfigTool.exe is:
An unhandled exception ('System.Management.ManagementException') occurred in RSConfigTool.exe [7632]
When I click a panel, it then pops up a message that says:
There was an error while switching panels. The most likely cause is an error retrieving WMI properties. The exception details are: Not found
Speaking of WMI, I had a weird error installing SP2 on a Windows 2003 Standard Edition server today that had two instances, one with RTM and one with SP1 on it. The SP1 instance (the default) upgraded fine but the RTM would not update and the error message said something like, "An error occurred. Run over to Google and find KB921896 for details."

So I did.

And I'm not friggin happy!!!

KB921896 is the list of bugs fixed in Service Pack 2....

So, what would you do next? Well, I tried installing Service Pack 1 onto this instance which lasted for a total of 2 minutes before throwing three errors in succession. The final error? "An error has occurred. Please point yourself quickly to KB913090."

You guessed it: KB913090 is a list of all the bugs fixed in SQL Server 2005 SP1 lol.

Okay....

So which is it: do the folks at MSFT have a huge sense of humor or are they just rushing stuff out the door to meet some deadline that we don't know about? I don't know and I'm just kidding around anyway - we all know they don't have a sense of humor!

;)

Labels: , , ,


AddThis Social Bookmark Button

Comments:
I saw that there's a thread with a lot of folks getting similar errors but nothing exactly the same: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265011&SiteID=1

BTW - I am logged in as a local administrator on a Windows 2003 machine with SQL 2005 when this happens.
 
Arrrggh - MSFT is still teasing me!

I just did a google search for "There was an error while switching panels." (with quotes) and the 2nd post was a Microsoft site with the title, "Cannot initialize Report Server in SQL Server Reporting Services" and the highlighted line of text was "There was an error while switching panels."

I was pumped - I'm finally going to resolve it!!!!

When I click the link, the MSFT page says instead, "No posts available for this thread. Return to Microsoft Communities."

Oh I am just spewing lots of four letter words right now...
 
So Steve Klass just pointed me to even more recent builds and I'm going to try those today to see if they offer any help. They don't say there are any SSRS fixes in the docs but who knows, right? Worth a try on a dev server...

http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=A7C903FE-35A7-4BB2-8E73-932770099711&displaylang=en
 
I'm having exactly the same issue you are Scott. I'm wondering if it is an issue with the service pack level of the OS since I have a fully functioning SP2 upgrade (ie RSConfigTool.exe works as it should) on a Windows 2003 SP2 server while on a server with only Windows 2003 SP1 the RSConfig tool is failing.

Sadly the rest of the SP2 upgrade went very smoothly but this one issue is preventing me from rolling this into my production environment.
 
You could be right, Bill. Since SP2 for Windows 2003 and SP2 for SQL Server came out so close, you wonder if internally they had enough time to test...

Both of my machines that received the Reporting Services errors were Windows 2003 SP2 but the machine that had the SP2-install failure was Windows 2003 SP1.
 
So I got my Reporting Services instance working along with the Report Server Configuration Manager finally. I installed the 3159 update but that didn't do it. I then uninstalled SSRS, reinstalled it and patched it up to 3159 and all works now.
 
Post a Comment

Links to this post:

Create a Link



<< Home

This page is powered by Blogger. Isn't yours?