Sage 100

911 ..I don't have any idea what happened, but my client can no longer access Sales Order Entry. The message ""Module J/C is not on file"" appears. They don't own Job Cost, never have, nor have we tried to install it. I've searched Sage, JobOps and Sage City and nothing on those sites helps. Their system was working just fine at 5:30 tonight, and now it's broken. At a loss ... anyone still working ... @AlnoorCassim ??

Any chance they moved to Sage 100c where the registration keys can be automatically updated?

That's the message one gets in programming and scripting when accessing S/O Entry object on an AvaTax enabled system. There are a bunch of old posts on this but I'm guessing you have AvaTax and you need to run the .BAT file in the \mas90\AvaTax folder. If on MAS 200 / Adv then do it from the server and you're done. If MAS 90/Std then every wkstn needs it done. If you're on MAS 200 but accessing S/O Entry thru a special means ""MAS 90"" style (e.g. you run S/O Entry from that one Sage CRM tab), then run the BAT file from the wkstn. I would rt-click / Run as Administrator. Also I usually like to edit the .BAT file and a new line with the word PAUSE in it so that when it runs the command window stays open and I can whether or not the DLL/TLB files successfully registered. Hope that helps.

they don't have Avatax ...

What mods do they have?

JobOps I just don't know how this could have all of a sudden happened.

Nobody has been on their system doing anything tonight but me, and I haven't activated anything, installed anything,changed anything, etc.

Since your the only on in the system in the LINKS folder you could temporarily rename SO_SalesOrder_bus.pvc, SO_SalesOrder_ui.pvc, SO_SalesOrder_svc (whichever of those exist). Then try opening a new S/O Entry window. If it works normally I would DFDM Sy_ClassEnhancement and Sy_Enhancement to trace the mod source for these Sales Order classes but in this case I guess it would mean Job Ops has stopped working. I'll send you something.

Is the integrate to JC flag set at Y in ar or so options?

I am very tired and cranky now. It is this un-intuitive JobOps setup screen. Wouldn't you think you should assign the default work ticket class in the WTC field INSTEAD of the description field? Man this one bit hard.

I never understood the logic of that screen either. Glad you found it.

What Jim said! I had this exact thing happen to me on Monday, at a client ""mid day"". I went into AR Options to check how many years they were keeping history... no changes were made. then started getting that same message. Checked AR Setup Options, and some how, they suddenly and mysteriously had the Integrate to J/C Flag set to YES. I set it to NO and the problem was resolved. This client is v2016 with JobOps 2016a. I am thinking this was the very first time I had gone into AR Setups since we upgraded them. If this fixes your issue, let us know.

So glad to know the west coast support desk is open past 5 PM. Rock on!!!!

Thank you @AlnoorCassim for your efforts in trying to get this issue resolved. To further complicate why this problem occurred, after talking with Tonya at JobOps this morning the WTC field in the Misc. Code file screen shot I provided above is not the default screen. Someone along the way added that field to that CL code class .. now I don't know why someone would have added that field but because I assigned a work ticket class in that field is the reason for the obtuse J/C module not installed message. Thanks everyone else for your comments and suggestions ... it's nice to have so many 90minds friends :)