Thursday, October 17, 2013

SnTT - Replication is NOT Disabled, But it says it is

Show and tell thursday, lotus, replication, keith_brooks
Did you ever wonder about what makes some changes more difficult than others? Why do people fear the upgrade? What paralyzes them from taking action? Usually it is because they got burned one time.

One day I decided to load Windows8 on an existing Windows7 machine to play with it and test IBM Notes and other apps. The upgrade went fine, but some things were not compatible with Windows8. In time I downloaded patches and updates and resolved messy security errors.

One of the errors was on IBM Notes and seemed to be the software firewall. resolved, started Notes and it replicated. Great. An hour later when I realized I had not gotten some emails i expected I checked replication and it had not replicated since logon. I asked it to replicate and it did.

An hour later, same thing. After looking at everything I saw the information on the bottom of the screen that says "Replication is disabled". It most certainly was not. I then proceeded to do the following, from my own past blog post, and this one, before calling IBM, with the same outcomes:
Disabling replication and then restarting it. - "Replication is disabled"
Tried restarting Notes - "Replication is disabled"
Change location to a different account - "Replication is disabled"
Login as a different user entirely - "Replication is disabled"
Check log on server and client and only saw - "Replication is disabled" or replication I forced
Tried IMAP - "Replication is disabled"
Domino 8.5.x server - "Replication is disabled"
Domino 9.0 server - "Replication is disabled"
Replaced design of template of PNAB from local - "Replication is disabled"
Replaced design of template of PNAB from server - "Replication is disabled"
Changed template of PNAB to a different template, then replaced it back as PNAB - "Replication is disabled"
Created a brand new PNAB with nothing but one server details in it - "Replication is disabled"

I began to wonder if I was missing some patch for Windows8 so I called IBM Support with a PMR.

I worked with Kristin T. who was great about working around my schedule and provided a number of areas to look at to see what else might be going on. Unfortunately she did not have a Windows8 machine at the time to play with so we both kind of flew blind.

In the end, it was not a Windows8 issue. The problem may have been caused by a rogue policy from one of my location documents that for some reason decided to kick in only after I loaded Windows8.

In order to see the policies and clear them if necessary, do the following:

  1. Open your personal address book (names.nsf on your client)
  2. Go to the Location document
  3. Press the CTRL and SHIFT keys at the same time then 
  4. Click on View -> Go To-> and find ($Policies)
  5. Click Ok

You will see your policies. If anything looks wrong or just want a blank list, delete it and then restart Notes.
A fresh set of policies will come down to you.

Only after we cleared the system policies and created a clean PNAB and then added one location and connection details back we were able to get replication rolling again.

Moral of the story is, you may know what you are doing, but the order of the troubleshooting could be holding you up from completing your task.

No comments:

Post a Comment