Error Message

In the Enterprise Vault (EV) Event Log on the EV server:
 

Type: Error

Event: 8390

Source: Enterprise Vault

Category: Storage Online

Description:

The EnterpriseVault.DirectoryConnection object reported an error.

Not enough storage is available to process this command.

For more information, see Help and Support Center at  http://evevent.veritas.com/rosetta/showevent.asp

V-437-8390

Type: Error

Event: 6796

Source: Enterprise Vault

Category: Storage Online

Description:

A COM exception has been raised.

Not enough storage is available to process this command. [0x80070008]

Internal reference

.\PartitionCache.cpp (CPartitionCache::ReadEntry) [lines {47,88,91}] built Feb 15 16:59:07 2008

An exception is raised when a process encounters an unexpected fault.

For more information, see Help and Support Center at  http://evevent.veritas.com/rosetta/showevent.asp

V-437-6796

Type: Error

Event: 6616

Source: Enterprise Vault

Category: Storage Online

Description:

Vault Store database Read SavesetInformation record.

[Internal reference VSDBRSI21]

For more information, see Help and Support Center at  http://evevent.veritas.com/rosetta/showevent.asp

V-437-6616

The TEMP and TMP folders on the EV server are running out of disk space.  These folders are typically for the Vault Service Account (VSA), but can also be system environment folders as well.

Verify that the EV Server has ample space for the TEMP and TMP directories for both the VSA and the default System Environment variables settings.  Best practice recommendation is to have from 20 to 60 GB of free space on the drive hosting the TEMP and TMP folders for normal EV Storage Service operations.  If the EV Server is also the EV Indexing Server, the best practice recommendation is to have from 40 to 80 GB free on the drive hosting the TEMP and TMP folders.

To determine the path to the TEMP and TMP folders:

1. Log onto the EV server as the VSA.
2. Open a Command Prompt window.
3. Execute the following command:
   1. set
4. Review the output by scrolling up and down as necessary to locate the TEMP and TMP folder paths (these paths are normally identical).
5. Note the drive letter in the path to these folders.

If the current drive and / or path for the TEMP and TMP directories needs to be moved to another drive, follow the steps below:

1. Access the Environment Variables page.
2. For Windows Server 2003 installations:
   1. Right click on the My Computer icon.
   2. Select the Properties option.
   3. Click on the Advanced Tab.
3. For Windows Server 2008 and greater installations:
   1. Click on Start.
   2. Navigate to and select Control Panel.
   3. Double click on the System icon.
   4. Click the Advanced system settings link.
4. Click on the Environment Variables Button.
5. Change the location of the TEMP and TMP directory.
   1. For the VSA:
      1. Locate and work in the User variables for window in the upper half of the dialog box.
      2. Locate and click on the TEMP variable.
      3. Click the Edit... button.
      4. Edit the Variable value: field contents to reflect the new drive and path to the VSA's TEMP folder.
      5. Click the OK button to save the change.
      6. Locate and click on the TMP variable.
      7. Click the Edit... button.
      8. Edit the Variable value: field contents to reflect the new drive and path to the VSA's TEMP folder.
      9. Click the OK button to save the change.
   2. For the System variables, if needed:
      1. Locate and work in the System variables window in the lower half of the dialog box.
      2. Locate and click on the TEMP variable.
      3. Click the Edit... button.
      4. Edit the Variable value: field contents to reflect the new drive and path to the VSA's TEMP folder.
      5. Click the OK button to save the change.
      6. Locate and click on the TMP variable.
      7. Click the Edit... button.
      8. Edit the Variable value: field contents to reflect the new drive and path to the VSA's TEMP folder.
      9. Click the OK button to save the change.
   3. Click OK as needed to close the Environment Variables and System Properties dialog boxes.
6. Reboot the server.