PHI Loader.accdb: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 20: Line 20:


=== Problem log ===
=== Problem log ===
* 2019-02-14 "
* 2019-01-30  Task error message: Run time error 58.  
* 2019-01-30  Task error message: Run time error 58.  
**Finding: 2 copies of CSV file, one OUTSIDE of the PHI_CSV_Archive, and the other copy is INSIDE the PHI_CSV_Archive.   
**Finding: 2 copies of CSV file, one OUTSIDE of the PHI_CSV_Archive, and the other copy is INSIDE the PHI_CSV_Archive.   
***Solution: relabeled the copy INSIDE the PHI_CSV_Archive and put extension _Twin on the end.  Ran the phi loader task scheduler.  Problem solved
***Solution: relabeled the copy INSIDE the PHI_CSV_Archive and put extension _Twin on the end.  Ran the phi loader task scheduler.  Problem solved
* 2019-02-14 "
* 2019-01-15 "
* 2019-01-15 "
* 2019-01-10 "
* 2019-01-10 "

Revision as of 16:35, 2019 February 20

X:\CCMDB\PHI\PHI Loader.accdb is an Access program that processes data in PHI.mdb as part of PHI copy automation.

Locked phi loader.lccmdb

see Lccmdb and ldb files

Missing, corrupted or stuck Phi Loader

We have had some problems with phi_loader over time.

When this sort of thing happens, restore a clean version of PHI_Loader.

Restoring PHI_Loader from backup

  • Close error message, and Click End
  • Navigate to X:\CCMDB\PHI\PHI Loader.accdb_Backup
  • Before you restore the backup
    • Try to log in to the PHI_Loader using the pw (located on a list in M shared drive). If this does not work then
    • Go to Task Manger to check if there is any access program running in Application and Process Tab. If they are running select application or process and press: End. If this does not work then:
    • reboot computer - this will disconnect any access programs that are still running in back round that you cannot see.
  • make a copy of PHI Loader.accdb_Backup in the same folder
  • removed the words COPY and Backup so the file name is as shown: PHI Loader.accdb

Problem log

  • 2019-02-14 "
  • 2019-01-30 Task error message: Run time error 58.
    • Finding: 2 copies of CSV file, one OUTSIDE of the PHI_CSV_Archive, and the other copy is INSIDE the PHI_CSV_Archive.
      • Solution: relabeled the copy INSIDE the PHI_CSV_Archive and put extension _Twin on the end. Ran the phi loader task scheduler. Problem solved
  • 2019-01-15 "
  • 2019-01-10 "
  • 2018-12-20 "
  • 2018-11-16 Task error message: Run time error 3078, "Microsoft Access can't find the input table or query tmp.
    • Solution: Replaced PHI loader with backup copy
  • 2018-11-15 "
  • 2018-10-31 "
  • 2018-10-23 "
  • 2018-08-23 Task error message: Run time error 7874, "Microsoft Access can't find the object "AppendNewRecords"
    • observation: this occurred at peak time an lots of staff sending.
      • Solution: Replaced PHI loader with backup copy.
  • 2018-06-19 Problem on Pull script found out the PHI loader is gone.
  • 2018-05-28 Task error message Run time error 3874. vbs debug highlighted the following error; DoCmd.OpenQuery "DeleteALLTempData"......
    • E6 last csv sent when error message came up. E6 sent an email to fix a serial#
  • 2018-04-20 Task error message: Directory name, or volume label syntax is incorrect. Microsoft VB error message: Run-Time error 3078: The MS Access database engine cannot find the input table or query L_PHI. Make sure it exists and that its name is spelled correctly.
  • 2018-03-09 there was an error "Microsoft Access can't find the object "AppendNewRecords"
  • 2018-02-28 "
  • the whole file was missing at some point

change log

19:49, 2014 July 31 (CDT)

  • added check for PHI.mdb to be present. Ttenbergen 19:49, 2014 July 31 (CDT)