Solved

SQL Server Agent: SSIS

Posted on 2008-06-23
7
1,180 Views
Last Modified: 2010-04-21
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
Comment
Question by:abussie
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 8

Expert Comment

by:srnar
ID: 21849564
"execute the package manually in Integration Services". Does it mean you are running package from Management Studio connected to an Integration service?
0
 

Author Comment

by:abussie
ID: 21850151
Yes, thats wut i mean by running package manually. SQL SERVER 2005 Management Studio connected to Integration Services and Execute package
0
 
LVL 8

Accepted Solution

by:
srnar earned 110 total points
ID: 21855857
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
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:abussie
ID: 21858126
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
 

Author Closing Comment

by:abussie
ID: 31469847
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
 

Author Comment

by:abussie
ID: 21864738
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
 
LVL 8

Expert Comment

by:srnar
ID: 21864775
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

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

I've encountered valid database schemas that do not have a primary key.  For example, I use LogParser from Microsoft to push IIS logs into a SQL database table for processing and analysis.  However, occasionally due to user error or a scheduled task…
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below. https://filedb.experts-exchange.com/incoming/2017/03_w12/1151775/Permutations.txt https://filedb.experts-exchange.com/incoming/201…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question