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

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.

School Project Update - Solved by Chris Toohey

My posting the other day lead me to talk to Chris Toohey on Sametime about this and he said he did it already!

I had thought of some more ideas but was wondering from the start how I could produce a Personal NAB and get it to sync to so many devices.

WAP!

I should have guessed, so much for my memory and no, WAP is not dead, just forgotten in this case by me.

Sure enough he has the page defined and pretty straightforward.
Given the holiday I may not get to it until after, but it's great to know someone out there did a similar project and I can get some guidance.

Oh and if you haven't used it yet, take a look at his Showtime app for pushing icons to Blackberry.

Thanks Chris!

R8 Addressing, You Worked Where?

As some of you know, Lotus Notes R8 is all about you/me... the user.
Make life better. And it does, it is and Outlook clients want to see it in action.

Now a part which I like is you can now retain email addresses from every email you send or receive in a sort of indexed view. So the email you deleted, you might find the person's email address still there. Thank the Lotus God.

On the other hand you may find yourself amazed at the email addresses you have in your history. I have about 15 that come up now. Cool, but weird since some are 12 years old.

Some users may find this odd that 6 years after the Lotus/IBM merger for instance, you can still come up as joe bloggs/sta/lotus as well as joe bloggs/sta/ibm.

The answer my friend is delving in deeper and you will need to wait for 801 to resolve this in a simpler manner.

In Notes 8, a view is created in the Personal Address Book (names.nsf) which stores up to 2000 contacts to which mail has been addressed. When you address a memo, the client will automatically provide entries from this view which correspond to the text being entered.

But if this is an issue for you or your client and they just can not be bothered to check who they are emailing, then you need to follow this tech note I have copied the text for those unable to link to the file:

The contents of the Recent Contacts view can be reset by shutting down the Notes client, and moving or deleting the contents of the directory,\workspace\.metadata\.plugins\com.ibm.notes.dip\...

where is the path to your Notes Data directory, such as C:\Program Files\IBM\Lotus\Notes\Data.

Note: The previous contents of the Recent Contacts view may still display until a new message is sent, which populates an entry in the Recent Contacts view and causes the dipTable.ser file in the com.ibm.notes.dip directory to be re-created.

In the end, moving ahead brings about more possibilities than previously known or thought of, so it is here too.

I look forward to where the 801 and later versions take us for the contacts/pnab/pnames.nsf/personal address book which so rarely gets a 2nd look by so many in the industry.