Sage 100

Sage 100 Standard VI_JOBIMPORTMAINTENANCE_UI message Client has a ""new"" 2012R2 server. Whenever we try to Import anything or create a new Import we get the message VI_JOBIMPORTMAINTENACE. Once we enter the Job name and select the Table, click Accept the message appears. You can't go any farther. No error, no Info button. Sage has replaced some MAS_SYSTEM files and the VI folder. No luck. All other modules work perfectly including VI Exports. I'm convinced that the problem is the server because I have installed Sage 100 Standard 2014, 2016, and 2017 - all produce the same message. Alan has suggested it may be permissions. We have reviewed every security location and can't find any irregularities. Any ideas?

Which modules are installed and any developer code on the system ?

Have you tried logging into the server as Windows administrator?

Is it possible that V/I is trying to access some .NET assemblies which are not available on 2012 R2 for some reason. I had a lot of trouble installing 2018 on a 2012 R2 server recently. It finally worked after I installed *all* the Windows updates. It seems the key update was KB2919355. Once this one finally got installed, I could do the rest. It wouldn't hurt you to at least try that. It may be a long shot, though.

Have you tried copying that installation to your laptop to see if problem persists?

There are no MD Enhancements and we are logged into the server as the Administrator. We haven't got to the point of Migrating and converting data. The problem exists on the fresh install using ABC demo data. We will try the KB article. Thanks for all your suggestions.

@HaroldWestover, keep in mind that the KB2919355 is not really an ""article"" so much as it is a patch. This is from Microsoft, not from Sage. I just want to make sure I'm clear.

Unfortunately, KB2919355 is already installed.

Anti-virus?

Thank you Kevin but anti-virus not yet installed.

PROBLEM SOLVED!! their IT guy installed an old version of Excel. It appears that VI checks for Microsoft Office v12 or above. Once I uninstalled Excel, VI works as expected. Thanks to Scott Brady.