Sage 100

I have an issue with paperless where it will work for 4.x level modules but any 3.x version will not work. It will prompt for the location to save the PDF. I found some references to the issue on sage but nothing that is working for me. Only on one workstation, windows 7 on 4.30.0.18 with Windows 7 patch installed. I have noticed that I am getting an error c:\windows\syswow64\mfc40.dll An event was unable to invoke any of the subscribers I run Regsvr32 c:\windows\syswow64\mfc40.dll runs fine Any Ideas? I have uninstalled and reinstalled and removed all the files and registeries. One sage article points to about.com article that lists 15 different things but nothing that appears to be in this case. It is a machine that was setup a few weeks ago. Nothing much on it.

1. Has this ever worked or is this a new upgrade/install? 2. Differences in errors between 4.x and 3.x modules - Crystal version conflict? 3. You've already done the easy stuff - re-run workstations setup, loaded the Windows 7 patch (only available on 4.3+) 4. Any chance that the workstation setup was run from someone without administrative rights and perhaps that's a factor. What if you login on one as admin and re-run? Any change? 5. Right click MAS 90 shortcut - run as administrator Not all of these may be applicable - just some thoughts

Thanks for the input. 1) New workstation that never had MAS on it before and this issue has existed for this machine since it was installed. 2) No other version of crystal exist. The report will print just not PDF if paperless is used. I would think crystal version conflict would exist for all modules. I would think the same for PDF but that is not the case based on this issue. 3) Yeah the easy stuff has been done 4) Workstation has been installed as administrator (admin group on local machine has domain users listed, plus this user is an admin for the domain) Workstation is part of the domain. This is with MAS 200 ???Maybe I should try running it as a MAS 90 install and see if the issue is still there??? 5) I have run the icon as admin and same issue. I also added the path to the server in the IE security local settings

I agree with your thinking of running it as a MAS 90 install. If there are multiple machines - and others are running ok -my thoughts would be some problem with the administrator privilege used to run setup for the workstation.

Same result from running it as a MAS 90 install.

OK this is where I feel like the idiot. This was a 64bit install and the following instructions were not followed: For Windows 7 64-bit and Terminal Service Users: a. After running workstation setup on the client machine, browse to the Printers and select the Sage PDF Converter. b. In the properties, add a new local port and assign the Sage PDF Converter to it. (Note: Sage PDF Converter cannot be assigned to ""NUL"" port.) Each time I was reinstalling I was not resetting the port from null. I went through everything else for windows 7 but forgot about this one part. OK time for a drink.

I was just about to suggest that when you added the post.............

@ToddMartin , where you mention above, ""After running workstation setup on the client machine..."", you're referring to the actual Terminal Server, correct?

In my case it was related to 64 bit so there was not a client involved but I believe the instructions were related to the primary machine and not the client.