I am getting the error as follows for one optimization problem :

## Calling Mosek 9.1.9: 21 variables, 7 equality constraints

For improved efficiency, Mosek is solving the dual problem.

MOSEK Version 9.1.9 (Build date: 2019-11-21 11:34:40)

Copyright (c) MOSEK ApS, Denmark. WWW: mosek.com

Platform: Windows/64-X86

## Mosek error: MSK_RES_ERR_HUGE_AIJ (A numerically huge value is specified for an element in A.)

Status: Error

Optimal value (cvx_optval): NaN

Unrecognized field name “sol”.

Error in cvx_mosek

Error in cvxprob/solve (line 429)

[ x, status, tprec, iters, y ] = shim.solve( At, b, c, cones, quiet, prec, solv.settings, eargs{:} );

Error in cvx_end (line 88)

solve( prob );

Error in opt_modified (line 202)

cvx_end

Whereas, the same solver can able to solve another problem.

How to resolve this issue?

Look for numerically huge input data in the problem which triggered the error message. The input data was so extreme that Mosek didn’t even try to solve the problem, rather than issuing a warning and trying to solve it.

if this was in an iterate of SCA, it may be that SCA was diverging with ever more extreme solutions, resulting in ever more extreme input data for the next iteration.

Error is displaying as of now:

Unrecognized field name “sol”.

Error in cvx_mosek

Error in cvxprob/solve (line 429)

[ x, status, tprec, iters, y ] = shim.solve( At, b, c, cones, quiet, prec, solv.settings, eargs{:} );

Error in cvx_end (line 88)

solve( prob );

Error in Opt_UplinkPower (line 173)

cvx_end

The error

```
Unrecognized field name “sol”.
```

always means Mosek didn’t even attempt solving the problem but exited with an error earlier. Your first post explains why: the coefficients were too large. If there is another reason then it will be similarly printed in the log output.

All that other stuff is a consequence of Mosek not trying to solve the problem, which CVX processed as “Error”.

Thanks sir, I will try to rectify it