A colleague moved MYOB AccountRight Enterprise v 19.5 users from Windows 2003 Terminal Server (situated locally) to a Windows 2003 Citrix Server (Data Centre) in his last working week with us, before leaving for another job. I didn't take it seriously until I got a call from the users to restart the server when one of their team of 6 was locked out of MYOB. He was receiving "the user is already logged in" sort of error. And the users told me the only option was to restart the server, which was always handled by other site system administrators.
I have got a very long queue, and I gave in for the first one. Then the next day, it happened again. This time it was a manager, who insisted to get this fixed as it was month end and heaps of work to be finished. I had to call other application users to log off for the reboot. Internally I felt guilty.
I contacted MYOB right away, and the Chat support suggested me to move the company database file to another folder. I did but it did not fix the problem, this happened again. I tried the Chat support again, the other end told me this should be supported by calling more senior engineer. I called and the support staff was very quick to tell me that I need to get all MYOB users log off and then delete all the *.flk files. I did it and this worked fine. Then the users requested to remove the lock files themselves. The following is a wrapper batch file to automate the lock file deletion.
Del C:\MYOBDATA\Lock0001.flk /F /Q
Start "MYOB" C:\Enterprise19\Myobp.exe C:\MYOBDATA\COMPANY.MYO
