Sage 100

We have a version 4.50.4.0 customer getting the wrong version of crytstal installed for this workstation. We ahve made sure that permissions to folders were correct application running as administarator and manually registered (as administrator) CRAXDRT.DLL. Any other ideas?

Have you tried re-running the workstation setup?

I have an old note that generally mirrors what Gary did with an additional note that if still receiving errors look for multiple copies of the DLL ( CRAXDRT.DLL )

Yes reran workstation setup. I will look for more copies of the DLL

I have ask the obvious question but do they happen to have crystal installed or a new version of sage installed?

No they are off maintenance and are using 4.50.4.0 I found an article from 4ACC that stated: From the ..\MAS90\Home directory for the Sage 100c 2018 copy pvxwin32.exe.config to the ..\MAS90\Home directory of the previous version of Sage 100. Copy the same file to the ..\MAS90\Home directory for ALL the workstations. Scares the heck out of me...

In some cases I recall installing full Crystal Reports and having that solve this type of problem (although this is not the typical first step)

@wayne that's what I was thinking. Gary, unless they have 2018 that part shouldn't be needed that seems to be talking about the new crystal in use for sage 2018 (at this point just 2018). Though the fix works like a charm its just the pvxwin32.exe.config file if I recall.

This is only happening on one workstation? Is it Standard or Advanced? I would uninstall Sage 100 and Crystal Reports (if it is installed on that workstation), remove the Sage printers, make sure that Add Remove Programs doesn't show any Crystal Reports or Sage 100, restart the workstation, reinstall Sage 100, verify the Sage Printer settings are okay, run as administrator if using a later version of Windows, then try previewing a Sage 100 custom report.

The problem was the version 4.50.4. In our ""incident"" our software repository was also damaged. Long story short, we migrated the machine to a new domain, we added a second server within that domain and installed a fresh workstation on that machine with terminal server/citrix access. The issue was only through remote desktop access. This resolved issue for customer.