Write, Bureaucrats, Administrators
3,306
edits
Difference between revisions of "OdataLink Error Code 8001: MYOB denied access to the endpoint"
Jump to navigation
Jump to search
OdataLink Error Code 8001: MYOB denied access to the endpoint (view source)
Revision as of 18:24, 3 December 2024
, Yesterday at 18:24no edit summary
| Line 1: | Line 1: | ||
'''Error 8001''' will be logged when [[MYOB]] denies access to the [[Endpoints|endpoint]]. | '''Error 8001''' will be logged when [[MYOB]] denies access to the [[Endpoints|endpoint]]. | ||
[[MYOB]] does further checks when accessing endpoints based on the '''MY.MYOB''' login used when adding the data file. As such, it is possible that the '''MY.MYOB''' login does not have access to all parts of [[MYOB]]. The '''MY.MYOB''' login may have access to one specific endpoint and not another. | [[MYOB]] does further checks when accessing endpoints based on the '''MY.MYOB''' login used when adding the data file. As such, it is possible that the '''MY.MYOB''' login does not have access to all parts of [[MYOB]]. The '''MY.MYOB''' login may have access to one specific endpoint and not another. | ||
The way to resolve this issue may vary depending on a number of factors. | |||
== If you can connect to some endpoints and not others == | |||
If you can connect to some endpoints and not others, you may want to try [[Reauthorising access to your data file|reauthorise access to your data file]]. Sometimes, authorising with a different login to MYOB will resolve the issue. We recommend using a my.myob login that has Administrator access if at all possible. | If you can connect to some endpoints and not others, you may want to try [[Reauthorising access to your data file|reauthorise access to your data file]]. Sometimes, authorising with a different login to MYOB will resolve the issue. We recommend using a my.myob login that has Administrator access if at all possible. | ||
Finally, some data files require setting an [[Editing a data file's details|explicit data file USER NAME and PASSWORD]]. (e.g. '''Administrator'''). | == If everything was working fine but it all stops working suddenly == | ||
If instead, you could connect fine and can't suddenly, it may be the '''MY.MYOB''' login has been revoked (in cases where the employee leaves the company). It's also possible MYOB naturally revoked the tokens, or some IT adminstrator forced a revoke. Typically, in these scenarios, none of the endpoints work. In this instance, [[Reauthorising access to your data file|reauthorise access to your data file]] should resolve the issue. | |||
== Some data files require an explicit USERNAME and PASSWORD (MYOB v19 like access) == | |||
Finally, some data files require setting an [[Editing a data file's details|explicit data file USER NAME and PASSWORD]]. (e.g. '''Administrator'''). This is particularly common for those that came from the desktop version of MYOB. See [[Editing a data file's details]] for further information. | |||
== Last Resort == | |||
As a last resort, you may also [[Removing data files|remove]] and [[Adding MYOB data files|re-add]] the [[Data Files|data file]]. This can cause some issues with OData Feeds and should only be done as a last resort. | As a last resort, you may also [[Removing data files|remove]] and [[Adding MYOB data files|re-add]] the [[Data Files|data file]]. This can cause some issues with OData Feeds and should only be done as a last resort. | ||