Software Distribution Cab File Errors
- Hi all,
We are having an issue with the software distribution using Motorola / Symbol MC75 devices.
There are two cab files that we are pushing out after all the initial software is installed. One is the Motorola base cab (symbol.all.arm.cab) and the other is SQL Compact Extensions (sqlce.ppc.wce5.armv4i.CAB).
On the SQLCE we have a dependancy of SQL Compact to be installed first, then this cab file installs. At the same time, the motorola base cab installs.
What seems to be happening with them is the following....
Everything installs fine and the application we are running works without any issues, we send them out into the field and approximately a week later, the application has issues because it relies on the two cab files and they appear to have removed themselves / stopped functioning.
The only fix we have found so far is to manually reinstall the cab files and everything works again as expected.
Has anyone come across this or have you any ideas as to what the cause could be? It seems like a completely random issue.
Thanks
Mike
Risposte
Did you configure dependencies when creating the distribution package to make sure the cabs install in the right order?
What is your policy re-calculation and schedule interval? If set too low you may end up in a loop of install-reinstall-etc. (Don't remember right now, but no less than an hour if my memory serves me correctly.)
Do the cabs contain an "Install" characteristic? Now, you haven't created these cabs yourself I guess, so you probably wouldn't know off the bat. But there's a few steps you could check; if installed manually does the cab generate a new entry in "Remove Programs"? Alternatively unpack the cab, look for the following in the _setup.xml file:
<characteristic type=”Install”>
<parm name=”InstallPhase” value=”install” />
If this info is not present, and it's not in the programs list it will not work properly with WSUS, and you may see the symptoms you describe. The fix for this would be to re-package the cab, or possibly it could be edited with WinCE CAB Manager to have the correct properties. I think it's the "Allow user to uninstall" checkbox, but I'm not a hundred percent on that.- Contrassegnato come rispostaWayne Phillips.MVP, Moderatorevenerdì 9 ottobre 2009 1.04
If the application hasn’t got the correct _setup.xml files inbuilt, or does not report itself as installed, then you can check registry settings to detect if the app has already been installed.
If the cab file creates a few registry keys / values than I suggest checking these values before installing. When you build your software package in Software Distribution console, specify a registry dependency. This should stop the application being installed multiple times, by MDM.Cheers Wayne
Airloom- Contrassegnato come rispostaWayne Phillips.MVP, Moderatorevenerdì 9 ottobre 2009 1.03
Tutte le risposte
Did you configure dependencies when creating the distribution package to make sure the cabs install in the right order?
What is your policy re-calculation and schedule interval? If set too low you may end up in a loop of install-reinstall-etc. (Don't remember right now, but no less than an hour if my memory serves me correctly.)
Do the cabs contain an "Install" characteristic? Now, you haven't created these cabs yourself I guess, so you probably wouldn't know off the bat. But there's a few steps you could check; if installed manually does the cab generate a new entry in "Remove Programs"? Alternatively unpack the cab, look for the following in the _setup.xml file:
<characteristic type=”Install”>
<parm name=”InstallPhase” value=”install” />
If this info is not present, and it's not in the programs list it will not work properly with WSUS, and you may see the symptoms you describe. The fix for this would be to re-package the cab, or possibly it could be edited with WinCE CAB Manager to have the correct properties. I think it's the "Allow user to uninstall" checkbox, but I'm not a hundred percent on that.- Contrassegnato come rispostaWayne Phillips.MVP, Moderatorevenerdì 9 ottobre 2009 1.04
- I've done this for lots of customers and I've never had an issue of SQL Compact Edition uninstalling itself.
Is this happening to all users?
Cheers Wayne
Airloom - Thanks Andreas, I will look into this.
From having a quick look at the symbol cab file, there is no _setup.xml file inside this.
Wayne,
SQL Compact appears to be ok and does not reinstall, we have noticed the extensions reinstalling themselves though.
I will do some digging into the cab files and report back. Thanks for your help so far.
Mike If the application hasn’t got the correct _setup.xml files inbuilt, or does not report itself as installed, then you can check registry settings to detect if the app has already been installed.
If the cab file creates a few registry keys / values than I suggest checking these values before installing. When you build your software package in Software Distribution console, specify a registry dependency. This should stop the application being installed multiple times, by MDM.Cheers Wayne
Airloom- Contrassegnato come rispostaWayne Phillips.MVP, Moderatorevenerdì 9 ottobre 2009 1.03
