Attempt was made to Print a Custom Report before setting the Authentication Method:
27 February 2007
After upgrading to Forms Printer for Dynamics GP 9.0 - and a Report is printed, you may be presented with a dialog that states:
Attempt was made to Print a Custom Report before setting the Authentication Method: Report Integration Setup Window will be opened.
The Custom Report Authentication Setup window will then be opened, however, the Crystal Report will continue to run and unfortuanately may sometimes Crash Dynamics GP before you can make and save the necessary authentication information.
To rectify the issue for a particular Great Plains Company, be sure to set the SQL User that should be used for Login by the Custom Crystal Report. This setting is new for forms Printer for Dynamics GP 9.0 and is described on P21 of the FPDOC90.pdf installed into the Dynamics GP folder by the Forms Printer installer.
Notes: To Set the Authentication Method to use for Custom Reports:
- Log into the Great Plains Company
- Choose Tools->Setup->Company->Forms Printer
- Press The Setup Button for "Setup the Authentication Method to use for Custom Reports."
On the window presented, do NOT check integrated authentication - (Dynamics GP does not currently support integrated authentication for SQL Server, so you would not want to use this except in very special cases.)
Instead, fill out a SQL Server username and password for the Crystal Reports Engine to use for logging in, either 'sa' , or some SQL user specifically created using SQL Enterprise Manager or SQL Server Management Studio. This SQL user should either be placed in the DYNGRP Role in all of the Dynamics GP Databases, or otherwise given appropriate database read permissions needed for all custom Crystal Reports printed. ('sa' will have permission by default)