Sage has detected Module Update inconsistencies that require activation for one workstation not others

SOLVED

I am getting the "Sage 300 has detected module update inconsistencies that require activation on one workstation which happens to be a VM". 

I can run logged in as the network ADMIN or logged in as the user as long as I run ACCPAC as administrator, but when I run it normally, it says the OE module is not installed. I checked permissions on the programs and shareddata folders, and they seemed correct. 

The programs and shared data are on a share on the app server, i.e. not installed locally . The other workstations in the network work ok. The other users in the network work ok on their own workstations, I haven't tried them on this one. 

Just for grins, I tried doing a data activation and it didn't even show the OE module in the list of modules to be activated. (There was nothing in the list at all, which is right, since all the modules have been activated using a different workstation). 

  • +1
    verified answer

    This was a permissions problem. Windows lets you set permissions on a root folder and makes a big song and dance about setting permissions in the folders below it. However, it doesn't seem to always set those permissions. In this case, the OE67A permission was not readable by the user who got the message although domain admins could read it. The fix is to do a directory on the programs folder and see if the programs that needed "installing" showed up. The other folders were all set correctly. So, the thing I will remember is to do a directory if Sage 300 says some module is missing in some configuration.