PHI Loader.accdb

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

Troubleshooting tree

The command window "black blob" on the Data Processor PC stays open and there is an error msg.

If task window is stuck open and there is no error message:

• Solution: close Task window. Next time it runs, files will get moved without an issue.

Run time Error 3051

If error msg: The Microsoft access database engine cannot open or write to the file. It is already opened exclusively by another user,or you need permission to view and write its data

• sender had error message: system resource exceeded
  • VB script error: DoCmd.TransferText acImportDelim, , "tmp", directory & "\" & strFile, True
    • Solution

Don't know what to solution is yet as Tina hot sure why to problem is occurring. What are you doing when this happens, then? And, is this still an issue? It seems it was happening and then it just stopped.

• SMW

• Cargo

• Categories

Run time error 58

If error msg:-File already exists then:

• 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
• and log occurrence under #Task error message: Run time error 58-File already exists

Run time error 3078

If the msg: Microsoft Access can't find the input table or query tmp then:

• Solution:
  • which table is missing? If it is one you would see in Centralized data.mdb then check if that file is somehow not accessible; same for PHI
  • if another table whose name means nothing to you is missing, then it's probably a table in PHI loader that got corrupted; Solution: Replace PHI loader with backup copy
• and log occurrence under #Task error message: Run time error 3078

Run time error 7874

If the msg: Microsoft Access can't find the object "AppendNewRecords then:

• observation: this occurred at peak time an lots of staff sending.
  • Solution: Replaced PHI loader with backup copy.
• and log occurrence under #Task error message: Run time error 7874 "Microsoft Access can't find the object "AppendNewRecords"

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

Task error: no error message, but phi loader task window stuck open

• '2019-May-21'
• '2019-Apr-04' - noted that only one of 4 CSV file were moved from output PHI folder on Regional server to X CCMD PHI folder. 3 other sent files remained stuck on Regional Server. No Error message, so not clear why this occurred.

Task error message: Run time error 3051 The Microsoft access database engine cannot open or write to the file.

It is already opened exclusively by another user,or you need permission to view and write its data.

• 2019-04-08-Occurring during sending
• 2019-03-22
• 2019-03-21
• 2019-03-18
  • this is odd, there were 7 files backup waiting to be loaded into PHI. Ran debug and closed. Next task ran, moved 6 files in PHI and moved copy to back up. 1 files not moved. HSC_ICUd. Also noted that there was 2 folders created in the CCMDB PHI folder, "new Folder" and New folder 2. The folder date/ time is when task ran second time after debug. Makes no sense to me at the moment.
  • Ran debug then closed closed out. Task scheduler ran and moved HSC_ICUd no problem. No one reported sending errors.
  • third time this error occurred today, just ignored it and PHI loader unlocked itself.

Could it be that this Scheduled task is running while people are sending and it is hanging/locking because tasks runs right in the middle of someone sending? And has this happened since?

• SMW

• Cargo

• Categories

• 2019-03-15 OAK MICU - collector sending error message system resource exceeded (Lisa spoke to Tina)

Task error message: Run time error 58-File already exists

• 2019-04-19 STB_MedD -locked when it ran April 19th. The STB MedD file was sent April 18th - file already exists in the PHI_CSV_archive
• 2019-03-12 HSC ICUA
• 2019-03-12 HSC D4
• 2019-03-12 HSC A4
• 2019-03-07
• 2019-02-26
• 2019-02-14
• 2019-01-30

Task error message: Run time error 3078 Microsoft Access can't find the input table or query tmp

• 2019-04-02 - STB ACCU reported sending problem "Systems resources exceeded" Debug show hang up at DeleteAllTempdata
• 2019-02-20
• 2019-01-15
• 2019-01-10
• 2018-12-20
• 2018-11-16

Task error message: Run time error 7874 "Microsoft Access can't find the object "AppendNewRecords"

• 2018-11-15
• 2018-10-31
• 2018-10-23
• 2018-08-23

Old miscellaneous errors

• 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

• 2019 Apr 10 - changed task schedule to only run once a day to see if this will stop sending errors.
• 2019 Mar 20 - decided to change schedule for this but did not have rights to; sent email to service desk Ttenbergen 16:25, 2019 March 20 (CDT)
• 2014 July 31 - added check for PHI.mdb to be present. Ttenbergen 19:49, 2014 July 31 (CDT)