Fax Service Extended COM

[Q. John Chen]

Hi, There,

I know this is not the best place to post this because I am on Win
2003 and XP. But at least it is related.

I am using Fax Service Extended COM with an Word Document attached. It
runs fine on local (XP Pro). But alway gets error on a Win 2003
Server. (Note, It runs fine on server w/o the attachment)

Anyone can give some clue?

Thanks.

- John

 

[Ananda Sarkar [MSFT]]

When you say, you get an error on Win2003, do you mean, it fails when you
try to fax from XP using a connected shared fax printer (shared from
Win2003) or you mean this is failing when you try running sitting on Win2003
console itself?

If it's the former one, did you ensure the client and server machines are in
same (or trusted) domain and the printer connection is already established
in your "printers & faxes"

When you get an error, what's the message like? Are there any eventvwr
message at that time?

Thanks,
Anand

--
Ananda Sarkar
Microsoft Printing, Imaging & Fax Team

This posting is provided "AS IS" with no warranties, and confers no rights.

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.'

 

[Alex Feinman [MVP]]

Also, do you have Word installed on that machine? Fax service will attempt
to invoke registered printing application and wordpad may not be able to do
it. Finally, with Word and other office documents there is an issue of
always presenting a "Provide User Initials" dialog box on the first start.
Since Fax service invokes the printing application in the context of fax
service (Local_Service account on W2K3), the dialog will fail causing Word
to appear hung.
A bit of a hack, but I was able to succefully overcome this problem by
copying a bit of registry data from an existing user account to the
LOCAL_SERVICE HKU branch