Sage 100

Anyone seen this before (MAS 90 4.3.21)? I've tried everything and no joy. Get this error when printing with BF modules, whereas all is fine in non-BF modules. No errors when using Admin account. I made sure user was in admin group on local domain and in active directory. Has full access to folder above MAS90, as well as paperless folders. Can create/delete files/folders within share. Set full permissions for SagePDF Converter and using SagePDF port. Running MAS with Admin privileges from desktop. Verified correct properties of Sage PDF Converter via Regedit and manually registered CDINTF300.DLL on w/s. After printing, the chart of accounts report entry is made in Paperless, but actual PDF file does not exist.

I had this exact same message recently. Another user had added a text box and had not assigned a font to it. When I went through the form and made sure all fields had a font assigned to it the error went away.

It's also written up in the ""Old"" knowledgebase - Resolution ID 496162

I recall seeing it before but do not recall the solution. Did you try rebooting the server (very long shot)?

Diana, can you post a link?

I've seen something similar when UAC is enabled and Paperless can't launch Adobe. Paperless can't launch/answer the ""Do you want to allow this program"" prompt.

http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=496162

Mark, what happened to suddenly start causing this? Is this only on one workstation? Since there are no errors under admin, then it is a security issue. Can local user access the local temp folder? I have encountered that issue before.

Mark - I just had this yesterday. It ended up being user rights, but I can't tell you exactly where because the IT guy on the other end of the phone was just muttering to himself and told us to try it again and it worked. I believe what actually make it work was rerunning WKSETUP with better user permissions.

Oh, and it worked after rerunning WKSETUP even though the size of the DLL (that CD one) was incorrect for the version of Win 7, the port on the Sage PDF converter was pointing to LPT1 again and the security on the printer was incorrect!!!!!

Or just a shot in the dark... ;)

Perfect @BethBowers - now everything we thought we knew about printing to paperless is worthless??

We have seen this a number of times. We usually build the PDF folder tree within the same parent folder as the MAS 90 folder and for those we have rarely seen the message. On networks we don't control, either it has been permissions the PDF folder or we have had to use the IP address instead of the server name.

@JohnBroadfoot - wasn't the case with this client, because I do the same thing with my PDF trees. Had to be something local that got fixed with the rerun. And @ThereseLogeais - I could NOT believe it was working! Client and I had gone through fixing those things, then when they reran WKSETUP it of course unfixed them - and it still worked! Usually the port and the security are my ""go to"" items for Win 7 - at least for 64 bit. This was a 32 bit, so must not be an issue there. And the DLL size must not be an issue, either, as it was running the 64 bit DLL. Or, it's those old Indian burial grounds the building is built on.

I am willing to bet a drink at the bar at the next Summit that it has to do with fonts or lack thereof on the form itself.

Installing on Win 7's is still an art. I have a round two with client today. Depleted most of my tricks last week trying to get paperless running. It isn't working as admin yet,so my list of gotchas are still endless. Need to sit down and develop a NASA like check list for installing on WIN 7's....

@BethBowers - Thanks for the reminder; we also have had to regularly change the report to a dummy called Sage. @LouisAraiza - At least for us, this issue doesn't seem to have been related to any particular form.

Thanks for everyone's input. Here's what I found: - Not the form, as it occurs on ALL reports, except non-BF modules. I'd expect to not be able to print properly from admin account, but I can. - tried changing the paperless path using IP address and also changed path to be inside MAS90 folder. Same results, so that's not it. - UAC has been disabled from the start, so that's not it. - PDF tree is at same level as MAS90 folder and share is one folder above that. I ended up creating a new network user and assigned the same security groups as original, which worked perfectly. I can only imagine that the original network users rights didn't propagate properly (even though IT guy says he forced it again last week). Lastly, I noticed that the file server has 2 Sage PDF printers, one of which is redirected to this users PC. Tried removing the printer from server, but it won't let me delete (even with Administrator account). So either the redirect is screwing it up or user rights are not propagated. Will have IT guy try to remove the redirected printer from server and try again. WHAT A PITA! So far, 4 effin hours on this task.

We have a lot of clients that use terminal servers and redirected printers has been the greatest pain. We have ended up puttiing a Queue on the terminal server for every printer at satellite offices that have more than one user and not allowing redirection from that office. Locations with a single remote user are allowed to redirect without issues. In our experience, MAS does not like multiple copys of the same printer and the issue affected both regular and paperless printing.

@MarkKotyla I feel your pain -- 2.5 hours yesterday on a user rights issue that I pegged from the start (first 15 seconds) but IT couldn't comprehend. Finally when they started making changes things just worked.

FWIW - Not sure if this is related, but will share since it was news to me. Something I got today from support re the Sage PDF Printer in a Win7 x64 environment. I had to make a folder; C:\SagePDF, and then when creating the new printer port in devices and printers, use C:\SagePDF\SagePDF for the name. I had not run across this advice before, but was able to successfully print to the Paperless Printer on this station after creating the port this way.

@MarkKotyla - is the resolution here that there was some issue with user security rights?

Thanks Greg. First I heard of this approach as well. @WayneSchulz Still awaiting call from IT guy, so not sure if it's the printer redirect or security. I'm thinking security, but will post back once resolved.

I agree with @JohnBroadfoot had the same issue with Server 2008 using redirected printers - could not get that to work at all. Had to install the printer on the server and set it up to print directly to the printers IP address and disable the re-direction for the remote users.