Socket Exhaustion and the MYOB .NET SDK
I am developing our inhouse application to go online using the MYOB .NET SDK to go live for STP2 in Jan I have looked at the .NET SDK Code from GitHub and for the API calls it uses a HttpWebReque...
Forum Discussion
Hi kjm ,
Sorry for the slow reply - been sidetracked on another project :-).
We've been using the .NET SDK for years. C# Console apps that run via Scheduled Tasks. The main purpose is to extract data from MYOB and import into a SQL Data Warehouse.
We see random communication error exceptions and have just been dealing with them by re-trying our tasks a number of times. Whether this is related to the socket exhaustion - we haven't investigated to find out.
Cheers,
Phil.
I use c#/Hangfire to run jobs overnight etc ... not unlike your consol app/schedule task setup
How are you doing this? are you manually logging in each time a scheduled task runs?
As I understand it myob has not allowed oauth flow for software clients without user interaction?
Hi kjm ,
Until now, we have had our datafile on-premises so have not had to worry about OAuth.
As STP Phase 2 requires the datafile to be in the cloud, that's changing. I'm in the process of testing whether I can get the token(s) initially by user interaction, and then persist and rely on the lifetime of the refresh token to obtain further access tokens without requiring any further user interaction.
Cheers,
Phil.
cool...I'd be interested to know how you get on with this...
