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:

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.

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.....RebootStill the sameCan 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

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".

Veeam

NiCE

Search This Blog

Didacticum

Pageviews last month

Visitors to this blog:

Why this blog?

On an almost daily basis I work with Azure, OMS & System Center related technologies. At the moment my main focus areas are Azure, OMS, SCOM & SCCM.

Because I bump into many challenges I decided to start this blog, which has two main purposes: to help YOU with mastering these products by covering the undocumented features and last, but not least, as my personal - but open to any one - knowledge base.

From January 2010 on I have been rewarded with the MVP award and until now this this status is prolonged every year.

MVP AWARD

Follow me on Twitter

Disclaimer

The information in this blog is provided 'AS IS' with no warranties and confers no rights. This blog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my own personal opinion. All code samples are provided 'AS IS' without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.