Solver mistakenly producing "Solver stopped by user" error

Hello,

I am working on a fairly complex macro that employs Solver, but I noticed that it would often skip over certain parts of my data. Upon further analysis, I noticed that it was producing a "Solver stopped at user's request" message when it skipped these rows in question. I can confirm that there is absolutely no way that the escape or break keys were being pressed during the macro's run, even going so far as to add "Application.EnableCancelKey = xLDisabled" to that part of the macro. Curiously, I could run the exact same solver setup without the macro on the same rows of data and it would work without issue. Does anyone know what circumstances can cause Solver to mistakenly believe that it was stopped by the user? I've included the code of my Solver setup below.

Please Login or Register  to view this content.

Hi

Could you upload the file as well? Don't forget to remove sensitive data first.

Aif

Ps The paperclip for uploading don't work so you have to scroll down and click on the line "Manage Attachment"