Sage 300 O/E Import Error 1000 - O/E Options. (2 replies)
Tom, your colleague raised this with us a while back, but we didn't hear anything further.
To answer, yes we have seen this same issue at one other client; though this other client didn't mention the 'System File issue, nor the CRM issues.
IMan doesn't do anything explicitly with O/E Options, this is a view opened and updated by the Insert method. My initial thoughts are that we can do little, however it help to have a quick call with yourselves so I can refresh myself with the client.
Tom, given the number of sites we have using IMan to import orders I wonder if this could have something to do with the Avalara. Is this is enabled at the client? If it's taking a bit of time to post an order (over webservices) it may be definitely be having an adverse affect.
I'm wondering if anyone has come across this before. I'm pretty sure it's a Sage 300 problem and I am calling Sage too.
When bringing orders into Sage 300 Via iMan. We intermittently get this error:
5/12/2015 02:21:52 Sage300OrderImport -1 Transform Started [Sage300OrderImport]
5/12/2015 02:21:55 Sage300OrderImport 11022 1000 - O/E Options.
Record has been modified by another program.
We have the job set to retry the import in 2 minutes, the next time it runs the order will import without a problem.
Users accessing the Sage 300 OE Screen will get a message like "System file temporarily in use. Do you want to retry." after a few attempts the O/E Order entry screen will load. Also users in CRM will see intermittent failures loading the customer statistics and O/E inquiry screens. So it appears that the Sage 300 API is getting locked temporarily so other applications cannot access it.
Thanks,
Tom Usselman, Frontline Systems