FP: Couldn't close table

This question has suggested answer(s)

Client is running Total Defense r12 from CA virus software.

Various Testing has shown the FP:Couldn't Close Table errors only happens if virus software is turned on. Error occurs when AP processing.

Have added the following exclusions to virus software: TNT*.idx, TNT*.dat and TNT*.tmp. These were added after looking at a post by others that have successfully by-passed the errors with these exclusions. The error continues if the virus software is turned on.

Are there other exclusions which should be added?

Currently have client turn of virus software during AP processing, but this is not an acceptable long term solution for obvious reasons.

Warren

All Replies
  • This is happening to us too with the virus protection software Kaspersky.  We can turn off the program at the desk top level, but the issue stays because the software is also at the network/server level which cannot be deactivated.

    We are on GP 2010 sp2/R2.  We upgraded to sp2 this year and changed our virus software at the beginning of the year, so I don't know if this is strictly an issue with sp2 or if it solely revolves around how Kaspersky works compared to our prior virus protection software (ie, we did not have this error...and others...last year).

    Dale

  • We have started experiencing this proble since yesterday and none sysmptoms mentioned here are valid in our situation. So what could be another situation ?

  • FP: Can't close table can also be cause by lost network connectivity. Are you experiencing router issues?

    Richard E. Wheeler 2013 and 2014 MVP

    Member Microsoft Academic Alliance

    www.rbsolutions.com Revered Business Solutions Ballston Lake, NY  518-877-0763 x10

  • It is not just TNT*.* files.

    There are also named *.dat and *.idx files in a TNT* subfolder. These are application "memory" tables as opposed to the temporary tables.

    David

    David Musgrave
    Microsoft Dynamics GP Support Asia Pacific

    Any views contained within are my personal views and not necessarily Microsoft policy.
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • The problem with our network and went away as soon as we addressed the network issue.

    Thank you all very much.