Windows form Application Deploy: Error while trying to run the executable file on w7 64 bit machine

Not Answered This post has 0 verified answers | 3 Replies | 3 Followers Thread's RSS feed.

Replied On: Fri, Apr 1 2016 5:28 AM Reply


Following the development of a windows form application with Infragistics trial license and the creation of executable EXE file, while trying to run the file on w7 64 bit machine an error has occured.

The W7 machine from which the error is detected is not the same machine used to develop and create the executable application.

The Infragistics version employed for the development of the windows forms application is 15.2 (2015.2) trial version.

The machine provided of the executable application has no Infragistics version installed.


N.B. The generated executable can start without errors on the development machine whereas the error presented if run on any machine w7.

Can you help me to knows the issue?

When i create the executable file with infragistics trial version, can i deploy on every machines or i have to buy commercial license for execute it without error?


  • Post Points: 20

All Replies

Mike Bowshewicz
Points 9,205
Infragistics Employee
Replied On: Fri, Apr 1 2016 5:50 PM Reply

Hi Giuseppe,

You should be able to test deploying your application on the other machine. The trial reminder message will still appear in this case, but the application should run with no error. I think it would be a violation of our license agreement to actually deploy to end users.

It appears that there is some other error occurring here. Perhaps the executable is not able to find the assemblies. Is there an error message displayed? If so, please let me know what it is and I will see if we can help. If there is no visible error, I recommend using a program like WinDbg to debug the executable. Please see this page for information on how you can attach the debugger to the process when it starts up:


Mike B
Software Developer

  • Post Points: 20
Replied On: Sun, Apr 3 2016 4:14 PM Reply

i have attached the screen capture of error after lanch of the executable file.

I have run also the windows debug on executable file, to follow the details of report of windows debug(i have marked in bold the error messages of stack):

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
ModLoad: 01260000 01310000 Menu.exe
ModLoad: 77d70000 77ef0000 ntdll.dll
ModLoad: 717c0000 7180a000 C:\windows\SysWOW64\MSCOREE.DLL
ModLoad: 75f30000 76040000 C:\windows\syswow64\KERNEL32.dll
ModLoad: 75720000 75767000 C:\windows\syswow64\KERNELBASE.dll
(1d3c.1ea8): Break instruction exception - code 80000003 (first chance)
eax=00000000 ebx=00000000 ecx=ab820000 edx=0014dd48 esi=fffffffe edi=00000000
eip=77e10e14 esp=0042f9a0 ebp=0042f9cc iopl=0 nv up ei pl zr na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246
77e10e14 cc int 3
0:000> g
ModLoad: 68000000 68038000 C:\windows\SysWOW64\QIPCAP.DLL
ModLoad: 758d0000 75971000 C:\windows\syswow64\ADVAPI32.dll
ModLoad: 76cc0000 76d6c000 C:\windows\syswow64\msvcrt.dll
ModLoad: 76e40000 76e59000 C:\windows\SysWOW64\sechost.dll
ModLoad: 77120000 77210000 C:\windows\syswow64\RPCRT4.dll
ModLoad: 756c0000 75720000 C:\windows\syswow64\SspiCli.dll
ModLoad: 756b0000 756bc000 C:\windows\syswow64\CRYPTBASE.dll
ModLoad: 716c0000 71739000 C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
ModLoad: 75ab0000 75b07000 C:\windows\syswow64\SHLWAPI.dll
ModLoad: 77070000 77100000 C:\windows\syswow64\GDI32.dll
ModLoad: 77490000 77590000 C:\windows\syswow64\USER32.dll
ModLoad: 775c0000 775ca000 C:\windows\syswow64\LPK.dll
ModLoad: 773f0000 7748d000 C:\windows\syswow64\USP10.dll
ModLoad: 76d70000 76dd0000 C:\windows\SysWOW64\IMM32.DLL
ModLoad: 75800000 758cc000 C:\windows\syswow64\MSCTF.dll
ModLoad: 66670000 666bf000 C:\Program Files\Manufacturer\Endpoint Agent\prntm.dll
ModLoad: 750b0000 750b8000 C:\windows\SysWOW64\Secur32.dll
ModLoad: 6b2d0000 6b321000 C:\windows\SysWOW64\WINSPOOL.DRV
ModLoad: 6cf30000 6cfef000 C:\windows\SysWOW64\MSVCR100.dll
ModLoad: 6cd30000 6cd99000 C:\windows\SysWOW64\MSVCP100.dll
ModLoad: 77290000 773ec000 C:\windows\syswow64\ole32.dll
ModLoad: 750a0000 750a9000 C:\windows\SysWOW64\VERSION.dll
ModLoad: 50580000 50c31000 C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
ModLoad: 6d670000 6d765000 C:\windows\SysWOW64\MSVCR120_CLR0400.dll
(1d3c.1ea8): Unknown exception - code 04242420 (first chance)
ModLoad: 79560000 7a6aa000 C:\windows\assembly\NativeImages_v4.0.30319_32\mscorlib\225759bb87c854c0fff27b1d84858c21\
ModLoad: 71740000 717c0000 C:\windows\SysWOW64\uxtheme.dll
ModLoad: 03960000 042e7000 C:\windows\assembly\NativeImages_v4.0.30319_32\System\0b980f1580b78efeb67af4884ae21c00\
ModLoad: 60cc0000 613ef000 C:\windows\assembly\NativeImages_v4.0.30319_32\System.Core\da179dca12c65389f0de319660361465\
ModLoad: 56220000 563eb000 C:\windows\assembly\NativeImages_v4.0.30319_32\Microsoft.V9921e851#\cd2690402cf09c1e97190e52044ae24c\
ModLoad: 0f430000 0f4ae000 C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
ModLoad: 77610000 7769f000 C:\windows\syswow64\OLEAUT32.dll
ModLoad: 502e0000 5046e000 C:\windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\cebdd889c7234fcae5cfb871a95e35a3\
ModLoad: 7a780000 7b3db000 C:\windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\d5e32df5d21eeb0f6fbf3d41ef612a60\
ModLoad: 665e0000 66664000 C:\windows\WinSxS\\comctl32.dll
ModLoad: 5b3c0000 5b3d3000 C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll
ModLoad: 716a0000 716b3000 C:\windows\SysWOW64\dwmapi.dll
ModLoad: 583e0000 584a5000 C:\windows\assembly\NativeImages_v4.0.30319_32\System.Runt73a1fc9d#\1023c65bb975fb0aaa94a65142a61a5b\
ModLoad: 045d0000 04a64000 System.Windows.Forms.dll
ModLoad: 58170000 58204000 Infragistics4.Win.UltraWinLiveTileView.v15.2.dll
ModLoad: 00f60000 00ff4000 Infragistics4.Win.UltraWinLiveTileView.v15.2.dll
ModLoad: 74ae0000 74af7000 C:\windows\SysWOW64\CRYPTSP.dll
ModLoad: 74aa0000 74adb000 C:\windows\SysWOW64\rsaenh.dll
ModLoad: 74a90000 74a9e000 C:\windows\SysWOW64\RpcRtRemote.dll
ModLoad: 04a00000 04ef8000 Infragistics4.Win.v15.2.dll
ModLoad: 06540000 06a38000 Infragistics4.Win.v15.2.dll
ModLoad: 59060000 590aa000 Infragistics4.Shared.v15.2.dll
ModLoad: 01060000 010aa000 Infragistics4.Shared.v15.2.dll
ModLoad: 6dc20000 6dc7f000 C:\windows\SysWOW64\sxs.dll
ModLoad: 75770000 757f3000 C:\windows\syswow64\CLBCatQ.DLL
(1d3c.1ea8): C++ EH exception - code e06d7363 (first chance)
(1d3c.1ea8): CLR exception - code e0434352 (first chance)
(1d3c.1ea8): CLR exception - code e0434352 (first chance)
(1d3c.1ea8): CLR exception - code e0434352 (first chance)
(1d3c.1ea8): CLR exception - code e0434352 (first chance)
ModLoad: 567f0000 568c4000 C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
(1d3c.1ea8): CLR exception - code e0434352 (!!! second chance !!!)
eax=0042f0c8 ebx=00000005 ecx=00000005 edx=00000000 esi=0042f180 edi=00000001
eip=7572c54f esp=0042f0c8 ebp=0042f118 iopl=0 nv up ei pl nz ac po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000212
7572c54f c9 leave

Thanks you

  • Post Points: 20
Replied On: Mon, Apr 4 2016 5:34 PM Reply

Hi Giuseppe,

   The exception doesn't seem to be related to our dll's the second chance exception seems to be triggered by the diasymreader.dll. I found an article that may help you with this issue. Especially if your development environement is different from the install environment. Such that you develop on a 64 bit environment and are getting this when installing in 32bit environment.  Or similarly going from CLR4 to CLR2.

Let me know if this helps,



Software Development Team Lead
Infragistics, Inc.

  • Post Points: 5
Page 1 of 1 (4 items) | RSS