MYOBCommunity
Partner Zone
|
|
Partner Zone

Accountright 2018 error 403 forbidden

3 REPLIES
MYOB Staff Post DeveloperJack
141 Posts
MYOB Staff Post
Australia
DeveloperJack
MYOB Staff Post

141Posts

31Kudos

21Solutions

Re: Accountright 2018 error 403 forbidden

Thanks @eJulia,

Hope you and the team have been able to get this sorted.

 

For the benefit of anyone reading through this thread in future, the API forums here are predominantly focused on folks who are working with MYOB's APIs directly (e.g. building an add-on solution).

 

If you're using an add-on product and encounter an error, the first course of action should be to raise those errors with relevant software/add-on provider.  Most of the the time, issues like this can be resolved without needing to escalate to the MYOB team.

 

If, per chance, the MYOB API team need to get involved then the developer partner/add-on provider, (in this case, TransPost) can reach out to developers@myob.com for technical API support to resolve the problem. The MYOB API returns various errors and ID's that need to be logged and collected before we can get involved to help out.

 

Cheers,

Jack

Jack Skinner
MYOBapi Evangelist

Are you a developer? Check out http://developer.myob.com
Looking for an Add-on? Check out http://myob.com/addons/
Trusted Partner eJulia
130 Posts
Trusted Partner
Australia
eJulia
Trusted Partner

130Posts

73Kudos

4Solutions

Re: Accountright 2018 error 403 forbidden

Hi @JillJACS@DeveloperJack

 

I have only just become aware of this post.

 

I would ask any TransPost user encountering such difficulties to contact us as well as MYOB as, although this problem would appear to be caused by the MYOB update, we are often in a situation where we can suggest a solution, and, if we are sent the TransPost Log file for the day(s) on which the problem occurs we can work with DeveloperJack's team to provide input to help diagnose the problem.

 

I hope the problem has been resolved but if not you or your client should definitely get in touch via the contact details below.

 

We are working on an FAQ page to assist TransPost (and other add-on) users with issues that arise with AccountRight upgrades.  For example we have found it sometimes pays, if using AccountRight SE with files on a server, to uninstall and reinstall the AccountRight API as that occasionally fails to be upgraded properly.

 

Any input that would contribute to a more complete list of suggestions for fixing issues in the upgrade scenario would be appreciated as it saves time for us and our users.

 

 

Regards

 

Julia Roberts
TransPost Support

Phone: 1300 768 993
Email: support@transpost.com.au

Web: https://www.transpost.com.au

 

MYOB Staff Post DeveloperJack
141 Posts
MYOB Staff Post
Australia
DeveloperJack
MYOB Staff Post

141Posts

31Kudos

21Solutions

Re: Accountright 2018 error 403 forbidden

Hi there @JillJACS,

 

Thanks for reaching out. I'd recommend reaching out to the Transpost team who can help dig into this in a little more detail. The "Communication exception" looks like an error from our SDK so they can dig into this in more detail and reach out to our API support team if they need any help fixing it for you.

 

Cheers!

Jac

Jack Skinner
MYOBapi Evangelist

Are you a developer? Check out http://developer.myob.com
Looking for an Add-on? Check out http://myob.com/addons/
Partner JillJACS
4 Posts
Partner
Australia
JillJACS
Partner

4Posts

0Kudos

0Solutions

Accountright 2018 error 403 forbidden

Hi, I have a client using AccountRight (just upgraded to 2018.1.1) who uses Transpost to post transactions from its point of sale software to myob. The sales and cogs come across as a general journal in myob, and it also creates customer account sales (most sales are eftpos) by raising a sales invoice.

 

This was working virtually every day but since upgrading from 2017.2 they have been plagued with communication errors and the entries regularly don't post. When the developer goes into the error log, they can re-post the batches, and they go through without any problem, so we know the problem isn't with the data. This is an example of the errors for one day, when creating the general journals:

 

29/04/2018 05:02, "CustomerSales_20180429.csv (59-60)", "Error", "", "Encountered a communication error (https://ar2.api.myob.com/accountright/610012d9-5ba2-4d0f-8d28-ffc05de91501/Sale/Invoice/Miscellaneou... eq Guid'c503d00e-2a38-4cd6-961d-0ff51da1f8cc' and CustomerPurchaseOrderNumber eq '99' and Date eq datetime'2018-04-28T00:00:00') -  (The remote server returned an error: (403) Forbidden.)", "Log", ""

29/04/2018 05:02, "CustomerSales_20180429.csv (59-60)", "Error", "99", "Encountered a communication error (https://ar2.api.myob.com/accountright/610012d9-5ba2-4d0f-8d28-ffc05de91501/Sale/Invoice/Miscellaneou... eq Guid'c503d00e-2a38-4cd6-961d-0ff51da1f8cc' and CustomerPurchaseOrderNumber eq '99' and Date eq datetime'2018-04-28T00:00:00') -  (The remote server returned an error: (403) Forbidden.)", "Log",

 

29/04/2018 05:02, "CostofSales_20180429.csv (2)", "Error", "", "Encountered a communication error (https://ar2.api.myob.com/accountright/610012d9-5ba2-4d0f-8d28-ffc05de91501/GeneralLedger/Account/?$f... eq '5-0001' and IsActive) -  (The remote server returned an error: (403) Forbidden.)", "Log", ""

29/04/2018 05:02, "CostofSales_20180429.csv (2)", "Error", "5-0001", "Account '5-0001' on journal line 1 is invalid.", "Log", ""

 

I'm an accountant not a developer, so this means very little to me. Can someone please tell me why this is happening and how we can fix the problem?

 

Jill

Didn't find your answer here?
Try using advanced search to find a post more easily Advanced Search
or
Get the conversation started and make a new post Start a Post