- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear all,
I am runningIVF 11.1.067 compiler and upgraded to IVF version 12 last week. I use FORTRAN code which executes EXCEL calls based on the AUTODICE example. My Office version is2007 (version 12).
So far - until last week - the program(built with 11.1.067 or earlier versions) ran successfully on different computers - independent of the EXCEL versionlocally installed. The only compromise was to selectWindows language as: English(US) to avoid execution failure.
However, now I encounter similar problems like Leonhard Bergstroem last July. Surprisingly, after de-installationof version 12 back to version 11.1.067 the problem remains. I can no longer maintain EXCEL sheets from within my FORTRAN program. Executions end with program crash.
I use COMCREATEOBJECT with "Excel.Application" (as generic call). Testing with "Excel.Application.12" (corresponding to my office version) gavethe same error on calling COMCREATEOBJECT: exception code 0x235 (565) - "invalid signal error". The problem is an assertion failure in some "C" routine called "winsig.c", line 419.
To make sure that I have no formal error in my code - I built the original AUTODICE example and also COMCREATEOBJECT fails to create an EXCEL object (error 0x235 (565)).
To be clearly understood - the old linked programs are still executing properly.However, I have nochance any more to maintain the code (!) with the current situation.
As I am no C programmer - I need desparately "good advice".
Thank you all
I am runningIVF 11.1.067 compiler and upgraded to IVF version 12 last week. I use FORTRAN code which executes EXCEL calls based on the AUTODICE example. My Office version is2007 (version 12).
So far - until last week - the program(built with 11.1.067 or earlier versions) ran successfully on different computers - independent of the EXCEL versionlocally installed. The only compromise was to selectWindows language as: English(US) to avoid execution failure.
However, now I encounter similar problems like Leonhard Bergstroem last July. Surprisingly, after de-installationof version 12 back to version 11.1.067 the problem remains. I can no longer maintain EXCEL sheets from within my FORTRAN program. Executions end with program crash.
I use COMCREATEOBJECT with "Excel.Application" (as generic call). Testing with "Excel.Application.12" (corresponding to my office version) gavethe same error on calling COMCREATEOBJECT: exception code 0x235 (565) - "invalid signal error". The problem is an assertion failure in some "C" routine called "winsig.c", line 419.
To make sure that I have no formal error in my code - I built the original AUTODICE example and also COMCREATEOBJECT fails to create an EXCEL object (error 0x235 (565)).
To be clearly understood - the old linked programs are still executing properly.However, I have nochance any more to maintain the code (!) with the current situation.
As I am no C programmer - I need desparately "good advice".
Thank you all
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
JUST A SHORT EXYENSION TO THE PROBLEM ABOVE:
if the code is compiled with the "Release" option - everthing works fine !
Apparently the IVF debugger ist the problem.
if the code is compiled with the "Release" option - everthing works fine !
Apparently the IVF debugger ist the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can build and run the AUTODICE sample with Composer XE in Debug mode and don't see any errors. I have Excel 2007 on my system. I suggest you try unzipping the COM.zip sample package into a new folder and try building and running that without changes.
Which Visual Studio version are you using?
Which Visual Studio version are you using?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry for answering so late.
My Visual Studio version is 2008.
In the installation of XE composer I selected to keep this version which I have used successfully before.
As to the AUTODICE example I tested: I did already exactly what you proposed.
None-the-less I encounter the crash under DEBUG mode and I find properly exeuting code under RELEASE.
I have re-installed 11.01.067 version hoping to sort out the problem - but now I find the result as with COMPOSER XE. So the secret must be somewhere in the installation of COMPOSER XE. It looks like something waschanged on my system - but I have absolutely no idea what that might be.
My Visual Studio version is 2008.
In the installation of XE composer I selected to keep this version which I have used successfully before.
As to the AUTODICE example I tested: I did already exactly what you proposed.
None-the-less I encounter the crash under DEBUG mode and I find properly exeuting code under RELEASE.
I have re-installed 11.01.067 version hoping to sort out the problem - but now I find the result as with COMPOSER XE. So the secret must be somewhere in the installation of COMPOSER XE. It looks like something waschanged on my system - but I have absolutely no idea what that might be.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try this experiment. Uninstall 11.1 and delete the "Intel Fortran" directory under Visual Studio 9. Reinstall 11.1 and try AUTODICE again. What happens? I doubt there will be a difference, but one never knows. I am not aware that there's anything that we install that would affect this behavior. Maybe other people here can try this experiment for themselves and report the results.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page