The System Center Operations Manager Support Team Blog

This is the OpsMgr 2007 blog for the Microsoft support team. If you were looking for the SCOM 2007 or MOM 2005 blog then you are in the right place.

Some of the top Reporting deployment issues and resolutions for SCOM 2007

Some of the top Reporting deployment issues and resolutions for SCOM 2007

  • Comments 2
  • Likes

imageWe see a lot of System Center Operations Manager 2007 Reporting installs around here and while they almost always work perfectly, when they don't it's usually because of a few common issues. I've listed some of these common issues below.  The log file for Operations Manager Reporting, MomReportingX.log, is located in the temp folder (%temp%) and in “MomReportingX.log,” the “X” is the number that is based on the installation. To locate an error in this log file, search for the text “value 3”.

The following sections list the issues that you might see and the steps that you can take to resolve them. These include both specific error messages and usage problems.

MomReportingX.log:  Error: Unable to get the Management Server Action Account

This error occurs when name resolution has not been configured correctly.  To fix this problem, add the correct DNS entries and reverse lookup entries for the fully qualified domain name (FQDN) of the root management server (RMS).  To validate this, from the Windows desktop, click Start, click Run, type the FQDN for the RMS, and then click OK. You should see a browser window view of the RMS.

MomReportingX.log:  Adding REPORT_SERVER_FULL_HTTP_PATH property. Its value is 'https://Servername:443/ReportServer'

This error can occur when SSL is not set up on the SQL Server Reporting Services server.  To fix this problem, remove SSL from the default reporting Web site in IIS. For information, see article 946418 available in the Microsoft Knowledge Base (http://support.microsoft.com/kb/946418).

Could not find OperationsManagerDW

This error usually occurs when UDP port 1434 and TCP port 1433 are blocked by a firewall between the Reporting server and SQL Server.  If you are using a named instance, SQL Server might have assigned a dynamic port to the instance.  Use SQL Server Configuration Manager to identify the port that your SQL Instance is listening on and then open the corresponding firewall port.

MomReportingX.log: Error (407) Proxy Authentication Required

This error typically occurs if you have a proxy server configured in your Internet Properties\Connections\Local Area Network (LAN) Settings.  To fix the problem, remove the proxy setting from the server on which you are installing Reporting.

Applications event log: Error 25156. Failed to create MOM database.  The system cannot find the path specified.

This error can occur when you specify a drive and directory that does not have SQL Server installed.  To fix the problem, make sure that you select the drive where SQL Server is installed.

Browsing to http://localhost/reports returns “Service Unavailable”

This error can occur when permissions are missing on the %Windows%\temp folder.  To fix the problem, grant “Full Control” permissions for the %Windows%\temp folder to the user account that is running the installation and the Localsystem account. 

Hope this helps,

Satish Phatge | System Center Support Engineer

Comments
  • Great article!

  • Hi

    I am new to scom 2007 r2 and Report navigation pane giving me error The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid. need your help.

    Note:  The following information was gathered when the operation was attempted.  The information may appear cryptic but provides context for the error.  The application will continue to run.

    System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.

      at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)

      at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)

      at System.Threading.ExecutionContext.runTryCode(Object userData)

      at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

      at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

      at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)

      at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)

      at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)

      at System.Net.ConnectStream.WriteHeaders(Boolean async)

      --- End of inner exception stack trace ---

      at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)

      at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)

      at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

      at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.ReportingService.ReportingService2005.ListChildren(String Item, Boolean Recursive)

      at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.ManagementGroupReportFolder.GetSubfolders(Boolean includeHidden)

      at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.WunderBar.ReportingPage.LoadReportingSubtree(TreeNode node, ManagementGroupReportFolder folder)

      at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.WunderBar.ReportingPage.LoadReportingTree(ManagementGroupReportFolder folder)

      at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.WunderBar.ReportingPage.LoadReportingTreeJob(Object sender, ConsoleJobEventArgs args)

    System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.

      at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)

      at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)

      at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)

      at System.Threading.ExecutionContext.runTryCode(Object userData)

      at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

      at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

      at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)

      at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)

      at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)

      at System.Net.ConnectStream.WriteHeaders(Boolean async)

    Regards,

    Anshumanv

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment