Production Temp Files

In addition to log files, Production generates numerous temporary work files. These are written to the system's temp folder. For example:

C:\Users\<user>\AppData\Local\Temp\ProductionService.

The User in this case is the user that the DiveLine service runs as.

If the DiveLine service runs as "Local System", storage of temporary files may be in a different place separate from Users. For example:

C:\Windows\system32\config\systemprofile\Application Data\

C:\Windows\system32\config\systemprofile\AppData\

If you are using parameter nodes or executing extensions (of type PHP), another location sometimes used for temporary files is:

C:\Windows\Temp\

Production attempts to clean up these files, but failure is possible. Clearing out the system's temp folders, no mater where they are located, is a good idea.

There is currently no way in Workbench or Production to change the location of the system's temp folder. It may be possible by adjusting the settings on a Windows server. For example, see https://www.howtogeek.com/285710/how-to-move-windows-temporary-folders-to-another-drive/

NOTE: Starting with Production 7.1(13), Production will write its work files to the temp folder inside the project. If a temp folder does not exist in the project, one will be added. These files are hidden from view when using the Workbench Explorer, since the folder starts with a period. For example:

DI/Projects/<project>/temp/.production-engine

The cleanup routines for all temporary files generated by Production have also been improved—most work files are now deleted when the process completes.

NOTE: Starting with version 7.1(19), the temporary work files with file extension .table-index are also written to a temp folder inside the project: /temp/.production-service/table-index.