Common ESS Errors

How do I re-export finalised timesheets?

Logon to ESS and change to the Timesheet Admin role, click on Finalized then click the "Re-export finalized Timesheets" button. 

On screen error:
Error creating datasource: employeeLeavecalendar- calendar data

Check:

• Periods/dates

• Holiday Group (check for duplicates)

• Leave tables (dates, etc)

• Leave Credit tab (check for duplicates)

• Leave Request settings (check for duplicates)

Login details incorrect

Check:

• end date on Appointment

• appointment is Default and Active

• no planned termination date

• no termination date

• using the correct password

• ESS Username and PayGlobal Logon is the same. If they are the same the employee’s ESS logon will not work. They MUST be different.

You are unable to access documents due to an invalid data setup. Please contact Payroll.

There is no ESS Security Profile attached to the Employee’s WAP.

The wrong days are available to apply for leave in the ESS calendar

If the Leave Request settings are set to "Roster", then the roster might be setup incorrectly or starting from the wrong date/day. There also might not be any shifts attached to the roster or no start and end times on the shifts attached to the roster.
If the Leave Request settings are setup as "Profiled", then check the employee has Profiled hours.

Error:
Error calculating projected annual leave balance for employee: 'xxxxx'.
System.InvalidCastException: Specified cast is not valid.

Solution:
The employee record has NULL (empty) values in fields used by ESS to calculate balance or projected balance.
Populate missing fields on employee record with “0.00”.
Examples are:
- Profiled Hours under the Payroll > Payments tab e.g. Saturday and Sunday.
- All fields in Leave area > Annual Leave tab.

Error:
Error creating datasource:EmployeeLeaveTeamCalendar-CalendarData ---> System.NullReferenceException: Object reference not set to an instance of an object.

Solution:
Error can be caused by missing or incorrect settings on employee record for:
1. Leave request setting are missing or incorrect settings (e.g. expiry date added).
2. Holiday Group is missing from employee record > Payroll > Contract tab
3. Roster/Tour/Shift are missing or have changed.
4. Leave reasons are missing.
5. Problem can also be caused by an invalid break code in one of the timeband tables - scripts to find them:
SELECT EmployeeCode,BreakCode FROM CurrentActualTimeBand WHERE BreakCode NOT IN (SELECT BreakCode FROM [Break])
SELECT EmployeeCode,BreakCode FROM CurrentRosterTimeBand WHERE BreakCode NOT IN (SELECT BreakCode FROM [Break])
SELECT EmployeeCode,BreakCode FROM HistoricalActualTimeBand WHERE BreakCode NOT IN (SELECT BreakCode FROM [Break])
SELECT EmployeeCode,BreakCode FROM HistoricalRosterTimeBand WHERE BreakCode NOT IN (SELECT BreakCode FROM [Break])
SELECT EmployeeCode,BreakCode FROM ScenarioRosterTimeBand WHERE BreakCode NOT IN (SELECT BreakCode FROM [Break])
SELECT *,BreakCode FROM ShiftTimeBand WHERE BreakCode NOT IN (SELECT BreakCode FROM [Break])

Error:
TEST database experiences an error when performing ESS functions that are working fine in LIVE database.

Solution:
The solution is to refresh Test.
If Test cannot be refreshed and a solution must be found, a consultant can be engaged to assist further.

Error:
An error occurred adding leave requests to open periods where employeeCode='xxxxx'.
System.NullReferenceException: Object reference not set to an instance of an object.

Solution:
Holiday Group missing from Employee record > Payroll > Contract tab.

Error:
An error occurred getting the timebands for date prior to leave where employeeCode='xxxxx and date='DD/MM/YYYY 12:00:00 am'

System.NullReferenceException: Object reference not set to an instance of an object.

Solution:
Holiday Group missing from Employee record > Payroll > Contract tab.

Error:
Object reference not set to an instance of an object. User is unable to delete Timesheet with status 'Not submitted' using Process Flow Delete.

Solution:
Check for submitted leave requests in period
Delete them from PG and using Process Flow Delete.
Re-submit leave. Process Flow Delete Timesheet before regenerating.

Error:
Server was unable to process request. ---> Error occurred when accessing the Timekeeping Service. Please check the application log file for full error details.
Object reference not set to an instance of an object.

Solution:
Employee is missing roster or roster does not contain Shifts. Or Shifts are missing hours.

Error:
Error creating datasource:ActiveItems-GridData ---> System.NullReference
Exception: Object reference not set to an instance of an object. at PayGlobal.Hrss.CoreBusiness.ActiveItems.Objects.ActiveItemsModel.FormatStatus(String status)

Solution:
Find workflow items with missing Status field and delete them using ProcessFlowDelete.
The following SQL script can be used to find errored workflows:
SELECT LodgedByEmployeeCode, DateCreated, Description FROM [Workflow].[WFE_ProcessFlowInstance] WHERE Status IS NULL

Error:
Exception message: Error creating datasource:CourseApprovalList-Invalid-GridData
Inner exception message: Object reference not set to an instance of an object.

Solution:
Download PayGlobal application version currently in use and copy bridge components to ESS\Bin folder. Run CommandUpdater.exe (answering 'Y' to all questions) and MVCCommandProcessor (Upgrade).
PayGlobal application can be downloaded from https://enterprise-support.myob.com/payglobal/myob-payglobal-downloads?

Error:
Error submitted calculation flow for guid: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'.
System.NullReferenceException: Object reference not set to an instance of an object.

Solution:
Employee has expired or invalid WAP Appointment.

Error:
Error creating datasource:SiteTemplate-MenuData ---> PayGlobal.Hrss.Presentation.UI.TransferObjects.TransferObjectException: Unable to evaluate menu item expression. Expression was {busobj:CoreSiteView.GetMenuItems('{var:datasourceName=Menu.MenuItems}')} ---> System.NullReferenceException: Object reference not set to an instance of an object.
at PayGlobal.Interface.Hrss.Query.QueryFacade.GetWhereSqlFragmentFromQuery(String queryCode)

Solution:
ESS Admin Role is using a employee Query that has been deleted. Query needs to be re-created.

Error:
There is a gap between a pay period with the end date of 'DD/MM/YYYY 12:00:00 a.m.' and the next pay period with the start date of 'DD/MM/YYYY 12:00:00 a.m.' for the employee xxxxx.

Solution:
Check period for a gap in the calendar when sorted by Period Sequence ID. If there is a gap, entries in the calendar after the gap will need to be removed and calendar re-generated.

Error:
Exception: The string was not recognized as a valid DateTime. There is an unknown word starting at index 18.

Solution:
Delete the LastControllerUpdate record in the HRSSSettings table.
DELETE FROM HRSSSettings WHERE [Key] = 'LastControllerUpdate';

Error:
Attempted to divide by zero.  at System.Decimal.FCallDivide(Decimal& d1, Decimal& d2)

Solution:
Custom workflow referencing Profiled Hours for a given day, that were set to '0.00' causing workflow calculation to fail.

Error:
System.Exception: Error refreshing form flow ---> System.NullReferenceException: Object reference not set to an instance of an object.

Solution:
Rates are missing from Award.

On screen error:
You have encountered an error during authentication. Click the link to try again. If problem persists, contact your administrator.

ESS error:
PayGlobal.Hrss.CoreSite.Objects.OidcEmployeeMapper | Caught at OidcEmployeeMapper:  An exception occurred on a Workflow service. Workflow engine is not aware of tenant with id: ba81e050-ec65-11df-98cf-0800200c9a66. This may be due to the tenant not being configured in the workflow engine or the workflow engine was unable to start the tenant - most likely due to invalid configuration. See the Workflow log for further details.

Workflow log error:
This may be due to the tenant not being configured in the workflow engine or the workflow engine was unable to start the tenant - most likely due to invalid configuration.
at PayGlobal.Workflow.Wcf.Infrastructure.WcfTenantContext..ctor(ITenantConfigurationProvider configurationProvider)

Solution:
There was a change made to the Tenants.config file that caused it to be corrupted or not well formed.

On screen error:
Timeout calling the workflow engine. This may be due to the workflow engine being unavailable or being too busy to respond timely to requests.

Solution:
Increase all the sendTimeout settings on the bindings.config file that is found in ESS 'Bin' subfolder, there will be more than one.
If they are set to 00:01:00, they should all be changed to 00:03:00 (3 minutes).