Skip to content

Est. 2011·Microsoft Partner ID 7033487·Delivery under 3 min·Support 7 days a week

Your vault is empty.

License Error 0xC0047062

SSIS Error 0xC0047062: Packages Fail as Agent Jobs but Run in Visual Studio

11 min read Updated October 5, 2026 SQL Server

Fix it now

0xC0047062 is DTS_E_USERCOMPONENTEXCEPTION: a managed component in the data flow threw an exception. The exception text carried in the message is the diagnosis – the code itself only says which layer reported it.

Run this on the instance to see the job step’s proxy, command line and 32-bit setting

EXEC msdb.dbo.sp_help_jobstep @job_name = N'Nightly Load';
  1. Find the .NET exception quoted inside the 0xC0047062 message. A BadImageFormatException loading a client library is the bitness case; a SqlException or an UnauthorizedAccessException is the account case.
  2. For the bitness case, tick Use 32 bit runtime on the SSIS job step. Microsoft documents it as running the package with the 32-bit dtexec, for packages that use a native provider with no 64-bit version.
  3. If the 32-bit run works, install the 64-bit provider on the server and take the workaround back off.
  4. For the account case, create a credential and an Agent proxy for the Integration Services subsystem, and point the job step at the proxy instead of the Agent service account.
  5. Replace mapped drive letters with UNC paths. A service account has no drive mappings, so M:\Imports cannot resolve for it.

The proxy has prerequisites. Microsoft documents that the credential login, the Agent service account and the SQL Server service account all need Replace a Process Level Token and full control over %SYSTEMROOT%\Temp, and that the failure without them reads “The job failed. A required privilege isn’t held by the client.”

If the job now succeeds under the proxy in the right bitness, you are done. If the exception points somewhere else entirely, the next section covers the four things that differ between your desktop and the server.

Why it happens

A package that runs perfectly in Visual Studio and fails the moment SQL Server Agent runs it has almost never developed a fault. It is running somewhere else, as someone else, in a different bitness, with a different set of installed providers. What makes this hard to see is the code people fixate on. 0xC0047062 is published as DTS_E_USERCOMPONENTEXCEPTION – A managed user component has thrown exception "..." – so it is not a component that could not be created; it is a managed component, a Script Component or a managed source adapter, whose own code threw. The exception it quotes is where the answer is.

The first difference is bitness. An Integration Services project has a debugging property that decides which runtime your packages use while you develop them, and the Agent job step carries its own independent setting. Microsoft describes that setting as running the package using the 32-bit version of dtexec on a 64-bit computer, and gives the reason: a native OLE DB provider that is not available in a 64-bit version. When the two disagree, a managed component that loads such a provider throws a BadImageFormatException, and that exception is what 0xC0047062 hands you.

The second difference is the installed providers. Your workstation has accumulated client software over years; the server has whatever was installed when it was built. ODBC data source names are the sharpest edge, because 32-bit and 64-bit system data sources are kept in separate lists and a name in one is invisible to the other. The third difference is identity: you are a member of things the Agent service account is not. The fourth is the environment – drive mappings, relative paths and configuration files that exist in your profile and not in a service account’s.

The provider exists in one bitness only

You have this one if The quoted exception is a BadImageFormatException or a failure to load a client library, and the job step succeeds with Use 32 bit runtime ticked.

  1. Install the 64-bit version of the provider on the server, then run the job in 64-bit.
  2. If only a 32-bit provider exists for that source, leave the option enabled and record why, because it caps the address space available to the data flow.
  3. For ODBC, create the data source name in the matching bitness of the ODBC administrator, and prefer a connection string over a system DSN so the dependency disappears.

The runtime account is not you

You have this one if The quoted exception is a login failure or an access denied, and the same package runs interactively under your own account.

  1. Create a credential for a domain account with the rights the package needs, and an Agent proxy for the Integration Services subsystem that uses it.
  2. Grant Replace a Process Level Token and full control over %SYSTEMROOT%\Temp to the credential login, the Agent service account and the SQL Server service account.
  3. Assign the job step to that proxy rather than running it as the Agent service account.
  4. Grant the account both share and file system permissions on every folder the package reads or writes.

Microsoft also warns that when the proxy credential’s password changes it must be updated in SQL Server, or the job step fails. That is a common cause of a job that worked for a year and then stopped.

Paths that only exist in your session

You have this one if 0xC001401E, or a file path error naming a drive letter, or a relative path resolving somewhere unexpected on the server.

  1. Use UNC paths everywhere. Service accounts have no drive mappings.
  2. Make every path a package parameter or configuration value so it can differ between environments without editing the package.
  3. Confirm the folder exists on the server and that the runtime account can list it, not merely reach the share.

The package cannot read its own stored credentials

You have this one if A decryption failure appears alongside the component error, and the package is on the default protection level.

  1. Change the protection level so sensitive values are not tied to your user profile, and supply passwords as parameters or from a catalogue environment.
  2. Re-enter each password after the change, because changing the level cannot restore values it could not read.
  3. Deploy the project to the Integration Services catalogue, where sensitive values are held by the catalogue rather than by a profile.

The destination rejects a column the package is trying to write

You have this one if 0xC0202049, which is specifically an insert into a read-only column.

  1. Look at the column named. An identity or computed column cannot be written to directly.
  2. Remove the mapping, or enable identity insert at the destination if writing the identity value is intended.
  3. Re-check mappings after any schema change; the adapter keeps the mapping it was configured with.

Full reference

Matching the symptom to the difference

Symptom Difference to check
Works when the job step uses the 32-bit runtime A provider installed only for 32-bit
A file path error naming a drive letter A mapped drive that does not exist for a service account
A decryption failure alongside the component error The package protection level, not the environment
“A required privilege isn’t held by the client” The proxy prerequisites: Replace a Process Level Token and rights on %SYSTEMROOT%\Temp
Worked for months, then stopped on no change The proxy credential’s password changed and was not updated in SQL Server
An ODBC data source the job cannot see The DSN exists in the other bitness’s administrator

The codes in this group

Code Symbolic name Published meaning
0xC0047062 DTS_E_USERCOMPONENTEXCEPTION A managed user component has thrown exception …
0xC0047017 DTS_E_INDIVIDUALVALIDATIONFAILED … failed validation and returned error code 0x…
0xC001401E DTS_E_INVALIDFILENAMEINCONNECTION The file name specified in the connection was not valid
0xC0202049 DTS_E_ATTEMPTINGTOINSERTINTOAREADONLYCOLUMN Failure inserting into the read-only column …

Two of those are narrower than they look. 0xC001401E is about the file name itself being invalid, not about permissions – a permissions failure produces a different error from the file system. 0xC0202049 is specifically a read-only column, which in practice means an identity column or a computed column, not any column the adapter could not write.

Setting up the proxy properly

  1. Create a domain account for the job, with only the rights the package needs.
  2. Grant Replace a Process Level Token and full control over %SYSTEMROOT%\Temp to that account, the Agent service account and the SQL Server service account.
  3. Create a credential in SQL Server for the account, then a proxy for the SQL Server Integration Services Package subsystem that uses that credential.
  4. Grant the job owner access to the proxy, and set the job step’s Run as to the proxy.
  5. Test by running the job, not by running the package. Adding an account to a group and assuming it worked is how these faults survive several rounds of fixing.

Do not solve this by running the SQL Server Agent service under your own domain account. It gives every job on the instance your rights, survives long after you have forgotten it, and breaks the day your password changes. Use a credential and a proxy.

Bitness in three places

  • The project’s debugging property decides which runtime Visual Studio uses when you press F5.
  • The Agent job step’s Use 32 bit runtime option decides which dtexec the job uses, independently of the project.
  • Anything the package loads – providers, drivers, assemblies – has to exist in the bitness the process is running in.
  • A 32-bit run has a smaller address space, which matters for a data flow with large buffers, so treat it as a workaround with a cost rather than a setting.

Choosing between the catalogue and package files

For anything scheduled, deploy the project to the Integration Services catalogue. It handles sensitive values properly, keeps environment-specific settings out of the package, and records detailed execution messages you will want at three in the morning. Running loose .dtsx files from a share works, but every environment difference in this article has to be managed by hand for each one.

When a licence is the actual fix

Almost everything here is free configuration and you should work through it first: bitness, providers, proxies, paths and protection levels cost nothing to correct. There is one case where a licence is genuinely the constraint. Integration Services is a component of SQL Server rather than a separate free download, so a server that runs packages on a schedule needs to be licensed for SQL Server. If your packages currently run from a developer workstation because the production server has no Integration Services installed, the supported way to schedule them is to license that server and run them from Agent, with a proxy and a catalogue deployment. Arco supplies SQL Server 2025 Standard licences and can check whether an existing agreement already covers you before you buy anything.

Every code this article covers

Code What it points at Source
0xC0047062 DTS_E_USERCOMPONENTEXCEPTION: a managed user component has thrown an exception, quoted in the message. The exception is the diagnosis Microsoft Learn
0xC0047017 DTS_E_INDIVIDUALVALIDATIONFAILED: the named component failed validation and returned a nested error code Microsoft Learn
0xC001401E DTS_E_INVALIDFILENAMEINCONNECTION: the file name specified in the connection was not valid Microsoft Learn
0xC0202049 DTS_E_ATTEMPTINGTOINSERTINTOAREADONLYCOLUMN: failure inserting into a read-only column, typically an identity or computed column Microsoft Learn

Confirm the fix worked

  1. The job runs from SQL Server Agent, not from Visual Studio, and succeeds.
  2. It succeeds with Use 32 bit runtime turned off, or the reason it must stay on is recorded.
  3. The job step’s Run as shows the proxy rather than the Agent service account.
  4. The destination row count matches what the package processed.
  5. Changing the proxy account’s password in a test environment and updating the credential leaves the job working, proving no credential is baked into the package file.

Questions people ask about this

What does 0xC0047062 actually mean?

Microsoft publishes it as DTS_E_USERCOMPONENTEXCEPTION: a managed user component has thrown an exception. It is a wrapper. The .NET exception quoted inside it is the error you need to read, and it is usually a provider that will not load or an access denied.

Is ticking the 32-bit runtime a fix or a workaround?

A workaround, and an acceptable one when no 64-bit provider exists for your source. It limits the address space available to the data flow, so for large loads install the 64-bit provider instead.

Why can the job not see my ODBC data source?

Because 32-bit and 64-bit system data sources are stored separately. A DSN created in one administrator is invisible to the other. Create it in the matching bitness, or avoid DSNs entirely.

The job fails with “A required privilege isn’t held by the client”. What is missing?

The proxy prerequisites. Microsoft documents that the credential login, the Agent service account and the SQL Server service account all need Replace a Process Level Token and full control over %SYSTEMROOT%\Temp.

Should I deploy to the catalogue or run package files?

The catalogue, for anything scheduled. It handles sensitive values properly, keeps environment-specific settings out of the package, and records execution messages you will want the next time something fails overnight.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Error 53 and Error 26: SQL Server Instance Not Found on the Network License Error Errors 14420 and 14421: Log Shipping Backup and Restore Alerts Firing License Error Error 17809: The Maximum Number of User Connections Has Been Reached Free Fix Error 7399 and 7303: Linked Server Provider and Authentication Failures
← Back to Knowledge Base