Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
TRK: TTK: 62175: Error code 27 TRK_E_INVALID_RECORD_TYPE
CMS-XML About: Error 126 when trying to install ODBC drivers or connect to database
When installing Tracker ODBC drivers or when trying to run Tracker you might get the error message "The Setup Routines for the Intersolv 32-bit {database} ODBC Driver Could Not be Loaded Due to System Error Code 126 or 1114 " or "Specified driver could not be loaded due to system error 126(Intersolv 32-bit {database}) ". This error message basically means that a dll file failed to load during the initialization of the ODBC driver.
CMS-XML TRKINET: Error ''The page you are trying to view requires the use of ''https'' in the address...HTTP 403.4 - Forbidden: SSL required''
Note: If are using the Sample.htm page to access the Configure Project page, and I-Net login page, you will need to modify the code for these buttons. The buttons on the sample page are hard-coded to use http://<servername >. They will have to be manually changed to use https://<servername >.
CMS-XML TRK: Error 'PVCS Version Manager disabled through ini setting or error loading.'
This error message is shown in Tracker SCR records under 'Source Code Changes' section when using module associations with VM.
CMS-XML How To: How to remove the Suspect flag from Tracker Databases on Microsoft SQL Server
Tracker Master and Project databases are marked as Suspect by Microsoft SQL Server after a DBMS failure or a log segment is full error message. WARNING : You must reboot SQL Server prior to ... Stored Procedure Code ... IF @@ error != 0 OR @@rowcount != 1 ... PRINT " WARNING : You must reboot SQL Server prior to "
CMS-XML How To: - Tracker INET - Multi-Lingual Functionality: European, Japanese & English
JAPANESE SERVER SCENARIO (for E & J): The above example shows TK 5.0E (E = English; J = Japanese) running on an entirely Japanese Windows NT 4.0 Server, with IIS 4.0J and IE 4.0J. This setup and the sequence of installation is described in the section below, entitled: Installing Japanese WinNT 4.0 w/Tracker 5.0E TKINET. Within Tracker Field Names - Japanese characters or European accented characters can break the name handles passed between the browser and the server, i.e. certain high ASCII character codes will prematurely terminate the field name being passed. When this error occurs it is still possible to use TKINET to submit new SCRs (defects), however users will quickly discover that defects can no longer be updated or closed.
CMS-XML Error: General Notify Problems
Error : General Notify Problems
CMS-XML Install: Errors while installing Trackerlink
Install: Errors while installing Trackerlink
CMS-XML Problem: #152 Network Communication Layer Error
Problem: #152 Network Communication Layer Error
CMS-XML Error: Need Graphics Server 4.0
Error : Need Graphics Server 4.0
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs