Failed to load task

Nov 9, 2012 at 4:20 PM

I am getting the following when I run my package via SQL job:

Error: 2012-11-09 10:10:56.81     Code: 0xC0010018     Source: Create Batch Upload Summary PDF      Description: Failed to load task "Create Batch Upload Summary PDF"<c/> type "SSISComponents.ReportGenerator.ReportGenerator<c/> SSISComponents.DTS.Tasks.ReportGeneratorTask<c/> Version=<c/> Culture=neutral<c/> PublicKeyToken=34fdc1d09bed9884". The contact information for this task is "".  End Error

The task works perfectly from the BIDS designer.


Thanks, Doug

Nov 9, 2012 at 4:52 PM

Hi Doug,

Can you explain your configuration, especially your authentication settings?



Nov 9, 2012 at 4:55 PM

Thanks for the quick response.

What configuration? the task, the package, the job?

Nov 10, 2012 at 2:53 PM
Edited Nov 10, 2012 at 2:53 PM

The configuration of the task. Can you send me some screenshots?



Nov 13, 2012 at 6:10 PM

Well I don't seem to be able to add screenshots.

Here is the what is in each field:

Properties Tab

Report: SQL Server Report
Reportserver: http://<servername>/reportserver
Authorization: Use Windows Integrated Security is checked 
Report: /<path>/ReportName
Save as: \\<path>\FileName.pdf
Add date as prefix to filename is not checked
Show report during execution is not checked
Create Snapshot is not checked 

Report Parameter

This tab is blank



Nov 15, 2012 at 2:37 PM

Does the task need to be installed on the server where the job runs?

Nov 15, 2012 at 9:28 PM


Yes, the component must be installed on server.
And you probably need to adjust permissions.



Nov 26, 2012 at 8:56 PM

Okay. Working on getting this installed on the server.

How should I set the permissions?


Nov 26, 2012 at 9:30 PM
Edited Nov 26, 2012 at 10:16 PM

Can you explain what you mean with "How should I set the permissions?"



Nov 26, 2012 at 10:11 PM

I do not understand your response.


Nov 26, 2012 at 10:18 PM

Sorry, evil clipboard :-) 
I've corrected my question above.



Nov 26, 2012 at 10:19 PM

You stated on 11/15: "And you probably need to adjust permissions."


Nov 26, 2012 at 10:26 PM

When you execute the package as a job on your server, normally the package runs under another user context as on your client machine.
Because you are using Windows authorization, it is quite possible that you need to adjust permissions.
Just a small hint, because I've seen this in your configuration.



Nov 26, 2012 at 10:27 PM

Okay, thanks.

Apr 13, 2015 at 3:39 PM
Is there any additional information that can be provided on how to resolve this? I am having the same issue, but the service account that I am using has fairly elevated permissions, so I would like to know what types of permissions need to be available in order to run this as a Agent Job on our SQL Server.