We've been getting these errors from time to time on our test environment...
AssemblyVersion: 04.03.06
PortalID: 0
PortalName: xxxxxx
UserID: -1
UserName:
ActiveTabID: 84
ActiveTabName: xxxxxxx
RawURL: /Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04320; InfoPath.2)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: e1ee3f2a-93f8-47f0-9eee-31a1d71e51e6
InnerException: Unhandled Error:
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException
StackTrace:
Message: System.Exception: Unhandled Error: ---> System.Security.Cryptography.CryptographicException: Bad Data. at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr) at System.Security.Cryptography.Utils._DecryptData(SafeKeyHandle hKey, Byte[] data, Int32 ib, Int32 cb, Byte[]& outputBuffer, Int32 outputOffset, PaddingMode PaddingMode, Boolean fDone) at System.Security.Cryptography.CryptoAPITransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount) at System.Security.Cryptography.CryptoStream.FlushFinalBlock() at System.Web.Configuration.MachineKeySection.EncryptOrDecryptData(Boolean fEncrypt, Byte[] buf, Byte[] modifier, Int32 start, Int32 length, Boolean useValidationSymAlgo) at System.Web.Security.FormsAuthentication.Decrypt(String encryptedTicket) at DotNetNuke.HttpModules.DNNMembershipModule.OnAuthenticateRequest(Object s, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---
Source:
Server Name: xxxxxxx
It occurs on both DNN 3.2.2 and 4.3.6. Has anyone seen this before? It hasn't happened on our production environment, but we're looking to do our 4.3.6 Upgrade in a few days and if this is an issue with 4.3.6 specifically, I want to know so I can wait until I can fix it. I get the feeling it's limited to our test environments, since both versions of DNN have triggered errors on those web addresses, but not the production. Still, has anyone seen these?