Requested registry access is not allowed.

Add-in Express™ Support Service
That's what is more important than anything else

Requested registry access is not allowed.
 
Sean Ram




Posts: 27
Joined: 2013-03-13
Hi,

One of our customer when running the add-in express addin is getting the following error. "Requested registry access is not allowed."

Please note it is not a problem for majority of our customers, it is just in this one installation we are seeing this issue. In fact, it happens only once in a while even for this customer.

I have attached the detailed logs below.

The exception seems to be thrown from

AddinExpress.Projects.Common.ADXRegistry.OpenKey(name As String, writable As Boolean)
mscorlib.dll: N 0192 (0xC0) IL

Is there a solution for the above?


Detailed technical information follows:
---
(Inner Exception)
Date and Time: 1/8/2019 2:50:55 PM
Machine Name: xxxxx
IP Address: xxxxxxxxxxxxxxx
Current User: xxx\YYYY

Application Domain: C:\Program Files (x86)\xxx\
Assembly Codebase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
Assembly Full Name: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Assembly Version: 4.0.0.0

Exception Source: mscorlib
Exception Type: System.Security.SecurityException
Exception Message: Requested registry access is not allowed.
Exception Target Site: ThrowSecurityException

---- Stack Trace ----
System.ThrowHelper.ThrowSecurityException(resource As ExceptionResource)
mscorlib.dll: N 0016 (0x10) IL
Microsoft.Win32.RegistryKey.OpenSubKey(name As String, writable As Boolean)
mscorlib.dll: N 0000 (0x0) IL
AddinExpress.Projects.Common.ADXRegistry.OpenKey(name As String, writable As Boolean)
mscorlib.dll: N 0192 (0xC0) IL



(Outer Exception)
Date and Time: 1/8/2019 2:50:55 PM
Machine Name: xxxxx
IP Address: xxxxxxxxxxxxxxxxxx
Current User: xxx\YYYY

Application Domain: C:\Program Files (x86)\xxx\
Assembly Codebase: file:///C:/Program Files (x86)/xxx/AddinExpress.MSO.2005.DLL
Assembly Full Name: AddinExpress.MSO.2005, Version=9.1.4620.0, Culture=neutral, PublicKeyToken=4416dd98f0861965
Assembly Version: 9.1.4620.0

Exception Source: AddinExpress.MSO.2005
Exception Type: System.Exception
Exception Message: OpenKey failed.
Exception Target Site: OpenKey

---- Stack Trace ----
AddinExpress.Projects.Common.ADXRegistry.OpenKey(name As String, writable As Boolean)
AddinExpress.MSO.2005.DLL: N 0292 (0x124) IL
AddinExpress.MSO.ADXAddinModule.AddinExpress.MSO.IDTExtensibility2.OnStartupComplete(custom As Array&)
AddinExpress.MSO.2005.DLL: N 1434 (0x59A) IL
Posted 11 Jan, 2019 17:12:13 Top
Andrei Smolin


Add-in Express team


Posts: 18817
Joined: 2006-05-11
Hello Sean,

Is your add-in per-user or per-machine? Did you ever change this setting?

Please reinstall your add-in, start the host application and, while the error message is shown, please get copies of these files and send them to the support email address (or post them here):

- %temp%\{AssemblyProduct attribute; see AssemblyInfo}\adxregistrator.log in the profile of the user who runs the installer
- %temp%\{AssemblyProduct attribute; see AssemblyInfo}\adxloader.log in the profile of the user who starts the host application


Andrei Smolin
Add-in Express Team Leader
Posted 14 Jan, 2019 04:57:21 Top
Sean Ram




Posts: 27
Joined: 2013-03-13
Hi Andrei,

Here is the complete logs from the adxregistrator.log.. The customer was not able to find the adxloader.log

1,"fusion","GAC",0
1,"WinRT","NotApp",1
3,"System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","C:\Windows\assembly\NativeImages_v4.0.30319_32\System\ef92fd4410d6b1e5d4b768767ad05aaa\System.ni.dll",0
3,"System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\08626441fe724b1934292c3f853032a6\System.Drawing.ni.dll",0
3,"System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\23d50fb89fbdff6e8c2eaf3fa5afb8e3\System.Windows.Forms.ni.dll",0
3,"System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Core\80902f10241caeaa71d97ea6c88115a1\System.Core.ni.dll",0
3,"System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\dabffeccb3ff451b4f21a9cfd08193d6\System.Configuration.ni.dll",0
3,"System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xml\cc3865159952f5c1821a3af6916363b0\System.Xml.ni.dll",0
Posted 16 Jan, 2019 19:25:45 Top
Andrei Smolin


Add-in Express team


Posts: 18817
Joined: 2006-05-11
Hello Sean,

Sean Ram writes:
Here is the complete logs from the adxregistrator.log.


This isn't an adxregistrator.log. You can install your add-in on your development PC and check if it produces that file. If the file isn't found, I see these explanations possible:

- theinstaller starts adxregistrator.exe passing it /GenerateLogFile=false;
- the installer does not start adxregistrator.exe at all
- the user looks in a wrong location. Before Add-in Express 8.7, adxloader.log and adxregistrator.log were created in {user profile}\Documents\Add-in Express; with 8.7 and later, you should look in {user profile}\AppData\Local\Temp\{product name (see AssemblyInfo)}.

Check the adxregistrator.exe version that you deploy.


Andrei Smolin
Add-in Express Team Leader
Posted 17 Jan, 2019 06:06:43 Top