1.6.0 to 1.6.1 Upgrade Error

Can you verify that the Operations Manager SDK service and Operations Manager HealthService are both running on the machine? If they are, you can check the F5 Monitoring Service and try to start that if it is currently stopped.

 

 

After checking all the services, you can check the F5 Monitoring Log in the Event Viewer to see if our service is spamming the event log with warnings and errors. You may see some errors in here even if all the services are running. If you see any warnings or errors, please post them here along with any information you can give me about starting the services as well.

 

 

If all of that seems okay, then you should be fine. I'm not sure why the installer would report back that the modules were not loading. I will look into that issue after I hear back from you.

 

 

Thanks,

 

-Dave

I wanted to also try to completely uninstall the MP, then reboot, then reinstall the MP. However, this appeared to produce the same result. The same error message was displayed at the end of the setup process. Also, the installer didn't seem to remove all traces of the previous MP installation; the program files directory was left behind, the F5 Monitoring Log event log was left behind, and other remnants may have existed that I didn't know about. Do you guys have a clean uninstaller that will get rid of all traces of the MP since your normal uninstall process doesn't seem to work correctly?

So after I uninstalled, rebooted, reinstalled, and received the same error message, I took a look at the F5 Monitoring Service service it was set to Automatic startup with the correct Windows account but was not started. So I manually started the service and shortly after the following error events began appearing in the F5 Monitoring Log event log every 20 seconds or so:

Event ID: 201

Event Source: F5 Events

Event Category: None

Event User: N/A

Event Details:

  
  Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host scom01 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.  
   : scom01  
    
  Detailed Exception Information:  
  F5Networks.F5Exception: Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host strvascom01 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.  
   : scom01 ---> F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionFailedException: The PerformanceDataSourceConnector connection to Operations Manager Health Service host strvascom01 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.  
   : scom01 ---> System.Runtime.Remoting.RemotingException: Failed to connect to an IPC Port: The system cannot find the file specified.  
     
    
  Server stack trace:   
     at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel, Int32 timeout)  
     at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel level, Int32 timeout)  
     at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)  
     at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)  
    
  Exception rethrown at [0]:   
     at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)  
     at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)  
     at F5Networks.Remoting.ServerBase.get_HostProcess()  
     at F5Networks.ManagementPack.DataAccess.OperationsManager.DataSource.DataSourceConnector`2.Connect()  
     --- End of inner exception stack trace ---  
     at F5Networks.ManagementPack.DataAccess.OperationsManager.DataSource.DataSourceConnector`2.Connect()  
     at F5Networks.ManagementPack.DataAccess.OperationsManager.DataSource.ManagedDataSourceConnection`3.CoreConnect()  
     at F5Networks.ManagementPack.DataAccess.ManagedConnections.ManagedConnectionBase`1._DoConnectWithRecovery()  
     at F5Networks.ManagementPack.DataAccess.ManagedConnections.ManagedConnectionBase`1.Connect()  
     at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2._CreatePoolMember()  
     at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2._InitializeCache()  
     at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.Initialize(UInt32 initialOperationSize)  
     at F5Networks.ManagementPack.Services.DeviceMonitor._CreateDataSourceConnection()  
     at F5Networks.ManagementPack.Services.DeviceMonitor._InitializeDataStore()  
     --- End of inner exception stack trace ---  
    
  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Here are some vital system details of the root management server for you:

Memory: 12GB

Processor: Dual, quad-core 2.53GHz with Intel Hyper-Threading

SCOM: SCOM 2007 R2

OS: Windows Server 2003 R2 SP2 x64 with latest hotfixes

.NET: .NET Framework 3.5 SP1 with "Family Updates" and latest hotfixes

Security Configuration Baseline: Microsoft Windows Server 2003 Security Guides "Enterprise Client" "Member Server" baseline policy

Antivirus: Microsoft Forefront Client Security

SQL Server: SQL Server 2008 SP1 on a remote 4-node Windows Server 2008 failover cluster, SQL Server 2008 SP1 Reporting Services binaries installed locally with DB on cluster

I've been running the installer through a remote desktop connection; which is how I did the initial installation of the older versions "way back when".

Hey Kevin,

 

Sorry for the delayed reply. It looks like the F5 service is having trouble communicating with our data source modules that get loaded by the SCOM Health Service.

 

 

Can you check a few things for me? First, go into the Operations Manager Event log and look for any events for the F5Networks.ManagementPack.DataSource workflow being unloaded. If it has been unloaded, try restarting the HealthService and checking the event log again.

 

 

Also, when you ran the upgrade, did you upgrade the RMS first and then the Management Servers, or did you just upgrade the Management Servers?

 

 

Finally, can you run the SystemInformation script attached to this post and reply with the results or e-mail them to managementpack@f5.com?

 

 

Thanks and sorry for the inconveniences you are experiencing,

 

-Dave

 

Fresh install of 1.6.2.285 (which although versioned as such on the download page actually displays as 1.6.1.285 in SCOM 2007 R2; note the revision field in the version number) didn't throw this error. So whatever it was appears to be fixed in that release.