Finance | Project Operations, Human Resources, ...

Table Open Error when Printing the Fixed Assets General Ledger Posting Report

(3) Share

Report

Posted on by texasbbqribs

172

Greetings!

When a client tries to print (screen or file, we didn't try printer) the Fixed Assets General Ledger Posting report from the Fixed Assets General Ledger Posting window, they get a message immediately that says, "Table open error."

We've tried it in Fabrikam and in the production company and get the same results, so it seems as though the issue is systemwide.

We stripped the dynamics.set file to only GP and Fixed Assets.

We modified the dynamics.exe.config to strip out all add-ins.

We went to the temp folder and deleted files starting with TNT.

There is no modified report.

They can perform every other function in GP they've tried.

They can post to GL. When they post and the system tries to print the report, a table open error appears.

Does anybody have any ideas as to what is causing this issue.

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Lisa at AonC.com 1,091 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Thank you for all the details!

A few questions:

Did this used to work and now is not working? (If so, did anything change?)

Is there any antivirus system that can be temporarily disabled to rule that out?

If you set up an Alternate/Modified Forms and Reports ID with NO access to modified windows and reports (for all products) and launch GP without any modified forms/reports dictionaries in place, does the report print?

If this is a new issue, have you restarted the SQL server and any server that has the modified forms/reports dictionaries?

Have you tried to print directly from the GP SQL Server (or GP App Server) and not just from a client workstation (in case it is ODBC-related)?

Was this reply helpful? Yes No
texasbbqribs 172 on at

Like (0)

Report
Copy link

Link copied!

I believe this is the first time since upgrading to the latest version of GP they have tried it. Prior to the upgrade, it worked.

I don't know about antivirus software, so we'll check on that piece.

Will have to try.

Will have to try.

Yes, we are testing this from the SQL server.

Was this reply helpful? Yes No
Suggested answer

David Musgrave MVP ... 14,137 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

I believe the table open error is caused by a mismatch in the table definition in the custom reports dictionary for the product and the main application dictionary for the product.

To confirm you will need to temporarily rename the custom reports dictionary for the product (Fixed Assets) and temporarily adjust security to make sure it is using the original report.

If that works, I would recommend exporting all the custom reports for Fixed Assets as packages, then move/delete the dictionary and then reimport the packages to recreate the custom reports dictionary. This process will recopy the base resources from the application dictionary including the table definitions.

Kind regards

David

Was this reply helpful? Yes No
BJ-09051414-0 389 on at

Like (0)

Report
Copy link

Link copied!
Hello,

I would give the following a try.

As the report is not modified and our Fixed Assets Dictionary is not part of the Dynamics dictionary, you would need to run a repair on GP to rebuild that R309 dictionary.

Have all users log out.

Make a copy of the Dynamics Code Folder.

For example, my location would be C:\Program Files (x86)\Microsoft Dynamics\GP20XX

I would right click and select copy. Then paste it to a different location.

Locate the R309.dic Dictionary on the workstation having the problem.

By default, the location is:

C:\Program Files (x86)\Microsoft Dynamics\GP$GP17\Data

Rename this to have .old at the end.

Run a repair on GP which will rebuild this Dictionary.

This is done in Control Panel.

Go to Control Panel >> Programs >> Uninstall a Program (or Add/Remove Programs dependent on your Windows version.

Highlight 'Microsoft Dynamics GP 20XX' and select 'Change'.

From the Microsoft Dynamics GP 20XX window that populates select 'Repair' >> 'Repair' and run through the resulting wizard.

This will recreate the R309.dic file in the code folder with the necessary resources.

When completed, launch Dynamics GP and say 'yes' to run Utilities.

Once completed with Utilities, log in into Dynamics GP as SA and verify if the error still occurs.

NOTE: You can put the original code folder back by renaming the current one and renaming the copy to be the correct name.
The below might not be helpful as our dictionaries for Fixed Assets are not in the Dynamics.dic and not stored in the Reports dictionaries. However, problems with reports, I also suggest going through the below as well if the above does not help.

Have all users logged out if your dictionaries are shared.

Export all Customized Forms and Reports.

Open the Customization Maintenance window.

Dynamics GP | Customize | Customization Maintenance.

Select the first item.

Scroll to the bottom. Hold Shift. Click the Last item which should select all.

Click Export.

Choose a name and location.

Click Save.

Go to the location where your dictionaries are stored.

Normally this is the Data Folder in the DYNAMICS GP Folder.

Locate the Reports.dic and Forms Dic.

Rename these to have .old at the end.

Now, go into the Dex.ini file and change the following lines to TRUE.

SYNCHRONIZE

INITIAL

Save the file.

Run Synchronization of the Dictionaries.

Start GP utilities.

Get up to the additional tasks window and click the drop down and select Synchronize Forms and Reports Dictionaries.

Click Process.

Click the folder look up in the next window and select the Dynamics.dic.

Click Next. Once the process finishes, and exit utilities.

Bring back in the Reports and Forms that were exported in steps 2.

Open the Customization Maintenance window.

Dynamics GP | Customize | Customization Maintenance.

Click import.

Point the Package file that was exported in step 2.

Click import.

This recreates new Forms and Reports Dictionaries.

Test if the issue still occurs.

If it still occurs, go through the Synchronization process again (Step 5)

Test again to see if the issue still occurs.

The order of operation can matter at times and why I suggest running Synchronization again.

Once all steps are completed, go back into the Dex.ini and change INITIAL back to FALSE.

SYNCHRONIZE automatically switches back.

One last thing, If the report is not modified, what if you move it to the modified sections, set security to use the modified version and see if that works?

Below is a screenshot of the main table of my report from TWO. Compare the Main Table being used on your report vs mine.

All tables used on the report.

I hope this helps!

Thank you!

Was this reply helpful? Yes No