Re: FaxStartPrintJob broke down again

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On further investigation I found that if fxsapi.dll from spooler directory
(%windir%\system32\spool\drivers\w32x86\3) is already loaded into your
process this error would arise. The reason being
%windir%\system32\winfax.dll is incompatible with fxsapi.dll present in
spooler directory. %windir%\system32\winfax.dll will only work well with
%windir%\system32\fxsapi.dll. I believe this is what is happening in your
case. If you call any print related APIs fxsapi.dll from spooler directory
would get into your process. After this any call on winfax.dll will fail
with this error. There is a problem with winfax.dll on XP machines. The
workaround would be for your application to do an explicit LoadLibrary of
%windir%\system32\fxsapi.dll on startup & keep the module handle returned
until exit. This way when winfax.dll does LoadLibrary of fxsapi.dll it will
the pick the one from %windir%\system32 & things would work fine.

Please let me know if this solves your problem. I tried it & it did work for
me!!

--
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.'

"Raghavendra R [MSFT]" <raghavr@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:42bd58d6@xxxxxxxxxxxxxxxxxxxxx
> You don't need to install modems on local machine if you are only
> connecting to remote shared fax printers. The event log entries you posted
> earlier are from the server machine (holm) right?
>
> I just wrote a test app & tried to repro it. But it works fine for me if I
> run it from any location except from
> %windir%\system32\spool\drivers\w32x86\3 directory. Are you running your
> app from this location by any chance?
>
> --
> 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.'
>
> "Sam Jost" <samjost@xxxxxx> wrote in message
> news:1119614763.334319.52890@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Do I need to install a modem on my client comp (name him Tang) to use
> the shared fax on my SBS 2003 server Holm? I thought if I use a shared
> fax I dont need to install a modem and stuff for every comp on my
> network?
>
>
> The program does not run on the server (Holm), it's running on some
> client on the network named Tang (XP with all patches)
> The program does still fail with the same problem even when I use NULL
> instead of the shared name.
>
> I tried uninstalling the fax stuffin software, but it didnt help either
> :(
>
> pity is, sending a file with com does work, but I got no way to make a
> file from the stuff I need to fax :(
>
> Sam
>
> Raghavendra R [MSFT] schrieb:
>> The two event log entries mean there is no Fax Device on your machine.
>> You
>> should install a modem & make sure it's shown up in the list of Modems in
>> Fax Configuration Wizard or Fax Service Manager.
>>
>> As such I still don't think the event log entries should be the reason
>> for
>> FaxStartPrintJob failure. By the way are you running the program on
>> machine
>> 'holm' it-self or is it run on a client machine which has a printer
>> connection to \\holm\fax? Does your program run if the printer name is
>> specified as NULL to mean local fax printer?
>>
>> --
>> 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.'
>>
>> "Sam Jost" <samjost@xxxxxx> wrote in message
>> news:1117011069.409251.185120@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> There are two event log entries about fax happening every boot. Since I
>> use a localized xp they are completely different, but just as useful :)
>>
>> I just copied these from this mornings boot log:
>> --
>> 32026
>> Fehler beim Initialisieren der zugewiesenen Faxgeräte (virtuell oder
>> TAPI) durch den Faxdienst. Es können keine Faxe gesendet werden, bis
>> ein Faxgerät installiert ist.
>> --
>> 32068
>> Die ausgehende Verteilerregel ist nicht gültig, weil kein gültiges
>> Gerät gefunden werden kann. Ausgehende Faxe, die diese Regel
>> verwenden, werden nicht weitergeleitet. Stellen Sie sicher, dass das
>> angezielte Gerät bzw. die angezielten Geräte angeschlossen, korrekt
>> installiert und angeschaltet sind. Stellen Sie außerdem sicher, dass
>> die Gruppe korrekt konfiguriert ist, falls die Weiterleitung an eine
>> Gruppe von Geräten erfolgen soll. Landes-/Regionskennzahl: "*"
>> Ortskennzahl: "*"
>> --
>>
>>
>> About FaxStartPrintJob, the printer name is \\holm\fax (holm is the
>> server name, fax the share name).
>>
>> Sam
>>
>>
>> Raghavendra R [MSFT] schrieb:
>> > I don't think the event log entry should have anything to do with the
>> > FaxStartPrintJob problem. But I am not 100% sure. To solve the issue
>> > reported by the event log I need more information about the log entry
>> >
>> > The log will look like this
>> > The outgoing routing rule is not valid because it cannot find a valid
>> > device. Check the routing rule configuration.
>> > Country/region code: '%1'
>> > Area code: '%2'
>> >
>> > What are the values for %1 & %2 that you see in event viewer? Depending
>> > on
>> > that identify the corresponding routing rule in Fax Service Manager
>> > (fxsadmin.msc) & see if the rule's target device or device group has
>> > all
>> > valid device(s). A value of '*' for %1 & %2 refers to the default
>> > outbound
>> > routing rule.
>> >
>> > About the FaxStartPrintJob failure ... what's the PrinterName parameter
>> > you
>> > are passing to FaxStartPrintJob?
>> >
>> > --
>> > 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.'
>> >
>> > "Sam Jost" <samjost@xxxxxx> wrote in message
>> > news:1116495351.921590.266910@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> > > The error code of GetLastError after calling FaxStartPrintJob is 127
>> > > (text is something like procedure not found)
>> > >
>> > > My app is standalone, no service. I get the error on shared fax
>> > > printer
>> > > both on SBS 2003 and Windows Server 2003 that did work just fine two
>> > > weeks ago.
>> > >
>> > > The Fax Send Wizard does work, as does the fax COM component.
>> > >
>> > > There are no fancy event logs on failure, but I just found a warning
>> > > I
>> > > never seen before on boot-up-time regarding fax:
>> > > EventID 32068 (I could append the german error message but I dont
>> > > think
>> > > it would help you much - it's something about rule for outgoing faxes
>> > > not existing. Funny, thats a new one).
>> > >
>> > > Well, so maybe this event log entry got something to do with it, but
>> > > where do I change the setting for outgoing traffic? On the server?
>> > >
>> > > Sam
>> > >
>
>


.

Relevant Pages

  • Audio Woes
    ... I have just upgraded my FC4 system with a fresh install of FC5 and all ... The card is detected but the error says that I am ... alias parport_lowlevel parport_pc ...
    (Fedora)
  • Re: Assigning a Permission Set to an Assembly
    ... to use it you'll need to install the SDK. ... server with any form of .Net on it will have the compilers. ... Please do not send email directly to this alias, ... >> This has to be the most frustrating experience with any security ...
    (microsoft.public.dotnet.security)
  • Re: FaxStartPrintJob broke down again
    ... Do I need to install a modem on my client comp to use ... The program does not run on the server (Holm), ... > The two event log entries mean there is no Fax Device on your machine. ...
    (microsoft.public.win2000.fax)
  • RE: Reporting Problems
    ... Select the Application Event log, right click it and select "Save Log ... Install MBExplorer by installing IIS 6 Resource Kit Tools: ... This newsgroup only focuses on SBS technical issues. ... you may want to contact Microsoft CSS directly. ...
    (microsoft.public.windows.server.sbs)
  • Re: assessing winusb potential
    ... I am now pouring over a USB book but the issue is still not clear. ... What prevents the host from ... Please do not send e-mail directly to this alias. ... able to install downlevle (IIRC, ...
    (microsoft.public.development.device.drivers)