Sign-in information is incorrect / "Invalid session..." (followed by a string of characters)
These error messages mean that the Intacct credentials that Nexonia uses to connect to Intacct could not be validated, so Nexonia could not connect to Intacct to run the Configuration Sync.
If the Intacct Administrator username and/or password have changed recently, that is likely the cause.
In Nexonia, please navigate to Intacct* > Integration Setup > Edit Parameters, and ensure that the Company ID, User ID and User Password are correct and match the Intacct Administrator credentials as entered on the Intacct login form.
You can then initiate a configuration sync from Intacct* > Configuration Sync > Synchronize Now.
Invalid session : This user is in INACTIVE state
This error message means that the Intacct administrator account associated with the login credentials that Nexonia uses to connect to Intacct is no longer active, so Nexonia could not connect to Intacct to run the Configuration Sync.
In Nexonia, please navigate to Intacct* > Integration Setup > Edit Parameters, and ensure that the Company ID, User ID and User Password are correct and match the credentials of an active Intacct Administrator.
If the Intacct administrator has recently been made inactive, they should either be re-activated in Intacct, or the Intacct login credentials stored in Nexonia should be updated to match those of an active Intacct Administrator.
You can then initiate a configuration sync from Intacct* > Configuration Sync > Synchronize Now.
Invalid session : This user is in LOCKEDOUT state
This error message means that the Intacct administrator account associated with the login credentials that Nexonia uses to connect to Intacct is locked out from the Intacct side, so Nexonia could not connect to Intacct to run the Configuration Sync.
This is likely the result of repeated login attempts with invalid credentials, either by the automated Nexonia integration, or directly on the Intacct login form by the Intacct administrator.
The administrator's Intacct access can be restored directly from the Intacct login form by attempting to log in and then following the prompts.
If the login credentials are changed, please update them in Nexonia by navigating to Intacct* > Integration Setup > Edit Parameters, and ensuring that the Company ID, User ID and User Password are correct and match the credentials of an active Intacct Administrator who is not currently locked out.
You can then initiate a configuration sync from Intacct* > Configuration Sync > Synchronize Now.
No permission for API operation 'READ' on objects of type <object name>
Nexonia uses a set of Intacct login credentials to connect to Intacct. This error message usually means that the Intacct Administrator to whom those credentials belong does not have the necessary permissions in Intacct to access an object that is part of the configuration sync.
The object name will appear in the error message.
To resolve this, ensure that the Intacct administrator user has the necessary role permissions/subscriptions in Intacct to access the object referenced in the error message.
UnknownHostException: api.intacct.com
The connection attempt to Intacct failed. In a nutshell, Nexonia called, but Intacct didn't answer. Usually this is a temporary issue and initiating the sync manually from Intacct* > Configuration Sync > Synchronize Now will result in a successful sync.
There is no harm in re-attempting the configuration sync when you see this error.
'<user name>' is the user running this synchronization and would be disabled as a result of running this integration. Please make sure that the integration is run manually by a user that's part of the integration.
The synchronization to Intacct will align the Nexonia active user list with the Intacct employees and/or vendors that qualify for integration. This error message means that the logged-in user who has initiated the synchronization was not synchronized from Intacct and/or does not have a matching employee or vendor record in Intacct.
As a best practice, user creation should take place in Intacct, as employees or vendors. New users will be created during the integration.
To work around this particular error message, either ensure that the user running the integration accurately matches an Intacct employee or user that qualifies for the integration, or navigate to Settings > Users > locate the user > Edit > set "Ignore for Integration: Yes" > Apply. Note that the latter method will result in user account duplication if an Intacct employee or vendor is later created for this user.
Unexpected error
The configuration sync failed due to a problem on the Nexonia side or received an error message from Intacct that couldn't be interpreted. Please contact help@nexonia.com or submit a request through this portal.
*This label may appear differently in your Nexonia instance.
Unexpected element (uri:"", local:"html"). Expected elements are <{}response>
Typically this is due to a bad request. This is rarely a recurring issue.
To resolve, manually trigger another configuration sync:
Integration > Configuration Sync > Synchronize Now
Please contact help@nexonia.com or submit a request through this portal if the issue is not resolved via a manual sync attempt.
SSLHandshakeException: Remote host closed connection during handshake
Typically this is due to temporary connection issues. This is rarely a recurring issue.
To resolve, manually trigger another configuration sync:
Integration > Configuration Sync > Synchronize Now
Please contact help@nexonia.com or submit a request through this portal if the issue is not resolved via a manual sync attempt.
There are too many operations running for this company.
This error means that Intacct was busy or had too many concurrent operations running and had to stop the sync.
To resolve, manually trigger another configuration sync:
Integration > Configuration Sync > Synchronize Now
Please contact help@nexonia.com or submit a request through this portal if the issue is not resolved via a manual sync attempt.
Comments
0 comments
Article is closed for comments.