ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

UIM 20.3 - Primary hub wasp won't start - mcs_ws is not valid


Article ID: 225625


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


Our Wasp on the primary hub has failed to start so Admin console is not working.

Log shows error complaining 'Failed to start component ... D:\program files (x86)\Nimsoft\probes\service\wasp\webapps\mcs_ws is no valid.

 Caused by: java.lang.IllegalArgumentException: The main resource set specified [C:\Program Files\Nimsoft\probes\service\wasp\webapps\mcs_ws] is not valid



Possible webapp corruption 



Release : 20.3



To workaround and resolve this issue remove the webapp mcs-ws

This Webapp MCS RESTful Web Services ( provides rest capabilities to the MCS.



1. Deactivate the affected wasp on the primary hub

2. Use Raw configure to delete the entire webeapp section. (Webapp > mcs-ws) and delete section


The entire section should be removed from the wasp.cfg:



        reloadable = true
        cross_context = true
                loglevel = 5
                loglevel = 5
                loglevel = 5
                loglevel = 5
                loglevel = 5
                loglevel = 5
                loglevel = 5
        load_on_startup = true
        unpack_war = true
        path = /mcsws
        doc_base = mcs_ws
            device_id_fields = name,origin


3. Start wasp. 


See if wasp starts. 

If wasp starts deploy the lates version of mon_config_service_ws to the same primary hub wasp and the webapp will be reinstalled and not it should work fine.