Major upgrade problem - DIRPROPERTY1
The problem is that I need to roll out a major update to the Documentum Desktop Client app. but the existing installed version contains the DIRPROPERTY1 error in the Directory table and as such when uninstalling via GPO produces the error:
'Error 1606. Could not access network location \.'
I've tried uninstalling/updating via the upgrade table which causes a similar problem and doesn't even install the new version; I tried adding a Custom Action running MSIZAP but this didn't uninstall fully or correctly; I tried amending the locally cached MSI and removed the DIRPROPERTY1 which did work and would be ok for a few users but even so the filenames are always unique so can't just replace automatically. It can be removed manually when signed on as an administrator but this is not really an option; this app. is computer assigned in a locked down environment.
The only solution that worked was to amend the old version and remove the DIRPROPERTY1 and then redeploy via GPO; once reinstalled this then allowed itself to be uninstalled.
This doesn't seem so bad at first but the app. is used by approx. 300 users.
Does anyone know if there is a way of forcing an uninstall regardless of errors?
"I thought I had removed this problem from all my apps but I guess this must be the one that got away." [&:]
'Error 1606. Could not access network location \.'
I've tried uninstalling/updating via the upgrade table which causes a similar problem and doesn't even install the new version; I tried adding a Custom Action running MSIZAP but this didn't uninstall fully or correctly; I tried amending the locally cached MSI and removed the DIRPROPERTY1 which did work and would be ok for a few users but even so the filenames are always unique so can't just replace automatically. It can be removed manually when signed on as an administrator but this is not really an option; this app. is computer assigned in a locked down environment.
The only solution that worked was to amend the old version and remove the DIRPROPERTY1 and then redeploy via GPO; once reinstalled this then allowed itself to be uninstalled.
This doesn't seem so bad at first but the app. is used by approx. 300 users.
Does anyone know if there is a way of forcing an uninstall regardless of errors?
"I thought I had removed this problem from all my apps but I guess this must be the one that got away." [&:]
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
paul_e
18 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.