Finding in the Wild | Citrix PVS – Database Connection Drops Because the vDisk Version Is 20!

Last updated:

Sometimes the smallest details lead to surprisingly extensive troubleshooting.

I recently received a report of particularly unusual behavior in Citrix Provisioning Services (PVS):

⚠️ The symptoms

The PVS environment experienced repeated, brief database connection interruptions.

The following events appeared regularly in the event log:

• Event IDs 201 / 214 – PVS database connectivity issues
• SQL Error 8023 – Error processing a supplied value
• PVS loses its database connection for a few seconds and temporarily goes offline.

The strange part: not all targets were affected, only one specific group.

🔬 The cause – reproduced by Citrix in the lab

After extensive analysis, Citrix reproduced the issue in its lab using the supplied data.

The cause lies in the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL), which PVS uses to communicate with its SQL database.

The decisive trigger?

vDisk version number 20!

When a PVS target starts or stops, PVS writes a license usage record to the database. This record also includes the version number of the vDisk in use.

If that version number is exactly 20, the driver transmits the value incorrectly.

SQL Server rejects the operation with Error 8023.

PVS interprets this error as a loss of database connectivity and briefly goes offline.

In the investigated environment, exactly one active vDisk was running version 20. This also explained why only the associated targets were affected.

🛠 The workaround

The solution is surprisingly straightforward:

✅ Do not use vDisk version 20 in production.
✅ Deploy a newer version, 21 or higher.
✅ Alternatively, merge the vDisk versions as appropriate.
✅ For other vDisks, avoid keeping version 20 in use long-term.

Important: this is not a general SQL connectivity issue. Restarting SQL Server or adjusting network timeouts does not eliminate the underlying trigger.

📌 Vendor status

Citrix has reproduced the behavior in its lab.

A permanent fix is planned for a future PVS release.

💡 My takeaway

A single version number can be enough to cause brief PVS database connectivity failures.

If you see PVS Events 201/214 together with SQL Error 8023, check the vDisk versions in use as well.

The number 20 certainly would not have been my first suspect. 😉

Author: Manuel Winkel

Manuel Winkel is an IT consultant at Deyda Consulting GmbH, specializing in Citrix, NetScaler ADC, Microsoft infrastructure, and IT security. In his articles, he shares field-tested solutions, technical insights, and practical recommendations for operating modern IT environments securely and reliably.

Leave a Reply

Your email address will not be published. Required fields are marked *