Sage 100

Uninstalling 3rd party applications Has anyone out there ever tried to uninstall a large 3rd party solution from Sage 100? I talking about something large and evasive like JobOps or Automated Service from Ascent. I have a client that used to used Ascent for about 5 years and has since moved his service operations to a solution that is written in Force.com. They are on version 4.3 and need to move up. However, they don't want to continue the Ascent piece. I have another client that has JobOps installed. They sold off the division that did Make to Order manufacturing and no longer want to pay maintenance on something they no longer use. They also need to upgrade. The rest of the company is happy with using Sage 100. Thoughts?

Hello Shawn - I just converted a company that was using JobOps and now using Work Order. If you would like to discuss, give me a call: 937-433-8122

I did a JobOps removal a few years back while doing an upgrade. It was just a matter of migrate and convert into a clean Sage 100. Now, you might have to work around the Sage testing for missing modules and add-ins. It could be a warning or an error that stops the process. My experience is before that was an issue. Highly recommend a different server for new version. But I found JobOps tech was understanding about lapsed subscription and knew what to watch for. Can't vouch if they still have the same caliber of help.

I have done several new, clean installs. Then copied data files from a Job Ops install, converted in the new version without any issues.

We used Hightowers Time and Billing for years but in moving toward more project based billing, decided to just use AR. Because HT also had LM extensions, we did a clean install on another server and temporarily hid the TB module. Definitely planned on two moves and some extra time to do it though. I still have the old copy running locally in case I need to reprint an invoice.

Thanks everyone for your input. I really appreciate the advice. The net takeaway I have gotten from your input and a call with Al Conway is: 0) make sure the client knows and signs off on the additional risk of moving forward without the add-on, 1) migrate to a new version of the software without the enhancements installed, 2) review the settings and configuration of the application to design work-arounds and/or adjustments to processes for the changes in functionality, 3) watch and be prepared for errors and warnings during the conversion process, 4) test, test, test the converted solution to make sure there aren't any holes or gotchas, 5) be ready to carry the old tables and added columns with you to the grave, 6) keep a copy of the prior version for history access as if you were implementing a new application from scratch I will update this post if we move forward. Thanks again for everyone's input.

Shawn, the Sage migration apparently uses a couple of different indicators to tell if a 3rd party mod is installed. One is obviously the SY_Module.M4T table, if it is, like JobOps and Ascent, a separate module. Another is in SY_Enhancement.M4T. You can use Data File Display and Maintenance in the old, source system to find the enhancement record(s) in that table and easily remove them when you're getting ready to migrate. The other place that I know that triggers the warning is SY0CTL.SOA. In that file, look for records that start with 'l' (that lower case 'L') followed by the module code affected by the enhancement, or the enhancement module itself. Once you remove those records, you can probably migrate without warning. When the time comes, I can help you if you need it. I've cleaned out a lot of trash from system tables over the years, including stuff that I put there.

I recently uninstalled JobOps. Here are the instructions I got from their support team: MAKE SURE TO HAVE A BACKUP OF MAS90 - Launch Sage MAS 90 / 200. 1. Remove the JobOps data from all companies - This is performed from Company Maintenance 2. Uninstall the J/T JobOps module from System Configuration (Uninstall button) 3. Manually reinitialize the SY_ClassEnhancement.M4T file of the JT158 records 4. From windows explorer - access the MAS_SYSTEM directory and remove the SY_158JobOps file (this holds JobOps Reg Keys and is not removed) 5. From windows explorer remove any JTxxx directories - these sometimes linger 6. From SY_Enhancement remove reference to JT or 158 7. From SY_Module remove JT Module - Install all Sage MAS 90 / 200 modules and any other custom enhancements/customizations into the current directory where MAS is installed. Doing the reinstallation of MAS puts all programs back to standard MAS. Then you will need to run workstation setup again to each workstation to reformat the menus. The end user also needs to be aware that by doing this process, they will no longer have access to any JobOps data that was created.

Thanks Mary Jo. This process removes all past data. I can't see how it can remove data or customized fields from the standard Sage 100 modules. Looks like we have a couple options to try. Should be interesting.

Received cryptic A/L is invalid on an HTI upgrade from 4.3 to 2014. Had to remove the enhancement records from SY_Class Enhancement. Sage asked for a copy of the data and then appeared to sit on it for 4 weeks. Whatever you do use 90 Minds first for any errors. Sage support is definitely slipping imho. Their new ""stall"" tactic is to ask for a copy of your data.... Back in the 1990's it was ""Fax the support question"" --- and then mysteriously your fax ""got lost""..... beware

I always come to 90 Minds before going to Sage. It has become my defacto step: 1) have we seen it before (internal inquiry), 2) what does Help say, 3) check Sage knowledge base, 4) check 90 Minds Evernote, 5) check 90 Minds Socialcast history, 6) post question on 90 Minds Socialcast, . . . Oh Shit) Ask Sage