I have a 2003 server, named ds9, with a fax modem attached to it.
I am using the following vbs script to send a fax through ds9 from another
machine:
Set objFaxServer = CreateObject ("FaxComEx.FaxServer")
objFaxServer.Connect "ds9"
MsgBox objFaxServer.ServerName & ", " & objFaxServer.MajorBuild
Set objFaxDoc = CreateObject ("FaxComEx.FaxDocument")
objFaxDoc.Body = "c:\temp\test.txt"
objFaxDoc.Recipients.Add "(123)123-4567", "test"
objFaxDoc.ConnectedSubmit(objFaxServer)
When I run this script on my XP Pro workstation, it runs fine.
When I run it on another 2003 server (an app server), Windows Script Host
gives this error:
Line: 7
Char: 1
Error: Operation failed.
Code: 800710D8
Source: FaxComEx.FaxDocument.1
This error might relate to not having a fax device installed (ms kb 841714).
I don't have a physical fax device on the 2003 app server, but I DO have a
fax printer configured for the shared fax on ds9, called \\ds9\fax.
I AM able to send faxes from the app server, through ds9, by printing to
"Fax on ds9" from notepad. The "Send a fax..." wizard also works.
The only thing that doesn't work on the 2003 app server is the above script
(and the script does work from XP Pro).
Any suggestions?
Thanks,
Darin
Please let me know if my answer helps you resolve the problem. If there is anything more I can assist you, please feel free
to let me know.
Thanks,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn
This posting is provided "AS IS" with no warranties and confers no rights.
Thanks for the suggestion. After reinstalling Fax Services, however, I'm
still getting the same error in my script.
The values in the registry key you mentioned are as follows. They were the
same both before and after the reinstall.
[HKEY_CLASSES_ROOT\CLSID\{0F3F9F91-C838-415E-A4F3-3E828CA445E0}]
@="FaxDocument Class"
[HKEY_CLASSES_ROOT\CLSID\{0F3F9F91-C838-415E-A4F3-3E828CA445E0}\InprocServer32]
@="C:\\WINDOWS\\system32\\fxscomex.dll"
"ThreadingModel"="Apartment"
[HKEY_CLASSES_ROOT\CLSID\{0F3F9F91-C838-415E-A4F3-3E828CA445E0}\ProgID]
@="FaxComEx.FaxDocument.1"
[HKEY_CLASSES_ROOT\CLSID\{0F3F9F91-C838-415E-A4F3-3E828CA445E0}\Programmable]
[HKEY_CLASSES_ROOT\CLSID\{0F3F9F91-C838-415E-A4F3-3E828CA445E0}\TypeLib]
@="{2BF34C1A-8CAC-419F-8547-32FDF6505DB8}"
[HKEY_CLASSES_ROOT\CLSID\{0F3F9F91-C838-415E-A4F3-3E828CA445E0}\VersionIndependentProgID]
@="FaxComEx.FaxDocument"
Thanks,
Darin
"Rhett Gong [MSFT]" <v-ra...@online.microsoft.com> wrote in message
news:HkA58jM...@TK2MSFTNGXA01.phx.gbl...
in addition, could you manually register fxscomex.dll again to see if it helps? --- to do so, you need to use cmdline regsvr32 fxscomex.dll.
Thanks for the suggestions!
(Prior to sp1, re-registering fxscomex.dll did not help. There must have
been another issue that was fixed in SP1.)
"Rhett Gong [MSFT]" <v-ra...@online.microsoft.com> wrote in message
news:AlmHj$YxFH...@TK2MSFTNGXA01.phx.gbl...
Have a nice day!