Error with 1.2.13

[pbb]

I get the following error when I try to log into EWA since I upgraded gbpvr to 1.2.13. I found that I was running version 74 of EWA so I upgraded to build 76 and I'm still getting this error. I'm using IIS and I've given full control to Everyone to the gbpvr directory (temporarily) and still get the error. Any suggestions?

Security Exception
Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

Exception Details: System.Security.SecurityException: Requested registry access is not allowed.

Source Error:

Line 492: if (!reload && (configWeb != null)) return;
Line 493:
Line 494: Logger.Verbose("RecorderHelperConfig: LoadFromFile()");
Line 495:
Line 496: configWeb = new XmlDocument();


Source File: c:\Program Files\devnz\gbpvr\web\App_Code\classes\Settings.cs Line: 494

Stack Trace:

[SecurityException: Requested registry access is not allowed.]
System.ThrowHelper.ThrowSecurityException(ExceptionResource resource) +48
Microsoft.Win32.RegistryKey.InternalOpenSubKey(String name, RegistryKeyPermissionCheck permissionCheck, Int32 rights) +246
Microsoft.Win32.RegistryKey.OpenSubKey(String name, RegistryKeyPermissionCheck permissionCheck) +35
GBPVR.Public.Logger.LogMessage(Int32 level, String message) +638
GBPVR.Public.Logger.Verbose(String message) +12
gbweb.Settings.LoadFromFile(Boolean reload) in c:\Program Files\devnz\gbpvr\web\App_Code\classes\Settings.cs:494
gbweb.Settings.GetSetting(Object moduleObject, String settingName) in c:\Program Files\devnz\gbpvr\web\App_Code\classes\Settings.cs:443
gbweb.Settings.Load() in c:\Program Files\devnz\gbpvr\web\App_Code\classes\Settings.cs:149
gbweb.Settings..ctor() in c:\Program Files\devnz\gbpvr\web\App_Code\classes\Settings.cs:141
gbweb.Global..cctor() in c:\Program Files\devnz\gbpvr\web\App_Code\Global.asax.cs:40

[jksmurf]

Whew, glad I'm not the only one...

k.

[BrainStormer]

Did you remember to go to services and check "Allow to interact with desktop" on the recording service?

[pbb]

This wasn't checked for the previous version and it worked ok. Is this something that has changed?

[jksmurf]

Did you remember to go to services and check "Allow to interact with desktop" on the recording service?

Argghhhh... Good pickup.

k.

[UncleJohnsBand]

EWA reads its settings and saved searches from the gbpvr\ directory (not the gbpvr\web directory) so you need to give IIS access (read/write) to that directory as well.

[pbb]

I did that. Is this code on line 494 in Settings.cs :

Logger.Verbose("RecorderHelperConfig: LoadFromFile()");

trying to write to the Windows event log?

[UncleJohnsBand]

I did that. Is this code on line 494 in Settings.cs :
trying to write to the Windows event log?

No....I don't think so....Logger would be witting to the log file in one of the sub directories found under here (the gbpvrpublic.dll will be in the sub directory that contains the logs)

Code:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\gbpvr\66372bc5\b1db62aa\assembly\dl3

[UncleJohnsBand]

I should note that this build (76) has very, very minor changes only at the page level so any issues that you may be experiencing are most likley not related to the new EWA version but environment changes with the GBPVR upgrade itself.

I stay away from IIS for running EWA....just think it is bloat to run the app...sometimes simple is better and the built in server for EWA provides plenty of performance....and it can run alongside IIS without issue.

[pbb]

Thanks for the info. I'll look into the writes on the temporary directory you mentioned. I've seen issues like that before with ASP.NET.