Originally posted by: UserCplex

I use Visual Studio 2017 Community edition with CPLEX 12.7.1 64 bit version.

When I run my C Callable library application under debug mode, it runs fine.

Under release mode, it does not. Problem crash occurs randomly, but in all cases, the following type of error is obtained:

Exception thrown at 0x00007FFD2580849D (cplex1271.dll) in cplex.exe: 0xC0000005: Access violation writing location 0x000006A273E3B490.

No symbol file loaded for cplex1271.dll

Module information: Version 12.07.1.0

Original Location: C:\Program Files\IBM\ILOG\CPLEX_Studio1271\opl\bin\x64_win64\cplex1271.dll

Sometimes, instead of violation writing error, it is reading error:

 Access violation reading location 0xFFFFFFFFFFFFFFFF.

I have checked that in release mode I use /MD option with mda versions of libraries and in debug mode, i use /MDd option with mdd version of CPLEX libraries.

I use x64_windows_vs2015 version of CPLEX libraries. Does Visual Studio Community 2017 not work with this? Looking at Visual Studio, Help->About Microsoft Visual Studio: I see that the version of Visual Studio release is 15.2.

Any help will be appreciated.

CPLEX 12.7.1 is not supported with Visual Studio 2017, and we actually don't expect this combination to work.  You need to use Visual Studio 2015.  You will find the list of supported platforms/tools at http://www-01.ibm.com/support/docview.wss?uid=swg27019100.

The next version should offer support for VS2017, but I can't say at this time when it will be available.

Originally posted by: UserCplex

Xavier,

Thanks.

I am a bit confused because the following thread and its responses seem to suggest that it should be possible from within VS 2017. I hope I am not misreading that post.

https://www.ibm.com/developerworks/community/forums/html/topic?id=1d316a0d-1df3-472f-80ff-bfd671d3207f&ps=25

It is indeed possible to use the Visual Studio 2017 environment, if you also have Visual Studio 2015 installed and you explicitly configure your projects to use that compiler. That's what Ryan (rkersh) refers to in his answer in that thread.  Did you look at the link he provided?

Originally posted by: UserCplex

Yes, I tried what is provided in that link.

I tried within VS 2017. That gave the same error. Then, I ran the same project from within VS 2015. That would not work either.

Debug version works, but release version build gives same error as I mentioned in the opening post.

With the examples that are shipped with CPELX (e.g., admipex1, etc.), I can not reproduce this behavior. One thing you can try is exporting your model to SAV format (just before the call to solve) and try running it with the interactive. If you can reproduce the crash using the interactive, and you don't mind sharing the model here, we can take a closer look. Alternatively, if you can provide a small C example that reproduces the issue that would be helpful too. By the way, have you tried running with the datacheck parameter turned on?