Hi, DavidR:

I had the same problem and was able to correct it.  I don't remember the
exact sequence of steps, as I didn't receive the error until after removing
and re-installing the beta a second time.   Instead of re-installing the
beta, simply try re-activating your software again: While in Outlook, go to
the Help menu, click "About.." >  "Activate" and then click "Convert" on the
pop-up wizard.  

Select the radial button for "Enter Product Key".  You should have received
a trial key in the confirmation screen, and also in an email from Microsoft
after registering and downloading the software.  

After the validation process is done, close everything and reboot your
system, even if you are not prompted to do so.  (I don't remember being
prompted to reboot, but I did it anyway).  Once I booted back up and opened
Outlook (I think there may have been a couple more steps to follow after
opening), I had no more problems.  

Even if you entered your trial key at some point in your original
installation, I would go thru the process of activating the software again.

Something to note:  I got a different key each time I downloaded the
software from Microsoft.  In addition, the second file in my second download
had a different filename from the second file in the first download; I also
received a different key from the first.  I assumed that the filename for the
second file was different because they had simply updated something in the
package.  The first installation was successful, but the second installation
generated the messages you and I received.  In addition, the second key
rendered my trial period as "expired", although it had only been a couple of
days between the installations.  When I re-activated the software according
to the steps above, I used the FIRST key, and have since experienced no
problems.  In my case, it may not have been a conflict in the key itself, but
possibly a problem generated after uninstalling the first installation.  It
is not a clean removal, and any piece of code left in the process could have
caused my problem.

Hope this helps! ~Sarah