I have an EXE that is scheduled every 10 minutes. It has been working successfully for over 6 months. Suddenly, it breaks. If I reboot it works for a couple faxes and then breaks again.
Here is the block of code that it is failing at:
FaxDocumentClass fd =
new FaxDocumentClass();fd.Recipients.Add(sFormattedFaxNumber, sRecipientName);
fd.DocumentName = sDocumentNameTag + sRequestId;
fd.Body = sFile;
sContext = "12";
fd.ConnectedSubmit(fs);
fs is a reference to the FaxServiceClass. The fs.Connect(sFaxServerName); which comes before the code above works fine every time.
Why all of a sudden is the ConnectedSubmit not working
Thank you.
Jon
FAXCOMEXLib - Operation Failed
Rafael Oliveira
I have started running into this same problem as well.
It occured when the servers were upgraded to win2003 sp1.
I get the following in my servers' event log
1st this:
EventID:11 Source: Print
Document 7, 1C66AFBE843C9.txt - Notepad owned by amccool was paused on Fax.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Followed by this:
EventID:13 Source: Print
Document 7, 1C66AFBE843C9.txt - Notepad owned by amccool was deleted on Fax.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
We just applied hotfix the this KB article
KB Article Number(s): 909906
this did not allivate the problem
MaheshS
Some simple question would be.
If the code has been working successfully for 6 months and your still using the same code on the same machine and its now not working .... What else have you changed on this machine recently
I'd be trying to identify when the process stopped working and what was installed at that time.
Now its not working, whats not working (ie. what is the exception or error being generated). Putting some error handling like a Try Catch around this code and catching the exception may provide some clues as to the cause of the problem.
So what is the exception being generated
At the moment the desciption is still lacking specifics to determine a cause - other than a component stops working on this machine where it previously was working fine.
Is this a VS 2005 / 2003 developed application
how is it scheduled to run
David Gwynn-Jones
turns out the soution is to call
fs.Connect(sFaxServerName);
twice in a row....go figure