Friday, April 2, 2010

SCOM R2 Console error message: Cannot initialize report.

Got this error on a Windows 7 client system. This error was thrown when a certain user tried to run a report from the Reporting Pane or a Targeted Report from the Monitoring Pane:
image

This is the whole error message:

Date: xxxxxxx

Application: System Center Operations Manager 2007 R2

Application Version: 6.1.7221.0

Severity: Error

Message: Cannot initialize report.

System.NullReferenceException: Object reference not set to an instance of an object.

at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.SetReportJob(Object sender, ConsoleJobEventArgs args)

When the same account was used on a SCOM MS, all ran just fine, without any glitch. Also when a connection to the SSRS instance by using Internet Explorer was made (using the same account!), the reports ran just fine. Checked the Data Warehouse Main settings and all was well: no empty string what so ever. I checked the OpsMgr eventlogs on the RMS, the Reporting server, the application- and system logs on the Windows 7 client system, nothing to be found…

It got even more strange since the same Windows 7 client system had no issues what so ever when some one else logged on. The reports ran like clock work. In order to isolate it even more, I ran a clean install of the SCOM R2 Console on another client system and let some users try to run reports from the SCOM R2 Console. Again, no issues.

So only a particular user account on a particular system experienced this issue. The Report tree was neatly shown, could also be refreshed but no way to run any report.

Hmm. Checked the firewall, the time zone settings, the regional settings but all to no avail. Reinstalled the Console, removed the cache but again, no reports! Dumped some regkeys related to that account profile for the SCOM Console but again no result.

Finally, I renamed the profile of the problematic account, let the user log on in order to create a new profile, and poof! The reports run just fine now!

Still it bugs me since I have no clue what was causing it. Something (duh!) in the profile. But what?

7 comments:

ile said...

Hi,

I have found that you need to remove temporary internet files on several occasions when you have issues with console, did you try that one? That would also support your test of renaming the user profile.

-Tero Ilenius

Marnix Wolf said...

Hi Tero.

Thanks for visiting my blog and your comment. No, I did not remove the temp. internet files. Good thinking! Next time when I bump into a similar issue I will try that first.

Cheers,
Marnix Wolf.

Marnix Wolf said...

Hi Tero.

I experienced a similar issue at another site. First I tried to remove the temporary internetfiles. But it did not help. I renamed the profile and then all was well again.

Cheers,
Marnix

John Bradshaw said...

Hi Marnix,
I'm so glad u blogged about this.....Here I was, happily Scomming along whan I went to add a new group. Clicked on Authoring/Groups and teh BIG RED X came across the screen!!!....with the cannot initialise.....
Reboot
Still the same
Can get to groups from another machine as another user fine.
After reading this Blog, rename Windows Profile for user to OLD and then log back in. No problems now. This really freaked me out!!
Thx for the simple fix.
John Bradshaw

Lance B said...

I was receiving this error while opening the console. I first received it when I clicked on Authoring then Groups, then every subsequent attempt to open the console popped open the error and closed the console. I just fixed this on Windows XP by renaming "C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Microsoft.Mom.UI.Console".

Mediterrano said...

What do you mean by "I renamed the profile of the problematic account"?

Do you mean the "Run as profiles" in operations console?

Marnix Wolf said...

Hi Mediterrano.

I mean the userprofile on the system experiencing this issue.

Cheers,
Marnix