Import Items Error Codes

Question

I update Item prices by exporting a file of items, altering the prices in that file and then importing it again.

This work a treat for many years in Premier and its predecessors.

In AR2020.2 (and 219. et al) the log contains a pile of error messages. They provide no help in resolving the problem.

Error -4077: You have sales for this item.
Error 0: Unexpected import error - Database already opened by a different user. [ Db name = C:\Users\Public\Documents\MYOB\My AccountRight Files\bcp195-2020-2.myox ]
Error 0: Unexpected import error - There is a file sharing violation. A different process might be using the file. [ C:\Users\Public\Documents\MYOB\My AccountRight Files\bcp195-2020-2.myox ]

These were generated when there was only 1 user using the system. None of the records looks to be irregular.

komal_s · Accepted Answer

Hi&nbsp;IanP&nbsp;
&nbsp;
If your file is online, we can run an online script in order to fix Error -4077 which would resolve the other error messages as well. In order to organise that, please send me your serial number by a Private Message.
&nbsp;
Update: File fixed and returned by data file repair team.

ianp · Answer

Still unable to import items.&nbsp; I export the items file, then without touching it, attempt to import it again.&nbsp;It rarely manages to go through the whole file,. It normally stops at some random record and presents the usual finished screen, for example, 29 records imported with out error, 2 warning messages and 3 records skipped (out of 3000 !!!! ).&nbsp; It invites me to click on a link for a log file, but none is present.&nbsp; I try to navigate to the log file link which is displayed, but it is empty.&nbsp;The number of records until it stops is completely variable.&nbsp; It might be 26 or 29 or 257 or 1500.&nbsp; I have truncated the file length from 3000 records to 1000 records and to 300 records.&nbsp; This makes no difference ot the behaviour.&nbsp; The randomness of the stops and the insensitivity to file length or content strongly suggest it is not related to the data but is a program fault.&nbsp; The only data in the items file is that which has been entered into the MYOB Items cards, so surely the program can cope with data which it has itself sent out (Maybe not, see the note about CRLF below). The failure to produce a log file is clearly a program fault.&nbsp;The file has been sent in to you several times for various reasons and each time it is returned with the statement "its fixed" but it never is.&nbsp;On the odd occasion it finishes, it displays a number of error and warning messages.They include the 0: File sharing violation which is odd because I am running on its own on a W10 machine with no one else accessing it.&nbsp;There are always a pile of warnings such as "name is too long truncated" which is weird since it is importing the file that it has exported from the same MYOB program just minutes before.&nbsp; Surely this is the simple most basic test of any export import system, can it reimport its own exported file.&nbsp; It also has item has purchases warning messages, which make no sense at all.&nbsp;If the item [Description] field includes a CRLF that causes the import to break the line at that point and attempt to start the content after the CRLF as a new line.&nbsp; This is clearly faulty software.&nbsp; I have tried a number of ways to escape the CRLF but nothing stops this anomalous behaviour by the program.&nbsp;I have been trying to get assistance with this from MYOB now for many months and it is consuming an enormous amount of my time.&nbsp; The phone contact today is at 2 hours and 34 minutes.&nbsp; As usual the phone response is to do over and over again the things which nhave lready been done which do not advance matters at all, but which do burn up an enormous amount of my time.&nbsp;I am VERY VERY VERY dissatisfied with the support.&nbsp;&nbsp;&nbsp;&nbsp;

mike_james · Answer

Hi IanP&nbsp;, just quickly, the 4077 error can only be corrected by MYOB, and it may come back.&nbsp;&nbsp;If you would like me to look at the actual file you are importing, send it to my email with the whole log file.&nbsp;

mike_james · Answer

Hi&nbsp;IanP&nbsp;, what program name and version number are you using?&nbsp;When I export items from Clearwater that have a multi-line description, from AccountRight 2020.3, I get this:&nbsp;This is a very long description
With multiple lines
This is line 3&nbsp;This text appears in the one (Description) field. I also see this text on our API extracts. I think version 19 included CRLFs which caused a new line in the file and therefore made it impossible to import the file back.&nbsp;&nbsp;&nbsp;Re file sharing errors - do you have continuous backup programs running, or is the file stored in Dropbox?&nbsp;I recently completed a very large import project, and once I had amended the data as required, the import routines were very stable.

ianp · Answer

Thankyou for the response.&nbsp; Here are the specifics you mention.&nbsp;AccountRight 2020.3 SE&nbsp;I have gone throughh the 3000 items and manually removed the new lines.&nbsp; Interestingly, if I put a new line back into the description it again misbehaves, so the AR2020.3 does not intercept and prevent the entry of stuff which stops the export/import from working properly.&nbsp;The file is local.&nbsp; I have only 1 user session operating.&nbsp; There is no continuous backup running.&nbsp; There is no drop box in place.&nbsp; I can see no way in which a file sharing problem can legitimately occur.&nbsp;I can live with all the spurious warning messages and the inability to use new lines (even though it is a nuisance).&nbsp; What I can't live with is the random failure to complete the import, and the random failure to import some items (showing the dreaded error 0: sharing violation).&nbsp;Here is a typical list of errors and warings.&nbsp; (From a rare run to completion). I have looked at every record flagged as a warning and they look OK to me.&nbsp; Basically the messages are unhelpful, and indicate to me that AR2020.3 has not been tested to any extent with export/import.&nbsp;-4077 You have sales for this item. Really, we would be out of business if we did not.0 File sharing violation. Really, only one person is using it.45, 49 Names too long.&nbsp; Truncated.&nbsp; Really, they were exported by ar2020.3&nbsp;71 Item Not Sold. What on earth does that mean.75 Items per selling unit...&nbsp; Really, the program gives no access to ability to change items per selling unit.&nbsp;2306 records imported without errors.924 records imported with warnings.15 records skipped.Summary of errorsError -4077: You have sales for this item.Error 0: Unexpected import error - There is a file sharing violation. A different process might be using the file. [ C:\Users\Public\Documents\MYOB\My AccountRight Files\bcp195-2020-2.myox ]Warning 45: Supplier name too long; name truncatedWarning 49: Unit of measure too long; unit truncated.Warning 71: Item is not sold; some information ignored.Warning 75: #Items per selling unit may only be specified for items that are sold and inventoried&nbsp;I do appreciate your input.&nbsp;I must confess I would really really appreciate some real input from MYOB (who have profitted mightily from us for the last 30 years) and fix the bugs in the program.&nbsp; What I see is a company that doesn't give a stuff about its existing customers.&nbsp; It is so busy putting fancy extras into the software, it has completely forgotten that it needs to make the basic stuff work properly.&nbsp; ( We have just discovered after 2 months of working with the API mob that if you install 2020.2 on a clean W10 machine then the API calls won't work.&nbsp; You have to remove the 2020.2, instal 2020.1 , which uses an earlier version of SqlSever, and then reinstall 2020.2 and voila, then it works.&nbsp; Obvioulsy no one has ever tested this.&nbsp; It obviously is still using some calls to the earlier SQLServer)&nbsp;Like most modern companies, they have walled themselves off so that it is impossible to get some one who actually knows something involved.&nbsp;Ever since we were forced to move from Premier to AcountRight2019 we have had nothing but trouble.&nbsp; ODBC calls vanished so all that had to be re written, but then the API calls did not work so months of investigation for that.&nbsp; Version 2020.2 blew up our netwroks because it was unable to run on a W7 machine, but no body told us that.&nbsp; Our automated price update system depends on impoirt export and wehave not been able to get that work properly yet.&nbsp;As I said, I am VERY VERY VERY dissatisfied.

komal_s · Answer

Hi&nbsp;IanP&nbsp;
We're really sorry for the frustrations caused by this and our teams are currently investigating this issue.&nbsp; You will be contacted by one of the product specialists to understand your concerns. In the meantime, as we have your serial number, we can run the online scripts for you to resolve the error 4077.

Forum Discussion

Import Items Error Codes

8 Replies

Related content

Import Item Error

IMPORT ITEM ERROR LOG- 4077

Importing Error 4077

Errors when Importing Items

Importing Items errors

Error 28, "Item is not sold" when importing item sale from CSV

Bulk Item Import: Changing Item Number

Import timesheet error