June 23, 2008 at 9:07 am
Hi,
I have created an SSIS package that open and excel file, rewrite it and then send an email with this file.
When I execute it, it gave me an error when try to open the excel files to rewrite, for additional info, we do not have the microsoft office installed in the server, only sql 2005. Do we need to install the ms office in the server in order to have this work?
Can anyone help me on this?
June 23, 2008 at 9:37 am
Uhmmmmm, not sure, but I dont think its necessary to install Office to work with Excel source and destinations.
Be a bit more descriptive of what the error is
June 23, 2008 at 9:51 am
When I run the SSIS package at the time to open the excel file I get this error:
Visual studio Just-In-Time Debugger
An unhandled exception('System.IO.FileNotFoundException')ocuured in OpenExcel.exe
Also, when I try to debug the error I get the following:
Could not load file or assembly 'Microsoft.Office.Interop.Excel, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.
To work with the excel file on the SSIS package, I use an Execute Process Task, that call the excel file,open it, updated it and save it.
June 23, 2008 at 10:15 am
I think all you need is that interop DLL file appropriately loaded into the Server's GAC. I used to have a procedure for getting that done, but for the life of me - I can't put my hands on it.
Look up loading items into the Global Assembly cache, and follow that for the Excel interop DLL.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
June 23, 2008 at 11:02 am
Thanks for your response. So I need to register this Dll on the server and that's solve the problem?
June 23, 2008 at 11:08 am
That's essentially what fixed it for something similar we were doing. Setting up the package on a dev bax and trying to move that over to a server didn't bring the external reference info.
Keep in mind it's not just the "regular" DLL register. Moving something into the GAC is a little different (you have to have signed assemblies, etc...). As i said - it's fuzzy to me right now, but be sure to specifically look for that.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply