Forum Replies Created
-
AuthorPosts
-
solentbMember
Thanks. That has helped indirectly. I did try that but it still would not work.
After much tinkering with various things I uninstalled winfax and then installed it again. Then I re-did all the firewall and rpc and dcom tweaks and finally it works. For now.
I did try the fax talk demo and it works well (it just works and imports winfax data easily) but the boss does not like it as much as winfax so I have to keep on keeping on making winfax work!
Thanks for helping.
solentbMemberThanks. Do I have to pay to read that post?
solentbMemberOK so I checked the settings for com security again and they look like this:
—
Which should be OK I think.
When I go into DCOM Config I get these messages though. Should I say yes?
—
I don’t understand how it can be working in the morning and not in the afternoon. I’ve been having problems with one of the clients which would work one day and then not the next and now none of the clients will connect. I have been able to keep Winfax clients and server working for about 10 years on win 98 and XP but this is being a problem for me.
solentbMemberI looked in the event viewer are there are lots of these errors. It doesn’t make sense as I made the required changes to allow the ‘ANONYMOUS LOGON’ access to remote activation of DCOM. Here is the error:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10021
Date: 31/01/2013
Time: 09:27:02
User: N/A
Computer: JAKE-DELL
Description:
The launch and activation security descriptor for the COM Server application with CLSID
{17EAB2A0-70E2-11CE-A7FB-008029E0ABE9}
is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Hope you can clear this up. -
AuthorPosts