Jump to content


CryptographicException error on logout


  • Please log in to reply
2 replies to this topic

#1 Guest_Jeffrey_*

Guest_Jeffrey_*
  • Guests

Posted 03 March 2009 - 08:35 PM

To all,

Recently, we've migrated a web application using .NET 1.1 to a .NET 3.5 environment. I began creating a new set of simple tests to check performance--the test simply logs a user into a site, loads an item into view, clicks several tabs, and then logs out. Upon playback, nearly invariably, i'm getting the following error on the logout page...

Server Error in '/' 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.


Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[CryptographicException: Bad Data.
]

Does someone know how I could have WAPT ignore this error? My users are all successfully logged out of our site, but because of this exception, i'm unable to tell an otherwise good test result from a bad one without inspecting all errors within the log.

Thanks in advance.

Jeff

#2 Guest_angela_*

Guest_angela_*
  • Guests

Posted 04 March 2009 - 12:52 PM


Hello Jeff,

This problem is much spoken about on the Internet. Most probably, it is connected with upgrade of .NET. Please search for corresponding discussions, there should be some pieces of advice regarding elimination of this issue there.



#3 Guest_Jeffrey_*

Guest_Jeffrey_*
  • Guests

Posted 18 March 2009 - 08:32 PM

QUOTE (angela @ Mar 4 2009, 06:52 AM) <{POST_SNAPBACK}>
Hello Jeff,

This problem is much spoken about on the Internet. Most probably, it is connected with upgrade of .NET. Please search for corresponding discussions, there should be some pieces of advice regarding elimination of this issue there.


Thanks Angela, I will take a look.

Jeff




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users