Troubleshooting application-related errors

This section lists possible error messages and some direction on how to troubleshoot them.

If you are experiencing technical difficulties uploading your application to the PMS Portfolio Management System, please contact AEMO Australian Energy Market Operator IT Support Hub.

The application fails without proper warning if the User Rights Management (URM User Rights Management; see the Guide to URM on AEMO's website) password expires. The URM password expires every 90 days.

If there are missing headers in the uploaded csv file, or extra columns (for example by addition of commas in any text), the application will not be processed further.

Sample error message	Resolution
Document cannot be uploaded	Check if the document contains all necessary files and reupload the document.
Portfolio must be selected.	Select a portfolio to associate with the application.
Incorrect file format	Upload the correct format of the file.
<FILE_NAME.zip> is below 1 byte size and it much be between 1 byte and 20 mb.	Make sure the file size is between 1b and 20 mb.
<FILE_NAME.zip> is more than 20 mb size and it much be between 1 byte and 20 mb.	Make sure the file size is between 1b and 20 mb.
Cannot find WDRU_Group.csv	Make sure you zip file has the correct WDRU_Group.csv file and reupload the zip file Check the zip file contains the WDRU_Group.csv file. This is a mandatory file and if the file name is misspelt or missing this error pops up.
Cannot find WDRU_NMI.csv	Make sure you zip file has the correct WDRU_NMI.csv file and reupload the zip file Check the zip file contains the WDRU_NMI.csv file. This is a mandatory file and if the file name is misspelt or missing this error pops up.
<Name of header> not found	Indicates a header is missing from the csv file
<Name of header> not provided	Indicates a header exists but a value is not provided in the csv file.
Application reference must be provided	Add in an application reference in WDRU_Group.csv file
Application .zip cannot be read	Make sure you are using a correctly configured zip file with the three mandatory csv files only.
NMI already exists	The NMI is already classified as a WDRU and you cannot add it.
NMI not provided	Add the NMI to the WDRU_NMI.csv file
NMI <NMI> does not exist in MSATS	Correct or remove the NMI in the WDRU_NMI.csv file
NMI <NMI> is more than max 11 digits limit.	Correct or remove the NMI in the WDRU_NMI.csv file
NMI <NMI> is less than 10-digit limit	Correct or remove the NMI in the WDRU_NMI.csv file
Retail customer cannot be empty	Add the retail customer against each NMI in the WDRU_NMI.csv file
Retail customer must be between 1 and 120 characters	Amend the retail customer entry to meet validation requirements in the WDRU_NMI.csv file
Baseline Methodology Id cannot be empty	Add a numerical Baseline Methodology Id against each NMI in the WDRU_NMI.csv file
MRC (MW) cannot be empty	Provide an MRC against each NMI in the WDRU_NMI.csv file or against the Group in the WDRU_Group.csv file
MRC (MW) must be between 1 and 9999	Amend the MRC entry to meet validation requirements in the WDRU_NMI.csv file or the WDRU_Group.csv file
MRC must be a numeric value	Amend the MRC entry to meet validation requirements in the WDRU_NMI.csv file or the WDRU_Group.csv file
MRC reason cannot be empty	Include an MRC reason against the NMI in the WDRU_NMI.csv file
NMI <NMI> listed in WDRU_NMI_ExclusionDay.csv document cannot be found in WDRU_NMI.csv	Amend the NMIs to ensure consistency between WDRU_NMI.csv file and WDRU_NMI_ExclusionDay.csv