Sage 100

Sage 100 v2014 Advanced - Attempting to install onto a 2008 server R2 - Keep running into this error 1317. Sage KB (which we followed) is attached. Makes no sense at all. Logged on as the System administrator. Rights are set at full. What is odd is that the install does copy the WKsetup prerequisites, but then bombs when starting the other file installs. Tech support was on issue last week, no progress to report. Thoughts???

I found this - http://answers.microsoft.com/en-us/office/forum/office_2007-office_install/error-1317setup-cannot-create-the-folder-during/9063e10c-22e1-4e7c-ab14-6e45a2b514e6

Had something similar at one time, it was file associations. Make sure that the vbs file type isn't associated with something odd, non vbs.

Jeff, not sure if it's the exact same one, but I had something similar not too long ago. Server 2008 and above do not like it when another application wants to install Net Framework 3.51. You need to go to Server Manager in the OS and install from there. Hope this helps.

Does the folder exist? If so, right click, choose Properties, security tab, advanced button, effective permissions tab, and see what you get. Most of what I Googled on this referred to corrupted NTFS permissions.

Had a client that redirected their Documents, I think, folder from the local drive to a network drive. Crystal didn't like that at all and wouldn't install.

Wow, so many 2nd shifters.... @MoiraGoggin - Windows Based Script Host is what opens VBS. @EricAnderson - Haven't tried it yet. The KB specified ""System"" which is what I did and it didn't resolve. @KennyDaniel - .net 3.51 SP1 is already installed. @PhilMcIntosh - Does the attached mean anything to you?? @BethBowers - Nothing is redirected that I am aware of...

@JeffSchwenk - While I haven't look at Server 2008 (not R2) for awhile, it appears that the effective permissions aren't checked for the C:\Sage\v2014\MAS90 folder to actually give the user the rights that are needed.

Epilogue - Took a while, but everyone was hitting around the issue. The resolution was actually in the KB article, although it was slightly hidden. The folder to set the SYSTEM permissions was actually the SAGE folder, NOT the MAS90 as it appeared. Thanks to all the second shifters who responded....