Queue Associates’ Help Desk team receives support tickets every day. Some of the issues raised are brought up repeatedly by our customers. We are going to share the three most popular incidents that we’ve received for Microsoft Dynamics SL, as well as what we’ll term “secret” solutions.

1. Error – ROI.EXE has stopped working when trying to print preview a report within Dynamics SL. This common error is typically caused if there isn’t a default printer set in Dynamics. To set a default printer in Dynamics follow the steps below.

1. From inside of Dynamics SL, please click on the Dynamics Icon (upper left hand corner of screen) and then select Printer Setup (see below).
   

2. Once the Printer Options screen opens up, please make sure that the Use Windows Default Printer is checked (see below) and Save as Default is checked. Then you can try to run your report again now.
   

2. If you try to release a batch in AP and AR and it is partially released, we recommend you run the AP/AR edit report. This report will show you the content of the batch. Many times, there may be a missing account, or a missing detail line item.
   
3. What to do if you receive error 10247 when trying to release a batch? Typically, if you log out completely from Dynamics SL and log back in, it usually resolves the error. Once you log back in, try releasing the batch from the release batch screen in the module in which you created the batch.  This error is usually caused by something stuck in memory.

Contact Queue Associates

Please contact Queue Associates (a Microsoft Dynamics Gold Partner) to learn more about our services related to supporting legacy Microsoft Dynamics solutions — Dynamics SL, AX, CRM, NAV, GP, etc. — and transformation to the cloud-based Microsoft Dynamics 365 suite.

You can reach us by completing the form on our CONTACT page, or by calling us at the Queue office phone number for your local region (U.S., as well as Global locations).