Errors when upgrading to OC v20.4 – Cumulative Update 1 (CU1)
.zip file does not conform to the Nimsoft package format.
Caution: filename not matched: info.pkg
Caution: filename not matched: info.crc
When trying to upgrade to Operator Console 20.4 – Cumulative Update 1, some customers are encountering a package format error message when trying to deploy the cumulative update package:
To avoid this issue, follow this process.
When you are on the Downloads page, select all of the packages by clicking the checkboxes.
Then click “Download Selected” at the TOP right-hand side of the page.
Note that when you click the button on the top right side of the customer portal page and choose “Download Selected," the downloaded package, (in this case the file name was 24520125.zip for instance), is a true zip file that contains other nested zip files. It is NOT a Nimsoft package .zip.
Therefore, you MUST extract ALL of the packages first, before importing all of them into the Primary hub local archive via drag and drop or rt-click on the archive window and choose ‘Import.’
To ensure a successful initial / 'first-time' deployment of the oc_cumulative_update:
1. Navigate to the following location on the OC Robot machine-> ...\Program Files (x86)\Nimsoft\robot\pkg\inst\
2. Open the file-> installed.pkg
3. Look for the presence of this section (note there could be 1 or more instances of the section from previous version installs)
type = ge
version = 8.40
Note that the OC wasp probe will turn green, but it will take a few minutes to obtain a PID and a port and fully Activate.
After wasp is up and running, Login to the Operator Console and check it.
"Updated Operator Console 20.4 - Cumulative Update 1" install steps now reflect the alternate approach to mitigate any distsrv deployment issues.
Please see the updated page:Operator Console 20.4 - Cumulative Update 1
1. metapack_helper gets installed and helps in stopping/starting wasp. It gets auto-deleted once all the required webapps are deployed.
2. Deploying the package oc_cumulative_update from IM GUI is currently no longer supported and this is noted in the updated documentation.
3. You can also deploy the individual webapps to the Operator Console Robot.
Deploying oc_cumulative_update (from the adminconsoleapp) should help to avoid the issue in IM when using distsrv, including avoiding the manual effort involved in lookup and deployment of each webapp.
Also it is the recommended way as it keeps a record of the patch level of the Operator Console.
Here is an example excerpt from the automated_deployment_engine log showing a successful deployment of the CU.
[attach_socket] TRACE AutomatedDeploymentEngineProbe - ADE - get_status callback PDS dump:
JobStatus=Success, JobDescription=Automated deployment job Created at 1649285721525, EndTime=1649285725037, JobName=automated_deployment-1649285721525, StartTime=1649285721529, , JobID=f46a7ccd9f264d1a980748ef0a2eae21 StatusTable: /<domain>/<hub>/<robot>/oc_cumulative_update: Status=Success, Type=Probe, TaskId=61, Description=, Address=/<domain>/<hub>/<robot>/oc_cumulative_update, Version=20.41, Error=, Host=/<domain>/<hub>/<robot>/, Package=oc_cumulative_update, JobID=f46a7ccd9f264d1a980748ef0a2eae21