: Critical: Server Hung
**
Vaibhav has provided the correct must have Overview performance hotfix..
However you need to check the people record of the users and based on the
application permission they have, you need to correct the application
preference record.. By default it has "Yes" f
was issue
>> with Overview console.
>> Overview console was single threaded. They provided a Jar file fix for
>> the same
>>
>>
>> Ravi
>>
>>
>> --
>> Date: Mon, 4 Feb 2013 13:52:12 -0800
>> From: rem
y provided a Jar file fix for the
> same
>
>
> Ravi
>
>
> --
> Date: Mon, 4 Feb 2013 13:52:12 -0800
> From: remedyr...@gmail.com
> Subject: Re: Critical: Server Hung
> To: arslist@ARSLIST.ORG
>
>
> **
> Kathy, how many rows a
T2068.C112 LIKE :"SYS_B_64") OR (T2068.C112 LIKE
:"SYS_B_65") OR (T2068.C112 LIKE :"SYS_B_66") OR (T2068.C112 LIKE
:"SYS_B_67") OR (T2068.C112 LIKE :"SYS_B_68") OR (T2068.C112 LIKE
:"SYS_B_69") OR (T2068.C112 LIKE :"SYS_B_70") OR (T206
Kathy,Check with BMC Support. we faced this in 7604 SP2 and there was issue
with Overview console.Overview console was single threaded. They provided a Jar
file fix for the same
Ravi
Date: Mon, 4 Feb 2013 13:52:12 -0800
From: remedyr...@gmail.com
Subject: Re: Critical: Server Hung
To
Kathy, how many rows are in the table referenced by the console? I've seen
this happen in some versions where the form doesn't get cleared, and the
SQL queries bog the system down.
Rick
On Mon, Feb 4, 2013 at 1:50 PM, Kathy Morris wrote:
> **
>
> Hi,
>
> ** **
>
> AR System 7.6.03
>
Hi,
AR System 7.6.03
ITSM 7.6.04 SP1.
The incident management console hangs and hoses the system when users access
the Incident Management Overview console.
My understanding is that thru a row-level access query, users see the
incidents for the group they are member of.
If users are a
7 matches
Mail list logo