Skip to main content

DTExec error: Unable to load the package as XML because of package does not have a valid XML format

Today I had some trouble to get a DTSX package up & running. On the command line I tried to execute the following command:

DTEXEC /FILE "S:\Data Files\dtsx\Package.dtsx" /REPORTING EW /CONFIGFILE "S:\Data Files\dtsx\importjob.dtsConfig"

But no luck, instead of a running DTSX package, I got a very explaining (*ahum*) error message:

143910:T:M584D4:tsk> Microsoft (R) SQL Server Execute Package Utility

143910:T:M584D4:tsk> Version 11.0.2100.60 for 64-bit

143910:T:M584D4:tsk> Copyright (C) Microsoft Corporation. All rights reserved.

143910:T:M584D4:tsk>

143910:T:M584D4:tsk> Started:  2:39:09 PM

143910:T:M584D4:tsk> Error: 2015-03-12 14:39:10.83

143910:T:M584D4:tsk>    Code: 0xC0011007

143910:T:M584D4:tsk>    Source: {4B5520B2-BF3D-41B0-83F6-C266A50A51BB}

143910:T:M584D4:tsk>    Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted.

143910:T:M584D4:tsk> End Error

143910:T:M584D4:tsk> Error: 2015-03-12 14:39:10.83

Now the error message is somewhat misleading. It had nothing to do with an invalid XML package or something but instead we were using an incorrect filename. My DTSX package was called ImportJob.dtsx and not Package.dtsx…

So after updating the filename, the DTSX was running happily ever after…

DTEXEC /FILE "S:\Data Files\dtsx\importjob.dtsx" /REPORTING EW /CONFIGFILE "S:\Data Files\dtsx\importjob.dtsConfig"

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...