Sage 100

Did anything change on Windows 8 with respect to permitting VB scripts for Sage 100 Advanced (MAS 200)? A customer replaced a working W7 machine with W8. We installed the Sage client and all of MAS is working fine from it, including printing (finally). We have some scripts running through BOI that read a pdf filename from a shared folder on a file server (which is not where Sage is). The script uses a mapped file drive, not UNC. With this new machine (and the same user as before), this statement now NEVER finds the file needed: if objFSO.FileExists(strFileName) is always FALSE. We have checked and the value of the variable is indeed a file in the folder. And logged into the W8 machine as the user we can path to the folder and file, and even open the pdf file as the user from the W8 machine. Jerry and I have been all over this, and we can't find what might have changed going from W7 to W8, or from the old machine to the new one. Any guesses?

All I know is that WIN 8 has very different security settings. Took my client's IT guy five days to final configure their WIN 8 workstations.

Yep. From what I am seeing the security in W8 is quite different. The shared directory on the server has security permissions for various users in the organization. In solving the strange Sage PDF print problem yesterday we turned on the ""run as administrator"" option for the program shortcut. I am now wondering which user (and thus which rights) are invoked when MAS200 is run? Since we turned on the ""run as administrator"" does that override the user's permissions to the network drives? Do software engineers do this stuff to us for some perverse sadistic pleasure?

is Windows defender running? Also, found this trick - ""If you wish to get a complete overview of the security system of your Windows 8 computer, it's enough to simply load the Start Screen and type ""security."" Click the ""Check security status"" option and you're done.

Thanks @MoiraGoggin. I'll give that a shot in the morning. Just trying to do a simple ""Run"" command on Windows 8 is a pain! But I REALLY like the tiles and ""Start"" area.

In IE did you set the unc file server path as a trusted site? Can you verfy the unc path can be verified first before pulling the pdf?

We accessed it through the drive mapping. Would that be different from using the unc value?

Without Run as Administrator, can you access the UNC by IP instead of server name? IP uses NTLM auth whereas name uses Kerberos auth. That could be your BOI workaround (but wait there's more). If it works it means tighter Kerberos security. There were several changes in Windows 8 and 2012 for Kerberos so possibly one of those is affecting you. These are controlled either through Active Directory Users and Computers or Group Policy. IT guy could check - http://goo.gl/gtRzo Having said that, there are 2 client side settings that could be the culprit instead: 1) Add an entry to Local Intranet zone (not Trusted zone) a) Goto Control Panel / Internet Options / Security b) Click on Local Intranet / Sites button / Advanced button c) Type the UNC or just type file://<server name> (without the <> ) 2. Goto Control Panel / Internet / Advanced tab a) Scroll down to Security settings b) ""Enable Integrated Windows Authentication"" should be checked Hope that helps. I do have 1 question - were you logged into the local machine instead of the domain per chance?

@ChuckPeddy do a Ctrl-Esc to bring up the Start / Run. The keyboard shortcuts still work fortunately. Have fun with the tiles :)

Alnoor, thanks. We'll check that out. We had two remote session: one on the cluent, which was logged in to the network, as the user was doing normal things including network file access. The second was direct onto the server's desktop, from which all continues to run as it's supposed to.

We found the answer to this problem. When the Sage tech helped us install the Sage PDF printer for Paperless Office he had to set the program to ""Run as Administrator"" in the properties of the shortcut. When I turned off this setting, the program was no longer running as a local Administrator and could access the network drive properly. And since the local admin rights were only necessary for installing the Sage PDF this did not prevent them from continuing to use Paperless Office.