Issue/Introduction

This article helps troubleshoot expired upload session errors when importing an OVF template into ZSphere.

Symptoms

• Uploading is interrupted or reports an expired upload session while an OVF template is being imported.
• The VMDK file exists when checked manually, but OVF import cannot continue.

Environment

• Product: ZVF
• Version: 4.x, 5.x
• Component: ZSphere
• Affected object: OVF template import
• Scenario: For template and tool issues, confirm the current version, deployment type, storage type, and operation timeline.

Possible causes

• The VMDK file name referenced inside the OVF file differs from the actual file name.
• The template file was renamed, file-name case changed after archive extraction, or special characters are present.
• The network was interrupted or the session timed out during upload, but template descriptor errors must be excluded first.

Resolution

Perform the following checks in order, and record the affected object, occurrence time, complete error message, and current status.

1. Extract the template archive and check the VMDK name referenced by the File or References node in the OVF file.
2. Confirm that the actual VMDK file name, case, and extension exactly match the OVF descriptor.
3. Correct the OVF reference or restore the original file name, and then upload again.
4. If the issue persists, record the browser time, management service logs, and upload task ID.

Remediation

1. Change the VMDK file name referenced in the OVF file to exactly match the actual VMDK file name, case, and extension, or restore the actual file name.
2. Package the template again and upload it again.

Verification

• The OVF template uploads successfully and import completes.
• The imported template can create virtual machines normally, and the management service logs no longer report an expired upload session.