TMS reporting error

[maciej_wilk]

Hi,

I have the following issue with TMS - while trying to generate one of the first 3 reports in Reporting -> Conferences I receive the following error:

Error details:
Server Error in '/TMS' Application.
Difference of two datetime columns caused overflow at runtime.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Difference of two datetime columns caused overflow at runtime.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
 
Stack Trace:
[SqlException (0x80131904): Difference of two datetime columns caused overflow at runtime.]
   System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +2030802
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +5009584
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() +234
   System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +2275   System.Data.SqlClient.SqlDataReader.HasMoreRows() +211
   System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout) +217
   System.Data.SqlClient.SqlDataReader.Read() +9
   System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping) +72
   System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue) +164
   System.Data.Common.DataAdapter.Fill(DataSet dataSet, String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) +424
   System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +204
   System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +319
   System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) +94
   Microsoft.ApplicationBlocks.Data.SqlHelper.FillDataset(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, DataSet dataSet, String[] tableNames, SqlParameter[] commandParameters) +270
   Microsoft.ApplicationBlocks.Data.SqlHelper.FillDataset(String connectionString, CommandType commandType, String commandText, DataSet dataSet, String[] tableNames, SqlParameter[] commandParameters) +129
   Tandberg.TMS.Framework.Db.DbHelperTransaction.FillDataset(String connectionString, CommandType commandType, String sqlString, DataSet dataSet, String[] tableNames, SqlParameter[] parameterValues) +87
   Tandberg.TMS.Framework.Db.DbHelper.FillDatasetWithSql(String sqlString, DataSet dataSet, String[] tableNames) +70

[DatabaseException: Exception of type 'Tandberg.TMS.Framework.Db.DatabaseException' was thrown.]
   Tandberg.TMS.Framework.Db.DbHelper.HandleDatabaseException(String spName, SqlException exception, ICollection`1 parameterValues) +381
   Tandberg.TMS.Framework.Db.DbHelper.FillDatasetWithSql(String sqlString, DataSet dataSet, String[] tableNames) +196
   Tandberg.TMS.Service.Statistics.StatisticsDataManagement.AddNewDataSetFromSQL(StatisticsSetupGraph statisticsSetupGraph, StatisticsQueryProperties statisticsQueryProperties, StatisticsAxisFormatEnum statisticsAxisFormatEnum, Boolean export) +138   Tandberg.TMS.UI.Statistics.StatisticsHost.BuildStatistics(Int32 statisticsId, Int32 TranslateType, Boolean exportData) +2889
   Tandberg.TMS.UI.Statistics.StatisticsHost.Page_Load(Object sender, EventArgs e) +643
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35
   System.EventHandler.Invoke(Object sender, EventArgs e) +0
   System.Web.UI.Control.OnLoad(EventArgs e) +91
   System.Web.UI.Control.LoadRecursive() +74
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207
MachineName:
TimeStamp:
AssemblyName:App_Web_kg0ilx1k, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
AppDomainName:
ThreadIdentity:
WindowsIdentity:NT AUTHORITY\NETWORK SERVICE
URL:http://x.x.x.x/tms/default.aspx?pageId=86

The only thing that was changed in TMS configuration wa the default times of keeping the data for reports.

Did anyone come across such an issue and a way to fix it? Seems like some SQL digging..

[thobonho]

Hi

Is your SQL server in English US? It looks like TMS application cannot parse the dates stored in the database.

It's possible to change the language setting for the account used by TMS to query the database.  In SQL Management studio, expand the "Security" folder, then "Logins"  and you will find the TMS account there. Right click on it, choose Properties, and at the bottom of the "General settings" page, select "English" as default language.

Real issue is not with the language itself, but the format used for the dates. TMS application expects dates to be in  Month/Day/Year format.

Hope that helps!

[maciej_wilk]

Hi Thomas,

Yes, it's English US and the TMS account has English as default language.

Strange  thing is that this was working fine. The only thing that was changed in  TMS configuration some time ago was the default times of keeping the  data for reports.

Kind regards

[Martin Koch]

Do you use the tms-installed express database or something external?

What is your collation? It has to be:

SQL_Latin1_General_Cp1_CI_AS or SQL_Latin1_General_Cp1_CS_AS.

[maciej_wilk]

This is the TMS appliance and nothing was reconfigured..

[Martin Koch]

Which TMS version do you run?

Any trouble with disk space or time setting of the TMS?

[maciej_wilk]

It's 13.0.

There is loads of free disk space and no warnings about date/time settings.

[Martin Koch]

Disk space issues on the appliance are quite common, thats why I asked.

I would consider to update anyhow to 13.2.1.

If you had a big time offset and then reset the time, not sure if this could have an impact.

If there is no other info here, please consider escalating the case as a service request to TAC.

Martin

[daleritc · Accepted solution]

Yes, I would upgrade to latest and greatest, i.e. TMS 13.2.1. There's actually a fix that went into 13.1 concerning this stack trace error when selecting this report

https://www.cisco.com/en/US/docs/telepresence/infrastructure/tms/release_note/Cisco_TMS_Release_Note_13-1.pdf

See reference id 87430.

[maciej_wilk]

Thank you Dale!