Pre-Upgrade Validation Fails ("SQL Standard media is not available") & Cache Corruption Error [68:1] in Dark Site Environment

Hello,

I am attempting to perform an in-place upgrade of my CommServe in a dark site environment, which includes upgrading the SQL.

I am facing a critical loop, and standard procedures have failed.

Problem 1: Pre-Upgrade Validation Failure

When I run the Setup.exe from my downloaded installation package, the Pre-Upgrade Validation check fails with this error:

Automatic upgrade of the existing SQL Server instance is allowed but SQL Standard media is not available in the source media.

Context:

• I downloaded the full installation package from the Commvault Cloud Services portal onto an internet-facing machine.

• I ensured to include all Third-Party Software (Microsoft SQL Server Standard).

• I have manually verified that the SQL media is physically present in my source package (in the ...\ThirdParty\MSSQL\SQL_Standard_Edition directory).

• My CommServe is a "dark site" and has no internet connectivity.

Problem 2: Software Cache Corruption (The Root Cause)

I suspect the validation is failing because it's checking the corrupt local Software Cache on the CommServe, not my new source package.

When I attempt to synchronize my new package with the CommServe using the standard procedure for dark sites (Tools > Add/Remove Software > Copy Software), the job fails with Error Code [68:1].

Checking the DownloadSoftware.log on the CommServe reveals the true underlying issue: a cache database corruption.

Log Error:

Summary & Troubleshooting Steps Taken

This puts me in a "Catch-22" situation:

1. I cannot run the Upgrade because the Pre-Upgrade check fails (it can't find the SQL media).

2. I cannot fix the cache using "Copy Software" because the copy job also fails due to the cache database corruption (the transaction id error).

What I have already tried without success:

• Manually clearing the contents of the C:\Program Files\Commvault\ContentStore\SoftwareCache directory. The subsequent "Copy Software" job fails with the same transaction ID error.

• Running the Pre-Upgrade Validation from the new, full source package (it still fails, likely because it defaults to checking the corrupt local cache).

• Attempting a manual in-place upgrade of SQL Server (this also did not resolve the Commvault validation check).

My Question: How can I forcefully reset or rebuild the local Software Cache database (the "DVD") in a dark site environment? I need a way to bypass the transaction id conflict so I can successfully copy my new, full installation media into the cache and proceed with the upgrade.

Thank you.