WDC_Field_security_Tag_TEMP

I thought I’d provide some context and troubleshooting steps for a common error that we’ve been seeing for a while now. Some of this information and further troubleshooting steps can be found in the following blog post too. 

SQL Connectivity Errors seen in Microsoft Dynamics GP - Microsoft Dynamics GP Community

The 'WDC_Field_Security_Tag_TEMP' table is a temporary table that is created by Dynamics GP when needed, and then deleted when it is no longer used. If the temp tables are not dropped after they are no longer needed by Microsoft Dynamics GP, this type of error can occur. The names of these .tmp files and matching folders in the TEMP directory will always start with ‘TNT’ and there will be a corresponding folder created with the same name as well. 

In the folder, there are .idx and .dat files for tables such as ASIEXP91, ASIEXP94, ASIEXP97 and others. Launching SmartList, it’ll add more to this folder. These are the files that, when missing, throw the type of error being seen, mentioning ‘the path does not exist’ as an example. 

Usually, this issue can be resolved by restarting the SQL Server or clearing out the user’s TEMP table on the workstation, but sometimes the issue can occur due to restrictions put on the TEMP table. 

It is recommended that any anti-virus software that you might be using isn’t putting restrictions on the user’s TEMP folder as well as the GP code folder (usually located in C:\Program Files (x86)\Microsoft Dynamics). We also recommend that you add the ‘Everyone’ security group and grant it full control to the two folders (TEMP and GP code) to ensure nothing like this happens again. 

Some other things that can be done are as follows:

1.  For the user(s) that are seeing these errors in Dynamics GP, on the machine they access Dynamics GP from, have them do the following while NOT currently logged into the Dynamics GP application:

 A. Click on Start > Run, type in %temp% and click OK, this will open their own TEMP directory on the machine.
 B. Delete as many files as you're able to; some files will be in use and cannot be deleted, but most should be able to be deleted.
 C. Once this is completed, have the user launch Dynamics GP on the machine again and see if the errors continue.

Even on a terminal server environment, Dynamics GP will be writing to a TEMP directory for that user's profile, which they should be able to get to by clicking on Start > Run, type in %temp% and click OK.

With the user(s) logged out of Dynamics GP, you can delete the files with extensions of .dat, .idx, .log and .ini.  Then, when launching Dynamics GP with that user, GP will re-write the objects back into the TEMP directory, where you can see if this resolves the errors or not.

Ideally, we'd want users to have a minimum of Read/Write permissions on the TEMP directory.

 2. If the errors continue or occur for multiple users/multiple machines, then please try the following as well.

  A. Have all users log out of Dynamics GP and any other applications that use the SQL Server.
  B.  Restart your SQL Server instance that holds the Dynamics GP databases.
  C.  After the SQL Server instance is restarted, have the users log back into Dynamics GP and see if the errors still occur.

 This should remove all temporary objects from the TEMPDB system database for SQL Server, which Dynamics GP also writes to.

 3. Antivirus can sometimes cause similar issues, to the point where we recommend having exclusions from the following:

--The GP code directory itself

--Dynamics.exe file

--Any shared directories that have the modified forms and reports dictionary files in them, for Dynamics GP, if any.

--The following file extensions:  .cnk, .dic, .chm, .set, .ini, .dat, .idx, .vba, .log.

Finally, we have seen some environments where a Group Policy or Registry entry is set up to remove the files from the TEMP folder periodically throughout the day and ends up causing this type of error to occur. While policies like that can be handy, it does tend to cause a lot of connection issues or app crashes. So, it’s best to either remove those types of entries or have them run at the end of the day when all the users are out of Dynamnics GP.