[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ngw
Subject:    Re: [ngw] Constant GroupWise Client Crashes
From:       "David Krotil" <David.Krotil () hilo ! cz>
Date:       2019-04-03 15:09:45
Message-ID: 5CA4CCB9020000100008BCB7 () mail ! hilo ! cz
[Download RAW message or body]

Nico,
have you tried to create new POA and move users there ? This should be
solve any data related issues, I done this couple times and every time
solved it problems with POA crashes.
 
David


------------------------------------------------------------------
Obsah tohoto e-mailu a všechny připojené soubory jsou důvěrné a mohou
být chráněny zákonem. Tento e-mail je určen výhradně jeho adresátovi
a jiné osoby do něj nejsou oprávněny nahlížet či s ním jakkoliv
nakládat, jinak se dopustí protiprávního jednání. V případě, že
nejste adresátem tohoto e-mailu, prosíme o jeho vymazání a o podání
e-mailové zprávy. 

The content of this e-mail and any attached files are confidential and
may be legally privileged. It is intended solely for the addressee.
Access to this e-mail by anyone else is unauthorized. If you are not the
intended recipient, any disclosure, copying, distribution or any action
taken or omitted to be taken in reliance on it, is prohibited and may be
unlawful. In this case be so kind and delete this e-mail and inform us
about it.

> > > "Nico Basson" <NBasson@scu.mb.ca> 03.04.2019 16:27 >>>
Thanks Marvin, the crashes has been over multiple versions of the
client, hence why I think it might be PO related?
If I need to send more crash dumps or log files then let me know
please
Pam, I've used both the methods you specified in the TID as well as
prodump to send files in.

This communication, including any attachments, is intended for the use
of the addressee and may contain information that is privileged and
confidential. If you are not the intended recipient, you are hereby
notified that any use, dissemination, distribution, copying or
disclosure of this communication, in whole or in part, by anyone other
than the intended recipient(s) is strictly prohibited and may result
in
liability for breach of confidential information. If you have received
this communication in error, please notify us immediately, delete this
communication from all data storage devices and destroy all hard
copies.
While we make every effort to ensure all information provided to you
is
accurate and complete, errors or omissions sometimes occur. SCU
reserves
the right to correct errors or omissions contained in this
communication.  

The individual sender and Steinbach Credit Union take no
responsibility
for any viruses that may have affected this email and/or
attachment(s).
Employee emails that do not conform to the rules set out in Steinbach
Credit Union's Computer Usage Agreement are deemed to be outside the
course of employment and SCU does not accept responsibility or
liability
for such emails. Thank you.

> > > <pkrobello@gmail.com> 2019-04-03 9:16 AM >>>
Thanks Marvin, and yes indeed.  You do hold our feet to the fire when
you have an SR that involves a crash and cores that you have supplied
> -)  And that is perfectly acceptable.  

The message about the cores posted the other day is a very good one as
is your with the list of things to do to get us the cores that we need.

I have, in fact, sent that around to my team to make sure we are all
on
the same page for getting the information necessary to help
engineering
get to the bottom of these.

As for the client crashes that Nico is seeing I am going to be digging
more into the SRs he has had opened and the resolution of those SRs
and
will work with Nico off list.  The tid that is the most helpful to us
when talking about Windows client crashes is
https://urldefense.proofpoint.com/v2/url?u=https-3A__support.microfocus.com_kb_doc.php \
-3Fid-3D7018025&d=DwIGaQ&c=aBi5H83Vbn6_H1y-B_2iSQ&r=jqSWVRB9K_V-PPSfjMQ7CSBed3tjb8d2RB \
t-cibr0LE&m=tUuG8p95dePb2bsBtyMmh3A_-au-tH3uC96ewKbGUY8&s=Gp9DnhihMu-nTJz09wpG7b8b3zNb5B-uzeWevt-SG8M&e=.
  As is your comment to make sure that the SR is opened and we have
sent
out the most recent FTF client build to make sure that the issue is
not
something that has already been fixed.


Thanks for keeping us honest!  We appreciate all that you do.

Pam

> > > Marvin Huffaker<mhuffaker@redjuju.com> 4/2/2019 6:51 PM >>>
I don't accept client crashes as "Normal" and I will push Microfocus
like a sonofabitch to get it resolved. Ask Pam..

I have a few thousand users spread out among my customers and once in
a
while we go through a rash of crashes but for the most part we're
stable. Sometimes on my own system, I have crashes and it's usually
related to proxy or functions that do things like switch accounts.  
But
again, unacceptable and it should be a high priority.   I can help you
push it up the flagpole if you're not getting the attention from the
developers and getting it resolved.

I saw someone post  a link to the tid on how to get a core dump. Make
sure you're configured for that on the problem machines and then start
sending cores in.

Marvin
> > > "Nico Basson" <NBasson@scu.mb.ca> 4/2/2019 9:52 AM >>>
Hi,

We have users with constant GroupWise client crashes which is getting
to the point of it being unusable for them.
We have tried various things like installing the latest GroupWise
client, re-imaging computers and even giving people different PCs
altogether as recommended by MicroFocus.
I have also ran multiple Analyze/Fix and Structural Rebuilds on a
bunch
of users. The POA also don't seem to be that busy, we have no CS reqs
pending and the threads seem to be all close to 0.
I have even doubled the RAM and the CPU on the POA server.
We currently have 18.1 installed.
I'm out of ideas and desperate to get this fixed, I have sent multiple
crash dumps and POA logs to MF, but they have not been able to help me
over the course of over a month.
If anyone has any suggestions that might help resolve this I will be
willing to try it.

Thanks,

Nico Basson
Steinbach Credit Union

This communication, including any attachments, is intended for the use
of the addressee and may contain information that is privileged and
confidential. If you are not the intended recipient, you are hereby
notified that any use, dissemination, distribution, copying or
disclosure of this communication, in whole or in part, by anyone other
than the intended recipient(s) is strictly prohibited and may result
in
liability for breach of confidential information. If you have received
this communication in error, please notify us immediately, delete this
communication from all data storage devices and destroy all hard
copies.
While we make every effort to ensure all information provided to you
is
accurate and complete, errors or omissions sometimes occur. SCU
reserves
the right to correct errors or omissions contained in this
communication.  

The individual sender and Steinbach Credit Union take no
responsibility
for any viruses that may have affected this email and/or
attachment(s).
Employee emails that do not conform to the rules set out in Steinbach
Credit Union's Computer Usage Agreement are deemed to be outside the
course of employment and SCU does not accept responsibility or
liability
for such emails. Thank you.

_______________________________________________
ngw mailing list
ngw@ngwlist.com 
https://urldefense.proofpoint.com/v2/url?u=http-3A__ngwlist.com_mailman_listinfo_ngw&d \
=DwIGaQ&c=aBi5H83Vbn6_H1y-B_2iSQ&r=jqSWVRB9K_V-PPSfjMQ7CSBed3tjb8d2RBt-cibr0LE&m=tUuG8 \
p95dePb2bsBtyMmh3A_-au-tH3uC96ewKbGUY8&s=BBcKBbL_uBDt1dfNZ3SK3Myrzk9l1FB2GbNRaSHgwVI&e=





_______________________________________________
ngw mailing list
ngw@ngwlist.com
http://ngwlist.com/mailman/listinfo/ngw


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic