I upgraded to 8.0.2 standard yesterday. I have Sametime set to use Domino Single-logon and automatically login.
Two issues:
(1) When I start Notes I get a pop-up of my buddy list and in the status bar the following message appears “You cannot use IBM Workplace instant messaging because Notes is already logged into the IBM Sametime server.” Workplace? And when people IM me, their messages pop up in the basic IM window, not the
new version of the Sametime client. This has changed from 8.0.1. Yes, I do see Sametime logged in in the sidebar and I can use it.
(2) This problem has been an issue since 8.0. When I log into Lotus Notes using the Offline (aka Island)location, it tries to connect to Sametime and gives me a Sametime login error: “Missing Password”. Well, I am offline, so why is it trying to login anyway? The pre 8.0 clients and the 8.x basic clients don’t do this annoying thing.
P.S. You need to add 8.0.2 to this forums Release field
P.P.S. Performance is amazingly improved BTW and I am otherwise thrilled with this release.
I got this too but resolved it by editing my location document and removing my sametime server from it.
I did a clean install (after hitting a couple of hurdles) and you are prompted for your Sametime server as per a basic client config. You then can log in to Sametime via the integrated client in the right hand side.
I presume there are two locations for configuring Sametime, one as per a basic client and one using Eclipse.
Just a hunch but any one shine some light on this, same goes for having to configure Notes to use IE other external browser in the location document and the main preferences of the client.
Everyone here agrees the performance is widly improved!!
Subject: Created new Offline Location document -no change
Ben,
Indeed, peeking into the fields of my Offline/Island Location document, I found I had the Sametime server field populated…was populated by a server policy. However, I created a new location documnet leaving it blank and I am having the same issue.
I then added my Sametime server to my location document and would expect for the additional ST client to appear, it did not. My colleagues have seen this too but there doesn’t seem to be a pattern we can tie it down too.
Try changing the Connect value on the Instant Messaging tab of the Location doc. We noticed this tab isn’t visible anymore if you edit thru the Perferences dialog, but is stil visible if you go thru Contacts > Advanced > Locations
Subject: Policy Settings Lock Sametime Server Field
We use Policies extensively to ease user setup and maintain consistency in the domain. We populate the Sametime field via a policy therefore its not an editable field.
That worked for a couple of my colleagues, good spot. Although I managed to stop the secondary Sametime client appearing by removing the Sametime server name by navigating via the preferences in my client.
I then added the server back into the “IBM lotus sametime server” field, restarted the client and still the secondary window doesn’t appear. This seems to go against our suggestions, entries in my notes.ini are below although I do not get the secondar “floating” window.
We’re having the same issue in our company. About 5 of us upgraded from 8.0.1 to 8.0.2 standard, and now when we’re sent a ST message, the old floating ST window appears. Initiating a chat uses the new integrated chat window. I’ve done the location doc and .ini suggestions with no luck. Very frustrating. Come on IBM!
Taking a tip from a blog (posted below), I have resolved the problem of the old Sametime client popping up.
I still have a problem with Sametime trying to connect when I use an Offline Location document. It pops up a missing password diaglog. It only happens in the standard client. My Sametime login is as follows:
Subject: Sametime Login Prompt when Offline fixed in 8.0.2 CCH2
The problem with 8.0, 8.0.1, and 8.0.2 with the Sametime “Missing Password” dialog popping up in an SSO environment using the Standard Client started using an Offline location has been fixed in 8.0.2 CCH2. That was a long sentence.
I have 4 users currently testing 8.0.2, and 2 of them are experiencing this same problem, the other two aren’t. All have the Sametime server in the location document.