RE: Word 2003 use within ASP.NET 1.1 -- Worked for months now fails...
- From: Bradley A. Hehe <BradleyAHehe@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 14 Apr 2005 08:39:03 -0700
Further input...
Tried using a UNC on the same machine.. No difference...
Tried using a UNC on another machine.. No difference...
Tried using another local drive.. No difference...
Tried Office Update to make sure Word 2003 was current.. No difference...
How can this be? This is ridiculous. The solution worked for a long time and
then suddenly fails... Something had to change. I've beat the NTFS
permissions thing to death I would guess... I've even granted permissions to
INTERACTIVE & SYSTEM.
"Bradley A. Hehe" wrote:
> I have a situation where I have used Word automation in ASP.NET on a Win2k
> SP4 Server machine. The solution simply opens a new document based on a
> template and then fills in the bookmarks. After this, it does a "SaveAs" and
> closes the document.
>
> This solution was in place and fully functioning throughout a development
> cycle and then deployed to a QA environment (Win2k3) where it continued to
> function.... Even with 8-10 users hammering on it.... This lasted for several
> months.
>
> What happens now is I get an error on the SaveAs method... "Word cannot
> complete the save due to a file permission error."
>
> I have the ASP.NET Worker Process configured to run as an identity that
> currently has full local domain admin priviledges. I checked the directory
> that I use for "temp" space and the NTFS permissions are set to grant
> Everyone with Full Access as well as explicitly granting the account we run
> as with Full Access....
>
> On a whim, another developer had a situation similar to this and deleting
> and recreating the directory resolved it for him. After exhausting my
> debugging options, I tried this and it suddenly began functioning again.
> During that same test, I also ensured that the template (.dot) and the output
> (.doc) had unique filenames to ensure we weren't trying to write to the same
> name as the template (file lock obviously would hit if they were the same).
> In addition, to ensure concurrency across multiple users, the 2 filenames
> (for .dot and .doc) include a GUID to create uniqueness.
>
> From everything I have inspected, nothing should have changed... at least
> from a developers perspective... We were testing GUI changes that invokes a
> black-box piece of code (quasi "controller") that did change. This black-box
> code calls upon another "black-box" that did not change *at all*. This
> unchanged "black-box" was the piece responsible for the Word automation.
>
> Additionally, I don't believe anything was "pushed" by the network team to
> this server, but I can't rule it out either.
>
.
- References:
- Word 2003 use within ASP.NET 1.1 -- Worked for months now fails...
- From: Bradley A. Hehe
- Word 2003 use within ASP.NET 1.1 -- Worked for months now fails...
- Prev by Date: Possible virus warning when sending a message through MAPI automation
- Next by Date: late binding with powerpoint - please help!
- Previous by thread: Word 2003 use within ASP.NET 1.1 -- Worked for months now fails...
- Next by thread: Filling Word 2003 Form with fields from a vb.net solution
- Index(es):
Relevant Pages
|
