PI UDS error

[Former Member]

Hello all -

We use the xMII PI UDS connector to connect to the PI server. I found the following error when browsing the Event Viewer - Application log

"COM error occured. Mode Log not supported"

Any idea what reason this error is getting generated.

The checked the Report from Network Manager Statistics in PI System Management Tools application. It lists the following messages -

0 pinetmgr 10/4/2007 10:28:06 AM

PInet accepted TCP/IP connection, cnxn ID 1848 Hostname: cplvpsql3.srv.gapac.com, 162.141.129.11:3065

0 pinetmgr 10/4/2007 10:28:06 AM

New Pinet 1 connection: LUDSE Protocol: 00010008

0 pinetmgr 10/4/2007 10:28:06 AM

New Pinet 1 connection: LUDSE, ID: 1848, No Trust established for: cplvpsql3.srv.gapac.com|162.141.129.11|LUDSE using default login.

0 pinetmgr 10/4/2007 10:28:27 AM

Deleting connection: LUDSE, [-10721] PINET: <b>Client Aborted Connection</b>. (4), ID: 1784 cplvpsql3.srv.gapac.com 162.141.129.11:1737

Appreciate any ideas? Thanks.

[Former Member]

As a minor digression, I would recommend censoring any client ( the business kind, not the technical kind ) specific information in your posts.

[Former Member]

First things first,

Is anything really broken? or is this just a curiosity question?

Check with the PI team what an -10721 error is (my guess is that it is a security error [user name/password], but I'm most likely wrong...).

Next, the COM error, can you send us more info on that.... are you trying to query for a 'log' mode?

Martin.

[Former Member]

The connection was broken. I checked the Event viewer and got the following messages.

COM Error occured, Mode log not supported

Failed [3] retry attempts

Disconnect from Data source

All these messages have almost the same time-stamps.

However Data server connection status in xMII shows proper connection for the PI UDS!

[Former Member]

Sam/Martin,

Talking with the PI team -

1) There are no DCOM settings on PI. Any COM settings are

done through the PI SDK from the connecting device, not the PI source

server.

2) Additionally they mentioned that the connection exe "LUSDE" that we are

seeing in the PI logs and is being called by the PIUDS on xMII server is a

PI API connection. This connection type cannot read tag values of a

string data type??

3) Looking at the PI server it is typically averaging about 3-5% CPU usage.

All well below any level that would indicate an issue with the PI

server.....

Thanks

[Former Member]

Looks like your PI server is going down...

The UDS will not shut down when this happens and will assume it is still connected.

Also try to configure the re-try logic.

Martin

[Former Member]

1 - Yes, Sam was thinking something else...

2 - 'LUDSE' is what you should see, not 'LUSDE', but that is the UDS service, and what you should see.

3 - I agree.

but what does the error (-10721) mean?

Martin.

[Former Member]

I have already configured -

AutoRetry True

AutoRetryCount 3

AutoRetryInterval 30

AutoRetryReconnect True

Could you please explain - "The UDS will not shut down when this happens and will assume it is still connected"

Also per the PI team -

The version of PI that they are running requires the PI base service to

shutdown for less than 5 seconds during a backup. PI Backups are

scheduled for 2am every day and have been running without issue since PI

was installed.

When I check the Error log during this time, I get a different Error -

COM error occured, pipt-wildcard search failed with [-10733] PINET:RPC Resolver is off-line

I see this error occurs consistently everyday whenever the PI baseservice is down.

However this is not related (I think) to the other error messages that in my earlier postings as they are based on different date-timestamps!

[Former Member]

Regarding 10721, I shall ask the PI team about this and get back to you.

Thanks

Srini

[Former Member]

10721

It is a normal informational message. Per OSI Tech Support page.

"----

---

The following messages indicate normal disconnects. The error number (in

square brackets) is given along with its translation.

-

---

0 pinetmgr 27-Oct-05 16:25:19

>> Deleting connection: pishutev(2540), Shutdown request received from

pishutev(2540) (8), ID: 20

0 pinetmgr 27-Oct-05 16:44:21

>> Deleting connection: RandE, [-10721] PINET: Client Aborted

Connection. (4), ID: 39 samson.osisoft.com 127.0.0.1:1106"

[Former Member]

"The UDS will not shut down when this happens and will assume it is still connected" -- Means that... if the PI server closes the connection (which it is) then the UDS doesn't do anything to correct this action (minus the retry logic).

As for you PI team, I agree that this is normal for some of the newer versions of PI, the server shutting down is not isolated to you installation nor is it a 'bad' thing. It is just something that happens.

As for querying while the PI server is down... isn't this kinda intuituve to know that something isn't going to work right? You should expect an error here.

The two are related. They both stem from PI server being unavailable!

Lastly, because you still haven't mentioned it. Are you seeing any real issues or is this just informational (I'm assuming everything is working fine).

Martin.

[Former Member]

There are no issues. Everything seems to be working fine.

But I was concerned about the following error message after the PI team told me that "PI Server did not go down during that time" !

Also they asked me to check maybe this problem was at the xMII PI UDS end...

0 pinetmgr 10/4/2007 10:28:06 AM

PInet accepted TCP/IP connection, cnxn ID 1848 Hostname: cplvpsql3.srv.gapac.com, 162.141.129.11:3065

0 pinetmgr 10/4/2007 10:28:06 AM

New Pinet 1 connection: LUDSE Protocol: 00010008

0 pinetmgr 10/4/2007 10:28:06 AM

New Pinet 1 connection: LUDSE, ID: 1848, No Trust established for: cplvpsql3.srv.gapac.com|162.141.129.11|LUDSE using default login.

0 pinetmgr 10/4/2007 10:28:27 AM

Deleting connection: LUDSE, [-10721] PINET: Client Aborted Connection. (4), ID: 1784 cplvpsql3.srv.gapac.com 162.141.129.11:1737

[Former Member]

I wouldn't worry about a non-issue then...

plus if some one turned on/off the UDS then that could cause these PI messages.

[Former Member]

Martin - how does the PI UDS determine which error(s) require a reconnect and which do not?

[Former Member]

The PI UDS will only try to reconnect if the PI server terminates the connection.

[salvatore_castro]

Srinivasan,

I have a couple of questions for you:

Do you have the PI SDK installed on the machine where the UDS resides?

Is the UDS installed on the PI Server or on a different machine?

What are the DCOM permissions set to on the PI Server?

-Sam

[Former Member]

Sam,

1) We have the UDS installed on the same machine as the xMII server.

2) PI SDK is installed on the xMII server machine.

3) DCOM permissions - I have to check on that with the PI team.

Thanks