cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1313
Views
0
Helpful
4
Replies
hazemelebiary
Beginner

TMS hangs many times

                   we have TMS verion 12.1 appliance (runing on winows special edition) it starts hanging almost every day

we lose conection to it and even cant ping it. a led on it flashes blue while hanging.

it must be restarted physically to get back a live

i went through its logs but i couldnt find any thing helpful

any idea what can cause the problem or how can i detect the cause?

the following are logs i got just before problem happened

PROVISIONING

2012-09-02 08:47:45,627 [main] WARN  com.tandberg.provisioning.syslog  - Event="Directory Service Starting" Detail="The directory service is starting." Level=1 Time=2012/09/02-08:47:45
2012-09-02 08:48:03,034 [main] WARN  com.tandberg.provisioning.logging.LogLevelReaderVCS  - IO error while extracting log level Connection refused: connect
2012-09-02 08:48:03,034 [main] WARN  com.tandberg.provisioning.logging.LogLevelReaderVCS  - Setting log level to default level: 1
2012-09-02 08:49:29,546 [btpool0-6] ERROR com.tandberg.provisioning.endpoint.core.LicenseServiceXPathEndpoint  - FAILED retrieving available movi  licenses with message: localhost:389; nested exception is javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused: connect]
2012-09-02 08:49:30,327 [pool-1-thread-1] ERROR com.tandberg.provisioning.external.tms.TmsAddressBookToLdapConverter  - Exception:localhost:389; nested exception is javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused: connect]
2012-09-02 08:49:31,977 [btpool0-6] ERROR com.tandberg.provisioning.endpoint.core.LicenseServiceXPathEndpoint  - FAILED retrieving available system  licenses with message: localhost:389; nested exception is javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused: connect]
2012-09-02 08:49:33,552 [btpool0-6] ERROR com.tandberg.provisioning.endpoint.core.LicenseServiceXPathEndpoint  - FAILED retrieving total number of movi licenses with message: localhost:389; nested exception is javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused: connect]
2012-09-02 12:49:57,343 [main] WARN  com.tandberg.provisioning.syslog  - Event="Directory Service Starting" Detail="The directory service is starting." Level=1 Time=2012/09/02-12:49:57
2012-09-02 12:50:29,156 [main] WARN  com.tandberg.provisioning.logging.LogLevelReaderVCS  - IO error while extracting log level Connection refused: connect
2012-09-02 12:50:29,156 [main] WARN  com.tandberg.provisioning.logging.LogLevelReaderVCS  - Setting log level to default level: 1
2012-09-02 12:51:31,718 [pool-1-thread-1] WARN  com.tandberg.provisioning.external.tms.TmsPhoneBookReaderImpl  - No TMS phonebook contact on localhost http://localhost/tms/public/external/phonebook/localphonebookservice.asmx without userName and password. Exception:IO error (Read timed out)
2012-09-02 12:51:31,718 [pool-1-thread-1] ERROR com.tandberg.provisioning.external.tms.TmsPhoneBookReaderImpl  - No Tms Phonebook contact.
2012-09-02 12:51:32,718 [pool-1-thread-1] ERROR com.tandberg.provisioning.external.tms.TmsAddressBookToLdapConverter  - Exception:localhost:389; nested exception is javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused: connect]
2012-09-03 10:54:39,836 [main] WARN  com.tandberg.provisioning.syslog  - Event="Directory Service Starting" Detail="The directory service is starting." Level=1 Time=2012/09/03-10:54:39
2012-09-03 10:54:52,362 [main] WARN  com.tandberg.provisioning.logging.LogLevelReaderVCS  - IO error while extracting log level Connection refused: connect
2012-09-03 10:54:52,362 [main] WARN  com.tandberg.provisioning.logging.LogLevelReaderVCS  - Setting log level to default level: 1
2012-09-03 14:18:19,032 [main] WARN  com.tandberg.provisioning.syslog  - Event="Directory Service Starting" Detail="The directory service is starting." Level=1 Time=2012/09/03-14:18:19
2012-09-03 14:18:35,962 [main] WARN  com.tandberg.provisioning.logging.LogLevelReaderVCS  - IO error while extracting log level Connection refused: connect
2012-09-03 14:18:35,962 [main] WARN  com.tandberg.provisioning.logging.LogLevelReaderVCS  - Setting log level to default level: 1
2012-09-04 16:15:46,156 [main] WARN  com.tandberg.provisioning.syslog  - Event="Directory Service Starting" Detail="The directory service is starting." Level=1 Time=2012/09/04-16:15:46
2012-09-04 16:16:02,331 [main] WARN  com.tandberg.provisioning.logging.LogLevelReaderVCS  - IO error while extracting log level Connection refused: connect
2012-09-04 16:16:02,331 [main] WARN  com.tandberg.provisioning.logging.LogLevelReaderVCS  - Setting log level to default level: 1
2012-09-04 16:16:10,309 [pool-1-thread-1] ERROR com.tandberg.provisioning.external.tms.TmsAddressBookToLdapConverter  - Exception:localhost:389; nested exception is javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused: connect]


PLCMDIR


16:13:21,406 [TMSStatusService: TMSPLCMDirectoryService] WARN  Tandberg.TMS.Framework.Db.DbHelper - procedure failed: NET_Status_AddEntry, underlying error: Cannot open database "tmsng" requested by the login. The login failed.
Login failed for user 'tmsuser'.
16:13:21,421 [TMSStatusService: TMSPLCMDirectoryService] WARN  Tandberg.TMS.Framework.Db.DbHelper - Procedure parameters:
    @intServiceType = TMSPLCMDirectoryService
    @strMachineName = TANDBERG-MS
    @intInfo = StatusStarting

16:13:21,421 [TMSStatusService: TMSPLCMDirectoryService] ERROR Tandberg.TMS.Framework.Db.DbHelper -
System.Data.SqlClient.SqlException: Cannot open database "tmsng" requested by the login. The login failed.
Login failed for user 'tmsuser'.
   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.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Tandberg.TMS.Framework.Db.DbHelperTransaction.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Tandberg.TMS.Framework.Db.DbHelper.ExecuteNonQuery(String spName, SqlParameter[] parameterValues)

TMSSNMPSERVICE


15:18:50,585 [processorThread] ERROR Tandberg.TMS.NetworkScanner.NetworkScannerServer -
Tandberg.TMS.Common.SystemExceptions.SystemNotFoundException: System not found. Host name: 10.20.20.51
   at Tandberg.TMS.TMSSystems.SystemDiscoveryHelperFunctions.GetHTTPSystemType(String networkAddress, SystemTypes lastKnownSystemType)
   at Tandberg.TMS.TMSSystems.SystemService.GetAddableHTTPSystem(String networkAddress)
   at Tandberg.TMS.TMSSystems.SystemService.GetAnyAddableSystem(String networkAddress, String SNMPGetCommunityName, Boolean addOnlySupportedSystems, Boolean addNonSNMPSystems)
   at Tandberg.TMS.TMSSystems.SystemService.AddAnySystemToDatabase(String networkAddress, String SNMPGetCommunityName, Boolean addOnlySupportedSystems, Boolean addNonSNMPSystems)
   at Tandberg.TMS.TMSSystems.SystemService.InternalAddRogueSystem(String networkAddress, String SNMPGetCommunityName)
   at Tandberg.TMS.Service.TMSSystemService.TMSSystemService.AddRogueSystem(String networkAddress, String SNMPGetCommunityName)
   at Tandberg.TMS.NetworkScanner.NetworkScannerServer.ProcessRequestsProc()
TMS Version 12.1
16:13:21,531 [TMSStatusService: TMSSnmpService] WARN  Tandberg.TMS.Framework.Db.DbHelper - procedure failed: NET_Status_AddEntry, underlying error: Cannot open database "tmsng" requested by the login. The login failed.
Login failed for user 'tmsuser'.
16:13:21,546 [TMSBackgroundServices] WARN  Tandberg.TMS.Framework.Db.DbHelper - procedure failed: NET_User_GetUserByUsername, underlying error: Cannot open database "tmsng" requested by the login. The login failed.
Login failed for user 'tmsuser'.
16:13:21,578 [TMSBackgroundServices] WARN  Tandberg.TMS.Framework.Db.DbHelper - Procedure parameters:
    @strUserName = nt authority\system

16:13:21,578 [TMSStatusService: TMSSnmpService] WARN  Tandberg.TMS.Framework.Db.DbHelper - Procedure parameters:
    @intServiceType = TMSSnmpService
    @strMachineName = TANDBERG-MS
    @intInfo = StatusStarting

16:13:21,578 [TMSBackgroundServices] ERROR Tandberg.TMS.Framework.Db.DbHelper -
System.Data.SqlClient.SqlException: Cannot open database "tmsng" requested by the login. The login failed.
Login failed for user 'tmsuser'.
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Tandberg.TMS.Framework.Db.DbHelperTransaction.ExecuteReader(String connectionString, CommandType commandType, String spName, SqlParameter[] commandParameters)
   at Tandberg.TMS.Framework.Db.DbHelper.ExecuteReader(String spName, SqlParameter[] parameterValues)

4 REPLIES 4
Magnus Ohm
Cisco Employee

Hi

First of all the tmsng SQL login errors are just generic. If it was in fact an issue you would not be able to see the TMS webpage other than "An error has occurred" these errors can be generated when you restart the SQL service/server or when changing the user.

The openDS issues you are seeing (OpenDS being resource demanding) can also be generic errors. The TMS logs does not show you errors of why the hardware is starting to malfunction it is an application running on the windows OS so if the NIC is failing this is a server issue not an application issue I would assume.

I would open a TAC case on this to get the server replaced if you have a valid service contract. If not I would look into migrating the TMS installation to a VM since the appliance is end of life, but you will still get support for it for several more years if you have a contract that is.

/Magnus

Magnus Ohm
Cisco Employee

I would have taken a look at the windows event logs they will probably tell you more about what is going on. If the NIC is failing you should see this under the system eventlog, look for TCPIP events.

/Magnus

i already thought in migration to WMware . but can i use my license key of the appliance on the VM ware or i had to purchase a new one?

as for windows eevnt log i will go through it

Hi, For swapping the license from TMS appliance to VM please reach out to Cisco Sales/Account Team of your region and they will share more inputs on the same.

I would suggest to upgrade to TMS 13.x version on TMS Appliance itself, so you can install Windows 2008 R2 on VM since Windows 2003 is EOS and then perform backup of SQL [ TMSNG] database, TMSAgent from TMS appliance and restore to VM.

For the upgrade steps please refer to the relevant TMS 13.x version installation guide, release notes prior upgrade.

BR,

Mahesh Adithiyha

Create
Recognize Your Peers
Content for Community-Ad