When you run the Generate Salaries and Allowances payroll job, it may stall for several reasons.
We have compiled a list of possible causes for why the job can be stuck, along with steps to resolve them.
Multiple users accessing the screen
If multiple users are accessing a record, this can cause the job to lock.
To resolve this issue, all back office users should exit any CorePay screens while the job is running. If the job still fails after five minutes, clear the users' sessions in either back office or portal to release the system from the lock.
Pending jobs
There are Other CorePay jobs queued ahead of the Pay290 job for this pay group.
To resolve this issue, all back office users should exit any CorePay screens while the job is running. If the job still fails after five minutes, clear the users' sessions in either back office or portal to release the system from the lock.
Invalid username/password
The log file contains an invalid username or password.
To resolve this, retrieve the relevant text files, such as pay290.log0000 and pay290.trc0000.
🤓Tip: Where 0000 represents the pay group number.
To do this, check how to retrieve a log file then raise a new case online, referencing this article's title and include a copy of the log and trace file.
Incorrect weekend date
The weekend date on the calendar is incorrect.
To resolve this, retrieve the relevant text files, such as pay290.log0000 and pay290.trc0000.
🤓Tip: Where 0000 represents the pay group number.
To do this, check how to retrieve a log file then raise a new case online, referencing this article's title and include a copy of the log and trace file.
Oracle instance shutdown
The Oracle instance is shutting down.
To resolve this, retrieve the relevant text files, such as pay290.log0000 and pay290.trc0000.
🤓Tip: Where 0000 represents the pay group number.
To do this, check how to retrieve a log file then raise a new case online, referencing this article's title and include a copy of the log and trace file.
Invalid increment date
The increment date for the employee is invalid.
To resolve this, retrieve the relevant text files, such as pay290.log0000 and pay290.trc0000.
🤓Tip: Where 0000 represents the pay group number.
To do this, check how to retrieve a log file then raise a new case online, referencing this article's title and include a copy of the log and trace file.
Timestamp issue
A timestamp issue exists in the background files.
To resolve this, retrieve the relevant text files, such as pay290.log0000 and pay290.trc0000.
🤓Tip: Where 0000 represents the pay group number.
To do this, check how to retrieve a log file then raise a new case online, referencing this article's title and include a copy of the log and trace file.
Employee table update failure
A new employee is not updating correctly in the employee table.
To resolve this, retrieve the relevant text files, such as pay290.log0000 and pay290.trc0000.
🤓Tip: Where 0000 represents the pay group number.
To do this, check how to retrieve a log file then raise a new case online, referencing this article's title and include a copy of the log and trace file.