Lots of DCOM errors after Empower2 installation

<p>After our Empower2 installation we got lots of DCOM errors when a server access via LACE is done. The connection senns to be OK. We get all chromatigraphic data.</p><p></p><p></p><p><span style="font-size: 10pt;">[quote]</span></p><p><span style="font-size: 10pt;">Event ID: 10006</span></p><p><span style="font-size: 10pt;"> </span><span style="font-size: 10pt;"> </span></p><p><span style="font-size: 8pt;"><p><span style="font-size: 10pt;">DCOM got error "General access denied error " from the computer SEPAFEMP201 when attempting to activate the server:</span></p><p><span style="font-size: 10pt;">{C783A0AC-DE1A-49CD-8AEF-ABCEDE313510}</span></p><p><span style="font-size: 10pt;">For more information, see Help and Support Center at </span><a href="http://go.microsoft.com/fwlink/events.asp"><span style="font-size: 10pt;">http://go.microsoft.com/fwlink/events.asp</span></a><span style="font-size: 10pt;">.</span></p><p><span style="font-size: 10pt;">[/quote</span><span style="font-size: 10pt;">]</span></p><p><span style="font-size: 10pt;"> </span></p><p><span style="font-size: 10pt;">The Waters technician says that all the DCOM settings are configured well. </span></p><p><span style="font-size: 10pt;"> </span></p><p><span style="font-size: 10pt;">What could be the reaason for these errors?</span></p></span></p>

Comments

  • Hello,

    DCOM errors it is possible to see on correctly set PC (watersservice.exe acount, DCOM settings, domain membership etc.) after antivirus installation or VLAN ports blocking change.

    Also some antivirus softwares has integrated firewalling named like Network Threat Protection and these modules block DCOM connection on ports like TCP 135, 136, 137, 139, 445 etc.

    The same effect is visible when Empower 2 CDS is "moved" to dedicated VLANs where this communication is closed also.

    Note: on PC with WinXP Pro SP3 updated is firewall switched off and all DCOMs confugured correctly.

    Note2: if you use Citrix access it will work correctly.

    Try to check what antivirus really control regarding network does.

    I hope it will help. Jiri

  • We solved the problem by changing the user rights for the domain user on the database server to all rights.

Sign In or Register to comment.