- This topic is empty.
-
AuthorPosts
-
May 16, 2006 at 10:11 pm #2973
pmarsh
MemberEverything has been working OK for awhile now. I got a call last week saying we can’t connect to WinFax. Every workstation gets the following error as soon as it connects to the WinFax host. I know something has changed but I can’t for the life of me figure out what has happened. I’ve reinstalled the host and the clients they’re all running 10.04.
Thanx
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 5/16/2006
Time: 6:04:57 PM
User: N/A
Computer: HPPAV
Description:
Faulting application wfxctl32.exe, version 0.0.0.0, faulting module wfxifwpp.dll, version 10.4.2005.125, fault address 0x0001c14c.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 66 78 ure wfx
0018: 63 74 6c 33 32 2e 65 78 ctl32.ex
0020: 65 20 30 2e 30 2e 30 2e e 0.0.0.
0028: 30 20 69 6e 20 77 66 78 0 in wfx
0030: 69 66 77 70 70 2e 64 6c ifwpp.dl
0038: 6c 20 31 30 2e 34 2e 32 l 10.4.2
0040: 30 30 35 2e 31 32 35 20 005.125
0048: 61 74 20 6f 66 66 73 65 at offse
0050: 74 20 30 30 30 31 63 31 t 0001c1
0058: 34 63 0d 0a 4c..May 18, 2006 at 2:35 pm #5405pmarsh
MemberAfter many hours of troubleshooting I’ve found that when “Check for new events on startup” is enabled WinFax crashes but when it’s disabled everything works fine. Does anyone have any information regarding “Check for new events on startup” What fires off? What port is it communicating to the host on? What could be causing this problem???
Thanx
May 20, 2006 at 1:23 am #5406Anonymous
MemberWinFax PRO uses DCOM to communicate with the Client/Host machines. The port it communicates with varies for each connection. Do you any firewall blocking turned on, or Symantec Worm Protection turned on? this will cause problems. You might want to try adding “wfxctl32.exe” and “faxmng32.exe” to your firewall list (excluding firewall blocking) for these apps.
It appears your clients can “talk” with the Host, but the Host can’t send data to the Clients.
May 22, 2006 at 4:35 pm #5407pmarsh
MemberClient firewalls have been turned off, they are wide open. Something is jacked up with the Host but I can’t figure it out. I can swap the roles making the client a host and the host a client everything works fine. Once I swap the roles back again that’s when I get the error. Everything was working fine two weeks ago but now we’ve got problems. Of cource the client says nothings changed it just stopped working……
The host is running Win2K SP4 it’s also an ACT server, SQL7 with a custom app, file server for the LAN and the DC for the domain EVERYTHING IS RUNNING HOT STRAIGHT AND NORMAL EXCEPT WINFAX????
I’ve reinstalled the host it works fine, it can send and receive without an issue but the clients keep failing when they try to connect.
ANY IDEAS?????
Thanx
May 23, 2006 at 12:19 pm #5408pmarsh
MemberUPDATE
How do I dislike this freaking product,,,,, let me counts the ways. OK so let me count how many times I’ve reinstalled this stupid thing.
This time I had to manually remove the program along with all the reg keys and reinstall.
I HATE WINFAX!
May 26, 2006 at 4:09 pm #5409Anonymous
MemberThis is a long shot, try changing the Video resolution on the client machine to 256 colors, and/or just standard VGA and try connecting to the Host. Some Video drivers have been known to cause strange problems when displaying a fax, and its possible the error occurs when it attempts to display the received fax from the Host on startup.
Edited By Moderator on 1148659816
-
AuthorPosts
- You must be logged in to reply to this topic.