Mike_James
Ultimate Cover User
User Profile
User Widgets
Contributions
Unable to open any local AccountRight files today
I'm attempting to open a local file, AccountRight v2026.3, Admin user with no password, error message advised incorrect password. My colleague also failed to log in to a local file, same version, error msg: unable to automatically confirm your file. A client's attempt also failed, same version, was prompted to confirm the file with zero days remaining. They are on a live chat session now. Any advice on what's going on?19Views0likes0CommentsRe: "Redirect URIs now need to use a secure https:// URL" (April 2026)
We have now resolved this with the assistance of our domain provider, but I'm still looking for an answer as to where the https:// requirement is documented. We used http://desktop for several weeks after the recent scope changes.15Views0likes0Comments"Redirect URIs now need to use a secure https:// URL" (April 2026)
Authorising a new connection from our app has failed with a "something went wrong". API support advise: We’re tightening validation around the web address your app uses to receive users back from MYOB after they grant access. Redirect URIs now need to use a secure https:// URL on a supported, registered hostname. If your app is still using an http:// redirect URI, localhost-style address, desktop/internal hostname, or any non-public callback address, the consent step may appear to proceed, but the final connection back to the app can fail with a generic message such as “unable to connect, something went wrong”. Could you please check the redirect URI registered for the app and confirm it is using: https:// a valid registered hostname a publicly reachable callback URL an exact match to the redirect_uri sent in the OAuth request I was not aware of this change, nor can I find any reference to it on this forum, developer.myob.com or apisupport.myob.com. Can anyone provide evidence?40Views1like1CommentRe: Pricing Import 4077 Error
Hi GD-mt , AlexUldis , the 4077 issue was explained in a forum post in 2025 (Import of item allows blank values for number of items per selling unit | MYOB Community). It was put forward to the developers as a bug, along with manual imports of new items allowing a blank for number of items per selling unit. Unfortunately these significant bugs have not been fixed. The explanation went as follows: "The important and more prevalent bug the developers need to fix is that when you create a new item with I Sell and do not use I Inventory, MYOB sets Number of Items per Selling Unit to 1 - it should not, it should remain as NULL, as it does for I Buy. This bug is triggering the error 4077 every time a new sold item is added which is not being inventoried. FYI the Number of Items per Selling Unit is not displayed on screen, even though it has been added to the database. Contrary to comments by moderators, the error 4077 issue is not caused by a user changing the item settings after creating the item, the issue is caused by MYOB itself when the item is first created. To confirm - you cannot use a clearwater file to confirm it works as this already has error 4077. Create a new file, and add one item and set to I Buy and I Sell only. Do not set Number of Items per buying unit or selling unit - this field should not even appear. Create a customer card and process a sale transaction for this item. Then try to import a new price for this item - you will get error 4077 - even though the Selling Details screen does not show the Number of Items per Selling Unit field. Run the error 4077 script over the file - this will clear the Number of Items per Selling Unit and you can then complete the import to update the price". Since MYOB moderators can no longer fix this or any other issues , contacting support is your only option. Requiring an admin user to make a request for a fix is a new constraint.Re: Expired refresh token will now require full re-authorisation??
API support have now replied as follows: "Refresh tokens have a limited lifetime. If a refresh token expires, you cannot refresh silently anymore, at that point you must go back through the interactive consent step to get a new authorisation code and new tokens." Some workarounds (that require us to research and develop) were suggested to keep the refresh token alive before the 7 day expiry. Saying "you cannot refresh silently anymore" confirms to me that this used to be possible. Clearly it is no longer possible (which is going to cause our non-admin users grief), but there has been no statement about that in the documentation about these changes. Seems to me it was/is a pretty important change. I'm marking this as a solution, which it isn't.110Views0likes0CommentsRe: AccountRight Single Sign-On EAP
Hi brunob , we do not share the same computer, as we operate at separate locations. I understand Mark is using SE build 2026.1.1.7, downloaded automatically. He has tried another login, and this time as part of the browser window there was an option to open the company file, which he did not see before. So it appears to be working correctly for him now. (I manually downloaded the latest SE edition which appears to be build 2026.1.1.9 - same as my PC version. I'll suggest to Mark that he does the same).Re: AccountRight Single Sign-On EAP
Hi Mike_MYOB , this new process appeared for me today when I signed in to an AccountRight file (desktop, PC version), and worked 100%, very nice. However, my colleague is using AccountRight Server edition, and after logging in, the browser message advised that he was logged in, but the desktop app did not appear. Then on re-opening AR SE and choosing the same company file, was taken to the browser, message said he was logged in, and repeat. So he is unable to log in to any AR file atm.117Views0likes4Comments