MicrosoftOffice Automation in asp.net 3.5 Office version 2007 & 2010

Question

0.00/5 (No votes)

See more:

Hi,
background:- I already developed office automation in my web site. where i done lot of settings like, IMPERSONATION, COM security, IIS and it is working as per required. but all these done for MICROSOFT OFFICE 2003. as far as good. no issue.

Problem:- by now i required to setup my application with MS Office 2010 and 2007 on two different servers. I started with 2007 and when i installed office 2007 and interop for 2007 on my development machine it is not working so i created a dummy application and it is working if i am not using IIS but when i configured this dummy application in IIS than it stops to work.
Key problem is wordDocument is null. so code is not able to open the document. Path impersonation is Okay.
Code:-

C#

object file = @"c:\test\01\test.doc";
ApplicationClass wordApp = new ApplicationClass();
object readOnly = false;
object isVisible = true;
object missing = System.Reflection.Missing.Value;
Document wordDocument = wordApp.Documents.Open(ref file, ref missing, ref readOnly, ref missing, ref missing, ref missing, ref missing, ref missing, ref missing, ref missing, ref missing, ref isVisible, ref missing, ref missing, ref missing, ref missing);

I am not able to understand why it is null.

Posted 2-Sep-11 1:34am

mahesh__kumar__sharma

Updated 2-Sep-11 23:04pm

v3

Add a Solution

Comments

Prerak Patel 2-Sep-11 7:36am

Use code block for code segments.

Philippe Mori 2-Sep-11 7:53am

Generally it is not recommanded to uses Office Automation on server. That technology is known to be relatively slow and was not designed for that purpose.

If you are an advanced programmer, you can look at the OpenXML SDK... but it is very low level and thus really not recommanded for beginners. Otherwise, there are plenty of third party solutions availables...

Philippe Mori 3-Sep-11 8:10am

Normally user application like Office do not run on servers.. Are you sure that Office is installed for the user that access it from your ASP.NET application.

As mentionned before, Office automation is not really intended to be used on servers. If you search the web, you will see that many people recommand not to uses Office automation to generate documents on a server. It won't scale well.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Prerak Patel · Answer 1 · 2011-09-02T01:40:00

Solution 1

I don't know the exact reason, but I have faced the same issue with Office 2010.
The work around is to put some delay between application creation and document open.
I hope this helps.

Posted 2-Sep-11 1:40am

Prerak Patel

Comments

mahesh__kumar__sharma 2-Sep-11 7:49am

I added System.Threading.Thread.Sleep(1000 * 5); before creating
System.Threading.Thread.Sleep(1000 * 5);
Document wordDocument = wordApp.Documents.Application.Documents.Open(ref file, ref missing, ref readOnly, ref missing, ref missing, ref missing, ref missing, ref missing, ref missing, ref missing, ref missing, ref isVisible, ref missing, ref missing, ref missing, ref missing);

But no Luck. :(

Prerak Patel 2-Sep-11 7:58am

Then let's just wait for some different answer. I was lucky that it worked for me.
I would still like you to do one more thing. Put a delay after document open and try to open it again. I read it somewhere while searching for that problem.