FP: Couldn't close table error

(0) Share

Report

Posted on by Community Member

We have GP2010 deployed for our users via terminal services. About three months ago, we began receiving reports from some of our users that there were receiving an error as follows:

FP:Couldn't close table!

The users who reported this error might receive it while changing databases, when exiting GP, or even sometimes when closing an open window within GP. We've been working with two different teams from Microsoft and have submitted every piece of information imaginable to them. They've made some recommendations, which we've followed, but our users are still getting the error at times. What I'm wondering is if anyone else has experienced this issue on a prolonged basis, and if so, what you did to actually resolve it once and for all.

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Richard Wheeler 75,848 Moderator on at

Like (0)

Report

This is caused by lost network connectivity. Check your server NIC, router, switch and cabling. If your server NIC is built into the motherboard try a firmware upgrade. You need to find the bad component. If it is the NIC in the server you will need a motherboard replacement.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have seen this with virus software, will need to confirm which ones. Try turning the virus software off and see if you get the error. Here is some troubleshooting I got along the way somewhere.

Since they cannot keep the antivirus turned off all the time and you have excluded the TNT*.idx, TNT*.dat and TNT*.tmp. file types but it is still happening the next step would be to exclude certain folders.

The best way to get around this issue is to exclude the GP folder on the workstations and the GL and SQL Management Studio folders on the server. This way you can keep the antivirus program running but it will not interrupt the normal processes in GP.

Was this reply helpful? Yes No
Brian_DiFi 2,410 on at

Like (0)

Report

Chris, did you find a fix for your instance of this error yet?

Was this reply helpful? Yes No