Others

How to Fix New-SPConfigurationDatabase SPPersistedColumnDefinition Error

WPS Editor Sep 30, 2026 869 views

Question details

The user needs to resolve an error that occurs when attempting to create a SharePoint Server farm using PowerShell.

How to Fix New-SPConfigurationDatabase SPPersistedColumnDefinition Error

Product: Microsoft SharePoint Server
Device & OS: not provided
Scenario: Creating a new SharePoint Server farm configuration database via the New-SPConfigurationDatabase PowerShell command.
Observed behavior: The command fails, throwing an SPPersistedColumnDefinition deleted error and an SPDeletedConcurrencyException.

Before you start

Gather your complete PowerShell script, the full error stack trace, and your SharePoint and SQL Server version details before seeking advanced technical support.

Solution 1Recommended

Consult the Microsoft Q&A SharePoint Server Community

Because this involves complex on-premises server architecture, the best resolution path is consulting dedicated Microsoft SharePoint Server engineers.

SharePoint Server farm creation issues involving the configuration database and concurrency exceptions usually point to deep SQL Server backend conflicts or stale configuration cache files.

Since standard Microsoft community forums heavily focus on SharePoint Online, you must direct this query to the specific Microsoft Q&A portal designed for on-premises SharePoint deployment.

Navigate to Microsoft Q&A

Open your web browser and go to the official Microsoft Q&A platform (learn.microsoft.com/en-us/answers).

Formulate your question

Create a new post detailing your server setup. Include the exact New-SPConfigurationDatabase PowerShell command you executed.

Include error specifics

Paste the complete SPDeletedConcurrencyException and SPPersistedColumnDefinition error logs, as well as the Correlation ID if provided by the shell.

Apply the correct tags

Tag your post specifically with 'SharePoint Server' to ensure it reaches enterprise deployment experts rather than SharePoint Online administrators.

Consult the Microsoft Q&A SharePoint Server Community

Important Context: Do not delete your original server deployment logs, as the Microsoft support team will likely request them to diagnose the database concurrency failure.

Free Microsoft Office alternative

Need a Lightweight Alternative for Your Office Documents? Try WPS Office

While setting up complex enterprise environments like Microsoft SharePoint Server requires intense technical troubleshooting, managing your everyday office documents should be simple. WPS Office is a highly compatible, fast, and free alternative to Microsoft Office that doesn't require heavy server configurations.

1. Download the software: Visit the official WPS Office website and download the free installer for your operating system.
2. Install WPS Office: Run the setup file and follow the quick on-screen prompts to complete the installation in minutes.
3. Open your documents: Launch WPS Office and directly open your existing Microsoft Office files to start working immediately.

Seamlessly open, edit, and save Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx) with zero formatting loss.Free, lightweight, and ultra-fast installation process.Familiar user interface that requires no steep learning curve.Built-in PDF editing, conversion, and collaboration tools.

microsoft office alternative - wps office

Frequently Asked Questions

What causes the SPDeletedConcurrencyException during SharePoint farm creation?

This exception generally occurs when multiple processes attempt to access or modify the same object in the configuration database at the same time, or if a previous failed farm installation left orphaned objects in the SQL database.

Why shouldn't I post SharePoint Server PowerShell questions in standard Microsoft forums?

Standard Microsoft 365 community forums are largely monitored by experts specializing in SharePoint Online. Because SharePoint Online and SharePoint Server have entirely different backend architectures, on-premises deployment issues like New-SPConfigurationDatabase errors require the specialized Microsoft Q&A SharePoint Server tag to find the right expertise.

How can I clear the SharePoint configuration cache to fix database errors?

Clearing the configuration cache involves stopping the SharePoint Timer Service, locating the cache folder (typically under ProgramData\Microsoft\SharePoint\Config), deleting the XML files (but NOT the cache.ini file), resetting the cache.ini value to 1, and restarting the Timer Service. However, proceed with caution and backup your servers before attempting this.

Office Quick Solutions