Sage 100

Has anyone run into this issue: ""Feature transfer error Feature: New Merge Module Holder Object 1 Component: File: Error: Access is denied."" when installing workstation for MAS90 or 200 I have located the KB entry which indicates the problem is a lack of permissions on the share -- to which (naturally) the customer proclaims they are the grand knowing and all accessing administrator. http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=513762

The problem with these knowledgebase entries that claim that you don't have access rights is there's never a way to TEST. So you tell the customer - ""well here's what the KB says"" and they 100% of the time respond: a. I am the administrator b. Show me what I need to fix for my permissions c. I am the administrator

Well, if the Crystal 2011 installer can tell ahead time that you don't have the proper rights, we may see this in Sage 100 v 2017..........

I always give the group/user ""Full Control"" in the ""Security"" tab of the main Sage sharepoint on the server. That seems to get me around this error. I've seen it before when IT managers try to be stingy with permissions.

We've waltzed the ""full control"" and nothing is working. This is a security conscious company and I strongly suspect that security rights or some other security issue is at play here and not necessarily the MAS it could also be fine tuning of anti-virus or malware.

In most situations like this I try to work with IT to ""turn off"" those measures, at least temporarily, so that we can track down the issue. Could they have security locked down so that the rights down extend to the ""children"" folders? I've seen this before and I've had to essentially go to each folder on the sharepoint and turn on full control.

It's extremely frustrating because without further guidance the customer is essentially asking you to debug the setup of their IT security. I think one of Sage's biggest challenges is to get rid of this type of issue where permissions are suspected and the customer essentially tells you ""prove that it's my computer and not a bug in your software"". I've very seldom seen an error with ""permissions"" that wasn't an issue with security of the local PC (antivirus, etc). Customers rarely think when we suggest ""give full rights"", ""turn off AV or MALWARE SCAN"" that they should need to try that....

I feel your pain. It's like trying to prove a negative. I assume this is a new Windows 7 workstation. I'd have the IT support log the workstation in as the Domain Admin and do the install that way. Then do the install so that anyone logging into the workstation can access it. Also, tell the IT support to turn off/exclude the AV software for the MAS directory. They can do that. Heck, I do it often because IT will shrug their shoulders at me and say ""whatever.

We are doing exactly that. It's compounded by the fact that another workstation now cannot run wksetup. The problem is that there could be any number of changes made to security since we first setup workstations (and there probably have been). IT just figures none of them are worth mentioning. Ultimately I blame the install routine because it just barfs instead of saying why it cannot continue. This is just pure sloppy programming on someone's part. Sage will never get measurable # of customers to trust advisor to self-update so long as this crap hangs out...

And 1:45 into the call I try to copy a file into MAS90 folder and get the ""permission denied"" ..... almost two hours of listening to how I'm logged in as admin....

I wonder if the new installer will be more helpful. Who am I kidding?! :-/

Ultimately after 2 hours of asking and pleading the IT department changed permissions on domain admin to allow full rights. They ad to add in domain admin as allowing access Then they had to change permissions for the EVERYONE group to allow full access. After this it worked fine... finally