Hi,
One of our customers had been using a Shell (MCC on PDA) without connecting to a MCC, now they've purchased the MCC and when I installed the latest MCC on the Ikôn I get a bunch of Resource missing errors (Dialog missing and a bunch of images are reportedly missing) when I try to exit the shell. Just before the screen where one enters the admin password is shown these errors are popping up, the OK button is grey after clicking away the errors.
I can still take possession of the Ikôn via the MCC on the server but I'm at a loss as to the cause of these missing resources.
Can someone shed some light on this issue?
Kind regards,
Miguel
Hi Miguel,
Is this one of the errors you are getting?
This is most likely a version issue/ difference between the MCC agent (client) installed on the Ikôn vs. the MCC server. In my case, the customer upgraded MCC to 5.03 then to 7.02. The agent upgrade for an unknown reason did not update correctly on some devices.
Have you verified/ compared the agent version installed on the Ikôn vs. the MCC server?
I suggest re-installing the appropriate MCC agent.
If problem persist, try a "clean" start on one of the affected units, install the agent then test again
Hope this helps
Americas Help Desk
This posting is provided "AS IS". No Warranty. No Guarantee. Maybe updated or changed without notice at any time. You can use the information provided at your own risk.
Hello everybody,
I have the same issue. I reinstalled MCC agent 8.02.4524 and it is not solved. I have seen at least three Id, for example, one is Id=476. Type = Image.
More ideas would be appreciated.
Thank you in advance,
Rodrigo
More info. Once unlocked the MCC in the device, clicking in green MCC icon bottom right, "About" shows Version 8.02 but "configure", "status" tab shows "Agent Version 6.03.3664"
Perform the . clean on the IKON and reinstall the appropriate add-on cab. Remove the following MCC files...
\Flash Disk\Startup\autorun.exe
\Flash Disk\PdbPkg
\Flash Disk\pdb.ini
\Flash Disk\NET_XS_...
Create a new Device agent from your MCC server and install it onto the device. It should resolve this issue.
Hello Mazhar,
This does resolve this issue, thank you.
Last doubt: We have 221 devices deployed in field all over the country, what would be your suggestion to update these devices without interrupting the service, i.e. "sending to HQ" each device, nor needing technical actions by holders? (I would not want to spread passwords, sequence to perform ".clean", etc.)
Thank you again,
Hi Rodrigo,
Can these devices talk to your deployment server?
Please also explain to me the exact scenario... How you end up with this message.......
What’s your Current MCC version? Device agent version?
Hi Mazhar,
Yes, all devices can talk with MCC server. All of them, but the one updated locally, appear with an exclamation indicating that the agent is not updated.
The exact scenario is:
- Current MCC server and client version: 8.02 build 4524.
- Previous version: 6.03 build 3664.
- All devices (but the one updated locally) have agent 6.03 build 3664.
- Error appears when agent starts only if the agent was updated remotly through MCC and HSDPA (no .clean). It is the case stated above. (in device, the agent shows in some tabs version 8.02 and in others 6.03.)
- This error does not appear after .clean (locally on device) + add-on (activesync) + agent 8.02 (activesync) installation.
Regards,
Is the Automatic device agent is enabled? If it is and you are still experiencing the problem try to downgrade the MCC to 7.02, then upgrade the device agent and if it works then upgrade it to 8.03. It's would be step by step upgrade.
"Once the Manager and Deployment Server software has been upgraded, the devices will appear in the Manager console with a warning sign. This is an indication that Agent Upgrade must be enabled in order for the automatic upgrade of the Device Agent to proceed.
For example, if after enabling a few test devices for which problems are found with the agent, the upgrade can be "rolled back" and the majority of devices will avoid the failed upgrade."
No, I just enabled automatic update for the first device and then I got the issue.
I understand that downgrading MCC to 7.02 implies database downgrading, MCC server downgrading, some MCC client downgrading, is that correct?
Do you know if there is some quick guide to execute this downgrading?
. If it’s a live server I would not mess around with it. I am not aware of issues like (Database downgrading, MCC clients downgrading) with downgrading to MCC version 7.02.
I would suggest contacting your local Psion help desk and they can send you all the relevant documentation. You can also see the Mobile control center Help. Most of the information is available under Help Tab.
Mazhar
Hello All,
Do any of these device configurations include a Total Recall profile? If Total Recall exists on the terminal and is restoring data that pre-exists the MCC upgrade, resources required by the updated agent could be considered unavailable by the device software.
Best regards,
Arthur - Americas help desk
Mazhar IqbalIs the Automatic device agent is enabled?
The option "Automatically Upgrade New Agent" will only work for newly added devices using an old version of the MCC agent.
per the MCC Help File:
This entry determines if the system will upgrade any newly added devices using an old version of the device agent.
Mazhar IqbalFor example, if after enabling a few test devices for which problems are found with the agent, the upgrade can be "rolled back" and the majority of devices will avoid the failed upgrade."
I believe the "rolled back" the MCC help file is referring to is using the backup copy of the MCCDB which was taken prior to the upgrade.
@Mazhar. Thank you Mazhar. With this mixed arrangement (6.03 in terminal + 8.02 in server and client) we can communicate with terminals, but in fact I wanted to update agents to avoid any uncompatibilities that could arise and to profit of new functionalities. We are no going to mess with DB
@Arthur. No, we are not using Total Recall.
@Luke. All these 221 devices are previous add ones (created with 6.03). We don't have yet the opportunity to add a new device with 8.03
Thank to all of you for your cooperation.