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