[THIN] Re: Web Interface Event Log Shows an Error of Type IMA with an Error ID of 0x80000001 Reported by the XML Service
- From: <GTaylor@xxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Mon, 5 Jan 2009 13:02:29 -0700
Yes, I brought it up on the list last week and also spent a day on the phone
with Tech Support. We tried a lot of things with IMA and the XML brokers, then
got the new KB article explaining it. Now the solution for me is to get rid of
the 4.0 farm, in the plans anyways.
George
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Carl Stalhood
Sent: Monday, January 05, 2009 12:03 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Web Interface Event Log Shows an Error of Type IMA with an
Error ID of 0x80000001 Reported by the XML Service
I think somebody reported this issue last week. A new KB article was posted.
This problem occurs in a mixed farm environment of Presentation Server 4.5 and
Presentation Server 4.0, where the XML broker is the Presentation Server 4.5
server. In Presentation Server 4.5, ccticket can talk to IMA using RPC or XML.
In Presentation Server 4.0, this communication is XML only. The LaunchReference
string fails because this API does not exist in Presentation Server 4.0. When
the RPC request fails, the Presentation Server 4.5 ccticket falls back to the
XML request, which is by design. The Web Interface generates an event log error
as a result of the fallback from RPC to XML.
http://support.citrix.com/article/CTX118905
________________________________
Regional Health's mission is to provide and support health care excellence in
partnership with the communities we serve.
Note: The information contained in this message, including any attachments, may
be privileged, confidential, or protected from disclosure under state or
federal laws . If the reader of this message is not the intended recipient, or
an employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution, or
copying of this communication is strictly prohibited. If you have received this
communication in error, please notify the Sender immediately by a "reply to
sender only" message and destroy all electronic or paper copies of the
communication, including any attachments.
Other related posts:
