Hi Alvin, Thanks for raising this with us. Typically this error occurs when the Reports.dic is damaged or the GL Account Index Master is corrupt. I suggest that we recreate the GL00105 first, then recreate the reports dictionary again, and see if this corrects the problem for you. Please follow the steps in this KB to recreate the GL00105: After this lets recreate the reports dictionary then see if the modified reports can now be printed.
If the problem continues after this the error may be occurring due to a damaged layout. If we recreate the problem report and update the table links this may correct the error. I suggest that we do the following to see if we can correct the error for one of the reports 1. Export the report that is creating the error from Customization Maintenance 2. Delete the report from modified reports in Report Writer 3.
Add it back over from the left side pane in Reports window 4. Recreate the modifications on the report 5. Verify security is still granted to the report in Alternate/Modified Forms and Reports After this try printing the report to see if the error occurs. If the error does not occur lets repeat these steps for the other modified reports that have this error. Please let me know if you would like any additional information on this issue Regards Rob. Hey Alvin, Any luck with your issue here? I am having difficulty here with another set of tables related to the GLAccountMaster I came across an issue where we are unable to create new accounts or modify existing accounts using the Account Maintenance Window.
Read the forum post on the Microsoft Dynamics Community. A save operation on table 'RM_OPEN' has created a duplicate key. - Microsoft Dynamics GP Forum Community Forum. Microsoft Dynamics GP 2018 R2 has been released. As promised, It has been recently announced that Microsoft Dynamics GP 2018 R2 is released with lots of new features.
This led me to create the auto procedures to try and fix the problem. (SQL Maintenance under the the MS GP menu).
However this gives me an error 'Unable to register GLAccountMSTRFilter1'. Hence I came across your post here.
I'm going to be attempting the same thing and trying to recreate the tables.
Option 2: Let me fix it myself Follow these steps to fix this problem yourself: Note All scripts that are in the “Resolution” section must be run in a query tool. To open the appropriate query tool, follow these guidelines:.
If you are using Microsoft SQL Server 2000, run the statement in Query Analyzer. To open Management Studio, click Start, point to Programs, point to Microsoft SQL Server 2000 and then click Query Analyzer. To run a script, click New Query. If you are using Microsoft SQL Server 2005, run the statement in Microsoft SQL Server Management Studio. To open Management Studio, click Start, point to Programs, point to Microsoft SQL Server 2005 and then click SQL Server Management Studio.
To run a script, click New Query. If you are using Microsoft SQL Server 2005 Express, run the statement in Microsoft SQL Server Management Studio Express. To open Management Studio Express, click Start, point to Programs, point to Microsoft SQL Server 2005 and then click SQL Server Management Studio Express. To run a script, click New Query. If you are using Microsoft SQL Server 2008, run the statement in Microsoft SQL Server Management Studio. To open Management Studio, click Start, point to Programs, point to Microsoft SQL Server 2008 and then click SQL Server Management Studio. To run a script, click New Query To run the script, follow these steps: 1.
Make sure that you have a current backup of the company database, and ask all users to exit Microsoft Dynamics GP. To create the backup in Microsoft Dynamics GP, follow these steps after all users log off from Microsoft Dynamics GP: a.
On the File menu, click Backup. In the Company Name list, click the company that you want to back up. In the Select the backup file box, click the yellow folder to open the location in which you want to put the backup file. View the contents of the following tables to verify that all users are logged off: DYNAMICS.ACTIVITY, DYNAMICS.SY00800, DYNAMICS.SY00801, TEMPDB.DEXLOCK, and TEMPDB.DEXSESSION. To do this, run the following script. SELECT. FROM DYNAMICS.ACTIVITY SELECT.
FROM DYNAMICS.SY00800 SELECT. FROM DYNAMICS.SY00801 SELECT. FROM TEMPDB.DEXLOCK SELECT. FROM TEMPDB.DEXSESSION Note When all users are logged off from Microsoft Dynamics GP, these tables will not have any records in them. If no results are returned, go to ‘Step 4’. Otherwise, clear the stuck records by using any of the following appropriate scripts.
DELETE DYNAMICS.ACTIVITY DELETE DYNAMICS.SY00800 DELETE DYNAMICS.SY00801 DELETE TEMPDB.DEXLOCK DELETE TEMPDB.DEXSESSION 4. Run the following script against the company database.
Replace XXX with the batch number or the name of the batch that you are trying to post or select in Microsoft Dynamics GP. UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 where BACHNUMB='XXX' Note The value of BACHNUMB is the same as the value of the Batch ID window in Microsoft Dynamics GP. Verify the accuracy of the transactions. Verify that you can edit and post the batches. Note For more information about Payroll check interruptions, click the following article number to view the article in the Microsoft Knowledge Base.