We are having problems with MYOB Premium Enterprise v6 Build H (Latest version and build) crashing for one user on Terminal Server.
We logged a call with their helpdesk but the girl had trouble understanding that the data and application which are running on a Terminal Server means that the other users arn't connecting across the network to access the data.
We have been getting errors similar to this
- Faulting application Myobp.exe, version 220.127.116.11, faulting module unknown, version 0.0.0.0, fault address 0x35f753d4.
- Faulting application Myobp.exe, version 18.104.22.168, faulting module msvcrt.dll, version 7.0.3790.3959, fault address 0x00038173.
- Reporting queued error: faulting application Myobp.exe, version 22.214.171.124, faulting module unknown, version 0.0.0.0, fault address 0x35f753d4.
- Reporting queued error: faulting application Myobp.exe, version 126.96.36.199, faulting module Myobp.exe, version 188.8.131.52, fault address 0x00215898.
Which we reported to MYOB. They claim that since the errors are put in the event log by Microsoft, that this is a Windows fault and they sent us the following link for our 'it people' to resolve, which is a eventid.net page...
Is anyone else having problems similar to this? Is there a workaround or solution, or alternatively has anyone had any luck getting actual support out of MYOB for their program crashes?
This is a clean build of Terminal Server done a month or two ago with the latest Service Packs and security updates and with nothing else installed apart from Microsoft Office 2003, ClickYes which is required for e-mailing from MYOB because they have not updated MYOB in the last 10 years to support the Outlook Security Update to stop I Love U virus, and Quicktime which is required for e-mailing from MYOB if you have a logo on your invoice.