Table of contents
- 1. NMC Controller inoperative
- 1.1. Review details problem
- 1.1.1. Solution(s)
- 1.1. Review details problem
- 2. Functionalities access
- 2.1. Review details problem
- 2.1.1. Solution(s)
- 2.1. Review details problem
- 3. Deconnection intempestive from the NMC interface
- 3.1. Review details problem
- 3.1.1. Solution(s)
- 3.1. Review details problem
- 4. Value cannot be null. Parameter name: source
- 4.1. Review details problem
- 4.1.1. Solution(s)
- 4.1. Review details problem
- 5. Value cannont be null. Parameter name: inner
NMC Controller inoperative
The NMC controller is in an inoperative state in the overview
Review details problem
Solution(s)
Check if the CTR_KEY_SOFT is the same between the database and the newtest.ini file.
Check the CMP_CODE between the database and the newtest.ini file
Update the newtest.ini entries if the fields are differents.
Functionalities access
Review details problem
You are logued with an administrator account but some functionalities are greyed.
Solution(s)
Ask ip-label support to see your license.
Deconnection intempestive from the NMC interface
Review details problem
You are regularly disconnected (especially when one person exports a project to the repository).
Solution(s)
Fix in 221R2
Value cannot be null. Parameter name: source
Review details problem
You got the error "Value cannot be null. Parameter name: source"
when a scenario is selected.
Solution(s)
Fix in 221R5
Value cannont be null. Parameter name: inner
Review details problem
Prior to version 2.2.1 user were not able to create robots without any scenarios added to the task list.
On 2.2.1 B10 we are able to create them, but afterwards not able to add any elements.
This GUI anomaly is due to be patched.
Solutions
There are two solutions:
- If the number of probes are limited, the most easiest way is to remove and recreate them by hand on the NMC.
- If your configuration contains a lot, it might be easier to use SQL to add a temporary scenario which will make it edittable.
Comments