471,348 Members | 1,524 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,348 software developers and data experts.

Fax server API version does not support the requested operation

Hi all,

I am trying to send a fax programatically using the FAXCOMEx.DLL with .Net
(C# and COM Interop).
I have built a little class to encapsulate the logic for sending the fax -
not much to it really. This works nicely when I include this class in a
Windows Forms project and call it from a button's event handler.

Then, when I include the class - as a component in our business components
DLL, and call it from a web service, the "submit" call fails, with the error
"Fax server API version does not support the requested operation". (Yet it
works from the WinForms app with exactly the same parameters, for server
name, etc.)

The code looks like this;
FaxDocument faxDoc = new FaxDocumentClass();

faxDoc.CoverPageType = FAX_COVERPAGE_TYPE_ENUM.fcptLOCAL;
faxDoc.CoverPage = coverPageName;
faxDoc.Recipients.Add(FaxNumber,RecipientName);
faxDoc.Subject = Subject;
faxDoc.Note = Notes;
faxDoc.Body = FileName;

faxDoc.Submit(faxServerName);

I've tried using impersonation to run this code under various "alias"
including the system admin! Same error :-( I've checked all the permission
on the fax server - which FYI is a Windows 2003 server running SBS 2003.

I have a unit test, calling and External facing web service, which calls a
web service behind the firewall, which calls this code. All this code is
running on my development machine at the moment, but once deployed will run
on two different servers.

If someone could shed some light on what this error may mean, and possibly
why it would run in one solution, and not the other, I would be most thankful.

Thanks in anticipation.

Stuart.

Jul 21 '05 #1
2 5687
Further Information:
This ONLY occurs when the code is called from a web service. If the code is
on the form, or in an external class, it works fine. The problem is, I need
to to be triggered by a web service. Is it possible?

"Stuart" wrote:
Hi all,

I am trying to send a fax programatically using the FAXCOMEx.DLL with .Net
(C# and COM Interop).
I have built a little class to encapsulate the logic for sending the fax -
not much to it really. This works nicely when I include this class in a
Windows Forms project and call it from a button's event handler.

Then, when I include the class - as a component in our business components
DLL, and call it from a web service, the "submit" call fails, with the error
"Fax server API version does not support the requested operation". (Yet it
works from the WinForms app with exactly the same parameters, for server
name, etc.)

The code looks like this;
FaxDocument faxDoc = new FaxDocumentClass();

faxDoc.CoverPageType = FAX_COVERPAGE_TYPE_ENUM.fcptLOCAL;
faxDoc.CoverPage = coverPageName;
faxDoc.Recipients.Add(FaxNumber,RecipientName);
faxDoc.Subject = Subject;
faxDoc.Note = Notes;
faxDoc.Body = FileName;

faxDoc.Submit(faxServerName);

I've tried using impersonation to run this code under various "alias"
including the system admin! Same error :-( I've checked all the permission
on the fax server - which FYI is a Windows 2003 server running SBS 2003.

I have a unit test, calling and External facing web service, which calls a
web service behind the firewall, which calls this code. All this code is
running on my development machine at the moment, but once deployed will run
on two different servers.

If someone could shed some light on what this error may mean, and possibly
why it would run in one solution, and not the other, I would be most thankful.

Thanks in anticipation.

Stuart.

Jul 21 '05 #2
Should anyone be interested - MS tech support offered this answer...

Change the user specified in "processModel" tag of machine.config to a
higher privileged user.

This indeed did fix the "Fax server API version does not support the
requested operation" problem but obviously will not be the final answer. I
am inthe process of finding out what privileges have to change for the
machine user that runs the ASPNET processes, or what the minimum requirements
are for a domain user that is to be used for this purpose. I'll post when I
find out.

"Stuart" wrote:
Hi all,

I am trying to send a fax programatically using the FAXCOMEx.DLL with .Net
(C# and COM Interop).
I have built a little class to encapsulate the logic for sending the fax -
not much to it really. This works nicely when I include this class in a
Windows Forms project and call it from a button's event handler.

Then, when I include the class - as a component in our business components
DLL, and call it from a web service, the "submit" call fails, with the error
"Fax server API version does not support the requested operation". (Yet it
works from the WinForms app with exactly the same parameters, for server
name, etc.)

The code looks like this;
FaxDocument faxDoc = new FaxDocumentClass();

faxDoc.CoverPageType = FAX_COVERPAGE_TYPE_ENUM.fcptLOCAL;
faxDoc.CoverPage = coverPageName;
faxDoc.Recipients.Add(FaxNumber,RecipientName);
faxDoc.Subject = Subject;
faxDoc.Note = Notes;
faxDoc.Body = FileName;

faxDoc.Submit(faxServerName);

I've tried using impersonation to run this code under various "alias"
including the system admin! Same error :-( I've checked all the permission
on the fax server - which FYI is a Windows 2003 server running SBS 2003.

I have a unit test, calling and External facing web service, which calls a
web service behind the firewall, which calls this code. All this code is
running on my development machine at the moment, but once deployed will run
on two different servers.

If someone could shed some light on what this error may mean, and possibly
why it would run in one solution, and not the other, I would be most thankful.

Thanks in anticipation.

Stuart.

Jul 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

40 posts views Thread by Matt | last post: by
8 posts views Thread by bryan | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.