All Collections
General
MYOB
-181: File is busy; Import did not start
-181: File is busy; Import did not start

How to resolve MYOB Receiving Error 181

Updated over a week ago

Description

This articles describes how to resolve MYOB Receiving Error 181 (Error -181) when Importing Transactions from WMS.

When importing data, the error message of the import log reads in Tools > Connect > Status Reporter: Error Code(-181) "File is busy; Import did not start".

Detail Steps

This alert indicates that MYOB file is busy and cannot send transactions across to MYOB.

How to rectify the issue:

Sales Register

1. First, try resending the ALERT after the interval of 10-15 minutes by right-clicking the order from despatch register and click 'Invoice Shipped sale' . This will normally clear the ALERTS in WMS and replicate to MYOB successfully.

2. Please ask all users to logout from MYOB and open Task Manager > Details Tab > make sure no one is logged in under Myobp.exe or wms-myob.exe and re-send transactions from WMS.

3. If this error ALERT is very frequent, it's better to restart the server to clear all the locked/ghost sessions and retry the step 1.

IF it didn't work , then follow the steps below to quick resolve the issue.

4. Change the option in Tools > Preferences > Replication Tab > Post sales as orders not invoice.
5. Go back to despatch register and highlight all sales/PO > right click and select Invoice shipped sales.
6. All sales came across to MYOB as Orders.
7 All sales in WMS change status from Alert to CLOSED.
8. Check MYOB for any possible duplicated and remove the sales/PO.

Receiving Register

1. First try to resend the ALERT after the interval of 10-15 minutes by right-clicking the order from Receiving and click 'Billed Received Order'. This will normally clear the ALERTS in WMS and replicate to MYOB successfully.

2. Please ask all users to logout from MYOB and open Task Manager > Details Tab > make sure no one is logged in under Myobp.exe /wms-myob.exe/ Huxley.Application.exe*32 and re-send transactions from WMS.

3. If this error ALERT is very frequent, it's better to restart the server to clear all the locked/ghost sessions and retry the step 1.

IF it didn't work, then follow the steps below to quick resolve the issue.

4. Change the option in Tools > Preferences > Replication > Post Purchases as orders not BILL.
5. Go back to despatch register and highlight all PO > right click and select Billed Received Order'.
6. All PO came across to MYOB as Orders.
7 All PO in WMS change status from Alert to CLOSED.
8. Check MYOB for any possible duplicated and remove the PO.

9. Ensure to reset back the Preferences settings once completed

Workflow Reminders

Check if some users logged in to MYOB using Multi user access and TCP/IP giving the error "Other users accessing the AccountRight Premier system are using a networking protocol other than the one you have selected. Either select the protocol being used by your co-workers or try again later".

Due to that, will cause replication error "File is busy, import did not start".

Please advise all MYOB users to select:

  1. File Access: Multi-user

  2. Protocol: TCP/IP

Related Information

If customer is under PTP setup, ending MYOB task via Task Manager on server is not enough. Request all users to log out from MYOB and restart their terminals.

Did this answer your question?