Is this standard behavior? If so, can this be configured to gather data pre-dating the Reporting install?

1.) I install the database server and data warehouse server on 2/1 (hypothetical date)

2.) I install the reporting server on 3/1 (again, hypothetical)

3.) The reporting server polls the database server and data warehouse when generating reports

If #3 is correct, then why would it be restricted to data created after 3/1? Why would it be tied to the date that the reports are created, rather than the data in the data warehouse?

"The data warehouse is not really aware until the SDK has added the MG group up to be updating the DW" - does this imply that the data warehouse is basically not collecting data until the Reporting Server is installed? I want to make sure I'm understanding this concept.

I'm not asking for a different answer - really! if it is the right answer then so be it - but just for clarification since this just doesn't add up with the way I expected these components to work together.

Thanks,

Chris

Hoping someone can point me in the right direction here. My install of an additional server to my OpsMgr environment is failing. Thank you in advance. Details below!

My current environment consists of two servers, both Windows 2003 R2 (32bit). One server is dedicated to SQL, the second has all other roles. OpsMgr 2007 R2 is installed along with Cumulative Rollup 1. I'm in the process of adding a third server to offload some of the management functions to. This new server is Windows 2008 R2. Running SetupOM, I run the pre-req test clearing only the operational database, reporting, and data warehouse options. All tests pass.

Now when I actually try to install, I get through to the point where (looking at the status window) services are created, and then the install rolls back. Looking at the log I consistently see this error:

Calling custom action WebCAManaged!Microsoft.MOM.Setup.WebConsoleCustomAction.WebConsoleCA.ConfigureAction
ConfigureAction: Error: Unknown error (0x80005000)
StackTrace:    at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.RefreshCache()
   at Microsoft.MOM.Setup.WebConsoleCustomAction.WebConsoleCA.Install(String targetDir, Int32 portNumber, String rmsServer, Boolean windowsAuthOn, String rootWebConfigFile, String mobileWebConfigFile, String rssWebConfigFile, String publicKeyToken, String version)
   at Microsoft.MOM.Setup.WebConsoleCustomAction.WebConsoleCA.ConfigureAction(Session session)
Exception thrown by custom action:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x80005000): Unknown error (0x80005000)
   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.RefreshCache()
   at Microsoft.MOM.Setup.WebConsoleCustomAction.WebConsoleCA.Install(String targetDir, Int32 portNumber, String rmsServer, Boolean windowsAuthOn, String rootWebConfigFile, String mobileWebConfigFile, String rssWebConfigFile, String publicKeyToken, String version)
   at Microsoft.MOM.Setup.WebConsoleCustomAction.WebConsoleCA.ConfigureAction(Session session)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
   at Microsoft.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint)
CustomAction _ConfigureAction.2FD07918_9082_437D_99BC_FD43602A4625 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (C4:B0) [12:48:13:379]: NOTE: custom action _ConfigureAction.2FD07918_9082_437D_99BC_FD43602A4625 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
Action ended 12:48:13: InstallFinalize. Return value 3.

"The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing..."

Clicking ok here gives another error: "The program failed to apply the Software Update..."

It almost sounds as if there is no patch available for 2008 R2 - server or agent, but I know that isn't true based on the KB article for the CU. Found a reference to this on Kevin's page from another person with a similar issue, didn't see a fix though.

I have a two node SQL cluster with two instances of SQL Server installed -- SQL Inst1 and SQL Inst2.  Both in seperate cluster groups.  I would like to run a report (or even build a perf view) that shows the processor usage for my application servers as well as the database servers for an app that uses SQL Inst1.  Adding and reporting on the application servers is easy since they're individual servers, I search the Windows Server 2003 Operating System class for my servers and add the % Processor Time counter and I get nice pretty graphs.  Now, here's where the problems starts.  I add both nodes of my SQL cluster and I see performance data from (of course) both nodes not knowing what node SQL Inst1 was running on.  I noticed the cluster name that's associated with the SQL Inst1 group is listed when I search the Windows Server 2003 Operating System class but if I try to add it to my report (or perf view) and no data is displayed.

How can I report on the clustered instance instead of using the physical nodes?

I believe that is default with all distributed application models. 

and this one from Marnix wolf http://thoughtsonopsmgr.blogspot.com/2009/11/running-opsmgr-web-console-from-non-rms.html

Also I would advise to first install only the management Server component before adding any other roles.

Regards,
Oskar

The reporting services were moved according to this article : http://technet.microsoft.com/en-us/library/cc540369.aspx

I have the reporting services working, just missing the majority of reports.  It does seem however that the reports that come from downloaded MP's are slowly repopulating themselves. 

My questions really : (is this usual behavior after moving the reporting)  is there some way to speed this re-import process up, and will I need to do any re-importing of the reports that were in my custom MPs?  Basically... do I just wait while it magically reimports the reports?

Do you know what the end result would be for any reports that were scheduled?  It seems that since my first post all the MP reports are back in, but I am not seeing any of the ones that I had scheduled.

Will those come along as well, or need to be recreated?

thanks again!

Event Type: Error
Event Source: Health Service Modules
Event Category: None
Event ID: 25004
Date:  3/12/2010
Time:  3:32:08 AM
User:  N/A
Computer: OpsMgr
Description:
The Windows Event Log Provider is still unable to open the File Replication Service event log on computer OpsMgr.xyg.com'. The Provider has been unable to open the File Replication Service event log for 614880 seconds.

Most recent error details: .The system cannot find the file specified.
 One or more workflows were affected by this.  Workflow name: UIGeneratedMonitorc82a8c009709494690905bcb6f04d328
Instance name: OpsMgr.xyg.com
Instance ID: {19742B56-24FE-ADFA-0E79-DD7E47E5A08A}
Management group: XYGOpsMgr

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I have disabled the monitor "Failed Accessing Windows Event Log" on OpsMgr server but still I am receving these error events on all member servers Operation Manager event log.

I verified that I don't see any such error events on Domain Controllers as you all know that FRS event log will only present on DC's but not on Member server...but then why this monitor looking for FRS log on all Member servers...

B'coz of this I have all my managed agent in warning state...I wanted to reset them in bulk to green...

 One or more workflows were affected by this.  Workflow name: UIGeneratedMonitorc82a8c009709494690905bcb6f04d328 
Instance name: OpsMgr.xyg.com 

Definitely wrong to have a monitor looking at that log targeting all systems. Find that monitor and you find your issue.

Reports are stored in the management packs and will slowly deploy into reporting services.  It will get there but can take some time, as you are finding out.  I'm afraid it's a case of just waiting...

In my experience working with OpsMgr I have found that rebooting the RMS can force reports to deploy a bit more quickly but I wouldn't recommend this in a production environment.  Just wait.

Hope that helps.

David

thanks!

What do you see in the logs? 

I would check the cluster MP guide as well for any notes on Server Core. I don't have access to the right just now.

I can use powershell to enumerate all views used within a role, but can't find a way to get the displayname of those views.

When using:

(Get-UserRole -Id ).Scope.MonitoringViews

i get a list of GUID's of the views the userrole has access to. How can i use these ID's to retrieve properties like displayname.

Because a view isn't a monitoring class or object, those cmdlets are useless.

Any ideas?

Today I have installed the OpsMgr reporting services; the installation went successfully without any issues. but after installation completed I can see the reporting node under the operator console and also I can see a reporting tab under the general settings.

But unfortunately I am not able to see any Default\Generic reports under the Reporting Node. I do have imported AD, DNS, Base OS, SCCM and SCOM ....etc mgmt packs.

Please find the enclosed screenshot. (Unable to updaload File)

I have data warehouse is hosted on different sevrer. Data warehouse writer and reader roles have been successfully configured during the reporting installation.

Regards,

Momeen Pasha