Distribution Question

[HRoarke]

Hi folks -

I have an ASP.NET web app that contains a class that uses the Excel (v9 in this case) Application object to convert a flat file to XLS. I need to distribute the class to a web server that does not have Office installed. I've created all flavors of Setup/Distribution packages, but keep getting a Class not registered error, and the CLSID of the Excel9 object does not exist in the target registry. What do I need to include / what do I need to do to register/install this darned class?

Two stars for any relevant info/reference!



"I swear by my life and my love of it that I will never live for the sake of another man, nor ask another man to live for mine."
— John Galt
Atlas Shrugged

If you want to get the best response to a question, please check out FAQ222-2244 first

 

[ca8msm]

The easiest solution would be to install excel on the server. I take it from your question that this is not an option?


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[sonya9879]

You shouldn't need to install the actual software on your production server just for what you are trying to achieve. Although that would make things easier I wouldn't do that unless someone uses the actual server as a desktop and needs to use Excel. Then if that's the case, why would you want all this hassle? . Are you using ExcelOWC.dll? In the past I needed to convert some files into Excel and I remember using ExcelOWC.dll. When installing the software on the server, I also had similar error messages. The way I fix it was to add a reference to ExcelOWC and then import OWC on my code. This is probably not too useful for you as you may be doing something totally different but I though sharing it with you all .

 

[ca8msm]

You shouldn't need to install the actual software on your production server just for what you are trying to achieve

From my experiences with Excel, that isn't the case. To be able to grant access to the Excel application, you have to configure DCOM priviliges which isn't possible if Excel isn't installed.


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[HRoarke]

Thanks for the feedback, folks. I'll reply one-by-one.

ca8msm - you are correct, installing Excel isn't an option on the production box;

sonya9879 - don't know about ExcelOWC.dll. I'll look into it, though I'm trying really hard to stay away from 3rd-party widgets.... I'm using the Excel.Application object exposed by Excel v9 (Excel9.OLB and MSO9.DLL), e.g. Office 2000;

ca8msm - good observation about DCOM settings, though that would be a different error (usually "Permission Denied" or a failure on CreateObject, which I'm not using, and I **think** that .NET uses a different access method for DCOM, though I'm not sure). In any case, I'm prepared to address any DCOM permissions issues if they arise (though they shouldn't - we use other OOP COM+ servers on the production box, and the access/launch permissions have already been given to the IIS process).

Anyway, thanks again, and any other ideas are Greatly appreciated....

"I swear by my life and my love of it that I will never live for the sake of another man, nor ask another man to live for mine."
— John Galt
Atlas Shrugged

If you want to get the best response to a question, please check out FAQ222-2244 first