An attempt was made to reference a token that does not exist

Issue description

When the addon Start (Default Group) is set to Automatic or Mandatory, the following error message stops the addon from starting:

"An attempt was made to reference a token that does not exist" 

Search terms

addon does not start, token, automatic, mandatory

Solution

There is currently no permanent solution available for this behaviour. The following workaround has been found to help avoid this issue.

  1. Install the attached addon coresuiteSupport (coresuiteStartUp)
  2. Set the addon Start (Default Group) for the additional addon to Automatic or Mandatory (the same as the coresuite addon!)
  3. change the addon order so the coresuiteSupport (coresuiteStartUp) starts before the coresuite addon

Older SAP Business One Versions:

  • According to SAP, Note 1669331 was created for error message An attempt was made to reference a token that does not exist and the fix has now been included in 8.82 PL5.

Remarks

It appears that the issue occurs as the SAPbouiCOM.exe is not available yet at the moment when the addon is trying to connect.

To our knowledge, this issue has resurfaced with SAP Business One 9.2 PL08 particularly in HANA environments. We will keep investigating this behaviour, and update this FAQ with our findings.

Should the above workaround not overcome the issue, please contact support.

 

 

Was this article helpful?
2 out of 3 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.