Hello Everyone;

I upgraded two DNN sites (10 total) from 4.5.5 to 4.6.2.  Everything seems to be running just fine, so far.

• Shared hosting sites through CrystalTech
• Used upgrade package
• No issues during upgrade process; worked like clockwork
• Minimal modules installed

One small issue.  In the Event Viewer, I no longer get the IP address captured for varioius events, such as "Login Success."    In the snapshot below, you'll note a login success two days ago with the IP address (username, portal, and IP address changed for public consumption).  Today a login occurs after upgrading to 4.6.2 and the IP address no longer appears.

I have done the following actions:

• re-reviewed the web.config file to ensure all changes were properly made
• cleared the Event Log through the Event Viewer command "Clear Log"
• use the SQL truncate command to clean out the Event Log:  TRUNCATE TABLE {databaseOwner}{objectQualifier}EventLog
• re-started the application a few times through Host Settings

No matter, the IP address is no longer being captured.

Anyone have ideas?

With no disrespect to you as you are considered the most valuable DNN contributor, I'd like to ask you to step back and consider why I posted this on the forum first. 

Please read through NukeAlex's responses (the support overseerer/traffic cop) to people who "first" go to the support.dotnetnuke.com (Gemini) and post problems. Often he tells people to post at the forum to see if anyone else has this problem.  That's exactly what I'm doing.   What you're suggesting for me to do is counter to his directions.  Let's be consistent.

If you're experiencing this problem, then help me by stating that you have the same issue.  I'm not going to waste the Core Team's valuable time and effort if they don't see it as a problem even though I personally may see a problem.

Thank you for all you do.  If there's a DNN Hall of Fame, I would nominate you for your invaluable help.

Regards,

  Jud

Thank you.

It's posted here: http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=6423

I bet the team, based on my last experience, will come back with one of the following:

1. Can't re-produce the error
2. Not an issue to the Core Team, won't fix
3. It was an issue, now it's fixed in the next forthcoming release, but we won't admit there was a problem in the first place (big grin)

Cheers.