Faxmaker for Exchange 12 & COM API

	Forums Register Login My Profile Inbox Address Book My Subscription My Forums Member List Search FAQ Ticket List Log Out

Faxmaker for Exchange 12 & COM API

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [Archiving & Fax] >> GFI FAXmaker >> Faxmaker for Exchange 12 & COM API

Page: [1] 2 next > >>

Message

<< Older Topic Newer Topic >>

Faxmaker for Exchange 12 & COM API - 27.Sep.2004 7:03:00 PM

joerocket

Posts: 4
Joined: 27.Sep.2004
Status: offline

Has anyone had trouble with the COM API after upgrading to v12?

I've been using the COM API successfully until the V12 upgrade today. I'm at a loss to figure out what has changed to hinder the COM objects functionality.

An error message reply goes to my mailbox: "No transport provider was available for delivery to this recipient." The fax server never aknowledges the reciept of the fax parameters. [Mad]

Post #: 1

RE: Faxmaker for Exchange 12 & COM API - 28.Sep.2004 4:56:00 AM

Patrizia

Posts: 8474
Joined: 18.Aug.2003
From: Malta
Status: offline

joerocket,

Go to the FAXmaker Client directory, and manually run the fmfaxapi.exe.

Try to use the FAX API again and check whether the error persists.

(in reply to joerocket)

Post #: 2

RE: Faxmaker for Exchange 12 & COM API - 28.Sep.2004 10:48:00 AM

joerocket

Posts: 4
Joined: 27.Sep.2004
Status: offline

Patrizia,

I ran the fmfaxapi.exe on the client directory but nothing changed. I then uninstalled the Faxmaker Client and installed the new v12 client.

Now I get a different error:
"From: FAXmaker[SMTP:FAX@FAXMAKER.COM]Description: No recipients were found in this message. Fax could not be sent."

I looks like the COM API is working, but it is not seeing the fax recipients in the COM object call.

I installed the MAPI client since we have Exchange 2003. Should I have installed the SMTP client?

(in reply to joerocket)

Post #: 3

RE: Faxmaker for Exchange 12 & COM API - 1.Oct.2004 6:03:00 AM

Nicks

Posts: 2772
Joined: 17.Mar.2003
Status: offline

Do you get the same error message if you send a fax using the normal FAXmaker client software?

(in reply to joerocket)

Post #: 4

RE: Faxmaker for Exchange 12 & COM API - 1.Oct.2004 10:27:00 AM

joerocket

Posts: 4
Joined: 27.Sep.2004
Status: offline

nicks,

The client software works fine.

I ended up rewriting my code to use the Text API. [Mad]

Its a real shame that the COM-API is not maintained. The TextAPI increased the chances for errors by having to write files outside my process.

I pay a lot of money for support every year. Telling customers that key feature is not supported is unacceptable.

(in reply to joerocket)

Post #: 5

RE: Faxmaker for Exchange 12 & COM API - 5.Oct.2004 4:28:00 AM

shagenus

Posts: 25
Joined: 4.Aug.2004
Status: offline

Hi all,

there is a quick work around for this without having to revert to using Text API.

If FAXmaker is getting the message but not seeing the fax number it is because it is being resolved by Exchange/AD before FAXmaker gets it, not so sure this is a FAxmaker problem.

What you could do is drop the recipient details in the top of the body of the message using the text API commands. eg ::FirstName,Company,LastName,FaxNumber (there are more options in the manual)

FAXmaker will read this and send the message.

you would probably have the COM API documentation so have a look at the section describing SetBodyText and then use the Text API commands in the body.

(in reply to joerocket)

Post #: 6

RE: Faxmaker for Exchange 12 & COM API - 5.Oct.2004 12:41:00 PM

joerocket

Posts: 4
Joined: 27.Sep.2004
Status: offline

Scotth,

Thanks, that makes sense. I will give that a shot. The Text API is working, but has a tendancy to miss some of the attachments.

Could this COM problem have been caused by changes to the Exchange Connector in V12? It worked fine in V10.

I'm still miffed that the GFI support answer is "we don't support that". Having a logical explanation does help.

(in reply to joerocket)

Post #: 7

RE: Faxmaker for Exchange 12 & COM API - 6.Oct.2004 3:44:00 AM

shagenus

Posts: 25
Joined: 4.Aug.2004
Status: offline

It should work as I was talking to a colleague the other day who ran into the problem and I made the same suggestion, he made the change and presto.... working fine [Smile]

I can't really answer that one on the connector, I wouldn't have thought so as it is a standard SMTP connector. The interesting thing is if you stop FAXmaker and grab the mail from the FAXmaker sink drop directory and open it up, the "To" field has already been resolved so that FAXmaker can't read it.

If you think about it, FAXmaker at this stage hasn't had an effect on it yet, so it must be something like Exchange's MTA changing the addressing?? Someone else might have an idea on that one.

Re support on the COM API, you can understand it though cause you get some pretty way out coding happening and you are talking about custom programming when getting into the COM area. Most if not all of what organisations are trying to achieve can actually be done without having to get into the FAXmaker COM API area. That's my take, but I have been playing with FAXmaker for a while now. Anyway hope the info has helped.

(in reply to joerocket)

Post #: 8

RE: Faxmaker for Exchange 12 & COM API - 6.Oct.2004 8:47:00 AM

mps_surcouf

Posts: 72
Joined: 5.Oct.2004
Status: offline

Hi Joe

I have exactly the same problem.

'No recipients were found in this message'

They have changed the addressing method to using xml in version 12 client and they send a message to address 'fax' which is picked up by the Faxmaker smtp connecter (no MTA stuff now).

This then reads the xml

As far as I can see the com api has not been updated to support this addressing method and I get the error above.

I have a call open now but have heard nothing yet.

I'll post here when I have news.

Unfortunately I don't have an option to use text api as I am printing access report which has no text equivalent.

Anyway I really don't want to have to start rewriting my apps.

Keep you posted

Mike

(in reply to joerocket)

Post #: 9

RE: Faxmaker for Exchange 12 & COM API - 6.Oct.2004 10:53:00 AM

shagenus

Posts: 25
Joined: 4.Aug.2004
Status: offline

Hi Mike

you dont need to use text api or rewrite, all you need to do is use the extra SetBodyText and put the recipient details in the body.

eg as description in previous post. This works and is about 5 lines of extra code if that. Hope it helps.

(in reply to joerocket)

Post #: 10

RE: Faxmaker for Exchange 12 & COM API - 6.Oct.2004 1:04:00 PM

mps_surcouf

Posts: 72
Joined: 5.Oct.2004
Status: offline

Hi Scott

You are a star!

Sorry misunderstood your earlier post and didn't think it applied to me. Just saw text api and skipped through post.

Using setbodytext works great for me.
I am only using com api because I need a way to render a dynamically generated ms access report. Do you know of any other way?
I would like to remove my relience on the faxmaker client.

Also do you know if it is possible to use default outlook new message form instead of faxmaker form (exe) after rendering?

I really appreciate your help.

Thanks

Mike

(in reply to joerocket)

Post #: 11

RE: Faxmaker for Exchange 12 & COM API - 7.Oct.2004 12:39:00 AM

shagenus

Posts: 25
Joined: 4.Aug.2004
Status: offline

Great Mike, glad to hear you have it going [Smile]

(in reply to joerocket)

Post #: 12

RE: Faxmaker for Exchange 12 & COM API - 7.Oct.2004 12:48:00 AM

shagenus

Posts: 25
Joined: 4.Aug.2004
Status: offline

Re other ways..have you tried using the NetPrintQueue2Fax network printer driver in FAXmaker?

if you generate the report with the fax number in the report eg get the report to have:

To: Name
Company: CompanyName
Fax: FaxNumber

At the top of each new report section and at the end of each one @#

and then print it to the NetPrintQueue2Fax it should read the first fax number take ev everything between that and the @# and send to the first fax number. It then looks for the next fax number in the next page after the @# and repeats process.

Its a great way of doing it as you can use Text API commands inside the report and all you need to worry about is having it auto Print [Smile]

(in reply to joerocket)

Post #: 13

RE: Faxmaker for Exchange 12 & COM API - 7.Oct.2004 6:15:00 AM

mps_surcouf

Posts: 72
Joined: 5.Oct.2004
Status: offline

Hi Scott

Interesting disscussion.

I have a lots of reports that I either print or fax from the print preview screen. Once at the print preview screen the report is already rendered. The user then decides where the report is going to. At this point there is no way to get this addressing info onto the report so the netprintqueue driver could not pick up this info.

Does the net print queue driver do OCR? I can't see how it would pick up the addressing info off a access report which is not text.

I would like the ability to print to a tiff rendering driver and have the driver notify my program via some mecanisim with the file name when it had finished. I could then use an api to send the email to fax@faxmaker.com with the adressing info in the body.

Mike

(in reply to joerocket)

Post #: 14

RE: Faxmaker for Exchange 12 & COM API - 13.Oct.2004 11:54:00 PM

shagenus

Posts: 25
Joined: 4.Aug.2004
Status: offline

Hi Mike, what is it rendering to? If the report itself can be generated with the client fax number in it Fax: FAXNUMBER and it is not an image or pdf file then the NetPrintQueue2Fax will be able to get the fax number out of it.

Try it with a Word doco going to print Preview and print to the NetPrintQueue2Fax.

Of course it is a diffrent story if one Report may or may not be sent to lots of different people depending on what the report shows after it has been created. Then I see your issue.

(in reply to joerocket)

Post #: 15