R8.0.2 is available on PWSW/PA

Tags: Lotus Notes Lotus Domino 8.0.2 Bug

I just downloaded the full eclipse/standard 8.0.2 client and upgraded my main client.

The upgrade itself went ok (complaining only about an open instance of FireFox), but after launching the full client I noticed that I can no longer connect to my company's SameTime server.

(I have no problem connecting to the Bleed Yellow ST server so it's probably a setting on the server that's bugging me).

Update: The client does appear to be a lot faster than the 8.0.1
keep up the good work

One thing is still not fixed:


The ST chat window that refuses to go away

Tags: Lotus Notes Bug 8.0.1

It's been a while since I ran into a new 'feature' in 'Beta 5' (as 8.0.1 is called over in the #notes channel on EFNet (irc)), but here it is.

When trying to close out of a ST chat window the client throws this usefull error message at me:
A picture named M2

The chat window disappears to the background but is still listed in the taskmanager.


Toolbar madness

Tags: Lotus Notes 8.0.1 Bug

This is what happened to my toolbars when I decided to send an excel sheet from within Excel 2007.

A picture named M2

Before, the toolbars were all neatly organised in three rows, and no, I did not switch to the administration and/or designer client in this session at all.


Notes 8.0.1 and COM glitch?

Tags: Lotus Notes 8.0.1 Bug

I executed a VBA macro in an Excel sheet that access the Lotus Notes client through COM objects.

This semi-launched the standard client to the point it showed the background screen (see below), with the last used location selected at the bottom right hand corner.

A picture named M2

Even after closing out of Excel, the client stays open in this state in which it does not respond to anything.

The only thing left to deal with this is to execute nsd -kill to terminate this client instance before it is possible to use the client again.


Yet another weird problem in R8.0.1 a.k.a. beta 5

Tags: Lotus Notes 8.0.1 Bug

I start the full client (which I closed out of normally previously on this computer), and open my mail and end up with this screen:

A picture named M2

It doesn't matter if I access the local replica or the one on my server.
When opening the blogsphere db that this site's hosted in I end up with this:

A picture named M3

No errors, just a blank page (btw, did you notice the toolbars?)

Sigh... R8 has got great potential but is still WAAAAY too unstable to be inflicted upon normal users.
How about paying as much attention to fixing 'features' as to adding new functionality?


Yet another error

Tags: Lotus Notes 8.0.1 Bug

At some point today when I was tinkering with some code in designer, I managed to crash the client, triggering nsd to step in and cleanup the mess (or so I thought).

I checked taskmgr, to make sure all notes processes had terminated and saw none running before I restarted my client, which resulted in the following:

A picture named M2

Clicking OK resulted in the following usefull error message (NOT).

A picture named M3

By he way, can somebody with a higher resolution than my laptop (1200x800) tell me if there's more than the one default action in this prompt?

After running nsd -kill I was able to finally start my client again.


Usefull error message

Tags: Lotus Notes 8.0.1 Bug

All of a sudden I started getting this error when trying to open a database:

A picture named M2


Widget Woes

Tags: Lotus Notes Widgets 8.0.1 Bug

Initially I had setup the client with a local widget store called toolbox.nsf.
When I configured a widget catalog on the server and changed the config to use the catalog from the server (toolbox.nsf) it came up with a prompt telling me that the toolbox.nsf was already present and that  a new replica could not be created. So I closed out of the client, and removed the toolbox.nsf from my client's data directory, and restarted the client, only to find the following error popping up again, eventhough there was no local toolbox.nsf anymore as you can see in the following screen shot:
A picture named M2

Changing the name to toolbox2.nsf in the widget prefs resulted in creating a local replica of the toolbox.nsf on the server with the name toolbox2.nsf and all is well now.

What leaves me to wonder where does he client store the information about the local widget store that caused the above error message eventhough there really was NO local toolbox.nsf


Productivity Killer

Tags: Lotus Notes Symphony 8.0.1 Bug

R8.0.1 Standard Symphony components (a.k.a. productivity tools) is still a productivity killer for me.
My client decided to hang 3 quarters in to writing a document , presenting me with an hour glass, with no apparent reason.

This isn't even on my company laptop where I've had issues with Symphony from the start. On this one it had worked fine in 'beta 4' (R8.0.0).

For some reason even regular alt-tab through applications was acting up, as was clicking on the taskbar icons to switch applications. Instead of activating the intended application it would not restore it to the foreground but would set the taskbar icon to blink.

After about 5 minutes as I was about to click the nsd -kill shortcut on my desktop, it decided to behave in such a way that I could actually save my document.
I ended up finishing my document using Open Office 2.3 which did not misbehave the way Symphony did.
After closing out of the R8.0.1 Standard client (or 'beta 5' as it's called by the regulars in the IRC channel #notes on EFNet), Alt-Tab and clicking on the taskbar icon went back to their normal behaviour.

Things like this make me rather reluctant to advise customers to consider upgrading to Domino R8.x. (the toolbars are still all over the place between client sessoins)

Is this just me or is the R8.x client code base still too unstable for actual deployment?


R8.0.1 Preference 'Feature'

Tags: Lotus Notes 8.0.1 Bug

Ran into a little snag today with the R8.0.1 Standard client, where the Preferences dialog becomes a bit hard to use as you can see below:

A picture named M2

Rebooting Windows appears to have solved this one (for now).

The fact that the toolbars are still moving around between restarts of the client is also a big disappointment for me.
Perhaps we should refer to this relase as 8.0 beta 5 instead?

When this happens, cancel out of the prefs and open prefs again and it should be fine once more (I like this consistency in the client)


Weird error after starting Symphony-Spreadsheet

Tags: Lotus Notes Symphony 8.0.1 Bug

While having the R8.0.1 Notes client open, I launched the built-in spreadsheet program using the shortcut on my desktop, which opened fine, but after about 10 seconds the following  error appeared:
A picture named M2
Pressing "Cancel" would result in this dialog reappearing after a small delay.
Eventually I clicked on "Yes" which lead to this:
A picture named M3

Very usefull indeed.


My first experience with 8.0.1

Tags: Lotus Notes 8.0.1 Bug

Just upgraded my 8.0 client, setup went fine, no errors or warnings of any kind.

First time I ran the client after upgrading I ended up with this:
A picture named M2

And an hour glass that just wouldn't go away.

Only after rebooting did I get the Standard client to run.

After the Notes Setup Complete dialog it still took quite a while before the client started working normally.

After going through some prefs and clicking on Apply I ended up with the following:

A picture named M3

Clicking 'Yes' resulted in the following:
A picture named M4

Clicking Ok led to the previous prompt, this repeats leading to

A picture named M5

Until you select 'No' on the 'Enter Lotus Notes Password' prompt.

These hickups aside, the upgrade fixed the Symphony components to actually launch instead of timing out after a minute or so with a message stating it cannot open a window (or something like that).

With the  8.0 release I never got the Productivity tools to work on the company laptop, initially with an upgrade from 7.0.3 to 8.0, but not even after doing a complete re-install of the client.