[ngw] Support response time

David Krotil David.Krotil at hilo.cz
Fri Oct 9 09:33:26 UTC 2020

Hi Simon,
I´m doing upgrade between major version only as migration and never had
a problem. Moving GW is only copy thing, eDirectory CA is well
documented and it works, DNS and DHCP is easy too, create only new DNS
and DNS servers , some configuration and thats is.


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.

>>> "Simon Shilton" <Simon.Shilton at acustica.co.uk> 09.10.2020 11:23 >>>
Hi Craig

Thanks for that, mine is also OES 2015 sp1 to OES 2018 sp2, clearly we
are not alone.

Mine is on a VM so at least I can roll back tot he snapshot after the
failed upgrade and recover the situation.

I am finding the eDir upgrade dialogue does not appear. eDir
configuration settings appear, and all setting appear correct.
Configuration fails during "Check for conflicting objects in directory"
stage, with error: Conflicting NCP Server object found "remove the
conflicting objects."

as you found, rebooting that failed upgrade server leaves some stuff
working and other stuff broken.

I was hoping not to have to do a new build or server migration as it
hosts DNS, DHCP, eDir CA and GW, which was a real pain to sort out last


>>> On 09 October 2020 at 09:57, in message
<5F8025DD0200004F00024315 at>, "Craig Meads"
<craigm at cwise.co.nz>
> I've had this too, and if I abort, and then let the Linux boot, and
go into 
> Yast, I get the same error. In two instances for reasons unknown it 
> eventually got past what it thought were Network latency errors and
> the upgrade I thought. (Going from SLES11/OES2015 to OES2018SP2)
> However iManager and Netstorage would not work, as Xtier had not been

> upgraded/installed for some reason.
> I had support looking at one Server for quite some time, and I had to
> the data off it and install it again from scratch with a new
> Redoing the upgrade doesn't fix it. reinstalling iManager didn't fix
> although I could drop GroupWise Webaccess 18 onto it and get iManager

> working, as it fixed Tomcat
> I have two other Servers do the same thing this week, so have given
up doing 
> the upgrades, I will simply nuke and put the data back.
> Something obviously got missed in QC for OES2018SP/SP2 upgrades
> Cheers
> Craig
>>>> "Simon Shilton" <Simon.Shilton at acustica.co.uk> 9/10/2020 9:39 PM
> Hi Pam
> SR#101305731701
> OES2018 upgrade. eDir fails with NCP server object error.
> Thanks
> Simon
>>>> On 08 October 2020 at 22:15, in message
<5F7F2CFB.A8FC.0089.1 at gmail.com>, 
> <pkrobello at gmail.com> wrote:
> Simon,
> What is the SR number?  I don't see a GW SR under your name.
> Thanks,
> Pam
> ‑‑ This email was Anti Virus checked by Astaro Security Gateway. 
> http://www.sophos.com 
>>>> Simon Shilton<Simon.Shilton at acustica.co.uk> 10/8/2020 2:31 PM >>>
> Hi, does anybody have any experience of support response times to SRs

> recently?
> I opened an SR about a failed upgrade to our main GW server 6 weeks
ago, and 
> apart from being asked to upload log files 3 weeks ago I have had
nothing to 
> date
> is this typical atm?
> thanks
> Simon
> ‑‑ 
> This email was Anti Virus checked by Astaro Security Gateway. 
> http://www.sophos.com 
> ‑‑ 
> This email was Anti Virus checked by Astaro Security Gateway. 
> http://www.sophos.com 

ngw mailing list
ngw at ngwlist.com 

More information about the ngw mailing list