I just decided to install (as a completely separate web application, with it's own completely separate database) another instance of DotNetNuke 4.4.1 on my server today.  It appears as if it can not run concurrently with the other one for some reason and gives me the following error in one or the other (depending on which one loaded first after an application pool reset):

I attempted separating them into their own application pools with the same effect.  Ideas?

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:

[CryptographicException: Bad Data.
]
   System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr) +33
   System.Security.Cryptography.Utils._DecryptData(SafeKeyHandle hKey, Byte[] data, Int32 ib, Int32 cb, Byte[]& outputBuffer, Int32 outputOffset, PaddingMode PaddingMode, Boolean fDone) +0
   System.Security.Cryptography.CryptoAPITransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount) +319
   System.Security.Cryptography.CryptoStream.FlushFinalBlock() +30
   System.Web.Configuration.MachineKeySection.EncryptOrDecryptData(Boolean fEncrypt, Byte[] buf, Byte[] modifier, Int32 start, Int32 length, Boolean useValidationSymAlgo) +154
   System.Web.Security.FormsAuthentication.Decrypt(String encryptedTicket) +247
   DotNetNuke.HttpModules.DNNMembershipModule.OnAuthenticateRequest(Object s, EventArgs e) +515
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210

DOH!  Makes perfect sense... I'll change my web config on the production version. -- I assume changing the forms authentication name will suffice?

Thanks!

Yeah, virtual folders;

One of them is as a "staging" environment (which I've had running for several months now); the other will be the "production" environment and eventually will be mapped to it's own host header so this issue would go away on it's own, but in the meantime I have to keep them both in the same context.

Thanks again