asked on 10/6/2011

Creating Microsoft Word Object in Thread Fails on Deployed Workstation

I am running some office automation in a thread. This works on my development machines, but fails when deployed. If I run the same code outside of a thread, it works on all machines. Does anyone have any ideas? I became so frustrated that I created the most basic non-class driven automation to make sure I wasn't going crazy:

Attached are two files, same program but one calling via thread the other direct.

Works.txt

Fails.txt

Programming .NET Programming Programming Languages-Other

Last Comment

DuBoisCG

10/7/2011

Anurag Thakur

10/7/2011

The first reason that comes to my mind in such a scenario when something works on development machine and not on deployment machine is the permissions of user under whose credentials the code/application is running under

generally on dev machines we always have admin rights and when we deploy the user credentials the application is using is generally restricted

DuBoisCG

10/7/2011

ASKER

It's a good thought, but the working test (same code, just not in a thread) runs as the local user.

I actually got it working by adding the office.dll into the working directory, but want to leave this issue open to see if anyone can explain why this dll wasn't required for the working test. If there are some important rules for threads that limit their ability to access resources, it would be nice to document it here (couldn't find much threaded function help).

ASKER CERTIFIED SOLUTION

Anurag Thakur

10/7/2011

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

DuBoisCG

10/7/2011

ASKER

We still don't know why the same code would run outside a thread on the same machine as the same user... but ultimately it needed the referenced dll in the working directory in order for the thread version to run.