Cannot Activate Blackberry Device to Domino Server.

I recently setup a Blackberry 4.1.3 server which will communicate with a Domino 7.02 server.  Currently there is only one user who will utilize this server.  I was able to successfully configure the Blackberry server, however, in the eventvwr log, I receive the following event id below:
Event Type:      Warning
Event Source:      BlackBerry Messaging Agent Blackberry-INT
Event Category:      None
Event ID:      20000
Date:            4/19/2007
Time:            9:56:38 AM
User:            N/A
Computer:      Blackberry-INT
Description:
{David X/consulting} HandleKeyGenCommand: ignoring KeyGen packet because current transaction is in progress


Event Type:      Error
Event Source:      BlackBerry Messaging Agent Blackberry-INT
Event Category:      None
Event ID:      10570
Date:            4/19/2007
Time:            9:36:47 AM
User:            N/A
Computer:      Blackberry-INT
Description:
*** Activation *** password is empty (UserConfig.KeyGenPassword)

This event is being logged when I generate a password and email the password to the Lotus Notes user mailbox.  The user proceeds to modify the blackberry to include the email address.  Once configured the screen says that it is initializing.  This screen is in place for about 10 minutes until it times out.  
I checked the Domino servers notes log to get a better picture at what is working in the background:
04/19/2007 12:40:47 PM  {David x/consulting} {David x/consulting} *** Activation *** transaction aborted.
04/19/2007 12:40:48 PM  Begin CD to MIME Conversion(Process: Router (00000500:00000005), Database: D:\Lotus\data\mail.box, Note: 00000946)
04/19/2007 12:40:48 PM  End CD to MIME Conversion(Process: Router (00000500:00000005), Database: D:\Lotus\data\mail.box, Note: 00000946)
04/19/2007 12:40:48 PM  Router: Transferred 1 messages to ETP1105.ETP.NA.BLACKBERRY.NET (host ETP1105.ETP.NA.BLACKBERRY.NET) via SMTP
04/19/2007 12:41:04 PM  BES pending count 0, sent 0, queued 0

I removed the option to only allow certain smartphones access.  In addition, I regenerated a new password so the device could connect.  Unfortunately, none of these changes are remedies to my problem.