Anyone I am getting the following exception by the hundreds followed by the failure statement. Is this me, or is there a bug.

Messaging seems to be functioning fine, but something is a miss here. Thanks for any ideas or help in advance.

AssemblyVersion: 7.0.6

PortalID: -1

PortalName:

UserID: -1

UserName:

ActiveTabID: -1

ActiveTabName:

RawURL:

AbsoluteURL:

AbsoluteURLReferrer:

UserAgent:

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID: 80d672be-71f1-49ab-9884-8e76e9695342

InnerException: Object reference not set to an instance of an object.

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: DotNetNuke.Services.Social.Messaging.Scheduler.CoreMessagingScheduler.SendMessage

StackTrace:

Message: System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Services.Social.Messaging.Scheduler.CoreMessagingScheduler.SendMessage(MessageRecipient messageRecipient) at DotNetNuke.Services.Social.Messaging.Scheduler.CoreMessagingScheduler.DoWork()

Source:

Server Name: WEB30

Thanks for the reply.

 It seems I have found the problem and it is connected to using a number first in the username.(IE 1TestUser). I have removed all accounts with a user name starting with a number and the exceptions and the failures have stopped. I don't remember any restriction on the first character in the user name but I may have missed it. There were only two user names that had numbers so it was not much of a fix. If this is a bug someone ought to check in to it.