The purpose of this article is to:
- Provide an overview of the @ptitude Analyst Thin Client Transfer (@TCT) system
- Describe common issues with @TCT- File Based mode that prevent data from being processed
- How to recognize these issues and
- Steps that can be taken to fix the issues and ultimately get collected data to appear in the database.
The issues described in this article are:
- Invalid uSKF files (the database field not set properly) (page 6)
- All TCT file based licenses are used (page 9)
- Missing (unavailable) TCT licenses (page 11)
- Brute force flag set in the uSKF file (page 12)
- POINT ID mismatch between an older dSKF file and the current database (page 14)
- Corrupt uSKF files (page 15)
Comments
0 comments
Please sign in to leave a comment.