FlowerPower

Having a slight problem.

In my opinnion client installation/migration should be able to be performed no matter what client lays underneeth.
So we where, as we are in the migration phase of about 15 000 users using the 8.0.1 as it came out. After launch of the 8.0.1 german we installed the german over the english client. That caused problems. The client refuses to boot up anymore after upgrade. We had that on multiple machines. With different people performing the update. So no layer 9 problem :-)
So we finaly ended up opening a pmr with ibm. Below is the anonymized answer we got. How helpfull is that??
Anyone knowing any workarround or how to?
Well i know most of you are english tonges so no need for localized installations....
I apreciate any help....

Hello Mr XXX,

My name is Rxxxx Mxxxxx and I am assigned to pmr 6xxxx,xxx,xxx ' notes client doesn't start after update'.

(1) In the pmr description it mentions that the 8.0.1 English was installed first and ten the German 8.01 build was installed over it.

Why was this done.  Could the German 8.0.1 Client be installed on its own.


(2) Please use one of the Client machines involved and remove the Client ( all clients ) installation from it.

Use this technote as guidance ;


Lotus Software Knowledge Base Document

Title:        How to perform a clean reinstall of a Notes client
Doc #:        1245159
URL:        http://www.ibm.com/support/docview.wss?rs=899&uid=swg21245159


(3) Reinstall German Client and see if it launches.


Best regards

Rxxxx Mxxxxxx

This is where the technote goes to
IBM - How to perform a clean reinstall of a Notes client

This was definetly the highligt on CEBIT

IBM asked me if i was interested meeting Jeff Schick while being on CEBIT. I asked what he is and what he does. So i was told that he is the second highest within Social Computing Software within IBM.

My first thought was.....
#after  all the problems we had migrating to 8.0.0 and 8.0.1 id rather talk to Rhodin and tell him what i think is optimizationable within the very stiff support structure.
On the second thought i was very enthusiastic talking to someone who might be a bright star and some mastermind standing behind social computing.

So we started by introducing ourselfes shakhands and busnesscardswapping :-)
Than i asked some of my prepared questions about beyond 2010 and i was suprised how onpenly Jeff talked about stuff that was not officialy released nor anounced. So i forgott about all my prepared questions anf we went on into a very hypthetical highlevel diskussion.

Mainly on technology but also on salesstrategy..... Wher Iam not sure if Jeff is aware that many ideas he has are not going to sell in europe.
We ran out of our shedule asJeff obviously found some interest in our little talk. As a result he asked me to join him into a telephonconference next week to go indepht about our conversation.

I wih IBM had more bright stars like him.


 

Ok here is part two of the traveler story.....
I could not get rid of the http error, so i decided to start with a fresh server install, which first did look very good. I fired the server up and did not receive any error.
So far so good than i got this severe messges.

Google or the forum did not return any answer so iguess i will have to ask big BLUE again for some help.

 Ok where do we start...
The good news is: no critical problem so far.
One thing bugs me so..... ever wanted to use the feature to synch your calendar with your sametime availability?
Welll i did to..... the only problem was...... it didnt work....... OK...
I reinstalled the client --> didnt work
i installed a fresh 8.0.1 client --> didnt work
upgraded mailDB to 8.0.1 design --> didnt work
I installed new XP and new client --> didnt work
OK one more
I installed Domino 8.0.1 and connected the client to it (was a 7.0.2 CCH1 before) --> didnt work

So i opened up a PMR priority 3 ... wel just a feature that seemed to not work in that particular environment.....
Got answer from BIG BLUE......
Problem HZHU7BG7ZB  report ist breits dokumentiert
The below issue can reproduce on both WCT801_20080201 and WCT801_20080202 build on Windows clients.

It'S a pitty.
How can i roll out a piece of software with known bug and a custommer testing it an hour after it was released gets a prepared problem report?

 

well well well......
Why not communicate.....
Hey there is a fine piece of client, but it has some known bugs.... you cant use the all new feature of bla bla..........
Would have saved myself some hours of new installation clients servers and osses.......
ok my hourerly rate is notexorbitant so the invested time was only some sent worth of money ;-)
and i do think i am not the only one ending up with errors like this.....
hmmm where is the accountability?

My boss would have had my fired for doing things like this.... in a photon torpedo outta space....
YEAAAAAAAAAAAAAAAHHHHHHHHHHHHHHHHHHHHHHH

 Here is the latest news of star suck we are writing the year 2008 and we are still having loads of problems with our comm system.

 

We are up to 51 open problem reports now. One of the mos anoying problem is that the jvm.dll is not going to be copied into the notes dir if you perform an upgrade from 7.xx.

Anyone having the same problem with a localized notes rcp client installer package? (was german in that particular case).

 

Live long and prosper