Umbraco Cloud
CMSHeartcoreDXPMarketplace
  • What is Umbraco Cloud?
  • Frequently asked questions
  • Security
    • Web Application Firewall
  • Sustainability Best Practices
  • Getting Started
    • Explore Umbraco Cloud
    • The Cloud Portal
      • Organizations
      • Sustainability Dashboard
    • Project Overview
    • Environments
    • Flexible Environments (beta)
    • Baselines
      • Baseline Merge Conflicts
      • Break Reference between Baseline and Child Project
      • Handling configuration files
      • Pushing Upgrades to a Child Project
    • Plans
    • Migrate to Umbraco Cloud
    • Repositories in a Cloud Project
    • Best Practice for Working in Teams
    • Migrate between regions
  • Set up
    • Ready to Set Up Your Project?
    • Working with a Local Clone
      • Legacy Umbraco Visual Studio Setup
    • Manage Environments
    • Project Settings
      • Managing Transport Security
      • CDN Caching and Optimizations
      • Dedicated Resources
      • Upgrade your Plan
      • Public Access
      • Managing Hostnames
        • New Certificate Authority for custom hostnames
        • Rewrite rules
        • Custom Certificates
      • Management API Security
      • Umbraco CI/CD Flow
        • Cloud API For CI/CD Flow
        • Configuring a CI/CD pipeline
          • Azure DevOps
          • GitHub Actions
        • Troubleshooting
        • Known Limitations and Considerations
      • External Services
      • Usage
        • Bandwidth
      • Availability and Performance
      • Team Members
        • Technical Contact
      • Secrets Management
      • Project History
    • Private NuGet Feed on Umbraco Cloud
    • Going Live
    • Media
    • External Login Providers
    • Azure Blob Storage
      • Connect to Azure Storage Explorer to upload files manually
      • Connect and Upload Files Programmatically to Azure Blob Storage
    • Users
    • Multi-Factor Authentication
    • Application Insights
    • Config Transforms
    • SMTP Settings
    • Payments
      • Subscription migration information and FAQ
    • Power Tools (Kudu)
      • View the Files on your Cloud Environments
      • Generate UDA files
      • Manually run Extractions on your Cloud Environments
  • Deployments
    • Deployment
    • Deploying between environments
    • Transferring Content, Media, Members, and Forms
    • Deploying Deletions
    • Deployment Webhook
    • Deploying Changes
    • Umbraco Forms on Cloud
    • Deploy Dashboard
    • Hotfixes
      • Apply hotfix by manually moving files
      • Apply hotfix by using Git
    • Restoring Content
      • Partial Restores
  • Databases
    • Keep Your Data Secure and Accessible
    • Working with databases
    • Database backups
    • Database
      • Connecting to the Database on Mac
    • Working with a Cloud database locally
  • Product Upgrades
    • Stay Up to Date with Umbraco Cloud
    • Product Upgrades
    • Major Upgrades
    • Minor Upgrades
    • Version Specific Upgrades
      • Migrate from Umbraco 8 to the latest version
      • Migrate from Umbraco 7 to Umbraco 8 on Umbraco Cloud
    • Upgrade your projects manually
      • Manual upgrade of Umbraco CMS
      • Manual upgrade of Umbraco Deploy
    • Dependencies on Umbraco Cloud
  • Troubleshooting
    • Resolve Issues Quickly and Efficiently
    • Troubleshooting FAQ
    • Log files
    • The Umbraco Backoffice
    • The Frontend
    • The Umbraco Cloud Portal
    • Site Performance checklist
    • Troubleshooting deployments
      • Extraction error: Config transforms failing
      • Extraction error: Data Type collisions
      • Dependency Exception
      • Merge Conflicts on Flexible Environments
      • Troubleshooting deployments failing with no error message
      • Troubleshooting duplicate dictionary items
      • Troubleshooting language mismatches
      • Path too long Exception
      • Schema Mismatches
      • How to resolve collision errors
      • Extraction error: "Type not found! "
    • Cloud Errors
  • Release Notes
    • Overview 2025
      • April 2025
      • March 2025
      • February 2025
      • January 2025
    • Overview 2024
      • December 2024
      • November 2024
      • October 2024
      • September 2024
      • August 2024
      • July 2024
      • May 2024
      • April 2024
      • March 2024
      • February 2024
      • January 2024
    • Overview 2023
      • December 2023
      • October 2023
      • September 2023
      • August 2023
      • June 2023
      • May 2023
      • April 2023
      • March 2023
      • February 2023
      • January 2023
    • Overview 2022
      • December 2022
      • November 2022
      • September 2022
      • August 2022
      • June 2022
      • May 2022
      • April 2022
      • March 2022
      • February 2022
      • January 2022
Powered by GitBook
On this page
  • How do I know I have this issue?
  • How to check for and resolve the issue

Was this helpful?

Edit on GitHub
Export as PDF
  1. Troubleshooting
  2. Troubleshooting deployments

Extraction error: Config transforms failing

PreviousTroubleshooting deploymentsNextExtraction error: Data Type collisions

Last updated 1 day ago

Was this helpful?

Sometimes you might notice that even though your deployments are coming through without errors, no changes are being applied to the Cloud environments. This might be due to Config Transforms failing during the extraction process.

This issue may occur if you have added custom to your project.

Since Config Transforms are applied on every data extraction, the behavior will continue until the Config Transform files are either corrected or removed.

How do I know I have this issue?

This problem is a bit tricky to spot, as the only indicator is that changes you made on the source environment are not being applied - even though the deployment was complete (although when pushing from local you might get a warning message).

The environment overview on your project will most likely not mention anything, which means you will have to delve into KUDU.

How to check for and resolve the issue

  1. Access on the environment where you expected to see your changes reflected

  2. Navigate to site > deployments folder in KUDU

  3. Find the latest deployment folder, either by date or by ID of the deployment (you can find the latest active deployment ID by opening the active file in the folder)

  4. If the deployment folder with the latest ID contains only two items (log.log and status.xml), that means something went wrong as we would normally see two more files - commits.uc and manifest

  5. Open the log.log file and look for anything mentioning XmlTransform.

An example of a faulty config transform not being applied could look something like this:

	2021-03-05T13:33:12.5380343Z,Handling custom config transforms for live,,0
	2021-03-05T13:33:12.5536435Z,Transforming Web.config using Https.Web.live.xdt.config,,0
	2021-03-05T13:33:12.7411430Z,Transforming Web.config using Web.live.xdt.config,,0
	2021-03-05T13:33:12.8193263Z,Exception while transforming: System.Xml.XmlException: 'xdt' is an undeclared prefix. Line 4, position 18.,,1
	2021-03-05T13:33:12.8349115Z,   at System.Xml.XmlTextReaderImpl.Throw(Exception e),,1
	2021-03-05T13:33:12.8349115Z,An error has occurred applying config transforms,,0
	2021-03-05T13:33:12.8505195Z,   at System.Xml.XmlTextReaderImpl.LookupNamespace(NodeData node),,1
	2021-03-05T13:33:12.8662176Z,   at System.Xml.XmlTextReaderImpl.AttributeNamespaceLookup(),,1
	2021-03-05T13:33:12.8818128Z,   at System.Xml.XmlTextReaderImpl.ParseAttributes(),,1
	2021-03-05T13:33:12.8818128Z,   at System.Xml.XmlTextReaderImpl.ParseElement(),,1
	2021-03-05T13:33:12.8974033Z,   at System.Xml.XmlTextReaderImpl.ParseElementContent(),,1
	2021-03-05T13:33:12.9130628Z,   at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace),,1
	2021-03-05T13:33:12.9130628Z,   at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc),,1
	2021-03-05T13:33:12.9286554Z,   at System.Xml.XmlDocument.Load(XmlReader reader),,1
	2021-03-05T13:33:12.9286554Z,   at Microsoft.Web.XmlTransform.XmlFileInfoDocument.Load(XmlReader reader),,1
	2021-03-05T13:33:12.9443101Z,   at System.Xml.XmlDocument.LoadXml(String xml),,1
	2021-03-05T13:33:12.9599000Z,   at Microsoft.Web.XmlTransform.XmlTransformation..ctor(String transform, Boolean isTransformAFile, IXmlTransformationLogger logger),,1
	2021-03-05T13:33:12.9599000Z,   at OutcoldSolutions.ConfigTransformationTool.TransformationTask.Execute(String destinationFilePath, Boolean forceParametersTask).,,1
	2021-03-05T13:33:12.9911902Z, Exception while transforming: System.Xml.XmlException: 'xdt' is an undeclared prefix. Line 4, position 18.
	at System.Xml.XmlTextReaderImpl.Throw(Exception e)
	at System.Xml.XmlTextReaderImpl.LookupNamespace(NodeData node)
	at System.Xml.XmlTextReaderImpl.AttributeNamespaceLookup()  
	at System.Xml.XmlTextReaderImpl.ParseAttributes()   
	at System.Xml.XmlTextReaderImpl.ParseElement()
	at System.Xml.XmlTextReaderImpl.ParseElementContent()   
	at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)   
	at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)   
	at System.Xml.XmlDocument.Load(XmlReader reader)  
	at Microsoft.Web.XmlTransform.XmlFileInfoDocument.Load(XmlReader reader)  
	at System.Xml.XmlDocument.LoadXml(String xml)  
	at Microsoft.Web.XmlTransform.XmlTransformation..ctor(String transform, Boolean isTransformAFile, IXmlTransformationLogger logger)
	at OutcoldSolutions.ConfigTransformationTool.TransformationTask.Execute(String destinationFilePath, Boolean forceParametersTask).
  1. Verify the Config Transform file mentioned in the error message and ensure the XML is valid.

  2. Update the Config Transform file as necessary on your local solution and deploy the change to the Cloud environments.

To find errors in the config transform, you can use an xml validation tool like https://www.xmlvalidation.com/

Run a to extract the schema that you previously deployed.

Config Transforms
KUDU
Schema Deployment From Data File