Re: [foxboro] AIM* OPC server problem

This appears to be a COM problem - the OPC server and client are on the same
box.
The OPC server appears to be communicating with the AWs OK - when I reboot
one of the AWs, I can see the connections on port 45678 by the OPC server
box.

I just can't find the OPC server with Matrikon Explorer.  I've tried a fresh
install of the OPC explorer on another PC and experience the same problem -
it may be that a windows update/patch has killed something.

Regards,

Kevin

On Wed, Dec 31, 2008 at 1:58 AM, Ron Schafer <
rschafer@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> One item I found once was someone had turned on simple file sharing.
> This messes w/dcom for some reason.
>
> Ronald G. Schafer
>
> Distributed Controls System Administrator
>
> White Birch Paper Company
>
> Bear Island L.L.C. Division
>
> 10026 Old Ridge Road
>
> Ashland VA, 23005
>
> Phone 804-227-4034
>
> Fax 804-227-4052
>
> Email: rschafer@xxxxxxxxxxxxxxxxxxxxxx
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Fitzgerrell, Kevin
> Sent: Monday, December 29, 2008 2:00 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] AIM* OPC server problem
>
> Hi all,
>
>
> This weekend one of our AIM* OPC servers quit working.  When we try to
> view it with Matrikon's OPC Explorer we get a COM error message:
>
>
>
> -----------------------------------------
>
> Header:
>
> An error was encountered while using COM services.
>
> The error may indicate incorrect configuration.
>
> If the problem persists, contact your system administrator.
>
>
>
> Detail box:
>
> COM/OPC error 0x80080005 on CoCreateInstance()
>
> Error string: Server execution failed
>
>
>
> Additional: Could not connect to server 'AIM.OPC'
>
> -----------------------------------------
>
>
>
> Any thoughts?  Normally when we have OPC server problems we reboot the
> OPC box and if that doesn't fix it reboot the AWs and the OPC box.
> That's not fixing things this time.
>
>
>
> Regards,
>
>
>
> Kevin FitzGerrell
>
>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>


 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: