Greenstone Data Hub (GDH) - Error Listing

This page is to help assist you in trouble-shooting errors in the datahub. The datahub is the mechanism to guarantee delivery of messages between the ERP system (i.e., a Greenstone enterprise resource planning system like AGRIS or CINCH) and the third-party system.

Table of Contents:

1 Error Listing - AGRIS / RJO Hrvyst Integration
2 Error Listing - AGRIS / FieldAlytics Integration
3 Error Listing - CINCH / Agworld Integration
4 Sample “Dashboard”
5 Sample “Errors”

Error Listing - AGRIS / RJO Hrvyst Integration

Error Type	Error	Error sub id	Cause	Possible Resolutions

Error Type	Error	Error sub id	Cause	Possible Resolutions
RJO	HTTPRequest	The remote server returned an error: (400) Bad Request.	!SCHEDULE'S COMMODITY/LOCATION INVALID OR INACTIVE	Validate that the contract type and commodity are available at the location.
RJO	HTTPRequest	The remote server returned an error: (400) Bad Request.	h!INVALID FUTURES MONTH	Futures months cannot be edited in Hrvyst. This cannot be resent. Either cancel and reenter in Hrvyst or manually do in Agris.
RJO	HTTPRequest	The remote server returned an error: (400) Bad Request.	D!COMMODITY CODE NOT FOUND OR INACTIVE	Validate that the contract locations, and commodities available at the location are enabled. Next steps include: Confirm the locations/or commodity on the contract is enabled in AGRIS. Verify the transaction was entered correctly in Hrvyst.
RJO	HTTPRequest	The remote server returned an error: (400) Bad Request.	B!LOCATION CODE NOT FOUND	Review locations sent from Hrvyst equals the contract and or inventory locations in AGRIS. Next steps: Reject the error in datahub, correct invalid location in Hrvyst and resend from Hrvyst.
RJO	HTTPRequest	The remote server returned an error: (400) Bad Request.	!APPLY NAME/ID NUMBER NOT FOUND OR INACTIVE	Check both systems name ids exist and are active prior to resending. Next Steps: Reactivate account in AGRIS and resend from datahub. Confirm that the missing name is a result of a AGRIS Combine or merge name id event. Review existing processes and security to ensure names cannot be entered on the fly in Hrvyst.
RJO	HTTPRequest	The remote server returned an error: (400) Bad Request.	C!CUSTOMER NAME/ID NUMBER NOT FOUND	Check both systems name ids exist and are active prior to resending. Next Steps: Reactivate account in AGRIS and resend from datahub. Confirm that the missing name is a result of a AGRIS Combine or merge name id event. Review existing processes and security to ensure names cannot be entered on the fly in Hrvyst.
RJO	HTTPRequest	The remote server returned an error: (400) Bad Request.	When the error contains “…nameid=\"######\" delete=\"true\\…” it means that a Name Id was deleted in AGRIS. This could be the result of merging one Name Id into another in AGRIS. Hrvyst does not support deletions of Names.	A result of a Name address event in AGRIS. Combine/Merge or partial add then remove. Next steps: Determine Hrvyst next steps to ensure the contracts on the deleted name ID need moved to a new customer manually. Contact Hrvyst Support for more details.
RJO	Maximum retry attempts reached	Cannot access a disposed object. Object name: 'ServiceBusConnection has already been closed. Please create a new instance'.	Datahub	Result of a process within the Datahub that was aborted before completion. Contact AGRIS support immediately and review both AGRIS and Hrvyst to make adjustments in one or both systems to correct the failed ticket.
RJO	Maximum retry attempts reached	{"Code":200,"Message":"Success","MoreInfo":{},"Exception":null}. The server was able to successfully deliver but the remote server did not acknowledge with a "success" response in a timely manner. Review the remote system to determine if delivery was successfully prior to resending.	Connectivity issue between the Datahub and AGRIS.	Indicates that the Datahub was able to connect to AGRIS to start processing a message without a final “success or failure” response within 2 min. Next Steps: Confirm the transaction was updated successfully in both systems. If the data was successfully updated in both systems - Reject the error message in Datahub. If successful in AGRIS but not Hrvyst - Update Hrvyst manually or contact Hrvyst support for next steps. If Not successful in AGRIS and Hrvyst - Resend from Datahub.
RJO	HTTPRequest	The remote server returned an error: (400) Bad Request.	2!SCHEDULED QTY CANNOT BE LESS THAN APPLIED/SETTLED	Typically encountered when the price schedule balances do not match between Agris and Hrvyst. Next Steps: If they do not match, the contract must be manually priced in Agris. This would only happen if pricings/edits occurred in Agris and not Hrvyst.
RJO	HTTPRequest	The remote server returned an error: (400) Bad Request.	No error listed in the message	Contact Greenstone Support immediately for additional steps. As an alternative Verify both Hrvyst and AGRIS and make adjustements if needed. Next Steps: Confirm AGRIS and Agent versions are at the supported levels.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	B!LOCATION CODE NOT FOUND	Validate that the contract locations, and commodities available at the location are enabled. This would only happen if a location code wasn’t mapped or mapped incorrectly. Typically only related to startup / beginning balance loaded contracts entered in error. Next steps include: Confirm the locations/or commodity on the contract is enabled in AGRIS. Verify the transaction was entered correctly in Hrvyst. If multiple instances are found contact Hrvyst support to discuss next steps to review processes and or beginning balances loaded between both systems.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	1!CONTRACT NUMBER OR SCHEDULE NOT FOUND OR INVALID	Is a mismatch of contract # and/or schedule # between Hrvyst and AGRIS. A result of either user data entry error in Hrvyst or a beginning balance entry error. Next Steps: Research the Hrvyst contract schedule details and compare to AGRIS to determine adjustments required
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	E!INVALID CONTRACT TYPE	Indicates that the Hrvyst Contract type mapping is incomplete or invalid. Next steps: Review Hrvyst setup for contract types. Confirm contract types are supported by the interface. Update your company’s policy based on changes to address this error.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	D!COMMODITY CODE NOT FOUND OR INACTIVE	Validate that the contract locations, and commodities available at the location are enabled.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	S!INVALID WEIGHT BASE	Validate that the contract type and commodity are available at the location.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	T!INVALID GRADE BASE	Validate that the contract type and commodity are available at the location.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	C!CUSTOMER NAME/ID NUMBER NOT FOUND OR INACTIVE	Check both systems name ids exist and are active prior to resending. Next Steps: Reactivate account in AGRIS and resend from datahub. Confirm that the missing name is a result of a AGRIS Combine or merge name id event. Review existing processes and security to ensure names cannot be entered on the fly in Hrvyst.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	!APPLY NAME/ID NUMBER NOT FOUND OR INACTIVE	Check both systems name ids exist and are active prior to resending. Next Steps: Reactivate account in AGRIS and resend from datahub. Confirm that the missing name is a result of a AGRIS Combine or merge name id event. Review existing processes and security to ensure names cannot be entered on the fly in Hrvyst.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	!SCHEDULE'S COMMODITY/LOCATION INVALID OR INACTIVE	Validate that the contract locations, and commodities available at the location are enabled. This would only happen if a location code wasn’t mapped or mapped incorrectly. Typically only related to startup / beginning balance loaded contracts entered in error. Next steps include: Confirm the locations/or commodity on the contract is enabled in AGRIS. Verify the transaction was entered correctly in Hrvyst. If multiple instances are found contact Hrvyst support to discuss next steps to review processes and or beginning balances loaded between both systems.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	j!SCHEDULED QUANTITY MUST BE POSITIVE	Review the transaction with Hrvyst. Suggests that more bushels are being applied to the AGRIS contract than available.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	!CANCEL CONTRACT FAILED	Review contract status in AGRIS and contact Hrvyst support if further assisatnce is needed. Typically the contract request sent is due to invalid data or other error messages reported at the same time should be resolved prior to resending from the Datahub.
RJO	Maximum retry attempts reached	The remote server returned an error: (400) Bad Request.	h!INVALID FUTURES MONTH	Futures months cannot be edited in Hrvyst. This cannot be resent. Either cancel and reenter in Hrvyst or manually do in Agris.
GDHEvents	Maximum retry attempts reached	StartIndex cannot be less than zero. (Parameter 'startIndex')	Value passed from the third party system is not acknowledges as a valid value	Contact Greenstone Support.

Error Listing - AGRIS / FieldAlytics Integration

Error Type	Error	Error sub id	Cause	Possible Resolutions

Error Type	Error	Error sub id	Cause	Possible Resolutions
AGRIS	CreateFarmError	CLIENT CODE MISSING OR INVALID	The Cusotmer or vendor record sent to AGRIS was not found	Research and update the client code in the originating system to the correct account number. Reject the message and resend once corrected or update the Datahub Farm cross-reference table and message to use the correct client code and resend.
AGRIS	CreateFarmError	FARM CODE IS INVALID.	The Farm Code in the cross reference table does not exist in AGRIS.	Review the Datahub cross reference table for the farm in question and manually match / update to include the farm referenced in AGRIS then resubmit.
AGRIS	CreateFieldError	FARM CODE MISSING OR INVALID.	The field could not find the associated farm in the cross reference.	Review the Datahub cross reference table for the farm in question and manually match / update to include the farm referenced in AGRIS then resubmit. If a Farm is not found .. Manually add in AGRIS and then update the DataHub cross reference. Resync the customer from the 3rd party system
AGRIS	CreateFieldError	Error in pushing message to the queue	Invalid data was included in the request from the originating system.	Resend the messsage from the datahub. The error provided in the top black box will provide additional troubleshooting tips.. Use the resulting data to make a decision to update the cross referenece docs and message before resending or reject the request and delete the cross reference entry and resubmit from the orginating system
AGRIS	UpdateFieldError	FIELD NAME ALREADY ASSIGNED TO FARM.	AGRIS does not allow more than one field name with the exact same Name/Descripton under the same farm	Update the third party system to ensure the field names are unique per farm.
AGRIS	CreateWorkOrder	CreateWorkOrderError
AGRIS	CreateDeliveryTicketError	INVENTORY ITEM NUMBER NOT FOUND OR INACTIVE	AGRIS item was not found for the specific location of the work order.	Review the work order and then AGRIS inventory to ensure the item exists at that location.
GDHEvents	Maximum retry attempts reached	StartIndex cannot be less than zero. (Parameter 'startIndex')	Value passed from the third party system is not acknowledges as a valid value	Contact Greenstone Support.

Error Listing - CINCH / Agworld Integration

Error Type	Error	Error sub id	Cause	Possible Resolutions

Error Type	Error	Error sub id	Cause	Possible Resolutions
GDHEvents	Agworld webhook		System event has happened that does not allow processing	Immediately contact Greenstone Support.
CINCH	CrossReferenceError		The provider configuration does not have a complete record	Navigate to the provider screen and review the cross reference configuration for the item in question prior to resending.
GDHEvents	Maximum retry attempts reached	StartIndex cannot be less than zero. (Parameter 'startIndex')	Value passed from the third party system is not acknowledges as a valid value	Contact Greenstone Support.

Sample “Dashboard”

Provider: Depicts the third-party API (Application Programming Interface) that communicating with the datahub.
Completed: The blue number shows the number of messages that are completed without exception. Click the number to see the list which can be filtered in various ways.
Failed to deliver: The blue number shows the number of messages that the hub could not deliver to are completed without exception. Click the number to see the list which can be filtered in various ways.
Errors: The blue number shows the number of messages that contain errors from the destination system. Click the number to see the list which can be filtered in various ways.
Rejected: The blue number shows the number of error messages from the destination system that someone evaluated and made a decision to Reject the message for various reasons. Click the number to see the list which can be filtered in various ways.

Sample “Errors”

Filters allow searching for and listing of more specific messages:

FIlter Created: Enter applicable date information.
Filter Request Type: Enter applicable message type information.
Filter System Type: Select system type from the drop-down list.
Filter Document Number: Enter applicable message number information.
Filter Error: Enter applicable message number information.
Filter Provider: Select Provider type from the drop-down list.
Select Top Records: Select the number of messages to display from the drop-down list.

Enter the information you are looking for in the applicable Filter column and then press the Filter button to search for that information.

Press the Reset button to clear the information in the applicable Filter column and shows all available messages in the filter.

Press the Edit button to see the detail of the message.