HP E200 VSS Provider/Microsoft Windows LTU and Media Kit manual Exec message

Table 3 Application Events (continued)

Event ID	Description	Action
	message indicates VSS has released the VSS Provider for Microsoft
	Windows from the VSS control.
5020	Snapshot ID <snapshot_ID> prepared.	None

Internal logging, <snapshot_ID>. is a unique identifier.

5040	SnapshotSet <snapshot_set> created.	None
	Indicates the SnapshotSet request has been fulfilled.

5041	Exec: <message>	None
	Internal logging, which records the task from the VSS Provider for
	Microsoft Windows to the HP 3PAR Storage System.
5042	Virtual Copy <virtual_copy_number> exported.	None

Apoint-in-time snapshot disk has been created and exported to the host.

5043 Virtual Copy <virtual_copy_ID> removed.

The exported snapshot disk has been removed from the host.

5050 Unsupported feature <feature_ID>.

The VSS Provider for Microsoft Windows received an unsupported request through the VSS framework.

5051 A snapshot in one set has exceeded the maximum limitation.

VSS Provider for Microsoft Windows supports up to 64 snapshots in one set. This request has exceeded the maximum limitation.

5052 Could not allocate memory.

Internal error, failed to allocate memory during computing.

None

The request is unsupported by the current release. Contact your local service provider for a future release.

Reduce the number of snapshot requests in one snapshot set to less than 64, and request again.

Insufficient memory is available to allow VSS Provider for Microsoft Windows to operate normally. Shutdown some of the idle applications that are still running and resume the previously failed task.

5053 Could not communicate with InForm CLI.

The initial check on the InForm CLI configuration has generated an error. This could mean several thing went wrong:

•the InForm CLI is not installed.

•A valid password file could not be found or its contents are not valid for this installation.

5054 <message>

This is an error message that usually is associated with Event ID 5041. This event describes the cause to the action on Event ID 5041.

See “System Setup” (page 10), to check for CLI installation.

Correct the error and retry again, or contact your local service provider if the error continues.

5055 <token_ID>: Invalid token.

Internal error. The output format does not match.

5056 Could not open the volume mapping file: <mapping_file>. Failed to open the mapping file that is generated by the showvv –dCLI command.

5057 Could not open file: <filename>

The VSS Provider for Microsoft Windows failed to open the temporary file <filename> that is generated internally.

Set the LogLevel to ‘4’ to show the detail error message to log file, and retry.

Set the LogLevel to ‘4’ and look for vvmap as <some_file_name> from the 3parprov.log.

Look for file <filename> to see the if the permissions are set correctly.

22 Diagnostics