Forum Discussion
Mosel does not see a DSO module provided by a C++ application - could Windows security be the problem?
We have an old C++ application that uses Xpress optimizer internally. It works by calling Mosel using `XPRMrunmod()`. In addition, it uses callbacks defined in the C++ application via `XPRMdsofct`, ...
In this case, I think, it is unlikely that the issue is caused by the security system (I assume that the program would not start at all if it was blocked).
Since the program works on other platforms, have you checked the environment: version of the system+patches, version of the C/C++-library? Are all systems running the same version of Xpress?
Do you check whether the registration of the static dso is successful (i.e. the return value of XPRMregstatdso, and does your implementation make sure that the initialisation function of the module is called and does not return an error status)? In particular the value returned by 'XPRMregstatdso' (if non-zero) can be helpful to analyse what is happening.
