Spell Check ASP.NET Word 2003

[Shawn]

Hi,

I have added a spell checker to my web application using the "Microsoft Word
Document" DCOM. Everything works great in my development environment. When
I move everything over to my production machine I get...

"Object reference not set to an instance of an object"

This is caused when the following Visual Basic line is executed...

"ThisDocume nt = WordApp.Documen ts.Add()"

I have everything working in my development environment. I have tried
several iterations of this spell check code and I have had it working
perfectly 3 differents time with relatively the same failed result on the
production server. The only thing I can narrow it down to is permissions in
IIS and DCOM. My development machine is running WinXP and IIS 5.0. My
production machine is Windows 2003 Server Standard edition. I have my dev
machine accessing the DCOM under the ASPNET account and the prod machine
accessing under the NETWORK SERVICE account. I can't seem to fiure it out.

[Sylvain Lafontaine]

A good possibility is that you didn't reference the PIA for accessing the
Word component. For security reasons, you must use the PIA (Primary
Interoperabilit y Assemblies) for Office if you want to distribute your
application to other machines and not an interoperabilit y assembly generated
by VS.NET (or you must compile the application directly on the target
machine if you don't want to use the PIA).

See "Referencin g the Office XP PIAs" in:
http://msdn.microsoft.com/library/de...dc_oxppias.asp
to make sure that you have the correct reference.

Be warned that using Word directly on a server is probably a bad idea.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
"Shawn" <Sh***@discussi ons.microsoft.c om> wrote in message
news:CC******** *************** ***********@mic rosoft.com...

Hi,

I have added a spell checker to my web application using the "Microsoft
Word
Document" DCOM. Everything works great in my development environment.
When
I move everything over to my production machine I get...

"Object reference not set to an instance of an object"

This is caused when the following Visual Basic line is executed...

"ThisDocume nt = WordApp.Documen ts.Add()"

I have everything working in my development environment. I have tried
several iterations of this spell check code and I have had it working
perfectly 3 differents time with relatively the same failed result on the
production server. The only thing I can narrow it down to is permissions
in
IIS and DCOM. My development machine is running WinXP and IIS 5.0. My
production machine is Windows 2003 Server Standard edition. I have my dev
machine accessing the DCOM under the ASPNET account and the prod machine
accessing under the NETWORK SERVICE account. I can't seem to fiure it
out.

[Shawn]

Thank you for the quick reponse.

I double checked the pia's installed on the server and everything seems
fine. I even re-installed them to make sure. I am simply using Word for the
spell checking functionality. It was already running Office 2003, so I
figured, why not. I still get the same error. Word is listied in the task
manager, but I can't do anything with it. It seems as if the application can
be started, but objects on the production machine cannot be created. weird.
Thanks again Sylvain!

"Sylvain Lafontaine" wrote:

A good possibility is that you didn't reference the PIA for accessing the
Word component. For security reasons, you must use the PIA (Primary
Interoperabilit y Assemblies) for Office if you want to distribute your
application to other machines and not an interoperabilit y assembly generated
by VS.NET (or you must compile the application directly on the target
machine if you don't want to use the PIA).

See "Referencin g the Office XP PIAs" in:
http://msdn.microsoft.com/library/de...dc_oxppias.asp
to make sure that you have the correct reference.

Be warned that using Word directly on a server is probably a bad idea.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
"Shawn" <Sh***@discussi ons.microsoft.c om> wrote in message
news:CC******** *************** ***********@mic rosoft.com...

Hi,

I have added a spell checker to my web application using the "Microsoft
Word
Document" DCOM. Everything works great in my development environment.
When
I move everything over to my production machine I get...

"Object reference not set to an instance of an object"

This is caused when the following Visual Basic line is executed...

"ThisDocume nt = WordApp.Documen ts.Add()"

I have everything working in my development environment. I have tried
several iterations of this spell check code and I have had it working
perfectly 3 differents time with relatively the same failed result on the
production server. The only thing I can narrow it down to is permissions
in
IIS and DCOM. My development machine is running WinXP and IIS 5.0. My
production machine is Windows 2003 Server Standard edition. I have my dev
machine accessing the DCOM under the ASPNET account and the prod machine
accessing under the NETWORK SERVICE account. I can't seem to fiure it
out.