ST-SnTT - Sametime 8.0.1 DWA Upgrade gotcha

So you, thought you, might like to... go to the show....then your client IM's you.
If not for my traveling clients I would have a quiet existence.
They really push the boundaries of what works ....or doesn't in one's environment.

The Sametime contact list in DWA/iNotes which we recently upgraded to Sametime 8.0.1 and Domino 8.0.2 is throwing a 404 error.

Wait I think I have seen that, yet a review of my blog says maybe. I see that the links in that post have been updated and you will see they discuss the BES update, which I brought to light originally as well that started some of the problems.

In any event, this time, the problem was found to be an entry in the servlets.properties file, found under the Domino\data directory.

This line is necessary:
servlet.DWABuddyList.code=com.lotus.dwa.stbuddy.DWABuddyList

NOTE: If you are using reverse proxy servers in your environment, you may need to add the following line with the fully qualified domain name or IP address of the Sametime server in the servlet.properties file:

servlet.DWABuddyList.initArgs=stserver=sametime.company.com

Then tell HTTP quit and the load HTTP.

Why not tell http restart? On Sametime servers the server does not wait long enough in some cases for all the Sametime threads to close appropriately leading to other errors. Thus I prefer a full stop and start of HTTP.

To troubleshoot this deeper, please review IBM technote #1317895

DWA 801 and ST8, errors 404 and 500 Resolved

This is one interesting piece of a puzzle and hopefully some one out there knows what happenned to my clients server that caused this.

As I know someone out there meets these odds and ends(not just me), I felt I should let everyone get the quick scoop.

This is what started it all, the 404 error.

This led to the status 500 error. Go here to get the file you need to make this work after you get the popup.

Eventually you need this one

The problem seemed to stem from incorrect IP addresses and/or qualified host names.
In tracing all locations of references for IP and/or name(server configuration docs, server docs, internet web docs, stconfig.nsf, sametime.ini, servlets.properties plus a few more pieces) it became obvious I had one mistake on tunneling ports. Added the trusted IP address to the communtiy connectivity section and restarted and all suddenly is fine.

What broke it? I have no idea, it was working fine for over a week since updating it.
I also note the backupexec software now has error messages.
Could there have been a Microsoft update that created this landslide? I have no idea yet.
But I will find out why we must add in a piece of BETA code from R8 beta 3 to make this work.

Federal Desktop Core Configuration (FDCC) and Lotus

Sales guys, more details if you sell to governments.
Stop the FUD, let them know we are approved!

Technote is here

Federal Desktop Core Configuration (FDCC) on Windows® XP and Vista is a mandate issued by the U.S. Federal Government. The most current versions (and future versions) of IBM® software products that are deployed by U.S. government agencies need to be able to install and run on Windows XP Professional and Windows Vista Enterprise with FDCC settings.

Lotus Notes

The following Notes® Basic and Notes Standard clients are supported in the FDCC Desktop Configuration on Windows XP:

Install by Administrators only.

Lotus Notes® 6.5.3 (and later)
Lotus Notes 7.0.3 (and later)
Lotus Notes Basic 8.0.1 (and later)
Lotus Notes Standard 8.0.1 (and later)

Lotus Domino Web Access
Lotus Domino Web Access was tested and will be supported on the latest Maintenance Releases of the server: 6.5.6, 7.0.3, 8.0.1

Lotus Sametime
Sametime® supports FDCC in both 7.5.1 CF1 and 8.0.

Logically, the list below is not approved one would imagine for average desktops.
The following is not supported in the FDCC Desktop Configuration*:
Install by Standard User
Nomad (USB device support)
Lotus Domino® Designer
Lotus Domino Administrator