Windows shortcut in the START bar didn’t work any more, had to be deleted an re-created.
The new installation put me to the FIRST location I had in my personal NAB (which unluckily was “Island”) and did not keep the last location I was in.
picked a wrong desktop.ndk file with multiple Notes versions installed
You should definitely check your Notes.ini before starting the newly-updated Notes 6.0.1 for any wrong path and location entries.
Well, that all is nothing you can’t solve easily yourself, this may just save you time while wondering what’s going on.
Yes, yes, I know Lotus recommends not to have multiple versions of ND6 and R5 on one machine, but lots of people need to, supporting different platforms and not running to buy a new machine with every release…
Have You set Your domino server to run as a service? And it is not allowed to interact with desktop?
Well, before trying to start the service again after an upgrade - run the dominoserver with the standard console instead!! Or You will end up with a service that try to start and try to start and … forever… that is because there is a question during the startup saying something like “Do You want to upgrade Your NAB?” and it is waiting for a Y/N answer. If You don’t have the console You can’t answer and the service wont start fully.
Since I also had my service to start automatically when Windows starts… guess what happened.
If You do this - there is only one thing to do:
Go to the registry and change the service startup value for the server from automatic (2) to manual (3). Then reboot windows and launch the console.
Oh - the registry key? It is:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Lotus Domino Server (LotusR6DominoData) and the subkey Start should be set to 3. It is a DWORD value.
use the SERVICES control panel applet to do this, don’t hack the registry
an INI setting to automatically answer this question would be nice so we don’t have to keep doing it ourselves, it’s not like you’d answer yes to this question except on one server
Nothing to add, just laughing at your post - I had EXACTLY the same problem as this, four days ago. Drove me loopy for about 30 minutes, wondering why the server wasn’t coming up, or closing “in a timely manner” (thanks MS).
Great list of gotchas… what gets me is on a 6.0.0 only machine, the shortcuts (in the quickstart toolbar, for example) are also blown away. Yes, it’s easy to drag/drop new ones, but why is Windows Installer searching out old shortcuts and whacking them? Since it found them, it could just as well update them (which doesn’t mean anything, since the path is still correct).
