- if it is a modified report, please use the Alternate/Modified Forms and Reports window (Administration | Setup | System | Alternate/Modified Forms and Reports) to temporarily switch to the default report when testing the issue.
If the default report prints fine it tells you there is something incorrect with the modification (possibly the template) that is causing issue and we can troubleshoot in this direction on next contact.
Regarding Templates, please insure that 'Standard' is the selection in the Report Destination screen and you are also printing the Edit List out to the screen in your testing.
- If not modified there is a chance that prior temp/cache information may be interfering with the new printing if it is linked to the User/Report in question in some manner (which will not populate the Process Monitor.
To help insure this is not the case please perform the following before re-testing the issue:
1. Insure ALL USERS are out of Dynamics GP.
2. Log into SQL Server Management Studio on the SQL Server housing Dynamics GP.
3. Make a new backup of the erring company db.
4. Run the following SQL commands against the erring SQL instance:
DELETE DYNAMICS..ACTIVITY
DELETE DYNAMICS..SY00800
DELETE DYNAMICS..SY00801
DELETE TEMPDB..DEX_LOCK
DELETE TEMPDB..DEX_SESSION
5. Right-click and stop | start the SQL instance, which will clear the rest of the temp/cache materials in the system from past processing.
6. Log into Dynamics GP as the 'sa' user and retest the issue.
We have attempted these solutions, but the issue persists.
- We are using the standard print, not the word templates
- The receiving edit list is not modified
- The live and TEST companies use the same dictionary,
and same report, and it prints In the test company, but not the live
- We also tested by using a clean gp client install and
clean dictionary with the same issue
- We ran the script and restarted the server
- We ran a complete check links and reconcile
- We logged in and tested the print as sa, but the report
does not print
-------------------------------------------------------------------
After a few days , the issue went away by itself, and the receivings edit list started printing again.
The only solutions we could think would be
- Some corrupted transaction was deleted, posted or processed to allow the printing to continue
- Some nightly process ran which allowed the printing to continue
No comments:
Post a Comment