FSI FAQs

Please follow the instructions below to create a GP Reports Viewer log file for our support team to troubleshoot issues.

On the Dynamics GP Home Page, right click on the Navigation Pane and choose Add, then Add Window.

Under Available Windows, expand GP Reports Viewer, then Company and select GP Reports Viewer - Support Debug.

Click Add, then Done.

You should now have a shortcut for the GP Reports Viewer - Support Debug window on the Navigation Pane, please click on it to open the window.

Click Run Log Viewer, a new GP Reports Log Viewer window will open.

Follow the steps to generate the report where you are receiving the error message.Once done, you should see a lot of entries in the GP Reports Log Viewer window.

Select all the entries using Ctrl+A, then use Ctrl+C to copy them and Ctrl+V to paste them into a notepad file (or another file).

Please send the file to us at [email protected] or attach it to your support ticket.

ISSUE:Receiving"Error creating shared memory (87)"when trying to print report using GP Reports Viewer. Issue reported on all reports on a particular computer, but only some (not all) computers.

SOLUTION: Please follow the steps below:

Exit Dynamics GP.

Launch Dynamics GP by right clicking on the shortcut and selecting Run as administrator.

Go into GP Reports Viewer and print a report.

If there are any errors, please send us the details.

If there were no errors, exit Dynamics GP.

Launch Dynamics GP regularly (without Run as administrator) and print a report using GP Reports Viewer.

KB ARTICLE:95366038

LAST UPDATED: July 15, 2015

If you have been asked by our Support Team to capture a Debug Log File, please follow the steps below:

Add a shortcut to the GP Reports Viewer - Support Dialog window. On the GP Home Page, right click in the Navigation Pane on the left, and choose Add | Add Window. Expand GP Reports Viewer, then Company and select GP Reports Viewer - Support Debug, click Add:

Click on the newly created shortcut on the Navigation Pane to open the Support Dialog. Enter a path to where the log file should be saved and include a filename (e.g. LogFile.txt), then click Start Log:

Follow the steps that are causing the error, click OK to any error messages received and then exit the area where the error is occurring (e.g. close the GP Reports Viewer window or the Sales Transaction Entry window).

On the Support Debug window click the End Log button.

In Windows Explorer, navigate to where the log file has been created and open it in Notepad. IMPORTANT NOTE: The log file captures the SQL password in clear text. Therefore, it is recommended that you open the file and look for entries for "LogonServer", ensure that the password listed is correct and then replace the password with some other value (e.g. "password" or "pw") and save the file.

Email the resulting log file to the Support Team.

KB ARTICLE: 21034032

ISSUE: Receiving"Remove range operation in 'GPRV_POP_PrintDocList_TEMP' failed accessing SQL data" error when printing a PO using the POP replacement functionality. Clicking More Info shows: "Number of results columns doesn't match table definition". This started happening after upgrading Dynamics GP and GP Reports Viewer from an older version.

SOLUTION 1:When emailing for SOP and POP documents was introduced to GP Reports Viewer a new parameter was needed for both SOP and POP reports to allow the emailing to work. Details on the parameters required can be found in the Modifying a Report for Use with Purchase Order Processing section of the GP Reports Viewer User Guide.

SOLUTION 2:If you have already added the additional parameter to your POP reports and are still seeing this error, it is likely that the SQL objects used by the POP replacement feature did not get updated properly during the GP Reports Viewer upgrade. Below are the steps to fix this:

1. Get all users out of the Dynamics GP company that is having the problem.

2. Make a backup of the SQL database for that company.

3. In SQL Server Management Studio run the following script against the company database:

drop table GPRV_POP50200 drop proc zDP_GPRV_POP50200F_1 drop proc zDP_GPRV_POP50200L_1 drop proc zDP_GPRV_POP50200N_1 drop proc zDP_GPRV_POP50200SD drop proc zDP_GPRV_POP50200SI drop proc zDP_GPRV_POP50200SS_1

4. Log into Dynamics GP as 'sa'.

5. Go to Microsoft Dynamics GP | Tols | GP Reports Viewer | Installation, select the company in the list, click Install, then Yes to the installation confirmation message.

6. If your Crystal or SSRS report is referencing table GPRV_POP50200 directly (as opposed to pointing to a view or stored procedure that includes that table), please open your report and update it to include the current fields in the table. In Crystal Reports this can be done by going to Database | Verify Database. In SSRS this can be done by refreshing the fields in your Dataset.

KB ARTICLE:101537506

LAST UPDATED:December 5, 2015

QUESTION:Dynamics GP 2013 R2 just came out, is my GP Reports Viewer compatible with it?

ANSWER:Yes. GP Reports Viewer build 4 for Dynamics GP 2013 has been tested with Dynamics GP 2013 R2 and is compatible. You may find that some of the menu icons are not where they used to be. This was caused by the addition of the new menu ribbonin GP 2013 R2. If you prefer to see the oldmenus, you can change this under User Preferences- this is a per-user setting.

KB ARTICLE:70724976

LAST UPDATED:June 5, 2014

QUESTION:In Dynamics GP 2013 you can name the sample company database anything you want. Will GP Reports Viewer still work without a registration key if the sample company database is not TWO?

ANSWER:Yes. Regardless of what you call the sample company database, GP Reports Viewer will still work with no registration key in the sample company.

KB ARTICLE:69599037

LAST UPDATED: May 29, 2014

ISSUE: Users receive error message "The permissions granted to user Domain/User are insufficient for performing this operation" when trying to print SSRS reports using GP Reports Viewer. This only happens for some users.

SOLUTION: Make sure the users printing the reports have permissions to them in the SSRS Report Manager.

KB ARTICLE:23740356

LAST UPDATED: May 7, 2013

ISSUE: Users receive"Catastrophic failure"error after printing report using GP Reports Viewer. Clicking OK on the error allows the users to continue working.

SOLUTION: Change the Regional Settings on the computer to English (United States) or English (United Kingdom).

SOURCE: Support ticket 1525

KB ARTICLE:23639576

LAST UPDATED: April 22, 2013

ISSUE:Receiving one of the following errors when printing a Crystal Report based on a stored procedure using GP Reports Viewer:

"Invalid argument provided"

"Login failed"

"Failed to open the connection. Details: [Database Vendor Code: 17]"

Another symptom of this issue is if the database the report is based on does not switch automatically to the current Dynamics GP company using GP Reports Viewer.

SOLUTION: Please contact us by emailing [email protected] or clicking new above to start a new support incident. We will send you a new GPReports.exe file. Steps to install it:

Rename your existingGPReports.exe file located in your GP installation directory to GPReportsOLD.exe

Unzip the file and remove the '.rename' file extension so that the file is now called GPReports.exe and copy it into your GP installation directory

Right click on the newGPReports.exefile and choose Properties, if you have an Unblock button at the bottom, please click it and choose Apply, then OK to close the Properties window

Launch Dynamics GP and try to print the report you were having trouble with again

If you receive an Open File - Security Warning saying that theGPReports.exe is from an Unknown Publisher, uncheck the box at the bottom left for Always ask before opening this file

If you are still having trouble printing the report properly after this, please let us know.

FIXED: The fix for this issue is included in builds 60 and higher for GP 2010.

SOURCE:Support Ticket 1409

KB ARTICLE: 21809891

LAST UPDATED: August 9, 2012

ISSUE: Receiving one or more of the following errors when launching Dynamics GP 2010 R2 (SP 2):

"Procedure trigger registration failed: SOP_DP_Opt_Single_Return"

"Procedure trigger registration failed: SOP_DP_No_Opt_Single_Return"

"Procedure trigger registration failed: SOP_DP_OPT"

SOLUTION: Build 55 or higher of GP Reports Viewer is required for compatibility with Dynamics GP 2010 R2 (or SP 2). New builds of GP Reports Viewer can be downloaded from our website: www.GPReportsViewer.com/downloads.aspx.

SOURCE: Support ticket 1367

KB ARTICLE: 21326968

LAST UPDATED: April 24, 2012

ISSUE: A shortcut is created in GP Reports Viewer, however after clicking OK and going back to the GP Reports Viewer - Report Shortcuts window, the details of the shortcut are not shown. This issue was reported on Windows 2008 Server (64-bit).

SOLUTION: This was resolved by changing the Language for non-Unicode programs to English in the regional settings of the server to match the settings of the SQL Server.

SOURCE: Support ticket 1318

KB ARTICLE: 21048977

LAST UPDATED: February 23, 2012

ISSUE: Receiving "Access violation at address 0046A807 in module 'GPReports.exe'. Read of address 00000000." when trying to print report using GP Reports Viewer. Issue reported on only some (not all) reports and on some (not all) computers.

SOLUTION: This was caused by Arabic characters in the names of some Crystal Reports. Changing the report names to English and confirming the path to them was showing up correctly in GP Reports Viewer setup fixed the problem.

SOURCE: Support ticket 1202

KB ARTICLE: 20840632

LAST UPDATED: October 26, 2011

ISSUE:Receiving"This field name is not known" error when running Crystal report using GP Reports Viewer.

SOLUTION: In this case the Crystal report was pointing to a Command that was then pointing to a SQL stored procedure. Changing the report to point directly to the stored procedure resolved the issue.

SOURCE: Support Ticket 1320

KB ARTICLE: 20942812

LAST UPDATED: February 3, 2012

ISSUE:Receiving"Failed to retrieve data from database. Details: [Database Vendor Code: 911]"when printing a Crystal report using GP Reports Viewer on a workstation. Printing the same report on the server works with no error.

SOLUTION: Open the report in Crystal Reports locally on the same network where the GP SQL data is and update the location of the data source(s) and all the SQL objects. Re-save the report.

DETAILED STEPS:

Launch Crystal Reports and open your report.

Navigate to Database | Set Datasource Location.

Select or create a new ODBC (RDO) connection in the Replace with section of the window.

Select the first SQL object listed on the Current Data Source section by clicking on it once, then select the corresponding SQL object on theReplace with section. Once both are selected click Update.

Repeat step 4 for each SQL object on your report.

Click Close, then save your Crystal Report.

SOURCE: Support ticket 1205

KB ARTICLE: 20946558

LAST UPDATED: March 27, 2012

ISSUE:Receiving"Database Connection Error: [Database Vendor code:229]"when trying to print Crystal report using GP Reports Viewer. Issue reported on only one report, but on all computers.

SOLUTION: Verify that the SQL user set up on the GP Reports Viewer - Setup Options window (GP | Tools | GP Reports Viewer | Setup Options) has permissions to the SQL objects used on the report.

SOURCE: Support ticket 1185

KB ARTICLE: 20930493

LAST UPDATED: July 5, 2011

ISSUE: The same report shows up twice on the Additional menu after a shortcut has been deleted and re-created for a report. This is also sometimes seen when switching GP companies right after creating a report shortcut.

SOLUTION: Restarting the Dynamics GP application will get rid of the doubled up item.

SOURCE: Support ticket 1160

KB ARTICLE: 20919591

LAST UPDATED: December 1, 2010

ISSUE: Receiving"A get/change operation on table 'GPRV_Trigger_Param' could not find a record." error when creating a report shortcut and mapping a parameter.

SOLUTION: Delete the shortcut and re-create it.

SOURCE: Support ticket 1189

KB ARTICLE: 20929147

LAST UPDATED: July 6, 2011

ISSUE:Receiving"Login failed. Details: [Database Vendor Code: 18456]"when printing a Crystal report using GP Reports Viewer logged in as a regular GP user. User 'sa' can run report with no error.

MORE INFORMATION: Error 18456 is a SQL Server error for an authentication/login issue.

SOLUTION: On the GP Reports Viewer - Report Maintenance window (GP | Tools | GP Reports Viewer | Reports), make sure that"Use Default SQL Login and Password from Setup Options Window"is selected for all Crystal reports.

SOURCE: Support ticket 1187

KB ARTICLE: 20914661

LAST UPDATED: July 7, 2011

ISSUE:Receiving"Login failed. Details: [Database Vendor Code: 233]"when printing a Crystal report using GP Reports Viewer. Issue reported on all Crystal reports and all computers.

SOLUTION: On the GP Reports Viewer - Report Maintenance window (GP | Tools | GP Reports Viewer | Reports), make sure that"Use Default SQL Login and Password from Setup Options Window"is selected for all Crystal reports.

SOURCE: Support ticket 1206

KB ARTICLE: 20923902

LAST UPDATED: November 1, 2011

ISSUE: GP Reports Viewer has been installed, but there are no options for it on the menus. User is POWERUSER in GP, so permissions are not an issue.

EXPLANATION: This can happen ifGP Reports Viewer is not installed to the same location as the Dynamics GP code.

By default, the GP Reports Viewer installer will suggest the location of the very first Dynamics.set file it finds on your computer for the GP Reports Viewer installation. If you have an older version or another installation of Dynamics GP on the same computer, the installer may have suggested the wrong location during installation.

SOLUTION:To fix this, uninstall GP Reports Viewer, then install it again. (Please note that simply moving the physical files does not usually work.)

SOURCE: Support ticket 1152

KB ARTICLE: 20876682

LAST UPDATED: October 4, 2010

ISSUE:Receiving"Exception EOleSysError in module GPReports.exe at 00074879. Error accessing the OLE registry."when trying to print report using GP Reports Viewer. Issue reported on all reports on a particular computer, but only some (not all) computers.

Another variation of the error message:

"Exception EOleSysError in module GPReports.exe at 0005E4BD. Error accessing the OLE registry."

SOLUTION: Please follow the steps below:

Exit Dynamics GP.

Launch Dynamics GP by right clicking on the shortcut and selecting Run as administrator.

Go into GP Reports Viewer and print a report.

If there are any errors, please send us the details.

If there were no errors, exit Dynamics GP.

Launch Dynamics GP regularly (without Run as administrator) and print a report using GP Reports Viewer.

ADDITIONAL INFORMATION: This error can be avoided in the future by installing GP Reports Viewer as the local built-in administrator and running a report in GP Reports Viewer while still logged in as the local built-in administrator.

SOURCE: Support tickets 1192, 1197

KB ARTICLE: 20886163

LAST UPDATED: January 15, 2016

ISSUE: Users receive"Catastrophic failure" error after printing report using GP Reports Viewer. Clicking OK on the error allows user to continue working.

SOLUTION: On GP Reports Viewer - ReportMaintenance window uncheck "Copy and run report locally instead of running from server"option.

SOURCE: Support ticket 1162

KB ARTICLE:20827456

LAST UPDATED: December 17, 2010