**
Thanks! Point 2 about plug-ins that previously ran using a 64-bit JRE now
requiring a 32-bit JRE sounds ludicrous.
Jason
On Mon, Nov 10, 2014 at 10:44 AM, Pierson, Shawn
<shawn.pier...@energytransfer.com> wrote:
**
I’m not the one that did the install so I haven’t investigated them in
detail, but a few of the issues are:
1) FTS became misconfigured, had to be reconfigured.
2) Several formerly 64-bit JRE plugins now require a 32-bit JRE (I was
skeptical about this but BMC support were the ones that told us that most of
the plugins can’t run against a 64-bit JRE.)
3) Custom approvals are not working correctly, after the approval
engine not running at all.
4) We can’t get rid of the Compatibility View error that sparked this
thread
5) ADDM is unable to write to the CMDB because of Normalization Engine
errors (even though we don’t have in-line normalization turned on.)
6) Other plugin and JRE issues.
This all happened from the AR System, Mid-Tier, and Atrium Core upgrades.
I think AR System is the main area all these are an issue in. Interestingly,
the ITSM upgrade that we did in one of our environments introduced no real
errors other than conflicting with several of our customizations. My strategy
has always been to try to remain as out of the box as possible but through some
events I don’t want to get into, we’ve painted ourselves into a corner around
email where we have a massively customized RBE as well as outgoing HTML
formatted emails. That’s not BMC’s fault though, that’s an internal
organizational failure, but the AR System issues shouldn’t be happening at all.
Thanks,
Shawn Pierson
Remedy Developer | Energy Transfer
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Miller
Sent: Monday, November 10, 2014 11:17 AM
To: arslist@ARSLIST.ORG
Subject: Re: ITSM 8.1.2 Mid-Tier Compatibility Mode Defect
**
What kind of issues are you running into with 8.1.2?
On Mon, Nov 10, 2014 at 5:41 AM, Pierson, Shawn
<shawn.pier...@energytransfer.com> wrote:
**
That’s odd but good that that worked for you because it didn’t for my
environment. It may be a moot point though, we’re running into so many issues
with 8.1.2 that I’m not sure we’re going to go live with any of it and just
wait for the next release.
Thanks,
Shawn Pierson
Remedy Developer | Energy Transfer
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Miller
Sent: Friday, November 07, 2014 6:09 PM
To: arslist@ARSLIST.ORG
Subject: Re: ITSM 8.1.2 Mid-Tier Compatibility Mode Defect
**
HA! You know what our standard desktop looks like :) There are a ton of
clinical web apps that have much more stringent browser
requirements/limitations and I really don't want to get involved in that mess.
We are a custom shop so our forms are typically much lighter than ITSM. The
newer JavaScripting engines past IE8 will be welcomed but IE8 is doing ok for
use right now.
Fortunately I found changing arsystem.compatibility_view from true to false
in config.properties and restarting MT did the trick. I wish there was some
documentation on this setting so I could see if there is some downside to doing
this but so far things look good.
Jason
On Thu, Oct 30, 2014 at 5:03 PM, LJ LongWing <lj.longw...@gmail.com> wrote:
**
I haven't investigated this thoroughly, but, I think it would be worth the
effort to work with your desktop team. It is my understanding that
compatibility mode is significantly slower than non, and that is the primary
reason that the message was instituted.
On Oct 30, 2014 5:44 PM, "Jason Miller" <jason.mil...@gmail.com> wrote:
**
Hi Shawn,
Did you get anywhere with this? We just upgrade our dev and QA to SP2 and
are now seeing this (annoying) message. Our browser it highly managed and I
really don't want to have to include our desktop team in order to update to
SP2. I am not going to put SP2 in production without getting rid of this
message though.
Thanks,
Jason
On Wed, Oct 8, 2014 at 7:11 AM, Pierson, Shawn
<shawn.pier...@energytransfer.com> wrote:
**
It looks like we found a defect in the combination of ARS and Mid-Tier
8.1.2. It is happening with both IE9 and IE11.
What happened is that after upgrading the mid-tier, we started seeing this
warning at the top of the screen:
IE is running in Compatibility View. Please remove Mid-tier URL from either
IE Compatibility View Settings or Registry location. (ARWARN 9429)
This is completely useless, because it’s not like the Remedy team or our
users have any say over whether we run things in compatibility mode or not, so
we added 9429 to our Suppress-warnings: list in ar.cfg.
This worked great until we also upgraded the application server. Now
either Suppress-warnings doesn’t work or this specific error is impossible to
disable. We’re working with BMC support and they’ve been responding quickly,
but it appears they don’t understand the reason we don’t want that error on the
top of every single screen. Unfortunately, if we can’t find a way to disable
this, we’re going to be unable to upgrade. Hopefully BMC recognizes the error
of their ways and releases a hotfix soon.
Do any of you have any ideas of how to suppress that message in the
meantime?
Thanks,
Shawn Pierson
Remedy Developer | Energy Transfer
Private and confidential as detailed here. If you cannot access hyperlink,
please e-mail sender.
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
Private and confidential as detailed here. If you cannot access hyperlink,
please e-mail sender.
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
Private and confidential as detailed here. If you cannot access hyperlink,
please e-mail sender.
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
