Sequence Contains More Than One Element Error
Symptom
"Sequence Contains More Than One Element" error occurs during Order Fulfillment transactions.
Cause
This error happens when duplicate document numbers are assigned to different transaction types (e.g., one is an order, one is an invoice). This may not be obvious in the Dynamics GP interface because the invoice transaction has likely already been posted. Posting typically moves transactions from work tables to history tables, but this doesn't always happen.
Solution
- Run the Remove Sales Documents utility in Dynamics GP. This utility moves sales records and removes any documents with no remaining quantities that haven't been moved to history.
- Consult the Dynamics GP user guide for specific steps on running this utility.
Best Practice
We recommend setting up sales documents with a prefix to uniquely identify invoices from orders. This prevents errors and confusion, as sequential numbering will eventually lead to duplicates.
Related Articles
GZip magic Number Error
Symptom "The Magic number in GZip header is not correct" message is displayed. Cause This rare error indicates that the IIS process on the server may have become corrupted. Solution Restart IIS on the server where PanatrackerGP is hosted: From the ...
INIT error on Android device
This error typically appears as "INIT ERROR Version is not in the proper format." Follow these steps to resolve it. Steps Log out and fully close the PanatrackerGP application on the device. Log in to your PanatrackerGP Portal and navigate to the ...
SQL Error is displayed: OpenAccessException
Symptom "OpenAccessException: Telerik.OpenAccess.OpenAccessException: SQL exception on 'CREATEDATABASE Panatracker'; already exists." Cause This error occurs after the Panatracker transaction database has been modified or moved. The Panatracker SQL ...
An error occurred performing the GenericTransaction transaction
About Generic Transactions The Generic Transaction feature is not used with standard Dynamics GP operations. It's a framework introduced in version 6.3 for custom data-collection transactions developed through Panatrack consulting services. Generic ...
Error message displayed on device: ThreadAbortException: Thread was being aborted.
Symptom "ThreadAbortException: Thread was being aborted" error appears on the handheld device. Cause This message often indicates that your SQL Server or Application server was restarting or experiencing a process failure while a transaction submit ...