Smart upgrade AllClient issue

I've been having an issue with smart upgrades with my secondary desktop. When I manually force the client to check for smart upgrade kits, it always came back saying:


There are no updates available for your notes client release 8.5.2FP1. There were no matching kits found in the smart upgrade database smartupgradedb.nsf on server1/org

I checked the InstallType and it was 2, checked the upgrade kit and it was set to Allclient. I get the notification on my main pc so I know it's not a rights issue. I checked the smartupgrade.log on my client:




TM=SUGetSmartUpgradeKitsInfo: SUSearchDownloadDBForKits: 'CN=server1/O=org!!smartupgradedb.nsf' '$activekits' error: There were no matching kits found in the Smart Upgrade database %s on %a.
..

TM=Error accessing Smart Upgrade database server1/org smartupgradedb.nsf

TM=SUSmartUpgrade: SUGetSmartUpgradeKitsInfo: error: There were no matching kits found in the Smart Upgrade database %s on %a.

...


IN=ErrorMessage IV=There are no updates available for your Notes client Release 8.5.2FP1. There were no matching kits found in the Smart Upgrade database smartupgradedb.nsf on server1/org.

...

Nothing really apparent in there. Then I opened my smart upgrade tracking database on my home server. Looked at my secondary pc failed attempts and found type:

Type: All Client (Notes Client, Admin Client, Designer) Basic Configuration

where my main desktop has a type of:

Type: All Client (Notes Client, Admin Client, Designer)


Ah ha! So for some reason my Lotus Notes AllClient is registering as a basic configuration install! This might be something residual from when I loaded the full AllClient basic configuration on 8.0.2 but that was years ago. So I installed 8.0.2 Allclient basic on a test machine, saved the notes.ini, uninstalled, installed 8.0.2 Allclient Standard and saved the notes.ini. Using ultraedit, I compared the two files and the only significant difference between the two notes.ini's was a parameter called "InstallMode". After some Google searching around I found the ini parameter but no description. The Allclient standard install set InstallMode=1. The Allclient basic set InstallMode=0.

On my secondary desktop I could not find the InstallMode parameter in my notes.ini. So I added InstallMode=1. Once I added InstallMode=1, smartupgrade found the upgrade kit with no issues.

Issues with Windows server 2008 and Lotus Domino java controller service

A special thanks to Pontus Wennergren for posting the following:

Your solution works very well since I had a similar problem. The service just refused to start but application worked fine.

But I prefer to make changes in notes.ini instead of the hosts file and when I found this:

http://www-10.lotus.com/ldd/nd85forum.nsf/5f27803bba85d8e285256bf10054620d/623744895c016a63852577310025230d?OpenDocument

and tried it, it worked just aswell so I am sticking to
TCPIP_ControllerTcpIpAddress=





Below is my original post for those that are interested:

Recently I've had an issue with a Lotus Domino 8.5.1 FP1 server running on Windows Server 2008. The service is setup to run

"d:\lotus\domino\nservice.exe "=d:\lotus\domino\notes.ini" "-jc" "-c"

However when I try to start the service I get this error:

The Lotus Domino Server (DlotusDominoData) service on local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

No matter what I do I cannot get the server to launch under the service! I can launch the server under my remote desktop session but then I can't log off.

So looking at the d:\lotus\domino\data\dcontroller.ini file I found this entry:

Host_Name=traveler01.theozzyblogger.com

and I decided to ping this address on the same server. When I did that I received the IP6 address! So as a troubleshooting measure I input the IP4 IP and server name in the hosts file ( c:\windows\system32\drivers\etc\hosts ) and the service starts with no issues! I ended up un-checking IP6 and removed my hosts entry and that worked too. It turns out when I un check the IP6 it uses loop back address of

::1:

So I had to put the hosts entry back in to make it work... I think I will call IBM on this one. I will update with what I find.

The strange thing is this has worked all along and just recently became an issue. I wonder if a Windows update is to blame...