After upgrading the PowerConnect, the UI seems to be disabled as no input is allowed and there is a Java error, “java.lang.IllegalArgumentException: local part cannot be “null” when creating a QName”
NW is caching the UI component so when upgrading from .24 to .26 the UI is still expecting 18 operations from the WSDL but we’ve added a further 4 in the new version so there’s a mismatch. Forcing the service group to be re-processed fixes this because it seems to invalidate whatever cache is storing the UI config.
- Go to NWA -> SOA -> Application Scenario and Communication -> Application Communication
- Click on the PowerConnectSG service group.
- Then click Edit and choose provider system None, click Save, then choose provider system Local and click Save again this will force the service group to get refreshed and should fix the UI without needing a restart.
- PowerConnect JAVA is working again