Problem with malformed device (big3d) version

(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

 

________________________________________