Re: [foxboro] ICC-CSA Errors
- From: "Landry, Scott" <scott.landry@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 11 Aug 2006 08:28:57 -0400
There is a quick custom available from Invensys CSC to correct the
(more than 32,767 requests to CSA). I think this was fixed in
V6.5/V7.1
Regards,
Scott
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: Thursday, August 10, 2006 2:08 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] ICC-CSA Errors
Re: Error codes
The csa.h header has the only documentation that I have seen.
#define CS_STATE_ERR -2 /* Invalid state for request */
#define CS_MISMATCH -3 /* CSA authorization code
mismatch; may not change CS */
#define CS_NAME_IN_USE -4 /* Cmpd or block name already used
*/
#define CS_NOT_FND -5 /* Required element not found */
#define CS_BLK_NOT_FND -6 /* Block not part of compound */
#define CS_DB_BAD -7 /* Invalid Informix reference */
#define CS_FILTER_BAD -8 /* User filter rejected */
#define CS_BAD_STATION -9 /* Location is not defined in
system */
#define CS_MISSING_PARM -10 /* Missing compound or block name
*/
#define CS_USER_IPC_ERR -11 /* process not set-up for CSA IPC
*/
#define CS_NAME_USED_ELSEWHERE -13 /* name used in another domain */
#define CS_LARGE_LIST -12 /* user list is too large for IPC
*/
#define CS_UNKNOWN -20 /* unrecognized CSA request */
#define CS_UNAVAIL -30 /* CSA server is unavailable */
#define CS_F_ERR -50 /* File I/O error detected */
#define CS_LIC_ERR -60 /* Licensing related error, except
for
not enough licenses */
#define CS_NOT_ENOUGH_TOKENS -61 /* Could not find enough licenses
*/
#define CS_STATYPE_ERR -62 /* Could not find station type info
*/
#define CS_BLKWT_NOT_FND -63 /* Could not find block weight in
table=3D20
*/
#define CS_STA_FTTYPE_ERR -64 /* Could not find if station is
fault=3D20
tolerant */
#define CS_OH_NO -100 /* Thought-to-never-occur condition
has occurred! (Such as some
station
has > "long" number of
compounds) */
Re: -30
The -30 error is a generic message indicating that communication to CSA
failed. On some versions of the I/A Series software, too many accesses
could cause such a failure, but, generally, any fault can result in this
error.
I've gotten this message due to CSA failures and network failures.
Re: What to should you do.
Check to see if the CSA Server are running and restart it if not using
go_ACSA.
Regards,
=3D20
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
Sent: Thursday, August 10, 2006 1:28 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] ICC-CSA Errors
An AW51D running V6.2.1 software had /var full problem. After the
problem, could not run ICC. Determined 'mles' was not running. Ran
go_Amisc. With ICC, tried to access station and got CSA error -30 dialog
box. After acknowledge, another dialog box 'CSA error Csgetstate' when
opening CP.
First, is there a comprehensive list of these ICC error codes? I know
what -30 is (more than 32,767 requests to CSA) but don't understand how
that happens immediately after a reboot unless there are buffered
requests in a file someplace.=3D20
Second, how can I get ICC to work? There is no saveall and no CSA_save.
All that exists is a good checkpoint.
Advice welcome. Thanks. Very frustrating.
Best Regards,
Ken Heywood
=3D20
=3D20
--------------------------------------------------------
=3D20
This message (and any associated files) is intended only for the=3D20
use of the individual or entity to which it is addressed and may=3D20
contain information that is CONFIDENTIAL, subject to copyright or
constitutes a trade secret. If you are not the intended recipient=3D20
you are hereby notified that any dissemination, copying or=3D20
distribution of this message, or files associated with this =
message,=3D20
is strictly prohibited. If you have received this message in error,=3D20
please notify us immediately by replying to the message and =
deleting=3D20
it from your computer. Messages sent to and from PCS may be
monitored.=3D20
Internet communications cannot be guaranteed to be secure or
error-free=3D20
as information could be intercepted, corrupted, lost, destroyed,
arrive=3D20
late or incomplete, or contain viruses. Therefore, we do not accept=3D20
responsibility for any errors or omissions that are present in this=3D20
message, or any attachment, that have arisen as a result of e-mail=3D20
transmission. If verification is required, please request a =
hard-copy=3D20
version. Any views or opinions presented are solely those of the
author=3D20
and do not necessarily represent those of the company.
=3D20
=3D20
_______________________________________________________________________
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
=3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D20
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
