Intel Fortran Module Wizard : Attempted an unsupported operation

[Rudy__Delcroit]

Hi All,

I'm trying to use a DLL into Intel Visual Fortran. From what I've understood module wizard should help me. Everything goes well up to the second step when I click "finish" the wizard says : ModWiz : Attempted an unsupported operation and it quites.

I've had the same behavior not only for my DLL but also for system DLL like Micorosft Excel and for assemblies ...

I tried with IVF 10.1 and the latest 11.

Any idea what it could be ?

Best Regards,

Vincent

[Steven_L_Intel1]

Would you please walk us through the steps you followed (what you clicked on, what you typed, etc.) to have this happen? Please use one of the MS DLLs as an example.

[Rudy__Delcroit]

Quoting - Steve Lionel (Intel)

Would you please walk us through the steps you followed (what you clicked on, what you typed, etc.) to have this happen? Please use one of the MS DLLs as an example.

Dear Steve,

Im running windows Vista with Visual Studio 2008.In the folder PictureModuleWizard,you would find screen captures of what I did. I can check any checkbox or change names in textbox, it all end-up at the same error message.

Best Regards,

Vincent

[Steven_L_Intel1]

You'll have to go into the folder for the files you uploaded, select each file and then click Add as attachment.

[Rudy__Delcroit]

Quoting - Steve Lionel (Intel)

You'll have to go into the folder for the files you uploaded, select each file and then click Add as attachment.

I might be blind but I can't see Add as attachment. Only edit or delete.

Any way, here is what I do :

- From tool menu launch Intel Fortran Module Wizard

- From the com tab select "Microsoft Windows Common Controls 6.0" Tylib version 2.0 file c:windowssystem32MSCOMCTL.oca

- I don't check The automation code (even if I do it do the same)

- Click Next

- I select one interface "Interface IListItem" the module name is set to MSCOMCTL

- I don't check Generate DLLEXPORT statements (even if I do it do the same)

- I click finish : I get the error message.

I try on a other PC and it is working fine. Uninstalling and reinstalling IVF didn't solve the problem. Are they any componant required ?

Best Regards,

Vincent

[Steven_L_Intel1]

My system doesn't have that exact entry under COM - I do have a Microsoft Windows Common Controls 6.0 but it is an OCX, not OCA. I followed the rest of the instructions and it worked fine. Which version of Visual Studio are you using?

[juergenrarey_net]

Quoting - Steve Lionel (Intel)

My system doesn't have that exact entry under COM - I do have a Microsoft Windows Common Controls 6.0 but it is an OCX, not OCA. I followed the rest of the instructions and it worked fine. Which version of Visual Studio are you using?

Hello Steve, I am experiencing the identical problem. I am just trying to move from DVF to IVF again. (My last try with Version 9 was very frustrating)

The modules are .exe with COM interfaces generated using Borland C++ Builder.

The DVF module wizard worked without any problems using:
"Type library containing COM interface information"

I am using

Intel Visual Fortran Compiler Integration for Microsoft Visual Studio* 2008, 11.0.3454.2008, Copyright (C) 2002-2009 Intel Corporation

Microsoft Visual Studio 2008

Vista 64

I am getting the "Attempted an unsupported operation" error whatever I try. Also when trying to generate a module for Microsoft COMM control 6.0

Can you give me a hint on how to solve the problem?

BTW: My module generated with the DVF wizard give me compilation errors, so I can't use the code generated with that wizard.

Error 1 error #5528: The REFERENCE attribute cannot be used with a passed length CHARACTER variable on this platform
Error 2 error #5529: CHARACTER variable 'ERR_MSG' has no length argument in routines with C or STDCALL attribute

best regards - Juergen Rarey

[Steven_L_Intel1]

That Microsoft COMM control seems to be from VB6, which I don't have available. A did a Google search and came up with this page which suggested "using something else". What are you trying to do with this?

Please attach the DVF-generated source that is giving the compile errors - I'll tell you how to fix it.

[juergenrarey_net]

Quoting - Steve Lionel (Intel)

That Microsoft COMM control seems to be from VB6, which I don't have available. A did a Google search and came up with this page which suggested "using something else". What are you trying to do with this?

Please attach the DVF-generated source that is giving the compile errors - I'll tell you how to fix it.

Hello Steve,
thank you for the quick response. Please find attached two example codes generated by the DVF Module Wizard.
The lines

!DEC$ FREEFORM
!DEC$ FIXEDFORMLINESIZE:72
!DEC$ INTEGER:4

were added by me but I think they shouldn't be the problem.

best regards

Juergen

[Steven_L_Intel1]

The problem is the !DEC$ ATTRIBUTES REFERENCE that CVF added for CHARACTER arguments. It is unnecessary and wrong. I've attached the modified files that compile ok.

I can also reproduce the "unsupported operation" error and will report it to the developers.

[juergenrarey_net]

Quoting - juergenrarey.net

If I change it this way:

INTEGER(INT_PTR_KIND()), INTENT(OUT) :: err_msg ! BSTR
!!!DEC$ ATTRIBUTES REFERENCE :: err_msg

there is an error

Error 5 error #8039: The INTENT(OUT) or INTENT(INOUT) attribute is not allowed for arguments received by value. [ERR_MSG] H:Visual Studio wrkTCF_I11ModulesParamDDB_2009.f90 99

So I remove the , INTENT(OUT) now, too. Just to inform you....

Thank you again for the fast and competent response. Like in the old times of DVF.

best regards - Juergen

[juergenrarey_net]

Quoting - Steve Lionel (Intel)

BTW: Are you sure, that a COM-interface passes strings as value?

[Steven_L_Intel1]

Change only the CHARACTER arguments and only for the contained routines.

Note that these routines are Fortran code called by Fortran - the interface can be anything you want it to be.

[Michael8]

Hello:

Has there been an progress made in resolving the "Attempted an unsupported operation" error message? I'm running into this same problem no matter which option I select in the Module Wizard. I'm trying to create a module for Excel 2007.

Thanks.
Michael

[Steven_L_Intel1]

Michael,

I will have to research this when I return to the office on Monday. What are the exact steps you follow to trigger the error?

[Michael8]

I have Visual Studio 2008, with IVF 11.1.038. I also have Office 2007 on my machine.

I started the Intel Visual Fortan Module Wizard and made sure the "COM" tab was selected. Then I scrolled down and selected the "Component Name" called "Microsoft Excel 10.0 Object Library". I also checked the "Generate code that uses Automation interfaces" check box, and clicked "Next".

I clicked on the "Select All" button and also put a check in the "Check for exception return status (Automation only)". I left the deafult "Module Name" as "EXCEL", and then clicked "Finish".

Note, that although I have specified the exact inputs I've used, in reality I have not found any set of inputs that works.

Thanks for looking into this.
Michael

[Steven_L_Intel1]

This is apparently not yet fixed. I will ping the developers about it.

[Michael8]

Thanks. So do you have any guess at when this may be fixed?

Thanks.
Michael

[Steven_L_Intel1]

I tried it on an 11.1.051 system and it worked. I will go back to the system I first tried it on, which had an older version, install 051 and see if it fails there. Which OS version and edition (32 or 64-bit)?

[Steven_L_Intel1]

This would appear to be fixed in 11.1.051 (Update 3). I could reproduce the bug in Update 2. Let me know how Update 3 works for you.

[Michael8]

I am running Vista, 32-bit. I will try upgrading IVF and see if that helps.

Thanks.
Michael