when i try to update intel It shows me

Setup failed

One more issues caused the setup to fail. Please fix the issues and then retry setup. For more information see the Log File

0x800713ec-Asia

This is fail what they ask open to me.

[0B80:00F8][2016-01-15T19:34:35]i001: Burn v3.9.1208.0, Windows v5.1 (Build 2600: Service Pack 3), path: C:\Documents and Settings\AD\My Documents\Intel Driver Update Utility Installer.exe, cmdline: ''
[0B80:00F8][2016-01-15T19:34:35]i000: Initializing numeric variable 'DCAOPTIN_Checkbox' to value '0'
[0B80:00F8][2016-01-15T19:34:35]i000: Initializing string variable 'LaunchTarget' to value '[ProgramFilesFolder]Intel Driver Update Utility\DriverUpdateUI.exe'
[0B80:00F8][2016-01-15T19:34:35]i000: Setting string variable 'WixBundleLog' to value 'C:\DOCUME~1\AD\LOCALS~1\Temp\Intel_Driver_Update_Utility_20160115193435.log'
[0B80:00F8][2016-01-15T19:34:35]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Documents and Settings\AD\My Documents\Intel Driver Update Utility Installer.exe'
[0B80:00F8][2016-01-15T19:34:35]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Documents and Settings\AD\My Documents\'
[0B80:00F8][2016-01-15T19:34:35]i000: Setting string variable 'WixBundleName' to value 'Intel Driver Update Utility'
[0B80:0E80][2016-01-15T19:34:36]i000: Setting version variable 'WixBundleFileVersion' to value '2.2.0.6'
[0B80:00F8][2016-01-15T19:34:36]i100: Detect begin, 2 packages
[0B80:00F8][2016-01-15T19:34:36]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'
[0B80:00F8][2016-01-15T19:34:37]i052: Condition 'NETFRAMEWORK45 >= 378389' evaluates to false.
[0B80:00F8][2016-01-15T19:34:37]i101: Detected package: NetFx45Web, state: Absent, cached: None
[0B80:00F8][2016-01-15T19:34:37]i101: Detected package: DriverUpdateUtilityInstaller, state: Absent, cached: None
[0B80:00F8][2016-01-15T19:34:37]i199: Detect complete, result: 0x0
[0B80:0E80][2016-01-15T19:34:44]i000: Setting numeric variable 'DCAOPTIN_Checkbox' to value 0
[0B80:0E80][2016-01-15T19:34:47]i000: Setting numeric variable 'DCAOPTIN_Checkbox' to value 0
[0B80:00F8][2016-01-15T19:34:47]i200: Plan begin, 2 packages, action: Install
[0B80:00F8][2016-01-15T19:34:47]w321: Skipping dependency registration on package with no dependency providers: NetFx45Web
[0B80:00F8][2016-01-15T19:34:47]i000: Setting string variable 'NetFx45FullWebLog' to value 'C:\DOCUME~1\AD\LOCALS~1\Temp\Intel_Driver_Update_Utility_20160115193435_0_NetFx45Web.log'
[0B80:00F8][2016-01-15T19:34:47]i000: Setting string variable 'WixBundleRollbackLog_DriverUpdateUtilityInstaller' to value 'C:\DOCUME~1\AD\LOCALS~1\Temp\Intel_Driver_Update_Utility_20160115193435_1_DriverUpdateUtilityInstaller_rollback.log'
[0B80:00F8][2016-01-15T19:34:47]i000: Setting string variable 'WixBundleLog_DriverUpdateUtilityInstaller' to value 'C:\DOCUME~1\AD\LOCALS~1\Temp\Intel_Driver_Update_Utility_20160115193435_1_DriverUpdateUtilityInstaller.log'
[0B80:00F8][2016-01-15T19:34:47]i201: Planned package: NetFx45Web, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: None, cache: Yes, uncache: No, dependency: None
[0B80:00F8][2016-01-15T19:34:47]i201: Planned package: DriverUpdateUtilityInstaller, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0B80:00F8][2016-01-15T19:34:47]i299: Plan complete, result: 0x0
[0B80:00F8][2016-01-15T19:34:47]i300: Apply begin
[0D44:069C][2016-01-15T19:34:50]i360: Creating a system restore point.
[0D44:069C][2016-01-15T19:35:00]i361: Created a system restore point.
[0D44:069C][2016-01-15T19:35:01]i000: Caching bundle from: 'C:\DOCUME~1\AD\LOCALS~1\Temp\{a699b395-cd93-4135-85ec-828113841355}\.be\Intel Driver Update Utility Installer.exe' to: 'C:\Documents and Settings\All Users\Application Data\Package Cache\{a699b395-cd93-4135-85ec-828113841355}\Intel Driver Update Utility Installer.exe'
[0D44:069C][2016-01-15T19:35:01]i320: Registering bundle dependency provider: {a699b395-cd93-4135-85ec-828113841355}, version: 2.2.0.6
[0B80:0B3C][2016-01-15T19:35:01]w343: Prompt for source of package: NetFx45Web, payload: NetFx45Web, path: C:\Documents and Settings\AD\My Documents\redist\dotNetFx45_Full_setup.exe
[0B80:0B3C][2016-01-15T19:35:01]i338: Acquiring package: NetFx45Web, payload: NetFx45Web, download from: http://go.microsoft.com/fwlink/?LinkId=225704
[0D44:03D8][2016-01-15T19:35:09]i305: Verified acquired payload: NetFx45Web at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\NetFx45Web, moving to: C:\Documents and Settings\All Users\Application Data\Package Cache\F6BA6F03C65C3996A258F58324A917463B2D6FF4\redist\dotNetFx45_Full_setup.exe.
[0D44:03D8][2016-01-15T19:35:10]i305: Verified acquired payload: DriverUpdateUtilityInstaller at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\DriverUpdateUtilityInstaller, moving to: C:\Documents and Settings\All Users\Application Data\Package Cache\{7B8CD972-B958-48BC-8727-7EE591A88AA5}v2.2.0.1\Intel Driver Update Utility Installer.msi.
[0D44:069C][2016-01-15T19:35:10]i301: Applying execute package: NetFx45Web, action: Install, path: C:\Documents and Settings\All Users\Application Data\Package Cache\F6BA6F03C65C3996A258F58324A917463B2D6FF4\redist\dotNetFx45_Full_setup.exe, arguments: '"C:\Documents and Settings\All Users\Application Data\Package Cache\F6BA6F03C65C3996A258F58324A917463B2D6FF4\redist\dotNetFx45_Full_setup.exe" /q /norestart /ChainingPackage "Intel Driver Update Utility" /log "C:\DOCUME~1\AD\LOCALS~1\Temp\Intel_Driver_Update_Utility_20160115193435_0_NetFx45Web.log.html"'
[0D44:069C][2016-01-15T19:35:23]e000: Error 0x800713ec: Process returned error: 0x13ec
[0D44:069C][2016-01-15T19:35:23]e000: Error 0x800713ec: Failed to execute EXE package.
[0B80:00F8][2016-01-15T19:35:23]e000: Error 0x800713ec: Failed to configure per-machine EXE package.
[0B80:00F8][2016-01-15T19:35:23]i319: Applied execute package: NetFx45Web, result: 0x800713ec, restart: None
[0B80:00F8][2016-01-15T19:35:23]e000: Error 0x800713ec: Failed to execute EXE package.
[0D44:069C][2016-01-15T19:35:23]i351: Removing cached package: NetFx45Web, from path: C:\Documents and Settings\All Users\Application Data\Package Cache\F6BA6F03C65C3996A258F58324A917463B2D6FF4\
[0D44:069C][2016-01-15T19:35:23]i330: Removed bundle dependency provider: {a699b395-cd93-4135-85ec-828113841355}
[0D44:069C][2016-01-15T19:35:23]i352: Removing cached bundle: {a699b395-cd93-4135-85ec-828113841355}, from path: C:\Documents and Settings\All Users\Application Data\Package Cache\{a699b395-cd93-4135-85ec-828113841355}\
[0B80:00F8][2016-01-15T19:35:24]i399: Apply complete, result: 0x800713ec, restart: None, ba requested restart:  No

Hello,

I am currently trying to use GDB fast tracepoint on the Xeon Phi, and I am running into some difficulties. I am using MPSS 3.4.5, and Intel parallel studio 2015. I have tried to use the libinproctrace.so library available with Parallel Studio 2015 and I have used gdbserver and libinproctrace.so that I have compiled from the MPSS 3.4.5 source.

I start the debugging server on the xeon phi using LD_PRELOAD=/tmp/libinproctrace.so ./gdserver localhost:3000 ./test_program, and I connect to it using gdb-mic from parallel studio (or gdb that I have compiled from the MPSS source). However, when I try to enable the fast tracepoint using tstart, I get a message telling me that the in-process agent library (which should be libinproctrace.so) is not loaded.

When I configured the gdbserver makefile from the MPSS source, I have used the --enable-inprocess-agent.

Thank you,

Didier Nadeau

Hi,

Actually, I am a petroleum engineer, I am going to modify one open source reservoir simulator. To compile the original simulator I use the win 7, 32bit, VS 2008, Intel(R) Visual Fortran Compiler Integration  11.1.3470.2008  : There are two solutions: 1: API to build library on HDF5 2: Simulator 

However I can build the API (without error), I can not run it and I face this error ( I am not sure if it is necessary to run it or just building is enough):

 Visual Studio cannot debug because a debug target has not been specified. 

After building the API , The library was created in the  related folder, I started to build in release as well as debug for simulator solution, at that time came up with this error: 

Debugging information for UTCHEM93.exe cannot be found or does not match. Binary was not built with debug information.

please help me to find out the problem to run the exe. file one time and after that start to modify the Fortran source codes because my main area is to focus on some function in the source code.

I have attached the simulator package (source codes and read me file).

Thanks

Dear All,

I have been checking program which was written by someone else. When I was trying to "start without debugging" the program,happened to find some errors. Images of those errors are attached with this post.

Please note that, I didn't get these errors during build.

Looking forward to your help and suggestions.

Thank you a lot. 

Dear all,

I am using Intel parallel XE on Win10. However I can not find the "intel parallel debugger extension" under the "Debug" button.

How can I enable this item?

Thanks so much!

Best..

 Hello,

I am new to using FORTRAN on Xcode so please bear with me.

I have been able to compile and run FORTRAN codes (under Xcode) so far but debugging is giving me a hard time. In essence, I cannot see local, or global, variables once the program stops at a breakpoint. I would like to check the value of variables as my code moves from one line to another. I am not looking for something fancy here as I have seen such capability under Visual Studio (windows). Can you please point me in the right direction? Should I install additional software to get debugging capabilities? Is there any setting in the Build section that I am missing?

I am using Xcode 7.3, OS X El Capitan (version 10.11.4), and Intel Fortran Compiler 16.0.

thanks

Farzin

Hi everyone,

I have a problem with Intel Rapid Storage Technology as you have seen in the screenshots. How can i solve this problem? 

http://imageshack.com/a/img921/8148/L9Fbiy.png

http://imageshack.com/a/img922/317/bB7eHK.png

http://imageshack.com/a/img923/6452/uQ61TN.png

I'm following the instructions for debugging a native Phi (KNC) under Eclipse, here:

https://software.intel.com/en-us/articles/debugging-intel-xeon-phi-appli...

After one or two minutes, the Eclipse debugging session terminates with a pop-up message:  "Connect to mic0 was cancelled" (see also the screen shot).  If I attempt to restart the clicking the "Debug" window again, it generates a 'Launching New_configuration' error (New_configuration is the name of the remote debugging configuration). I have to go back to Run->Debug to actually get a new session to start up on mic0, but that terminates after a couple of minutes as well.

Seen this? Found a fix? Thanks, -John

Problem:
I am porting a program with VB6 UI + Compac DLL to VB.NET 2013 + Intel Fortran (11.1) DLL
A small dummy program, in VS 2 projects (UI and DLL), works fine, i.e.:
- data input in UI
- data changed in DLL
- changed data displayed in UI

I'm using the following configuration:
- VS 2013
- Intel Frotran 11.1 for windows
- IMSL 7-1

When I replace the UI by the UI of the target program, but keep the interface to the DLL
and the DLL the same as in the dummy program:
- I can debug the DLL: so the interface is ok,
- but data changed in the DLL is not returned to the UI
- property pages are kept the same

Any suggestion what the cause might be, is highly appreaciated.

I was buiding a program with ifort and at linking stage I received such report.

How to solve this? 

I was building a program with ifort, however at the lingking stage, it was reported that 'ld: cannot find -lm'

How to solve this?

Hello world,

I have been searching around and I have come so far as to find that one can have access to module variables in the watch window through modulename::variable, which helps.

Is it possible to get this as a mouse-over as well? We have a large code base with legacy code so it happens that one has to debug unfamiliar code. It is very useful to be able to glance through variables to see what they contain. It is possible to use the watch window, but it takes much longer time.

I am also having trouble debugging when in a contained subroutine. I have to jump across the stack to maybe get access to a variable which should be in scope, ex:

module my_module

use statements
use more, only: statements

integer, allocatable :: shared_values(:,:)

!some code doing something
call a_contained_routine()

contains

subroutine a_contained_routine()
!variables

call suba()
call subb()

end subroutine

subroutine suba()
!variables

where (shared_values<0) shared_values=0
end subroutine

subroutine subb()
!do smtn
end subroutine

end module

In such a setup I would have troubles debugging the values in shared_values and often have to introduce a local copy just to see the contents. Code is always executed as expected, I just have trouble seeing it.

Regards, Knut

PS: Currently using Visual Studio 2013 for debugging, code is compiled with Intel Fortran 14.0.2.176 build 20140130. I also have Parallel Studio XE 2016 with ifort 16.0 build 20151021 but our code does not compile with an internal compiler error so I have not tried debugging with the latest and greatest.

Hi

I am trying to debug a C++ application with gdb-ia, but some functions are missing debug information (while other functions are ok).

All files are compiled with the same compiler options. This is an extract from the Makefile:

CC=icc

CFLAGS=-I../cpp_src -O0 -debug all -g -W -Wall -fPIC -march=native -fast -ansi-alias \
                        -fopenmp -finline -funroll-loops -no-prec-div -qopt-prefetch -unroll-aggressive \
                        -m64 -auto-ilp32 -I../src -xCORE-AVX2 -mkl -fma -I/opt/local/include/

LDFLAGS=-L/opt/local/lib -O0 -debug all -g -fopenmp -lboost_system-mt -lboost_timer-mt -lstdc++

When starting the executable in gdb-ia, there is no debug information at the first line of "main", (i.e. "step" results in a warning about no line number information, and the function runs to completion), but breakpoints in other places do stop on a line with valid source.

If I strip all source from the Makefile, and reduce main.cpp it to a simple one-liner, it eventually does debug properly.

Is there something obvious I've missed (I have not used icc before)? If it is important, this example makes use of AVX2 instructions, #pragma unroll's, and #pragma omp directives.

Many thanks,

Kevin

I am using Intel Visual Fortran Composer XE 2013 SP1 Update 6 for Windows, Version 2013.1.6.241, with Visual Studio 2013 on Windows 7. I created a default "Hello World" console application and added a single local variable, integer i. The Win32 Debug build allows me to step through with the debugger and view the value of i where I added it in the Watch 1 window. So far, so good. I then used the Configuration Manager to add builds for x64, copying settings from Win32. When I now build and debug the x64 Debug configuration, I cannot view the value of i. Instead, the value is listed as "Undefined address," and the Type is blank. How can I view variable values when debugging an x64 Debug build?

Hi,

When we run debug configurations under Visual Studio, stepping through code is extremely slow.  The more variables we add to the watch window, the slower it gets.  In some cases, we’re seeing ten second delays stepping from one line to the next.  This is true for projects with one source file or 100 source files.  Interestingly, if we hide the watch window, then performance returns to normal.  We’ve tried many suggestions from the forum, such as setting FEE_MAX_LOCALS to a small number, enabling “Managed Compatibility Mode”, and enabling “Edit and Continue”.  We’ve applied all patches that we know of, and are running Intel Parallel Studio XE 2016 Update 3 Composer Edition for Windows under Visual Studio Professional 2013.  Hopefully there’s a patch or setting we’ve overlooked, but we’re about out of ideas.

Thanks in advance for any help.

Robert Young

Hi,

when using gdb I normally use it inside Emacs, which provides a nice environment for debugging while in text mode (image attached), but this doesn't seem to work with gdb-ia. When invoking gdb from inside Emacs, I change the name of the gdb executable to gdb-ia, but I get the error:

angelv@carro:~$ Error: you did not specify -i=mi on GDB's command line!

Is there any way to get gdb-ia to play nicely with GDB Emacs mode?

Thanks,

Ángel de Vicente

Incomplete crosswalk project. How can i fix this problem?

Hi,

When we run debug configurations under Visual Studio, stepping through code is extremely slow.  The more variables we add to the watch window, the slower it gets.  In some cases, we’re seeing ten second delays stepping from one line to the next.  This is true for projects with one source file or 100 source files.  Interestingly, if we hide the watch window, then performance returns to normal.  We’ve tried many suggestions from the forum, such as setting FEE_MAX_LOCALS to a small number, enabling “Managed Compatibility Mode”, and enabling “Edit and Continue”.  We’ve applied all patches that we know of, and are running Intel Parallel Studio XE 2016 Update 3 Composer Edition for Windows under Visual Studio Professional 2013.  Hopefully there’s a patch or setting we’ve overlooked, but we’re about out of ideas.

 Thank you in advance for support.

When i unlock certificate pop up window certificate unlocked. But when i build my app window show that certificate still lock

Hi

Trying out 2017 beta version of Fortran (I also have the previous 2013 ifort version) but I'm having a challenge with  gdb-ia. I have my .bash_profile set so that DYLD_LIBRARY_PATH is set so that on the command line I get 

echo $DYLD_LIBRARY_PATH/libiomp5.dylib

/opt/intel/compilers_and_libraries_2017.0.039/mac/compiler/lib/libiomp5.dylib

When in gdb-ia I get the following

(gdb) set environment DYLD_LIBRARY_PATH /opt/intel/compilers_and_libraries_2017.0.039/mac/compiler/lib

(gdb) run

The program being debugged has been started already.

Start it from the beginning? (y or n) y

Starting program: ~/LMSafe 

dyld: Library not loaded: @rpath/libiomp5.dylib

  Referenced from: ~/LMSafe

  Reason: image not found

Program received signal SIGTRAP, Trace/breakpoint trap.

0x00007fff5fc01075 in ?? ()

(gdb) 

in gdb-ia show environment gives.. 

DYLD_LIBRARY_PATH=/opt/intel/compilers_and_libraries_2017.0.039/mac/compiler/lib

If I run from 2013’s idb it works (even though I had to manually set the path in idb)

(idb) set environment DYLD_LIBRARY_PATH /opt/intel/compilers_and_libraries_2017.0.039/mac/compiler/lib

(idb) run

Program exited normally.

Starting program: ~/LMSafe

 Levenberg Marquardt XOR took::  4.892110824584961E-003 seconds.

                   200

 Output:=   0.461050158803991                          1

 Output:=   0.464174557964011                          2

 Output:=   0.463944152735494                          3

 Output:=   0.466966905109538                          4

Program exited normally.

(idb) 

any ideas?