Sage 100

I'm caught between Sage and TrueCommerce support and neither want to take responsibility. Customer is getting an error when trying to import EDI transactions into Sage100, ""Module J/C not on file"". They never used or installed JC. Other stations are able to do the import, its just one workstation. Everything else runs fine in Sage100 on this PC. We tried all the KB articles, uninstalled/reinstalled WKSetup and TC setup several times. Been working on this for 2 weeks now with no resolution in sight. Anyone seen this or has any ideas. TIA

I've found that the 'Module J/C not on file' error is kind of a catch-all when scripting (it's probably error #0 or something like that). Is it just that user on that workstation, or anybody at the Workstation level (my first thought was ODBC security).

I'm with Steve. 'Module J/C not on file' is a red herring.

@SteveIwanowski It's all users. I logged on as Network admin and Sage Admin and we get the same error. Seems to be something on that PC interfering with TC since other PC's are working fine. I even logged on to another PC as the user with the error and it worked.

It's probably something wrong with the COM or Script object, but if an uninstall/reinstall didn't help, then can we burn that PC to the ground and collect the insurance? :)

Do they use Sage Sales Tax? I've had this error before. Has nothing to do with Job Cost

Reach out to Tony Tineri at True Commerce. He's a great technical resource there and can usually resolve my ""weird"" issues. I also agree with the above comments about that particular error.

This happens a lot with BOI apps (like True Commerce) when AvaTax is also involved. The machine that's running the True Commerce BOI code, you need to copy the \mas90\AvaTax folder to its local drive (e.g. to C:\Sage\Avatax) then run the .BAT file there to register the DLLs. Then it should be okay.

@AlnoorCassim we tried that with Sage Support actually. Didn't help @SteveIwanowski I'm starting to think that is the solution. Except its a brand new i7 Win10 and NOT insured :).

I agree with Alnoor - we see this message when Avalara is not properly installed/registered on the PC that is running True Commerce - I suggest putting a pause in the avalara batch file to see if it is actually working, and be sure to run from a command prompt from the ""C"" drive, where the command prompt was started ""as administrator"". (then take the pause out when you are done)

I was going to add exactly what @JeffFiddelman mentioned. Start the admin command prompt and run the BAT file that way but first add a PAUSE at the end of it so you can verify it registered. You can also verify this is the problem area by starting up Sage from the machine running the True Commerce BOI and going into S/O Entry. The error may not be ""Module J/C is not on file"" but an error should occur.

@AlnoorCassim and @JeffFiddelman. I did what you mentioned with the Pause and Admin C prompt, etc. It does say DLL registered successfully but when I try TC I still get the same error. The PC with the TC error has no issues at all in Sage100. In fact it's a customer service PC and it's in SO all day. Thank you for you help.