Skip to main content

How to configure the NuGenesis RPC service to use a TEMP folder on a different drive - WKB22278

Article number: 22278


Configure the NuGenesis RPC service so that it uses a TEMP folder on a large drive other than it's currently-configured TEMP location.


  • NuGenesis 8 SDMS
  • NuGenesis 7.1 SDMS
  • Windows Server 2012 R2
  • Windows Server 2008 R2


  1. Identify the NuGenesis RPC service user
  2. Log in to the NuGenesis File Capture server as the RPC service user
  3. Open the Control Panel > System applet
  4. Click the Advanced tab
  5. Click the Environment Variables button
  6. Under the heading "User variables for <username>", modify the TEMP and TMP variables to point to a path on a large drive
    • Example: TEMP = G:\Temp; TMP = G:\Temp
  7. Click OK to the dialog boxes
  8. Create the Temp folder if it does not already exist
  9. Restart the NuGenesis RPC service


NuGenesis creates temporary files in it's TEMP folder as a normal part of the operation of the four File Capture modules.  As such, it is recommended to move the RPC service's to a non-system drive with plenty of free space for all NuGenesis File Capture servers.  It is best to dedicate a drive in the server to the RPC service's TEMP folder, and a separate drive for the NuGenesis TE_TEMP folder.  The size of the RPC service's TEMP drive is dependent on the amount of data that will "flow" through the server; a good baseline size is 50 GB.  More space may be needed if the server routinely archives large data sets.  This is particularly true if the TE module reports "[NG14510]" errors in it's log file.

Here is a description of how the four modules use the TEMP folder:

  • Archive Agent: it copies archived files to TEMP in order to produced a compressed copy of the file.  The compressed file is moved to TE_TEMP and the uncompressed copy is deleted from TEMP.
  • Transport Engine: immediately after a successful upload of a file to the database or Managed Storage, the TE module will download a copy of the file to TEMP and run a CRC32 checksum on it.  The module then compares the calculated checksum with the checksum as stored in the database, in order to verify that the file has not been corrupted in transit.  The file in TEMP is deleted if the CRC comparison is successful.
  • Data Management: when the DM prepares to delete an archived file from it's original location, it first downloads the file from the database or Managed Storage, generates a CRC32 checksum on the downloaded file in TEMP, and compares the value to that of the stored checksum in the database.  The purpose of this comparison is the same as with the Transport Engine: to ensure that the files have not been modified in transit, and to ensure that the files can be successfully downloaded from NuGenesis.  The file in TEMP is deleted if the CRC comparison is successful.
  • Offline Storage Manager: the OSM module performs CRC checks on files similar to that described above for the TE and DM modules when OSM prepares to move files to offline storage.  It checks that the files have been downloaded correctly from the primary storage location, and checks that the files as stored in the offline location are not corrupted.

Not able to find a solution? Click here to request help.