	My Account Logout My Account My Account Site Admin

Products Company Support Contact Us

asi_script Login Failed, or Error Exporting File. Error: Logon Failed. after upgrade to GP 9.0

8 February 2007

Issue Description

When users are attempt to print Crystal Reports, after upgrading to Forms Printer for GP 9.0, they get these errors or similar :

Sent to printer:

asi_script
Logon failed.
Details: [Database Vendor Code: 18456]

Sent to screen:

Screen
Error Exporting File. Error: Logon Failed.
Details: [Database Vendor Code: 18456] Error Number: -2147189176

The cause is that the Custom Report Authentication Window Login information has not been correctly set to allow the Crystal Engine to Log in to the SQL Database:

Solution

Here is some information about a new Setup screen in FP for GP 9, if you have not set up this screen correctly, it can cause a 'login error'

In Forms Printer for GP 9.0 there is a new Company Specific Setup window for the Authentication method to use for Crystal Reports - Make sure this is set for each company. (see P21 of FPDOC90.pdf in the GP application folder) (this setup window is reached from Setup->Company-> Forms Printer, then the Setup Button on that window for Custom Report Authentication.

The Typical setting for Great Plains Installations should be the_last_ Option (in build 28) : Use SQL Authentication Information for Crystal Reports - where you uncheck all options, and just specify a valid SQL user and password (created using SQL Enterprise Manager) that has appropriate SQL permissions to print the reports (typically put the user in the DYNGRP Role of SQL Server in the Company Databases). (the username and password is not validated upon entry into this screen, so make sure they are correct by using them to log into SQL server using Query Analyser or some other sql tool, and make sure they have permissions to SELECT data from the Great Plains Databases.) (by convention, many create a SQL user named "CRYSTALUSER" or similar, and assign it a fixed password in enterprise manager, but 'sa' can be used to get started..) (note that it must be a SQL user and password that was created with SQL enterprise manager, not one created by Great Plains - since Great Plains re-encrypts the password and does not actually create the user with the password you type)

From the SETUP (authentication method) button on the Forms Printer Setup window... is this window:

If you chose to use the far less typical option (Integrated authentication) - then each Windows domain user that will print a report needs to be set up as a SQL user in SQL Server.

the words "Integrated Authentication" (aka Windows Authentication ) have a specific meaning for Micrsosoft SQL server, and in most cases , this method would _not_ be used with Great Plains (see SQL Books online - Windows Authentication )

If these values are correct, and you can print the Sample Report from the Forms Printer "Generic Reports" folder, It may be that the Custom report you are printing is using a DSN that exists on the machine where the error is occuring - and is attempting to use settings from that DSN that are inappropriate (trusted login). It is recommended that the report be designed to insure that the DSN it is designed with, does not exist at runtime on the workstations (see "Making reports generic") in the FPDOC90.pdf.