Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...CryptographicExceptionCryptographicException
Previous
 
Next
New Post
10/16/2007 5:19 PM
 

I keep having a problem with DNN on my localhost.  I have been having this problem with DNN 4.5.5 and DNN 4.6.2.  After creating the site and getting a successful installation, after working with it for awhile (adding pages, modules, etc), I log off and leave it for awhile, then log in again (as admin), and frequently as soon as the login succeeds I get this:

Server Error in '/DNN462' Application.
--------------------------------------------------------------------------------

Bad Data.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Security.Cryptography.CryptographicException: Bad Data.

After logging in and getting this error, I can generally get into the site successfully by simply eding the url back to the default.aspx.  This is really annoying.  Any ideas?

 
New Post
5/8/2008 2:03 PM
 

I guess I'll have to "bump" my own post from way back when.  No answers to three previous postings on the same problem.

I keep trying to migrate to DNN from Rainbow on my localhost (as a personal web portal).  I ran into this problem before, could never solve it or even get a response from anyone in the community, and the problem is so severe on my localhost as to make DNN useless there. 

It's running on a Win XP machine. 

Any ideas?

 
New Post
5/8/2008 2:41 PM
 

Have you tried clearing your cookies for your localhost? This used to occur back in the day


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
5/8/2008 6:40 PM
 

That sounds like a really good thing to do, however, although I know how to clear cookies from my browser, I haven't a clue how to clear cookies from my localhost.  I opened IIS and looked around for something like this, but nothing came up. 

I went ahead and cleared my browser cookies...  this didn't help.  So how do you clear cookies on localhost?

I did delete all other instances of DNN on the machine (there were quite a number, from all my playing around).

 
New Post
5/9/2008 1:42 PM
 

Chris Hammond, I reviewed the older thread you referenced and found it of interest, though one thing struck me and that is that this problem supposedly happens because of somebody checking "Remember Login", which I almost never do, and can confirm that I have not done with any instance of DNN on my local host.  I have also never run two instances of DNN on the same installation; I've always run each instance independently.  Also, if things are as described with respect to cookie clearing, then surely my having cleared the cookies would stop the problem, but it hasn't.

But I tried an experiment that suggested itself from what was said in that other thread and what I know of the Rainbow portal

I'm running the Rainbow portal (trying to transfer a lot of content from it to DNN), and if I am not incorrect, Rainbow, although a C# product, was apparently ported from an earlier version of DNN (or its predecessor, IBuySpy) and thus may share a similar cookie scheme.  I DO "remember login" with the RB portal.  Since I have not been running DNN without running RB at the same time (while attempting to transfer content), I thought there was an outside chance of interference.  Clutching at straws, I thought, since RB has never barked at me with the cryptographic exception thing.

I made the experiment as follows:  I made sure to log out of Rainbow, then cleared cookies.  I brought up DNN and began throwing a lot of editing at it: adding pages and modules, editing content, just going to town on it.  No cryptographic exceptions whatsoever, and I had never before been able to do so much work without the exception coming up and in pretty short order.  After a while I went ahead and brought up Rainbow and signed in, remembering the login.  I then went back to DNN and tried to edit something I had successfully edited before and WHAM.  First thing right out of the box I got my cryptographic exception.  I then logged out of Rainbow and tried to edit a text/html box, and no problem.  But as soon as I logged into Rainbow I would get the exception in DNN, which would go away once I logged out of Rainbow.  Highly repeatable.  At least with the version of RB that I have been running.

I've done this now enough times that I am dead certain that RB and DNN do not mix on the same machine.  You don't even need to be remembering the login; it happens either way.

So, have I discovered something brand new?  If so, I feel especially privileged, even though it is going to make transferring my content to DNN a bit harder.

 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...CryptographicExceptionCryptographicException


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out