Problem with malformed device (big3d) version

Hi Jean-Baptiste,

 

 

You mentioned that you’ve done a manual upgrade on the big3d version. Would be correct to assume that you have not authorized the big3d version upgrade within the F5 Management Pack setup? It’s the checkbox on the bottom of the install window (see the screen capture attached).

 

 

Or, did you follow the procedure described here?

 

http://devcentral.f5.com/Wiki/default.aspx/MgmtPack/Big3dManualUpdate.html (Click here).

 

 

If you ran a device discovery task without authorizing the big3d update on your device, then probably the big3d version on your device is different from the one the F5 Management Pack would update to (10.0.1.600.0.0). We could find out more by looking at the trace logs, but we would recommend running the discovery with authorizing the big3d update on the device, or make sure the big3d version on the device is at least matching the one the F5 Management Pack is shipped with, or is newer.

 

 

What is the current big3d version on the device you tried to discover?

 

 

We can further assist you if you send us the trace logs related to the device discovery.

 

Just follow the steps described here to activate (and gather) the trace logs (see the "Verbose Logging Support" section):

 

http://devcentral.f5.com/Wiki/default.aspx/MgmtPack/GeneralTroubleshooting.html (Click here).

 

 

Thanks.

 

Julian

(originally posted by: Roquencourt, Jean-Baptiste

 

Hi Julian,

 

As usual, I appreciate your support.

 

That’s good news that you will fix the installation folder issue.

 

For the 2nd point, I ran the manual installation mentioned in http://devcentral.f5.com/Wiki/default.aspx/MgmtPack/Big3dManualUpdate.html

 

I did not authorize the automatic update.

 

In fact after searching a little more I found that the Operation Manger Connector in the integrity explorer of my MS was down.

 

I think it’s the reason of the 2nd issue.

 

I tried to restart the health service, but that didn’t solve the issue.

 

I think the source of the problem is a problem with SQL Server.

 

The ENDPOINT is not created. I hope you can help me.

 

* * * * *

 

Résumé

 

The SQL Server Service Broker or Database Mirroring endpoint is disabled or not configured.

 

Causes

 

This event is logged in the Windows application log as MSSQLSERVER event ID 9666.

 

Solution

 

Either create the endpoint or enable it. To create the endpoint, use the CREATE ENDPOINT statement. To enable the endpoint, use the ALTER ENDPOINT statement.

 

External Information

 

For information about creating an endpoint, see "CREATE ENDPOINT (Transact-SQL)" in Microsoft SQL Server Books Online.

 

For information about altering an endpoint, see "ALTER ENDPOINT (Transact-SQL)" in Microsoft SQL Server Books Online.

 

* * * * *

 

Regards,

 

Jean-Baptiste

 

________________________________________

Hey Jean-Baptiste,

 

 

My first guess is that you may not have the SQL Service Broker enabled for the OperationsManager SQL database. Folow these steps please to enable it. Make sure you have sufficient SQL privileges on the OperationsManager database to perform these actions (~db_admin).

 

 

1.Stop the SCOM SDK service.

 

2.Open SQL Server Management Studio and connect with SQL admin privileges to the SQL Server hosting the OperationsManager database.

 

3.Click New Query.

 

4.In the query window, enter the following query: ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE

 

5.Click Execute and make sure the command completed successfully: you should get something similar to: “Nonqualified transactions are being rolled back. Estimated rollback completion: 100%.”

 

6.Clear the content of the current query window and enter the following query: ALTER DATABASE OperationsManager SET ENABLE_BROKER

 

7.Click Execute and make sure the command completed successfully.

 

8.Clear the content of the current query window and enter the following query: ALTER DATABASE OperationsManager SET MULTI_USER

 

9.Click Execute and make sure the command completed successfully.

 

10.Clear the content of the current query window. You can verify the setting for ENABLE_BROKER is set to 1 by using this SQL query: SELECT is_broker_enabled FROM sys.databases WHERE name='OperationsManager'. You would get something similar to: is_broker_enabled | 1.

 

11.Restart the SCOM SDK service.

 

 

Let me know how it goes.

 

 

Thanks,

 

Julian