Load Report Failed error when trying to print on a Terminal Server or Citrix Server.  When you try to print or preview a report in Microsoft Dynamics SL, you receive the following error message:

SolomonReporting
Load Report Failed

This problem occurs when the Windows Terminal Server or the Citrix Server configuration does not contain a C: drive.


How to add a help file for a third party screen in SL 7.0?  If you need to update your SL 6.5 code for SL 7.0, try using the freeware program called HelpMaker to create any of the standard kind of help files. Others have been successful in importing their old  .HLP file and compiling a .CHM file using this approach.

Troubleshooting Performance Issues in Microsoft Dynamics SL 7.0 There are a number of possible places users can see performance issues and there are a number of possible causes for these issues.  Here are some steps to take to help troubleshoot most performance issues:

General slowness during login or opening screens:

1.    The TCP/IP offload engine (TOE) is turned on in Windows Server 2003.  Knowledge Base Article 945130 has more information on this issue.

2.    If running Windows 2003 server, apply the update available in KB 948496 to disable various Scalable Networking Pack features which can cause connection/performance issues.

3.    If the computer(s) running SL do not have a connection to the internet, or have a slow or unreliable connection, then the "Check for certificate revocation" setting in Internet Explorer can cause a 5-10 second delay opening most screens.  KB 941009 goes into more detail on this

4.    Installing the program files on the client machine can improve performance.  KB 939242 goes into more detail on why.

5.    If using Terminal Server and the "Delete Temporary Folders On Exit" setting is set to YES, then each time a user logs into SL, the menu will be regenerated causing a noticeable delay during login.  Changing this setting to "NO" in Terminal Services Configuration can help prevent this.  KB 947428 goes into more detail.

6.    If you notice a 5-10 second delay when opening customized screens after moving SL to a new server and disconnecting the old server, there may be some stray registry entries left on the client machine that still references the old server name.  The slowness occurs as SL attempts to contact the old server and times out.  KB 946304 goes into more detail.

7.    A bad printer device or slow connection to a printer can slow down the start of Dynamics SL.  Verify that the printer specified in Printer Setup (98.220.00) is valid.

Slowness during specific processing or report running:

1.    If the slowness is relatively consistent, running a SQL Profiler trace is the best place to start.  KB 925033 shows how to run a SQL Profiler trace in SQL 2005.  This should help narrow down what specific SQL statements are causing the long duration and what tables are involved. 

2.    If the slowness can be narrowed down to a specific table or group of tables, then reindexing those tables can help.  This can be done by running the "Master Indexes, Views, and Stored Procedures" scenario in Database Maintenance.  As an alternative, the specific drop and create statements for the indexes can be found in SQL files in the \DB\Scripts\App folder in the SL program files directory.

3.    If the slowness is seen when tabbing off of the company ID field in various screens, it may be due to the issue described in KB 945132.  This should be corrected in SL 7.0 Service Pack 1.

4.    If the slowness is seen when printing Flexible Billings invoices, it may be due to crystal attempting to reload the subreports that are on the invoice format.  KB 950713 goes into more detail on how to correct this.

 The Pay When Paid Process in 7.0 is fully automated, based on a new "Pay When Paid" terms code in the voucher. There is a new table that links A/P vouchers to A/R invoices in the AR data base. This link is automatically established if you are using Flexible Billings in Project. If you are manually creating invoices in A/R, you can manually link an invoice to an A/P Voucher (and also inquire into all linked and unlinked invoice and vouchers) using 2 new screens: Pay When Paid Link Assistant (03.080) and Pay When Paid Link Entry (03.090). Once linked, there is no manual flag to be updated. The AR Payment Release batch will automatically update the link status if it finds that a linked invoice has been fully paid. AP Payment selection will then automatically select pay-when-paid vouchers whose linked invoice is fully paid.

BP 4.0 & SDK  The Business Portal SDK was discontinued in 4.0. Custom development should be done in the WSS SDK and/or the MOSS SDK to incorporate additional SL data into Business Portal. MOSS provides the Business Data Catalog, which allows you to connect to any SL SQL table and display it in MOSS Web Parts. In the MOSS SDK, a tool is provided called the Business Data Catalog Definition Editor, which allows you to connect to a SQL data source, and drag/drop the tables in which you want to connect.

Business Ready Licensing - what's different?  Business Ready Licensing is a new method of licensing for Microsoft Dynamics SL 7.0.  When entering the registration keys, instead of having to enter one key for every module... you enter one key which will unlock the majority of the modules.  This is either the A1 or B1 key.  For example... instead of having to enter a key for GL, AP, and AR... you only need to enter the A1 or B1 key.  If you attempt to enter the GL, AP, or AR key, you will get an "invalid registration key" message.  You may also notice that not all the modules show up in the PV list on the registration screen.  This again is because the modules that are not listed will be unlocked by the A1 or B1 keys.

Do you know where to find the Solomon.ini file?  (Click the link to find out.)

Tips On Installing Microsoft Dynamics SL 7.0 on a Terminal Server.  This hot topic covers server settings and hot fixes that should be installed for the best performance when running Dynamics SL on a terminal server.