I too am getting this unspecified error for a custom crystal report.   I have a crystal report that is using a numeric parameter.  when I add the report to the Sage 100 menu, try and run the report I get the error message, unspecified error.  When I run the report in crystal and NOT from Sage menu I don't get the error.  Here is my environment and what I have tested.   I would like to know why a numeric value works and sometimes doesn't work.   

Sage 100 advanced

Upgraded from 2015 to 2018

Created the report in 2018 NOT 2015

Installed on a windows 10 machine - the report ran fine - no errors

We have a hosted server - connect via RDP - running windows server 12 R2 - the report will get an error message we running off Sage menu

Installed Sage 2018 on a separate server 12 -  added the report to the Sage menu and DID NOT get an error message. 

So my question is, is this a Sage issue since it doesn't run on Sage menu OR is this a Crystal issue?  

Thanks again for keeping this post open. I am too still looking for an answer from Sage as It only happens on some workstations so is it a hardware issue?    How do you compare ODBC versions on different machines? Client has been using Sage 100 std  how would ODBC get changed.  Reports from 2016 still run fine on the problem machines.

I found the issue (I think) On the server and the one WS that got this error Sage 2014 was installed. The client keeps all the PR old stuff in the old companies for archive, Once I removed sage 2014 I removed 2018 and crystal and reinstalled and no problems. Look for older versions of Sage installed - The server which still has the issue says

DSN has architecture mis match between driver and application  I cannot remove the driver and am working with IT to resolve this Thanks for the ODBC hint

I have this problem for a customer with v2018 Premium. This was a new install, not an upgrade. But, they have Sage 50 on the same server and workstations. Might that cause this problem?

What is the issue with crystal 2011 and 2016 not be able to select date parameters correctly. Now have a new are report selecting invoices for a certain date range runs fine in sage 2014 but hangs and never finishes in sage 2018. 

Are you running this through the Sage 100 Application?  What happens if you run the report directly inside of Crystal Reports?

Are you running this through the Sage 100 Application?  What happens if you run the report directly inside of Crystal Reports?

I just ran into this error for the first time ever and wanted to let everyone know what I did to resolve it. My client just got all new Windows 10 computers and all reports ran just fine standard/custom-written except for this one report. After reading thru this thread someone mentioned above about numeric parameters. When I changed the numeric parameter from numeric to string, the report ran just fine. This is version 2017 PU6. Hope this helps anyone else that runs into this issue.