Procare Network Status

Service Operational Maintenance Issue/Outage
Tuition Express
Procare Cloud
MyProcare
  • – Operational
  • – Maintenance
  • – Issue
Tuition Express
Procare Cloud
MyProcare

Known Issues and Resolutions

Payroll Report Inconsistencies

Symptom

In specific circumstances (see cause below), you may find that earnings and withholdings on certain payroll reports do not show the expected amounts. This may occur on any report that includes both earnings and withholdings.

Cause

This will happen only if you post and print checks on different days—and choose a Date Range for the report that does not include both the Post Date and Print Date. With the recent release of version 2018.6, earnings are now based on Print Date (date of issue), while withholdings are based on Post Date (date of entry).

Work Around

While we work on a long-term solution, the best course of action is for you to either:

  1. Post and print checks on the same day (so the dates match) – or –
  2. Make sure the Date Range of your report is broad enough to include both the date checks were posted and the date they were printed.

Royalties Report Shows Employee Filter

Issue

When running one of the two new Royalties Reports, the Select Filter (image below) is for employee information. The filter does not apply to these reports and should not be shown.
Employee Filter on Royalties Report

Although it shouldn’t be there, the employee Select Filter has no effect on the Royalties Reports, so it’s perfectly fine to use those reports. The filter will be removed in the next scheduled Procare update.

Database Backup Failed

Issue

When a non-Cloud customer attempts to restore a backup on a new computer (for example, when moving Procare to a new server), they may receive the following error:

Database backup FAILED!

The operating system returned the error ’32(The process cannot access the file because it is being used by another process.)’ while attempting ‘RestoreContainer::ValidateTargetForCreation’ on ‘C:\Program Files\\Procare\Database\Procare.mdf’.

Although a second message may say the restore was successful, it really was not successful. The data will be as it was before you attempted to restore the backup.

Cause

The double backslash in the file path (\\Procare) causes the restore process not to be able to locate the backup file.

For the time being, please Contact Support for assistance in restoring your backup. This issue will be fixed in the next scheduled Procare update.

Still experiencing an issue or have questions? Contact Support at 800-964-1729, M – F, 4 AM – 5 PM PST

Search Procare Support