I heard back from EQeus support this morning and they asked the same thing. Apparently the SetParams method defaults to DOC output type, and it checks for Word immediately.

I normally set TargetType to PDF immediately after Setparams(). Too late apparently.

My virtual machine that was having the problem did not have Word installed - all the other machines here have it.





>Are you sure that correct parameters are passed/set for XFRX?
>
>>(this is XFRX 12.5 PDF only version)..
>>
>>I've been using XFRX for years w/no serious problems.
>>
>>Now I've added XFRX PDF printing to a client's existing application. Works fine on 3 tester PCs (XP SP2 running as EXE) and my development PC (EXE or dev environment).
>>
>>We've submitted this to acceptance testing - they test on an XP SP2 virtual machine running under Microsoft Virtual Server. Works fine except for a single report which, when XFRX tries to initialize, pops a Windows messagebox titled 'XFRX' saying 'Cannot access Word application'...??
>>
>>Again, this EXE and this particular report works fine on our other machines and in my development environment. I've moved identical data to the virtual machine and still get the error message. This is PDF only version - Word is not involved.
>>
>>Anyone seen this before?
>>
>>I want to either isolate this to the virtual environment or fix it because this will go out to a couple hundred field users once testing is complete.
>>
>>I've sent email to Eques support twice (including _XFRX log file) but haven't got any response as of yet.