Content Feed

 Domino  Verse  Traveler 25 May 2016

Known Issues after upgrading to Verse 9.4 for Android and Something That Worked For Me

This evening the following technote was published by IBM:

Overview of known issues affecting users after upgrading to Verse 9.4 for Android

After I upgraded I was having issues syncing. One thing I noticed was that if I went into the main Verse app the prompt to force a new sync would appear, but the sync never finished. Each time I opened the Verse app, I saw the same prompt.

This morning I finally thought about deleting the local data and trying again. After doing this, I was prompted to login to my Traveler server and it performed a full sync and I've been working as expected since.

Hope this helps and sorry for the very long, IBM-like title.

 Connections  DB2 25 May 2016

DB2 HADR configuration reminder

This one is a reminder for me more than anything:

When setting up DB2 HADR, for IBM Connections, IBM Sametime, or anything, don't forget to make sure you've set the logging for the database before trying to configure the standby database.

It's easy to do when you're working with the number of databases that Connections involves and that's what happened here. We somehow skipped over one of them, even though we were using the DB2 directory as a guide. We were trying to start the database as a standby - one of the final steps - and got the SQL1767N error, reason code=1.  This indicates that the database wasn't in a roll-forward pending state which is what we want for setting up the standby.

After looking around I decided to check the log folder on the primary server and found that there weren't any folders for this database in the archive log folder.  So this meant that since the database wasn't configured for logging, it wouldn't be in the state we wanted after a restore.

This was a quick fix of just running the commands we needed to setup the database for logging on the primary side and then taking a new offline backup and restore it on the standby server and run the commands.  Lo and behold - it did what we expected - started as the HADR standby.

I should probably work on scripting this out to avoid this in the future.

Hope this helps someone else!

 Connections  DB2 12 January 2016

IBM Connections dbWizard issue - it’s all about the bits

Started a Connections 5.5 deployment for a customer last week. Things are going well, but when we got to the database Wizard, the wizard wan't cooperating. We couldn't choose the DB2 instance - which normally auto-populated anyway. We basically could bounce back between the Create/Update/Delete menu and the Database type and couldn't move forward.

We were able to create databases manually, but with other deployments coming up we wanted to make sure it was working.

After looking around the systems, I noticed some memory errors and discovered that the 32-bit version of DB2 was installed. Upgrading the version to 64-bit version resolved the dbWizard issue.

Just to be safe - and since we had only populated some test users - we dropped the original databases and created a new set using the Wizard.  

Moving on!

 Lotus Notes  Lotus Notes Domino 17 February 2015

Notes 9.0.1 FP3 IF1 - Updated Support for Google Calendar

Recently, the focus of the Domino community has been on the Interim Fixes and Fix Packs for the Domino server around the POODLE issues.  Yesterday I noticed a TechNote about an Interim Fix and reading through the Fix List for it, I can upon a fix for an issue we had noticed previously with a client.  That is that the federated calendar with Google was throwing an error.  The error was pretty generic, but it was something with authentication.

The Fix List yesterday referenced that they were updating the version of the Google Calendar API.  It appears that the API version that was in use was deprecated back in November 2014.  The new version prompts you to login to Google and accept that Notes will manage your calendar.  If you've used any other 3rd party product with Google, it will look familiar. supports two-factor authentication as you'd expect.

Create the calendar as normal and you'll get a prompt like one above.

Federate away!

Interim Fixes for Notes 9.0.1.x

 Sametime 18 August 2013

Sametime Policy Naming - One character to not use in a name

Working with a client last week, they had reported an issue getting a policy setting from Sametime to apply properly.  The Chat History setting wasn't getting set as expected.

Looking at the issue, we determined that the policy file - policies.user.xml - wasn't getting updated. In fact, it had been a few days since it was updated. Looking at the trace output on the community server, everything looked OK. We could see the policy that was updated on the SSC getting read by the community server, and even see that the setting was what the client wanted. The XML wasn't getting updated.

Looking at it later in the week, I noticed a meeting policy had a date in it and that date coincided with the last date the policy XML file was updated. The date had a slash in it and I thought that was odd. Checking the documentation, it isn't listed as a prohibited characted, but I changed how the date was entered and waited to see if the policy XML file was updated. Lo and behold it was. Checking with a couple of users, they reported that the policy that was set incorrectly was now showing up as expected.

Two takeaways:

  • Do NOT use anything but alphanumerics in the policy name. Stay away from special characters.
  • Don't use dates in the policy name.
It would be good to have a comment field in the policy document that would allow some kind of tracking of changes, but that might need to be retained elsewhere for now. Also, I believe that changing the name of the policy whenever a change is made would potentially cause some issue with updating clients since they have to pick up what is essentially a "new" policy and then apply the "new" settings.

Coming this week - SPNEGO. Fun times ahead!

 Sametime 15 July 2013

Due by Thursday, July 18 - Update your Sametime Proxy certificates

The current set of security certificates used to send push notifications to Apple iOS devices expire this week.  So by the 18th, you'll want to download and install the "fix" for Sametime Proxy server that updates the certs.

See IBM Technote 1641787 for more info including instructions on installing the update.

 Lotus Domino  SNTT 17 January 2013

Installing Domino on Linux - Resolving missing requirements


Recently, I was installing the Domino 9.0 Social Edition on a new CentOS 6 Linux install. It started very smoothly, the CentOS install went very well and the system updates worked flawlessly.  I prepped the notes user and group and was ready to install the Domino code.

Then it came to a screeching stop.

The installer stopped with the message below:

To run this installer you need 32bit (i686) packages installed on your 64 bit Linux Redhat.

They are not installed by default, but are mandatory. The installer will exit after this message.

Notice, I'm installing 64bit Domino on 64bit CentOS and the installer is still a 32bit application. Also, the version numbers mentioned are old and not the latest. Trying to run the yum install for these exact versions failed.  After some searching, I had two options. First, download the RPM from a site and run the rpm installer. Second, I could try to install the most recent version and try that.

I ended up going for the second option after I backed into an install option for the latest version. Basically, leave the version info out and just use the package name and architecture version to find the current version available and install it. For example, below is the command to get te glibc package installed.

yum install -y glibc.i686

Lather, rinse, and repeat for the other packages and I was ready to go. The installer worked fine and Domino is up and running on a test VM.

BTW - For a very good walk through of the process, check out Devin Olson's YouTube videos on installing CentOS 6, Domino and Traveler. Here's the first one on installing CentOS  They're well done - and that's not just cuz I would like a beer!

 Lotus Notes  Lotus Notes Domino 15 January 2013

Location document MailServer field - what not to use

Working with a client recently on some policy setting updates and we ran into an issue where the new policy wasn't taking effect on his client. We made the change to the policy (in this case an Archive policy) and could see that it had been processed and applied to the mail file. Checking the user's Notes client, the link to the Archive was not showing up.  

I opened up the ($Policies) view in the user's local names.nsf to check the policy documents there and noticed that it had been a couple of months since the last update. Something was not right. We cleared the policy docs out of the view and restarted Notes. No policy documents at all were getting pulled down to the client.

This is a remote client and he had emailed me this update. I couldn't work with him immediately, so I asked him to send me the output from Help - Support - Collect Support Data in his Notes client.  This is a very useful tool for pulling out all configuration and diagnostic data from the Notes client (Standard client only, I believe). This grabs the notes.ini, Eclipse related config files, etc and dumps them into a ZIP file in the same folder structure as the client.  Very easy for a person to use and then send the resulting ZIP file.

Looking through the ZIP file I received, I went to the notes.ini to see what might be there. Scrolling through I find the MailServer= entry and an IP address listed instead of the Notes name of the server.  I contact the user and have him open his location document and behold, the IP address.  We change it to the correct name and restart the client.  Now the policies are downloading and the link to the archive is present in his mail file.

Apparently, he had changed the setting during a problem with network routing.  This was a good time to show him how to setup a connection document in case the routing issue ever comes back.

To recap, we discovered:
1 - The Collect Support Data tool in the Notes client is very helpful
2 - IP addresses in certain Location doc fields are not very helpful

27 November 2012

Giving Tuesday - Help cure Cystic Fibrosis

Last week, my son Andrew turned 18.  Andrew was diagnosed with Cystic Fibrosis when he was 4.  CF primarily affects the lungs and pancreas, allowing lung infections to occur and inhibiting weight gain due to lack of enzymes. When he was diagnosed, the average life expectancy for someone with CF was around 21 years of age. Shortly before he was diagnosed, researchers discovered the gene that CF affects and since then have been working to finding a cure.  With the advances and discoveries since that time, currently the average life expectancy is about 37 years, with many CF adults well past that age.

Today, we are closer than ever to finding a cure. A drug released earlier this year resolves the cell defect in about 4% of the CF population.  Another drug that will work for about 80% of CF patients (including Andrew) is slated for Phase III trials early next year.  With these drugs, CF patient lung function and weight gains have been incredible. While not a "cure" it is a significant step in improving the lives of those with CF.

Today was designated "Giving Tuesday" after the Black Friday and Monday shopping days.  I invite you to consider a donation to the CF Foundation, the organization that provides the majority of financial backing to drug manufacturers for CF related drugs. All amounts are welcome and very much appreciated.

8 October 2012

A New Day

After 4 1/2 great years, I have left GBS to start a new chapter in my professional life. My time at GBS (Lotus911 included) was a great time for me professionally and personally, getting to work with an incredible group of talented professionals and making some great friends. However, as someone said, change is good. Now is that time for me.

I have joined the team at Best Methods as of today and will be helping to expand and extend the Collaboration Solutions reach with the team there.  

I hope you'll continue to follow me on this new chapter in my life.