Forum Discussion
tomtux_93477
Nimbostratus
NimbostratusUnsuccessful Installation
Hi
I've installed MSSQL2005 SP2 (incl. Reporting), IIS and SCOM2007 on a W2K3-SP2-Server. The "F5 Monitoring Service" is running under a explicit F5-Account, which has local administrators-rights.
I tried to install the F5-MgmtPack, but it always fails:
The Mmgt-Pack-"setup.log" shows the follwing fatal-error:
----------------------
...
...
<03-26-2010 09:25:13> Info: HealthService service state is: Running
<03-26-2010 09:25:13> Info: Stopping service: HealthService
<03-26-2010 09:25:15> Info: HealthService service has been stopped.
<03-26-2010 09:25:15> Info: HealthService service state is: Stopped
<03-26-2010 09:25:15> Info: Starting service: HealthService
<03-26-2010 09:25:20> Info: HealthService service has been started.
<03-26-2010 10:16:55> Info: Licensing of F5 Networks Management Pack has completed successfully.
<03-26-2010 10:16:55> Info: Verifying the DataSource and ConditionDetection modules required for the F5 Monitoring Service to run are loaded by Operations Manager monitoring host.
<03-26-2010 10:16:57> Info: DataSource and ConditionDetection modules successfully loaded by Operations Manager monitoring host.
<03-26-2010 10:16:57> Info: F5MonitoringService service state is: Stopped
<03-26-2010 10:16:57> Info: Starting service: F5MonitoringService
<03-26-2010 10:17:01> Info: F5MonitoringService service has been started.
<03-26-2010 10:17:01> Info: F5MonitoringService is starting up.
<03-26-2010 10:41:33> FatalError: The F5 Monitoring Service did not start within the timeout period.
<03-26-2010 10:41:33> FatalError: There was a problem attempting to make calls into the F5 Monitoring Service. Check the Windows Event Log and trace logs for the reason and try starting the service again manually.
----------------------
In the system-eventlog, I have the following warnings:
----------------------
Unexpected SQL failure: Invalid object name 'DynamicData.Entity'.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
----------------------
----------------------
Unable to initialize data storage: Unexpected SQL failure: Invalid object name 'DynamicData.Entity'.
Detailed Exception Information:
F5Networks.F5Exception: Unable to initialize data storage: Unexpected SQL failure: Invalid object name 'DynamicData.Entity'. ---> F5Networks.ManagementPack.DataAccess.NonfatalDataAccessException: Unexpected SQL failure: Invalid object name 'DynamicData.Entity'. ---> System.Data.SqlClient.SqlException: Invalid object name 'DynamicData.Entity'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at F5Networks.ManagementPack.DataAccess.SqlServer.SqlConfigAdapter.<>c__DisplayClassbf.<_LoadEntityInfoCache>b__bc()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.<>c__DisplayClass6.b__5()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.CoreDoOperation[TReturnResult](GenericVoidHandler`1 operation)
at F5Networks.ManagementPack.DataAccess.SqlServer.SqlConnectionPool.CoreDoOperationWithExceptionMapping[TReturnResult](ManagedSqlConnection connection, GenericVoidHandler`1 operation)
--- End of inner exception stack trace ---
at F5Networks.ManagementPack.DataAccess.SqlServer.SqlConnectionPool.CoreDoOperationWithExceptionMapping[TReturnResult](ManagedSqlConnection connection, GenericVoidHandler`1 operation)
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.<>c__DisplayClass9`1.b__8()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ManagedConnectionBase`1.DoOperationWithRecovery[TReturnResult](GenericVoidHandler`1 operation)
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.UseConnectionForOperation[TReturnResult](TManagedConnectionType& connection, Object connectionTag, GenericVoidHandler`1 operation)
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.UseConnectionForOperation(TManagedConnectionType& connection, Object connectionTag, VoidVoidDelegate operation)
at F5Networks.ManagementPack.DataAccess.ManagedConnections.LockedConnectionPoolReference`2.UseConnection(VoidVoidDelegate operation)
at F5Networks.ManagementPack.DataAccess.SqlServer.SqlConfigAdapter._LoadEntityInfoCache()
at F5Networks.ManagementPack.DataAccess.SqlServer.SqlConfigAdapter._Initialize()
at F5Networks.ManagementPack.DataAccess.SqlServer.SqlConfigAdapter._EnsureInitialized()
at F5Networks.ManagementPack.DataAccess.SqlServer.SqlConfigAdapter.Initialize()
at F5Networks.ManagementPack.DataAccess.Configuration.ConfigManager`8._Initialize()
at F5Networks.ManagementPack.DataAccess.Configuration.ConfigManager`8..ctor(ConfigAdapterBase`4 configAdapter, MonitoringAdapterBase`4 monitoringAdapter)
at F5Networks.ManagementPack.Services.DeviceMonitor._CreateConfigurationManager(MonitoringAdapterBase`4 operationsManagerConfigurationAdapter, ConfigAdapterBase`4 sqlConfigurationAdapter)
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.
----------------------
Any hints? I have also reinstalled the whole system, but -> no success.
Every 10 seconds, the F5-Monitoring-Service is started, stopped, started, stopped...and so on.
Thanks a lot.
Tom
- Hi,
It sound like there may be a problem with the F5 database. Could you please verify that the database looks correct?
1. Verify that the F5 service has the correct connection information for the database:
a) Open the F5 service configuration file (C:\Program Files\F5 Networks\Management Pack\f5mpsvc.exe.config)
b) The value specified for "SQLHostName" should match your SQL Server host name
c) The value specified for "DatabaseName" should match a database in the above SQL Server instance
2. Open the database specified in the config file and verify that the "DynamicData.Entity" table exists:
a) Open SQL Server Management Studio
b) Connect to your SQL Server instance
c) Expand the list on the left to Databases => F5_ManagementPack => Tables
d) Verify that there is a table named "DynamicData.Entity"
If the database and/or table is missing, something probably went wrong in the installation process and we can diagnose further. 
tomtux_93477Hi
My "f5mpsvc.exe.config"-File looks like this:... ...
Within the installation of the MgmtPack, there was no sql-database "F5_ManagementPack" created. The only one I see in the SQL-Studio is the "OperationsManager"-database. The server, which is defined in the attribute "SQLHostName" is properly resolvable -> no name-resolution-issue. I had created a Active-Directory-User with administrative rights on the "F5-Management-Pack"-Server and also full db-rights on the sql-server (same box). During the installation, I was asked for this f5-user. There I entered this active-directory-f5-user (full privileges).
Is there a way to initiate the db-creation step again? Or can I just add the missing table? I logged in also with the f5-user and started the "F5Networks.ManagementPack.Setup.exe" again. There I was able to click the option "Repair" -> but no success.
I have also created the database "F5_ManagementPack" manually and repaired the installation -> also no success. In the windows-eventlog is still the same error:Unable to initialize data storage: Unexpected SQL failure: Invalid object name 'DynamicData.Entity'. Detailed Exception Information: F5Networks.F5Exception: Unable to initialize data storage: Unexpected SQL failure: Invalid object name 'DynamicData.Entity'. ---> F5Networks.ManagementPack.DataAccess.NonfatalDataAccessException: Unexpected SQL failure: Invalid object name 'DynamicData.Entity'. ---> System.Data.SqlClient.SqlException: Invalid object name 'DynamicData.Entity'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) ... ...
Thanks a lot for your help.
Kind regards,
Tom- Tom,
If you run setup and it does not correctly create the database, there should be an error like "Unable to create database: ... " in the setup log with details as to the cause of the failure.
I can give you a much better diagnosis if you can send your setup log (send directly to ManagementPack@f5.com if you would rather not post here). Ideally, first delete your F5_ManagementPack database and then re-run setup so I can determine why the DB is not being created correctly in the first place.