Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1194
  • Last Modified:

SQL Server Agent: SSIS

I have an SSIS package in SQL Server 2005. When I deployed the package to the SQL Server and execute the package manually in Integration Services. The package executes without a problem. However, when I schedule a new jon under SQL Server Agent and start the job i get the following error

 Source: Import Nmcbq ConvertToMDY [2454]     Description: System.NullReferenceException: Object reference not set to an instance of an object.     at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.CreateUserComponent()  End Error  

Why is the package erroring out when executing the Job but not when i run the package??
0
abussie
Asked:
abussie
  • 4
  • 3
1 Solution
 
srnarCommented:
"execute the package manually in Integration Services". Does it mean you are running package from Management Studio connected to an Integration service?
0
 
abussieAuthor Commented:
Yes, thats wut i mean by running package manually. SQL SERVER 2005 Management Studio connected to Integration Services and Execute package
0
 
srnarCommented:
Can you create a simple SSIS package without any scripting tasks, deploy it on Integration services, run it manually and from Agent?

Than you can eliminate possible deployment problem or concentrate on the scripting task.
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
abussieAuthor Commented:
Yes, i did the previous tasks without any problems. So does the problem reside in the scripting? If so, why does it run without any problems locally and in integrations then craps out in SQL Server Agent
0
 
abussieAuthor Commented:
You were right the error was in the scripting code i updated the custom script and it ran without any problems. Its still wierd that the error was never caught until I scheduled a job via SQL Server Agent you would of thought that the bug would of got caught in Business Intelligence Studio or Integration Services.
0
 
abussieAuthor Commented:
I had to set the property Pre-compile to TRUE on the Custom Script Component for it to run with the SQL Server Agent. Problem solved my package runs under SQL Server Agent now after i set the pre-compile on the custom script component to TRUE
0
 
srnarCommented:
Yes, it is good option. On 64 bit a must. Than you can see compilation error right by red icon in control flow.
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now