Ihave reached out to both sage and amyuni (the developer of the driver). Amyuni says that sage uses a developer version and they need to supply the arm version. Amyuni does have an arm version of their driver. I have tried to install it but sage uses their developer version with some enhancements. Sage seems to have no clue. And are requesting me to ask the community.
Sage 100 is supported on Intel based chips. ARM has never been supported. That said, current versions of Sage 100 distribute 6.0x version of the Amyuni PDF Converter. If you downloaded a 6.5x version of the Amyuni driver that includes ARM support it will not work without a separate license key (purchase) from Amyuni.
John I have downloaded the new amyuni driver for arm. And even created a printer called Sage 100 PDF Converter. However when going to paperless office it opens a dialog box to save. And then errors out.
If you own a separate license key, it can be passed to the driver, otherwise the Sage license key is passed. Using an ARM chip is not supported and I have no way to validate a purchased license key on an ARM processor.
So I purchased a seat. Which does get me a valid Amyumi PDF Converter driver for ARM. However install still fails with Sage. If I work around by creating my own printer using the new Amyuni 650 ARM driver and name it Sage 100 PDF Converter it does trick sage into thinking it has the driver. If I Electronic deliver an invoice for instance it opens a dialog box to pick a location to save the file. Which it does generate. But does not complete the process through sage.
Seems like with more windows machines moving to ARM. And all mac virtualization moving to ARM. It would be nice to have a solution for this. So again I will keep up with this and hopefully for future users we come up with something workable.
When attempting to invoice out emails from Navision 2009, navision uses a tool "amyuni pdf converter" which when installed you have to rename "navision PDF converter". The converter saves a pdf to a temp location where navision grabs it and emails it out. It also does the same for payslips and remittance emails within navision.
Nav 2009 requires version amyuni 4.5.0 which could be issue with that version and windows 10. I installed version 5.5.0 and that worked but it brings up a prompt when exporting and then you need to save the name of the pdf identically to the name navision looks for the pdf in the temp location and doing that can take a good 5 minutes per email. When your doing 20 emails at a time this can cause a bit of an issue
I have spoken with our Dynamics Navision support partner and asked them to remove the Amyuni PDF converter and setup bullzip to work in its place. Their support department has said it will work but it may have a problem with batch emailing. Is this correct? or will bullzip work with one or multiple invoice or payroll emails with PDF printed attachments?
Hi Stephano, sorry this might be slightly off the original topic but can you tell me if NAV 2009 R2 is fully supported for windows 10, and if so is there any documentation that states this from Microsoft? reason i say this is our support partner for NAV is trying to brush their hands of our issues due to Windows 10 being installed and they are stating that its not supported.
Thanks for the reply stephano. Yea this is correct. Amyuni pdf printer was setup by external company. What can I setup to make this work and allow silent printing without the popup and file location requirements.
The Alpha Anywhere Application Server for IIS installer will notify you if an error occurs during installation with details on where to find the installAmyuniPrints.log file. If the installer for Alpha Anywhere Application Server for IIS is run in silent mode, the error will be logged to the Windows Event log. If the Alpha Anywhere Application Server for IIS installer is not running in silent mode, the IIS installer will display a message similar to the one below:
If an unsigned printer driver was installed prior to installing the Amyuni Printer driver, the Amyuni installer will fail with an "Error Code: 87 Invalid Parameter" error. As Amyuni explains on their website:
"During installation the Microsoft certified printer driver, the Windows operating system copies and renames the amyuni.inf file and related printer driver files to the %system32%\DriverStore\FileRepository folder. Under some situations, Windows fails to copy the .inf file because of previous installations, mainly if the previous installation was for an unsigned printer driver. When installing a new version of the printer driver, the error 87 Invalid Parameters appears."
Before attempting to reinstall the Amyuni printer, the DriverStore\FileRepository folder needs to be cleaned up. For more information about this error and how to resolve it, follow the instructions detailed on Amyuni's website, Invalid Parameters installing PDF Converter printer driver.
Once you have resolved the issue causing the Amyuni installer to fail, you need to install the Amyuni printer. This is done by running the A5IISInstallServer.exe file found in the installation directory for the IIS Application Server.
Locate the A5IISInstallServer.exe file. It can be found in the installation directory for Alpha Anywhere Application Server for IIS. Open command prompt with the "Run as Administrator" option and run the installer:
3a8082e126