Topics > Messages > DataPlus Diagnostics > FAQ ID # 5120

FAQ ID # 5120
Last Update : 2018/03/02
Print this FAQ

Question / Issue
DataPlus Diagnostics

Answer / Solution
PROGRAM: DataPlus Diagnostics
Table of Contents
DataPlus Import Confirmation
Reasons for import failure
    Diagnosing DataPlus Import
    Reasons for Import Failure
  1. Microsoft Task Scheduler not executing
  2. Microsoft Task Scheduler username or password incorrect
  3. DataPlus configuration Act username or password incorrect
  4. Depending on integration solution you are using, SQL Linked Server lost ODBC connection
  5. Act field needed to be created and could not lock the Act database
  6. DataPlus not activated
  7. DataPlus subscription expired
  8. Script error
1st Test
    Diagnosing DataPlus Import
    Import History
    After each DataPlus import, whether manual or auto, the import is time stamped for each procedure.
  1. In Act goto DataPlus tab
  2. Click on Browse All... button
  3. View drop down
  4. Scroll down to DataPlus / DataPlus Import History
  5. Entity | Procedure | Date:Time is displayed
  6. The Date:Time indicates the last time the procedure imported

    Note: The import Date:Time indicates the last time the procedure was imported. It does not indicate success or failure of import.

2nd Test
    Diagnosing DataPlus Import
    Application Last Update
    Successful imports will time stamp the Application Last Update field in Act.
  1. In Act create lookup on Application Last Update field for today or date
  2. Click on Browse All... button
  3. View drop down
  4. Scroll down to DataPlus / DataPlus Import History
  5. The menu will provide the import procedure and Dste:Time of last import
  6. If import was not completed and errored out, the last line should explain why

    Note: Replace Application with the integrated software you are using. The field is normally in the Status Tab

    There are several procedures that are normally executed. Therefore 1 procedure can update the field and other procedures could have failed.

3rd Test
    Diagnosing DataPlus Import
    Import Log File
    If you use Windows Scheduler to auto import from your application to Act, a log file is created with import results.
  1. Browse to "[Drive]:\Program Files (x86)\Hogan Data\DataPlus 4.0\Logs"
  2. Open latest log file and analyze the data
  3. If necessary go to the last line of text to determine if import completed or errored out
  4. If completed, then the import was successful on the time stamped date of file
  5. If import was not completed and errored out, the last line should explain why
4th Test
    Diagnosing DataPlus Import
    Manual Import
    Determine what data is not being imported.
    Below is example for "Customer" not being imported
  1. Manually import Customer from within Act
  2. Act Tool Bar: Tools/DataPlus 4.0/Manual Import
  3. Click on your Application Profile
  4. Click on Import Options: [ ... ]
  5. Click on Only Run Selected Items
  6. Scroll down and click on Customer
  7. Click on Okay
  8. Click on Import Selected
  9. A manual import will be performed and will either display success or failure of import
  10. If import was not completed and errored out, the last line should explain why
Resolution
    Diagnosing DataPlus Import
    Resolution
  1. Configure Microsoft Task Scheduler to execute
  2. Correct Microsoft Task Scheduler username or password
  3. Correct DataPlus configuration Act username or password
  4. Check ODBC connection
  5. Perform manual import with "Enable Database Locking" when Act field needs to be created
  6. Activate DataPlus with assigned key
  7. Renew DataPlus subscription if expired
  8. Email log file to Hogan Data containing script error
  9. Email error message to Hogan Data


Direct Link to This FAQ
http://kb.hogandata.com/?f=5120

Back to Top