StrataFrame Forum

Security Exception Error

http://forum.strataframe.net/Topic26920.aspx

By Bill Cunnien - 4/20/2010

I keep getting the following error message when I attempt to access the properties window within the Business Object Mapper. After clearing the error window, the BOM will not close. Can anyone suggest a method of attack on this problem?



Thanks!



=============

SecurityException

Requested registry access is not allowed.



Source : mscorlib



Stack Trace:

at System.ThrowHelper.ThrowSecurityException(ExceptionResource resource)

at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)

at MicroFour.StrataFrame.AddIns.PartialClassBuilderBODialog.ᜀ()

at MicroFour.StrataFrame.AddIns.PartialClassBuilderBODialog.ᜁ()

at MicroFour.StrataFrame.AddIns.PartialClassBuilderBODialog..ctor(Int32 BusinessObjectPK, String BusinessObjectName, DTEprojectsBO ProjectsBO)

at MicroFour.StrataFrame.AddIns.PartialClassBuilderDialog.ᜀ(TreeNode A_0)
By Charles R Hankey - 4/20/2010

I think this is what I was getting when I first started running SF on Windows 7. Try going to the BOM in the Microfour folder in Program Files and setting the properties to Run as Administrator. ( you might be ok just by making sure you run VS as administrator )
By Bill Cunnien - 4/20/2010

(bows)



Right on. Normally, I do start VS in admin mode; however, I did not do that yesterday for some reason. I am good to go.



Thanks a ton, Charles!



Bill
By Dustin Taylor - 4/20/2010

Yep, sounds like visual studio isn't running as a true administrator. If you are running with user account control turned on, you will likely want to start VS by right clicking and selecting "Run As Administrator". The other option would be to work through the access issues by opening up the SF folder and registry permissions, but that will likely take some trial and error depending on where the access is getting blocked.

I typically turn UAC off on my Dev machines, but whether or not that is a good idea is a matter of opinion (loosing some security in the name of convenience.) With UAC on, even an administrator account isn't really an administrator, and can cause some security headaches here and there.

By Dustin Taylor - 4/20/2010

Too late, done been solved.

Just ignore my ramblings Smile

By Bill Cunnien - 4/20/2010

Charles, did you just hear something?



Smile