Sage 100

I had a customer with a bad IT department who copied some files over my recently upgraded Sage 100 2016 -- specifically VI. This caused VI not to run properly. I repeatedly asked that they restore from backup from which they replied it would be too time consuming and can't I just reinstall VI. Hesitantly I agreed and unfortunately there's no practical way to reinstall just one module in 2016. I did the repair after renaming VI to old.VI This seemed to bring back VI Now, however, when I go into certain menu options such as AP - Trial Balance Report I get ""AP_TRIALBALANCE_UI"" and just an ok button. I found this https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=62339&sliceId=1&cmd=displayKC&dialogID=101775&docType=kc&isLoadPublishedVer=&stateId=101777&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl And followed the steps which appeared to complete. Yet I am still greeted in many places with the xx_xxxxxxx_UI"" error. I know I've seen this before but am not sure what the cure was. Ideas?

Do all users get this?

Run sy_menu_ui just to get the menus to update?

Same thing. When I try to , for example, print an AP Trial Balance Report - I get AP_TRIALBALANCE_UI with just an OK button. So far as I can tell it's for all users. I get it on my login and another user does.

I am constantly amazed by clients who don't want to do time consuming tasks but are willing to pay for us to do time consuming tasks which may not work as well. We have become better at telling people who have old incompatible printers with current operating systems to buy a new printer as it would be cheaper than the support call to us and they would get a better printer too!

I'm opening a case with Sage as I can't rule out something newish in Sage 100 2016. Was pretty sure this would be an S Show so I pulled a full copy of the \MAS90 folder first. Worst case I'll copy it back but what should be (used to be) a relatively easy task of reinstalling a module is now a half day of praying ..

Uninstall VI from System Configuration, then reinstall the server to add back the module...? Maybe the repair didn't re-create all the program ID's properly.

This is news?

Sage is clueless

LOL. Sad but true.

I just basically take a Sage Case # to pacify the customer. If Sage doesn't come up with a hidden problem report then I find it's just a lot of ""wheel re-creating"".

Am I missing some change that happened with 2016 in that it's hard to add a module now? It used to be just running the server install again, and selecting the option to add a module (then re-applying PU's / enhancements...).

Sounds like IT did more than just copy over VI. Probably copied over other programs, and/or erased them. Restore would make the most sense but they probably don't have a backup to restore from...hence the hesitation .You should probably do a full reinstall of 2016. I doubt Sage or anyone else can resolve this since you really don't know what got erased, moved or copied over.

I had what I believe is the same problem once (where they had restored but it wasn't a perfect restore) and they were getting the same message box with the OK button (like attached) but only for certain reports from the menu. I traced the errors down to reports that also happen to be run by the BI Dashboard (like the A/P and A/R Aging reports). That is these reports first check to see if they are being run via BID and if not they run the normal way. But to do the first part it checks an ES program. Well the whole ES folder was missing. I copied mine over for the same version and Halle Berry Lujah.

Thanks. Just to add to the issue above. SYMPTOMS: 1. The customer's IT copied VI folder from 2014 version over 2016 VI folder 2. This resulted in VI Jobs giving an error about a missing VI program when certain jobs were selected to run. I suspect the damage was limited to VI only as the customer ran all other parts of Sage 100 2016 for about a week without error 3. So far as I could tell IT took their prior VI (v2014) and copied over the \VI folder only ISSUE: 1. For a myriad of reasons IT would not restore backup (yes, yes and yes this is the preferred method of solving this but it was not available to me). Did I mention restore is the preferred method of solving this? Again, restore was not an option to me. 2. Therefore I needed a way to re-install VI to get back to 2016 version program files STEPS TO ATTEMPT TO REINSTALL: 1. I took their 2016 ..\VI folder and renamed to old.VI 2. I took the Sage 100 2016 disk and selected ""REPAIR"" - There does not seem to be a way to select ""reinstall"" for just one module - A better way may have been to uninstall VI through System Config then reinstall 3. The repair seemed to have repaired VI so I could run a job (VI was fixed) 4. Repair broke something else as reports I ran would come up with a similar message to what Alnoor posted - just an OK button with no info . Also when the customer imported to AP Invoice data entry they were unable to run an Invoice Register. 5. I did not exhaustively test all reports to see if some would run - enough did not run that I know I had an issue. Before I did all of the above I took the \MAS90 folder and copied to my desktop. To fix the issue I just copied \MAS90 back. Now VI is broken but people can at least work in Sage 100. I'll report back today once I gain login access on what ultimately fixes the issue.

Maybe it's a DEP issue? Try propagating security to MAS90 folder again and disable DEP.

That's a good observation. I found that some of the properties appeared to be set to read only. I un-checked the read-only setting and propogated. Did not seem to resolve howeverI would not rule out.

@AlnoorCassim - THAT was a very interesting one. I'll keep that one in mind (maybe - any brain cells left for that?).

I would tell them to restore the VI directory - and ask what other files did they originally restore. What is too time consuming? Is the VI directory that large? Then you might could ignore some of the large files in the vi directory as these are just the job logs..

FYI - they probably do not have a backup is my bet..

Did you ever get this working? If so, what was it?

I got this working and I think it was that the IT department both copied something (the 2014 VI folder) over the \MAS90\VI and when I renamed that to old.vi and repaired using the 2016 install disk the v 2016 repair hosed something on the install. So, I renamed that ""new"" install to ""bad.mas90"" and brought back the former \mas90 (which I started with). Removed the VI program file from that install (which had been overwritten) and copied in the full VI from the second install which I believe was clean. That solved the problem. I think there's still an issue with the Sage 100 2016 repair feature but I don't have enough time (or curiosity) to toy with it.

Good to know, thanks Wayne!