Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Event ID 18 is logged in the System log on a computer that is running Windows Storage Server 2003

View products that this article applies to.


On a computer that is running Microsoft Windows Storage Server 2003, an event that resembles the following may be logged in the System log:

Date: 7/15/2005
Source: psman5
Time: 07:58:24
Type: Error
Event ID: 18
User: N/A

This issue occurs when the used section of the Persistent True Images cache exceeds approximately 90 percent.
Note A Persistent True Image is also referred to as a Snapshot in Persistent Storage Manager 2.1 for Server Appliances.

↑ Back to the top


This issue occurs because Persistent Storage Manager 2.1 for Server Appliances deletes the oldest least-prioritized Persistent True Image. This behavior occurs when the deletion threshold of the Persistent True Images cache is reached or exceeded. However, when the used part of the Persistent Storage Manager cache exceeds the deletion threshold, the oldest Persistent True Image cannot be deleted. Therefore, the new Persistent True Image cannot be created.

↑ Back to the top


To resolve this issue, increase the Persistent True Images cache file size.

To increase the Persistent True Image cache size, follow these steps:
  1. Open the Persistent Storage Manager WebUI, and then click Disks.
  2. On the Disks page, click Persistent Storage Manager.
  3. On the Persistent Storage Manager page, click Volume Setting.
  4. On the Volume Setting page, click Configure.
  5. In the Cache box, type a new value that is larger than the value of the default percentage.

↑ Back to the top

More information

All Persistent True Images must be deleted before you increase the Persistent Storage Manager cache file size.

Cache settings are not always displayed correctly. For example, if you configure a volume in the Volume Settings section to have a cache file size of 2 percent, and then you create a Persistent True Image, the Cache field is unavailable. Then, if you click Restore Defaults, the value of the cache file size changes to 20 percent. When you click OK, the Volume Settings page is displayed and the cache file size appears to have been changed. However, when you return to the configuration page, the Cache field displays 2% instead of 20%. This is the designed behavior.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

↑ Back to the top

Keywords: KB925635, kbprb, kbnofix, kbtshoot

↑ Back to the top

Article Info
Article ID : 925635
Revision : 3
Created on : 10/11/2007
Published on : 10/11/2007
Exists online : False
Views : 269