Re: Problem using ForeignToRTF32
- From: "Sterling Wight" <work@xxxxxxxxxxxxxxxxx>
- Date: Tue, 14 Feb 2006 09:52:37 -0600
"SteveS" <SteveSpencer@xxxxxxxxxxxxxxxxx> wrote in message
news:6F24E105-7DD1-4665-AADD-F735BA411CD8@xxxxxxxxxxxxxxxx
I agree with what Peter is saying. What context is the service running in?
Is
it LocalSystem account or whatever? There are issues with permissions on
DCOM
objects not being able to be started from certain accounts (rather than an
interactive user), which you may be running into.
--
Steve S
The service communicates through SOAP, not DCOM. It has administrative
priviledges. I have the problem if I run the service as a service, or simply
as an executable that happens to be listening on a port. I don't think its
any sensible permissions problem, given that I have debug code that opens
and closes the file just prior to calling ForeignToRTF. Also, the problem
does not occur with all of the conversion dlls, for example "WORKS632.CNV"
runs just fine, converting a MS Works file.
"Sterling Wight" wrote:
I am having a problem using the word conversion dll (MSWRD832.CNV). I
call
the routine from two different programs. One is a typical MFC
application,
and the conversion always works without a problem. The other is a
service,
with no visible interface, and from there the conversion always fails,
returning -1 (could not open input file). This is true even though I pass
exactly the same arguments to the routine from both programs. Also, I
tested
opening and closing the file just prior to calling the routine in
debugging
code, and the file opens without complaint using standard file system
calls.
I already tried adding an invisible window to my service, in case there
is a
hidden dependency on having a window available from the calling program,
but
that did not change any results. So I'm very puzzled. Anyone got an idea
of
what kind of undocumented dependency the routine could have?
.
- Follow-Ups:
- Re: Problem using ForeignToRTF32
- From: Peter Jamieson
- Re: Problem using ForeignToRTF32
- References:
- Problem using ForeignToRTF32
- From: Sterling Wight
- Problem using ForeignToRTF32
- Prev by Date: Re: Problem using ForeignToRTF32
- Next by Date: Re: Problem using ForeignToRTF32
- Previous by thread: Re: Problem using ForeignToRTF32
- Next by thread: Re: Problem using ForeignToRTF32
- Index(es):
Relevant Pages
|