am I the only one having this issue in the current stable release? I read in Gemini where this was a known issue in an earlier release and was "Verified Fixed" in this release? I have three clean 05.04.02(66) installs and every one of them still has this issue. Here is the event log off the most recent and defining crash for me:

ModuleId: -1
ModuleDefId: -1
FriendlyName: User Registration
ModuleControlSource: DesktopModules/Admin/Security/ManageUsers.ascx
AssemblyVersion: 5.4.2
PortalID: 0
PortalName: PacoWang
UserID: -1
UserName:
ActiveTabID: 39
ActiveTabName: Home
RawURL: /Register.aspx?ReturnUrl=http%3a%2f%2fwww.pacowang.com%2fHome.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.pacowang.com/Register.aspx?ReturnUrl=http%3a%2f%2fwww.pacowang.com%2fHome.aspx
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.70 Safari/533.4
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: f6c812c2-3346-409d-aefc-7e74e89a923a
InnerException: Mailbox unavailable. The server response was: <vertical_snaproll@yahoo.com> No such user here
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Net.Mail.SmtpTransport.SendMail
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Mailbox unavailable. The server response was: <vertical_snaproll@yahoo.com> No such user here ---> System.Net.Mail.SmtpFailedRecipientException: Mailbox unavailable. The server response was: <vertical_snaproll@yahoo.com> No such user here at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception) at System.Net.Mail.SmtpClient.Send(MailMessage message) at DotNetNuke.Services.Mail.Mail.SendEmail(String fromAddress, String senderAddress, String toAddress, String subject, String body) at DotNetNuke.Services.Mail.Mail.SendMail(UserInfo user, MessageType msgType, PortalSettings settings) at DotNetNuke.Entities.Modules.UserModuleBase.CompleteUserCreation(UserCreateStatus createStatus, UserInfo newUser, Boolean notify, Boolean register) at DotNetNuke.Modules.Admin.Users.ManageUsers.UserCreateCompleted(Object sender, UserCreatedEventArgs e) --- End of inner exception stack trace ---

My question is, since I saw three sign-offs on this issue in Gemini as Verified fixed then why do I have three brand new sites that are not going along with that assertion? I seriously doubt anyone answers this but I have been trying to find a fix for this for the last 12 hours. Unfortunately I found this out on a very large production site I rolled out yesterday. And the client is not very happy

Is there anyone out there that can truthfully point me to the last stable release that DOES NOT HAVE THIS ISSUE? Because my @$$ is in a sling because the fix aint fixed!!!!!!!!!!!!!!

I believe this could be the same issue as that discussed at:
www.dotnetnuke.com/Community/Forums/tabid/795/forumid/118/postid/369620/scope/posts/Default.aspx

Search for 369620 to find others with the same issue.

No answer from anyone that I can find yet. I tried to add a comment or link to a separate but potentially related issue in Gemini without success.

---

- John
www.VashonSoftware.com

Actually I started seeing this issue two days ago and my Hosting company sent that thread to me when I was talking to them. I blindly ignored it thinking it was just a rogue instance since I was so close to deploying. After that I started eyeing them as the potential problem. I have been putting DNN out there for large and small companies for many years and found it to be mostly stable and reliable. I have sold this package to some pretty large clients.

After the culmination of last night's melt down and seeing this issue around for a while now after researching it I am immediately ceasing any more DNN production sights until I am satisfied this issue is fixed. And honestly how in the hell will I know it is fixed since it was fixed and it's not fixed.

I have been on a rant for most of the night and morning but I have to ask what is going on here. I too am no pro with Gemini but after exhausting all avenues of finding a fix for this and all the unanswered posts I am at a loss.

I see it was supposedly fixed with this release, And I consistently see posts as far back as 2008 & 2009 about this but no responses from DNN Core members (that I can find). If you guys can't or won't respond it would be nice if you just said so. But maybe you are since you aren't saying anything. There's a thought

It is difficult to believe that with all ( I am assuming here) the current DNN 05.04.02(66) sites out there, there are not more posts about this. If I am wrong I will publicly apologize but show me and hurry up about it. I feel after this round of losses as if my faithful old wife was caught cheating. I have zero confidence in deploying this any more. How can anyone sell a platform to someone knowing there is a great possibilty they will be called up from a client and put on the carpet for this and they will have no answers to give.

I have to go sift through the ashes of these burnt to the ground sites and come up with a new plan to salvage it. It is easy to tell why no one has an answer. I hope for the sake of our (DotNetNuke Team) relationship that you boys step up and lets get some dialogue going on this and quick. I would not call this error a "Show Stopper" I would call it "Nuked" no pun intended.

Maybe it's time to start dating Joomla a little more seriously. Until now I have had way to much invested in DNN. Should'nt have put all my eggs in one basket. Live and learn.