If this message appears | It means | Try this to fix it |
|---|---|---|
“Maximum number of transactions reached. The import file is not allowed to have more than 9999 transactions, the remaining transactions will be skipped.” | This means that you have over 9999 transactions in the external file and have exceeded the maximum allowed by Denali. | You could break the external file into two files to decrease the number of transactions and retry the import again for those transactions that were skipped. |
“Tran # xxxxx - Tran Date xx/xx/xxxx is not within fiscal calendar.” | This means that the indicated transaction you have tried to import is not within the fiscal calendar in which you are currently working. | You can change the transaction date in the external file to correspond with the fiscal calendar you are working in, or you might need to modify your organization’s fiscal calendar to accept the transaction. To modify your fiscal calendar, refer to Setting Up the Fiscal Calendar. |
“Tran # xxxxx - Tran Date xx/xx/xxxx is less than Block Date.” | This means that the indicated transaction date precedes the date you have determined as the Date Block Period for accepting transactions in the system. | You can either change the date in the external file to a date after the Date Block Period, or modify the Date Block Period in Denali. |
“Invalid date detected. xx/xx/xxxx is an invalid date.” | You will receive this error message when the date is outside of the allowable date range. For instance, if the date is accidentally entered as 02/04/1007, you will receive this error message. | Check the transaction dates in your external file and retry the import process. |
“Invalid date format. xxx is an invalid format length.” | This means that the date is not in the required format of MM/DD/YYYY. | Revise the date format in the external file to match the required format of MM/DD/YYYY. For additional information, see File Formats Supported by Denali for Importing Transactions. |
“Record xxx in the import file is the wrong length. Record skipped. The record is x characters too short (too long).” | The import file must be in the proper format to be imported. If a transaction contains too few, or too many characters, it cannot be imported. | You will need to adjust your external file to meet the file format requirements for importing into Denali. Refer to File Formats Supported by Denali for Importing Transactions for the specific requirements. |
“Record xxxxx in the import file is not correctly delimited with tabs. Record skipped.” | There are specific requirements when you import a tab-delimited file, and this indicates that there is an error in the file format. | Refer to File Formats Supported by Denali for Importing Transactions for the correct format and make necessary changes to your external file. Then you can retry the import process. |
“Record xxx in the import file is not correctly delimited with semi-colons. Record skipped.” | There are specific requirements when you import a semi-colon delimited file, and this indicates that there is an error in the file format. | Refer to File Formats Supported by Denali for Importing Transactions for the correct format and make necessary changes to your external file. Then you can retry the import process. |
“The import file exceeds the maximum number of 32767 records. Please fix the file and try again.” | This means that you have exceeded the maximum allowance of records that can be imported at one time by Denali and the import process was cancelled and no transactions were imported. | You could break the external file into separate files to decrease the number of records and retry the import process. |
“Unable to open the file xxx. Please make sure no program is using this file and try again.” | The file you are attempting to import is open by you or another user and Denali cannot open it. | You will need to close the file and/or program using the external file and retry the import process. |
“An unexpected error has occurred. The error number is xxx at record xxxxx with message x.” | Due to the complexity of this error, we recommend contacting Customer Support for assistance at (800) 390-7053. | |