We meet lots of this similar issues. And the probable reason is
1. Check the compatiable version
2. Check the license and the resource.
Confirm with the engineer. The version is compatiable. So it almost caused by the reason 2,
a. Check the license and the used resource. Use the command `display license`and `bnrm sysres`
b. We find there is used resource after we print the `bnrm sysres`.so this error almost caused by this phenonmenon.
c. We feedback this info. To customer and doubt there is conf in SMC2.0. so the resource is occupied.
d. But customer confirm that there is no conf. In SMC2.0. but we can use command `conf get` to find some conf existing. So we use command to end the conf.
e. After we enter the commmand. And then check the conf list. It is solved.