Link to home
Start Free TrialLog in
Avatar of Chintpal
Chintpal

asked on

Running SSIS package through the JOB

Iam having issues while running SSIS package through the sql Job. The job is running file wiyhout any exceptions when i run through Integration Services on the service. But when i call the same package through the job iam getting some assembly not found exception.

System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Office.Interop.Excel, Version=14.0.0.0, Culture=neutral

It there is an issue with the assembly then it shouldn't work when i run the same from Integration Services. This is SQL 2008 on Windows 2008 server. I tried to run the job with Proxy account and Agent account, but still getting the same error i also tried both file system and MSDB to install the package, but still iam getting the same error.

Any help would be appreciated.

-Srinivas
ASKER CERTIFIED SOLUTION
Avatar of Anthony Perkins
Anthony Perkins
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Chintpal
Chintpal

ASKER

But the same this is working fine when i run it from the Integration Services.
Hi,

Integrations services where? On your machine?

Integrations Services doesn't have to be run on the server ...

HTH
  David
>>But the same this is working fine when i run it from the Integration Services. <<
Right.  Excel is installed there.
I was able to resolve the issue. I was using Excel interop assembly to do some validations in the package and that assembly was not installed on the server. So i installed MS Office (Excel) on the server and now the package is running without any issues.
>>that assembly was not installed on the server. <<
Which is exactly what I stated here http:#a37469377

>>So i installed MS Office (Excel) on the server and now the package is running without any issues. <<
If this is production box, than this is not a good idea (as I also mentioned previously).  And I am not even talking about the questionable logic of using a licensed copy of MS Office on a server.