Accessing OPC Server causes Reboot

[Florian Probst]

Hi!

We are using the OPC library(0.4.2) for accessing an INAT OPC server.
Since the server where the application and OPC server are running
changed from 2003 to 2008 (not R2!!) the machine restarts after the
first access. The Windows event log shows that the RCP Process was
terminated and therefore the machine restarts. Other (non java)
applications can access the OPC server without any problems.

On Java side we are getting the following exception:
22.10.2010 13:00:31 rpc.DefaultConnection processOutgoing
INFO:
Sending REQUEST
org.jinterop.dcom.common.JIException: An internal error occurred.
[0x8001FFFF]
at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:
546)
at
org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:458)
at org.jinterop.dcom.core.JIComServer.<init>(JIComServer.java:
427)
at test.Test.main(Test.java:436)
Caused by: java.io.IOException: An existing connection was forcibly
closed by the remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(Unknown Source)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
at sun.nio.ch.IOUtil.read(Unknown Source)
at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
at sun.nio.ch.SocketAdaptor$SocketInputStream.read(Unknown
Source)
at sun.nio.ch.ChannelInputStream.read(Unknown Source)
at
org.jinterop.dcom.transport.JIComTransport.receive(JIComTransport.java:
136)
at
rpc.DefaultConnection.receiveFragment(DefaultConnection.java:182)
at rpc.DefaultConnection.receive(DefaultConnection.java:68)
at
rpc.ConnectionOrientedEndpoint.receive(ConnectionOrientedEndpoint.java:
227)
at
rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:
124)
at rpc.Stub.call(Stub.java:112)
at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:
538)
... 3 more

The error messge from the event log is:
Faulting application svchost.exe_RpcSs, version 6.0.6001.18000, time
stamp 0x47919291, faulting
module rpcss.dll, version 6.0.6002.18005, time stamp 0x49e041eb,
exception code 0xc0000005, fault offset
0x00000000000629ba, process id 0x348, application start time
0x01cb71df44496ee0.

Has anyone seen an scenario like this? What can be done to fix this?
When using Server 2008 R2 everything works fine, but our customer has
to use just 2008.

Thanks in advance!

[Jens Reimann]

Hi,

I would recommend to try Utgard 0.7.0 instead of the old 0.4.2 version at first.

jens

[Florian Probst]

At first, thanks for your quick answer Jens!

This was my first thought - trying a new version, but there was just a
0.5.0-SNAPSHOT at the maven repository. Did the repo change?

Unfortunately there is the same error with the 0.7.0 version of
utgard :-(

On 28 Okt., 16:51, Jens Reimann <ctron1...@gmail.com> wrote:
> Hi,
>
> I would recommend to try Utgard 0.7.0 instead of the old 0.4.2 version at
> first.
>
> jens
>

[Jens Reimann]

First of all .. maven is not supported anymore since it only made problems for us.

Beside that we still convert out P2 repository into a Maven2 repository at http://repo.openscada.org/maven2-bob-release ... but I am not sure if it works 100%.

Anyway the jars can be downloaded at:

http://download.openscada.org/external/R/0.15.0/openscada-external-R.0.15.0.zip
http://download.openscada.org/aurora/R/0.15.0/openscada-aurora-R.0.15.0.zip
http://download.openscada.org/utgard/R/0.7.0/openscada-utgard-R.0.7.0.zip

You shouldn't need more than those three which contain all jars you actually need.

[Florian Probst]

Ok, thanks for that information. We will import the current artifacts
manually into our repository manager!
The issue seems to be located in the windows services. I think there
is nothing we can do on Java side to reolve these reboots, right?

On 28 Okt., 17:29, Jens Reimann <ctron1...@gmail.com> wrote:
> First of all .. maven is not supported anymore since it only made problems
> for us.
>

> Beside that we still convert out P2 repository into a Maven2 repository athttp://repo.openscada.org/maven2-bob-release... but I am not sure if it

> works 100%.
>
> Anyway the jars can be downloaded at:
>

> http://download.openscada.org/external/R/0.15.0/openscada-external-R....http://download.openscada.org/aurora/R/0.15.0/openscada-aurora-R.0.15...http://download.openscada.org/utgard/R/0.7.0/openscada-utgard-R.0.7.0...

>
> You shouldn't need more than those three which contain all jars you actually
> need.
>

[Jens Reimann]

A spontaneous reboot seems like a major Windows  bug ;)

Am 29.10.2010 08:40 schrieb "Florian Probst" <florian...@gmail.com>:

Ok, thanks for that information. We will import the current artifacts
manually into our repository manager!
The issue seems to be located in the windows services. I think there
is nothing we can do on Java side to reolve these reboots, right?

On 28 Okt., 17:29, Jens Reimann <ctron1...@gmail.com> wrote:

> First of all .. maven is not support...

> Beside that we still convert out P2 repository into a Maven2 repository athttp://repo.openscada.org/maven2-bob-release... but I am not sure if it

> works 100%.
>
> Anyway the jars can be downloaded at:
>

> http://download.openscada.org/external/R/0.15.0/openscada-external-R....http://download.openscada.org/aurora/R/0.15.0/openscada-aurora-R.0.15...http://download.openscada.org/utgard/R/0.7.0/openscada-utgard-R.0.7.0...

>
> You shouldn't need more than those three which contain all jars you actually
> need.
>

> On Thu, Oct 28, 2010 at 5:10 PM, Florian Probst <florian.pro...@gmail.com>wrote:

>
>
>
>
>
>
>
> > At first, thanks for your quick answer Jens!
>

> > This was my first thought - try...

[Jens Reimann]

As mentioned in another groups post:

We recently ran into the same problem and there is a solution from Microsoft for this issue:

http://support.microsoft.com/kb/2518423