Re: [foxboro] syserror 3205
- From: "Johnson, Alex P (IPS)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 31 Mar 2009 14:57:28 -0400
Dirk,
Where do you see the error code 3205? If it is a block parameter, which
block type and which parameter?
Regards,
Alex Johnson
Invensys Process Systems
10900 Equity Drive
Houston, TX 77041
713 329 8472 (desk)
713 329 1600 (operator)
713 329 1944 (SSC Fax)
713 329 1700 (Central Fax)
alex.johnson@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of dirk.pauwels@xxxxxxxxxx
Sent: Tuesday, March 31, 2009 1:33 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] syserror 3205
Hi Guys,
We had a number of sequences which kept producing syserrors 3205
(request
type mismatch?) some of the sequences didn't even seem to process the
error exception handling code, although this was present, tested and
proven to be good.
We recently upgraded from Mesh 8.3 (with ZCP270/CP60) to 8.4.2 . and
reimaged the CP's. We also re-installed batchsuite (redundant), so a lot
of possible causes....The problem sequences hadn't been changed and
were
running fine before the upgrade. The problem seemed to be related to 2
CP's, the others were doing fine. I couldn't pinpoint the cause. No
sysmon
errors.....Rebooting the AW70 host seemed to solve the problem for now.
But it's not very re-assuring.... Any known problems with 8.4.2 and
ICC/CSA etc? As far as I know the invensys engineer installed all the
QF's
so we should be up to date.
Could the problem be related to the CSA server? Other than that I
wouldn't
know what rebooting the host would solve...
Thanks & rgds,
Dirk
_______________________________________________________________________
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
** Confidentiality Notice:
This e-mail, including any associated or attached files, is intended solely for
the individual or entity to which it is addressed. This e-mail is confidential
and may well also be legally privileged. If you have received it in error, you
are on notice of its status. Please notify the sender immediately by reply
e-mail and then delete this message from your system. Please do not copy it or
use it for any purposes, or disclose its contents to any other person.
This email is from the Invensys Process Systems business unit of the Invensys
Group, a group of companies owned by Invensys plc, which is a company
registered in England and Wales with its registered office at Portland House,
Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of
European legal entities within the Invensys Group, please go to
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail
inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail and any attachments thereto may be
subject to the terms of any agreements between Invensys (and/or its
subsidiaries and affiliates) and the recipient (and/or its subsidiaries and
affiliates).
_______________________________________________________________________
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:
- » Re: [foxboro] syserror 3205 - Doucet, Terrence
- » Re: [foxboro] syserror 3205 - Johnson, Alex P (IPS)
- » Re: [foxboro] syserror 3205 - Sascha Wildner
- » Re: [foxboro] syserror 3205 - dirk . pauwels
- » Re: [foxboro] syserror 3205 - Menting, H.J.M. (Hein)
- » Re: [foxboro] syserror 3205 - dirk . pauwels
- » Re: [foxboro] syserror 3205 - Doucet, Terrence
- » Re: [foxboro] syserror 3205 - dirk . pauwels
- » Re: [foxboro] syserror 3205 - Johnson, Alex P (IPS)
- » Re: [foxboro] syserror 3205 - David Johnson
- » Re: [foxboro] syserror 3205 - dirk . pauwels
- » Re: [foxboro] syserror 3205 - Johnson, Alex P (IPS)
- » Re: [foxboro] syserror 3205 - steve . shimp
- » Re: [foxboro] syserror 3205 - dirk . pauwels
- » Re: [foxboro] syserror 3205 - dirk . pauwels
- » Re: [foxboro] syserror 3205 - Johnson, Alex P (IPS)
- » Re: [foxboro] syserror 3205 - Johnson, Alex P (IPS)
- » Re: [foxboro] syserror 3205 - Badura, Tom
- » Re: [foxboro] syserror 3205 - Moore, Kenneth, Celanese/US
- » Re: [foxboro] syserror 3205 - Johnson, Alex P (IPS)
- » Re: [foxboro] syserror 3205 - Airhart, Chad M.
- » Re: [foxboro] syserror 3205 - Jack.Easley
- » Re: [foxboro] syserror 3205 - Gregory A Hurwitt
- » Re: [foxboro] syserror 3205 - BrianLong
- » Re: [foxboro] syserror 3205 - dirk . pauwels
- » Re: [foxboro] syserror 3205 - dirk . pauwels
- » Re: [foxboro] syserror 3205 - dweinbrenner