Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Close

How satisfied are you with our online help?*

Just these help pages, not phone support or the product itself

0
1
2
3
4
5
Very dissatisfied
Very satisfied

Why did you give this rating?

Anything else you want to tell us about the help?

Article ID: 36163

Accountants Office Suite
Accountants Enterprise Suite
Australia
New Zealand
AE Statutory Reporter (AU)
AO Statutory Reporter (AU)
AE Statutory Reporter (NZ)
AO Statutory Reporter (NZ)

ARTICLE LAST UPDATED: 17 September 2019 10:56 AM

In MYOB Client Accounting, you might experience the error "Period X to Y is locked by <Username>" when opening a Workpaper period.

When opening a workpaper period, the system locks the period so other users can't open or work on the same workpaper period, at the same time. When the user closes out of the workpaper period, it's automatically unlocked.

There are two reasons why you might experience this error:

  1. Another user is currently working in the workpaper period.
    To resolve this error, check with the user that they don't have the workpaper period open. If they do, they'll need to close the period before you can open it.

  2. The workpaper period hasn't closed correctly.
    If a workpaper period isn't closed correctly – for example, because of a system crash. The workpaper should unlock after 5 minutes of receiving the error, so try waiting for 5 minutes before attempting to open the workpaper again.

If the workpaper is still locked after 5 minutes, contact MYOB support on 1300 555 666 and quote KB 36163.

MYOB INTERNAL STAFF ONLY

In the VPMSER (also called AEDB1 or AODB1) database view the dbo.WP_Lock table.

Where there is only 1 record, the lck_message matches the message you are experiencing.

If it is > 5 minutes since the lck_locked date (i.e the lck_duration is 300 seconds), delete this record.

If there are multiple records, determine the required record and delete only the record relating to the client code experiencing the issue.