Hi nduro
Sometimes a time out message is not really a time out message. If you set the time out to 15 mins and a report times out after 3 minutes, you will likely find another issues such as a corruption in your file, or a duplicate record etc is to blame. However developers may have coded the particular situation to send a time out message.
A user recently successfully ran a AR2023 report - the report took over 15 hrs to generate, well over the set timeout. This is because AR2023 was continuously working and notifying the running process during this 15 hrs. The company file was local not online. See here for details.
Certain corruptions cause AR2023 to shut down, others don't.
Ensure your anti virus scans, system backups, syncing services etc are set to exclude Huxley.Application.exe. Also that your system has at least 4 GB RAM that it can presently allocate to AR2023. System should have a minimum of 8 GB RAM, or more if numerous programs are running at the same time.
Once you have checked all these, you need to look at the file. Send me an email if you want contact details for a MYOB Specialist who can run some free tests over the file to see if there is anything obvious causing the issue.
Another thing to consider is the load on MYOB's servers. During peak times, if their resources are stretched too thin, response times will stretch out. See if trying the same report after hours is any quicker.
Regards
Gavin
