Advanced Queue failed to deliver

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

Advanced Queue failed to deliver

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [Archiving & Fax] >> GFI FAXmaker >> Advanced Queue failed to deliver

Page: [1]

Message

<< Older Topic Newer Topic >>

Advanced Queue failed to deliver - 19.Oct.2009 4:17:48 AM

bgi

Posts: 2
Joined: 19.Oct.2009
Status: offline

I'm strugling for some days now with our faxmaker installation...
We have exchange 2003 + on same box faxmaker 14.
We installed it because last week faxmaker 12 stopped working. We could not send any faxes out...
So i installed 14 with the hope of getting it solved, but it stays the same....

When we send a mail to [fax:xxx], we get in the message tracking the message failed to deliver to advanced queu...

I already tried several things(disabling anti-virus, etc)...but nothing seems to work...

Can someone please help me on this one. Faxmaker worked fine for several years, and now....

Rgds
Benny

Post #: 1

RE: Advanced Queue failed to deliver - 19.Oct.2009 10:34:55 AM

rpoor

Posts: 15
Joined: 12.Apr.2006
Status: offline

Is this the message your getting?
"Warning. Could not add fax-sent event to main events process queue"
I started getting this message after updating to 14.3 v. 2009625. I was running 14.3 v.20090303 before the update and had never seen this message before.

(in reply to bgi)

Post #: 2

RE: Advanced Queue failed to deliver - 19.Oct.2009 10:50:57 AM

bgi

Posts: 2
Joined: 19.Oct.2009
Status: offline

Nope,
did not get any message in log or anywhere, except this in the mail tracking center....

(in reply to rpoor)

Post #: 3

RE: Advanced Queue failed to deliver - 19.Oct.2009 12:28:18 PM

rpoor

Posts: 15
Joined: 12.Apr.2006
Status: offline

We didn't get the message as a bounce back but the error message was showing in the fax monitor in the Fax server view at the bottom of the view. As far as we know we're the only one's who have been getting this error after updating to the recent build.

(in reply to bgi)

Post #: 4