Re: time to submit job (objFaxDocument.ConnectedSubmit)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Yes this gives me more insight into the problem. I think the problem might
be in rendering the body file. Try a fax with only cover page & no body &
let me know the time it takes. If this case goes fine, then it's almost
clear that the time is spent in rendering the body file. We can then look
into the associated application that renders the document.

--
Raghavendra R
Microsoft Printing, Imaging and 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.'

"Rene Anstötz" <rene_antsoetz@xxxxxxxxxx> wrote in message
news:u$1SHBGiFHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
> Ok, let´s explain some details...
>
> Our Application generates up to 500 demand notes for our customers. The
> coworker decides by his human brain, if the customers get the demand note
> or not. So, when the application transmit the demand note to the fax
> server, it takes about 10-12 seconds. After this the application gets the
> jobid from the faxserver. For me its clear that the fax can´t be sent yet,
> it´s only in the queue for transmitting (we schedule the transmitting at
> 3:00 am). So the only problem we have is the large time to transfer the
> documents to the fax server (500 x 11 seconds= 5500 seconds= about 1.5
> hours !!!)
>
> It´s regardless of document type (PDF, tiff) and also regardless of
> workstation or server by itself.....
>
> my sample vb project:
>
> Dim objFaxDocument As New FAXCOMEXLib.FaxDocument
> Dim objFaxServer As New FAXCOMEXLib.FaxServer
> Dim objSender As FaxSender
> Dim JobID As Variant
>
> 'Error handling
> On Error GoTo Error_Handler
>
> objFaxServer.Connect "" 'regardless if remote server or local server
>
> objFaxDocument.Body = "C:\Faxdocuments\test.tif"
>
> objFaxDocument.Priority = fptHIGH
> objFaxDocument.Recipients.Add "126", "---126---"
> objFaxDocument.AttachFaxToReceipt = True
>
> objFaxDocument.ScheduleType = fstSPECIFIC_TIME
> objFaxDocument.ScheduleTime = CDate("3:00:00 AM")
>
> JobID = objFaxDocument.ConnectedSubmit(objFaxServer)
> MsgBox "The Job ID is :" & JobID(0)
>
> I compile it and execute the programm directly on the fax server, it takes
> 12 seconds, but if i print the same document on the fax server to the
> faxprinter it takes about 1 second
>
> Hope this explanation helps
>
> Rene
>
>
> "Raghavendra R [MSFT]" <raghavr@xxxxxxxxxxxxxxxxxxxx> schrieb im
> Newsbeitrag news:42d6363e@xxxxxxxxxxxxxxxxxxxxx
>> Do you mean the call ConnectedSubmit doesn't return until after 11-12
>> seconds? Note that fax is not transmitted immediately (synchronously).
>> The fact that ConnectedSubmit returns doesn't mean that Fax Transmission
>> is completed. It only means that your fax request is successfully queued
>> at the Fax Server & it will be sent as & when the Phone Line becomes
>> available. So I am not quite sure what you mean when you say user has to
>> acknowledge every recipient?
>>
>> --
>> Raghavendra R
>> Microsoft Printing, Imaging and 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.'
>>
>> "Rene" <Rene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:02457882-A2AF-4986-8EA1-32D3BA92A73F@xxxxxxxxxxxxxxxx
>>> Hello,
>>>
>>> i would like to fax with the fax service from VB or VB.NET and 99% works
>>> fine. But regardless of which Server or client I try, it takes about
>>> 11-12
>>> seconds to transmit the job. I tried to transmit PDF and tif documents,
>>> but
>>> no change. Even if i compile the sample code and execute it on the
>>> server it
>>> takes so long.
>>> Some times we have to fax hundreds of documents, but the user have to
>>> acknowledge every recipient and when one fax takes about 11 seconds, we
>>> can
>>> forget it :(
>>>
>>> The very interesting thing is, that when i Print it with user
>>> interaction
>>> over the shared faxprinter, it takes only 1-2 seconds, even regardless
>>> of the
>>> client / server...
>>>
>>> Any ideas?
>>>
>>> Thx in advice
>>>
>>> Rene
>>>
>>> p.s. sorry for my bad english
>>
>>
>
>


.

Relevant Pages

  • Re: time to submit job (objFaxDocument.ConnectedSubmit)
    ... So it seems as you wrote that the time is needed for rendering the body ... I transmit a tiff file for faxing with my program to the server. ... That the version with the body file. ...
    (microsoft.public.win2000.fax)
  • Re: ethernet nic performance
    ... FTP test involves moving the same 9gig file between servers. ... Server B can ftp the same file from Server A at 109meg per sec. ... Max Packets on S/W Transmit Queue: ... XON Flow Control Packets Transmitted: ...
    (comp.unix.aix)
  • Re: ethernet nic performance
    ... FTP test involves moving the same 9gig file between servers. ... Server B can ftp the same file from Server A at 109meg per sec. ... Max Packets on S/W Transmit Queue: ... XON Flow Control Packets Transmitted: ...
    (comp.unix.aix)
  • Re: ethernet nic performance
    ... FTP test involves moving the same 9gig file between servers. ... Server B can ftp the same file from Server A at 109meg per sec. ... Max Packets on S/W Transmit Queue: ... XON Flow Control Packets Transmitted: ...
    (comp.unix.aix)
  • Re: Server side preview of IE rendering...
    ... > Hi Dave, ... Or are you just rendering straight HTML? ... > And in your server code: ... >> like when it has been rendered in IE and display it in the form designer. ...
    (microsoft.public.dotnet.framework.aspnet)