Informxi CSDK - ConnectTest Demo
Posted in 2015
Topics: Installation, Setup & Upgrades, Migration, Import/Export & Data Conversion
Hi, Just installed 12.10FC4DE with the CSDK on Win 7 Pro (64-bit). When running ConnectTest Demo I get the error messages below. What am I missing? Thanks. Guy See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.UnauthorizedAccessException: Access to the registry key 'HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Informix\\\\Environment' is denied. at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str) at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck, RegistrySecurity registrySecurity) at ConnectTest.ConnectTest.getenvkey(String envstr) at ConnectTest.ConnectTest.ConnectTest_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll ---------------------------------------- ConnectTest Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/IBM%20Informix%20Software%20Bundle/bin/ConnectTest.ex e ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e 089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/Sy stem.Drawing.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
Hi Guy, If the logon user has administrative privilege then you may adjust User Account Control (UAC) setting on your system to solve the problem (as long as you are comfortable with security aspects of new UAC setting) If the logon user do not have administrative privilege then it makes things complex. Windows a problem can be solve by N number of ways. Well in otherworld N number of things may create problem too. Let me give you some background about the problem you are facing. Then you may choose to apply solution that best suited for your system. The process of the ConnectTest tool needs administrative privilege since it is modifies entries from HKEY_LOCAL_MACHINE. Since the introduction of Windows Vista, the windows process do not inherit administrative privilege even if the logon user is an administrator. By default, standard users and administrators access resources and run applications in the security context of standard users. There are multiple ways to overcome such problem, including redesigning the application to grab administrative access token internally if the logon user has administrative privilege else prompt user asking for Admin password etc. Unfortunately this tool do not have any of such built-in mechanism to grab administrative privilege so we need have workaround outside of the application Based on your system security level you may have to choose a way to induce administrative privilege to this process. Regards, Satyan Advisory Software Engineer R&D - IBM Information Management Division 11200 Lakeview, Lenexa, KS 66219 Tel: 913 599 8792 (T/L: 337-8792) ids-bounces@iiug.org wrote on 03/27/2015 01:44:27 PM: > From: "GUY DILLEN" <guy.dillen@hotmail.com> > To: ids@iiug.org > Date: 03/27/2015 01:45 PM > Subject: Informxi CSDK - ConnectTest Demo [34881] > Sent by: ids-bounces@iiug.org > > Hi, > > Just installed 12.10FC4DE with the CSDK on Win 7 Pro (64-bit). > When running ConnectTest Demo I get the error messages below. > What am I missing? > > Thanks. > Guy > > See the end of this message for details on invoking > just-in-time (JIT) debugging instead of this dialog box. > > ************** Exception Text ************** > System.UnauthorizedAccessException: Access to the registry key > 'HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Informix\\\\Environment' is denied. > > at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str) > > at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, > RegistryKeyPermissionCheck permissionCheck, RegistrySecurity > registrySecurity) > > at ConnectTest.ConnectTest.getenvkey(String envstr) > > at ConnectTest.ConnectTest.ConnectTest_Load(Object sender, EventArgs e) > > at System.Windows.Forms.Form.OnLoad(EventArgs e) > > at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) > > at System.Windows.Forms.Control.CreateControl() > > at System.Windows.Forms.Control.WmShowWindow(Message& m) > > at System.Windows.Forms.Control.WndProc(Message& m) > > at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) > > at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr > wparam, IntPtr lparam) > > ************** Loaded Assemblies ************** > mscorlib > > Assembly Version: 2.0.0.0 > > Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) > > CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll > ---------------------------------------- > ConnectTest > > Assembly Version: 1.0.0.0 > > Win32 Version: 1.0.0.0 > > CodeBase: > file:///C:/Program%20Files/IBM%20Informix%20Software%20Bundle/bin/ > ConnectTest.exe > ---------------------------------------- > System.Windows.Forms > > Assembly Version: 2.0.0.0 > > Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) > > CodeBase: > file:///C:/windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0. > 0__b77a5c561934e089/System.Windows.Forms.dll > ---------------------------------------- > System > > Assembly Version: 2.0.0.0 > > Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400) > > CodeBase: > file:///C:/windows/assembly/GAC_MSIL/System/2.0.0. > 0__b77a5c561934e089/System.dll > ---------------------------------------- > System.Drawing > > Assembly Version: 2.0.0.0 > > Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) > > CodeBase: > file:///C:/windows/assembly/GAC_MSIL/System.Drawing/2.0.0. > 0__b03f5f7f11d50a3a/System.Drawing.dll > ---------------------------------------- > > ************** JIT Debugging ************** > To enable just-in-time (JIT) debugging, the .config file for this > application or computer (machine.config) must have the > jitDebugging value set in the system.windows.forms section. > The application must also be compiled with debugging > enabled. > > For example: > > <configuration> > > <system.windows.forms jitDebugging="true" /> > </configuration> > > When JIT debugging is enabled, any unhandled exception > will be sent to the JIT debugger registered on the computer > rather than be handled by this dialog box. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
Hi Satyan, Thanks for the info. I solved it but just starting the app running as Administrator (right-click). Thanks. Guy