| |
Results |
|
Try to sort by memo field for users in the Admin tool when database is Oracle - you get the error "Error in SQL statement reading TS_USERS table."
|
Try to sort by memo field for users in the Admin tool when database is Oracle - you get the error " Error in SQL statement reading TS_USERS table .
|
|
|
|
Notification events for archived items give Application Log error: "Record xx, in Table xxx could not be found"
|
The complete warning messages from the Event Viewer Application Log is: NOTIFICATION_NAME: (notification) context - Unable to read item with id xx from database . And:
|
|
|
|
GetAvailableTransitions call against aux table creates two errors in application event log
|
An exception occurred while attempting to fetch a record count or a record integer value from the database . The SQL is:
|
|
|
|
When deleting an item that has a relational field used in a Virtual Aux table you get an error that shouldn't show.
|
An exception occurred while attempting to fetch a record count or a record integer value from the database . The SQL is:
|
|
|
|
Continual logging of TS_CONCURRENTLOGINS table errors
|
Error occurred in CAppRecord::UpdateInDatabase. Problem occurred while reading record. Current Record: RecordId:422, TableId:86 SQL Select String: select TS_CONCURRENTLOGINS.TS_ID, TS_CONCURRENTLOGINS.TS_USERID, TS_CONCURRENTLOGINS.TS_USERIP, TS_CONCURRENTLOGINS.TS_USERACCESS, TS_CONCURRENTLOGINS.TS_LASTACCESSTIME, TS_CONCURRENTLOGINS.TS_WEBSERVERIP, TS_CONCURRENTLOGINS.TS_LICENSING, TS_CONCURRENTLOGINS.
|
|
|
|
Error when creating SLA from service in SRC - Error in SQL statement reading TS_NOTIFICATIONCONDITIONS table
|
Error when creating SLA from service in SRC - Error in SQL statement reading TS_NOTIFICATIONCONDITIONS table
|
|
|
|
Trend report may not work after upgrade to 11.0+ - error begins with - Database exception in CReportExecTrend::ExecuteDataCollection() using SQL:
|
SBM system introduced changes within Trend reports that uses an alias instead of table names and parts for generating drill-down SQL that was not modified (which still uses table name instead of the alias). This affects pass-thru SQL functionality which references to the main table as a result, these Trend reports no longer work after the upgrade. This error message below is an example of this issue.
|
|
|
|
Using read() in MashupScript can lead to Server Error 500
|
Using read () ... after a long while with "500 Server Error ": . ... closed the connection while reading the response. ... those cases the system needs to be ... Type: ERROR Error occurred in file: ... ... _TRANSITIONS' table . Row not found: The record with ID 0 could not be found in the 'TS_TRANSITIONS' table . ... Type: ERROR ... Error occurred in file: '.\ThreadPool.cpp', ... Unknown Exception occurred : User: testusr Request: TransitionForm ... Type: ERROR ... Error occurred in file: '.\HtmlFormTransition.cpp', line 439.
|
|
|
|
Importing data from Teamtrack 6.6.1 to SBM 10.1.3 error TS_Resources table - Invalid column name
|
There are some columns missing in the TS_RESOURCES table from teamtrack 6.6.1 when the import is required to SBM 10.1.3. The workaround for this issue is creating these invalid columns name in the source database Teamtrack.
|
|
|
|
Killer Import Error: Executing SQL directly; no cursor. Incorrect syntax near the keyword 'order' doing import from db
|
This problem happens when you go through the wizard to setup the import. On the screen where you "Specify Data to Import" you pick your table and if you choose the "Data type of matching column" and choose "Character" your import will work fine as long as you don't put anything in the "where" box. So if you choose "Character" as the matching column and put anything in the "Select records from source table when" box then you will get the following error when you run the import.
|
|
|
