GOOGLE DESKTOP
Hi,
When I package google desktop,the package works fine on adminuser but fails to launch on testuser.
Also it self heals on each login on testuser but does not heal when the shortcut is clicked.
Pls help asap.need the solution urgently.
When I package google desktop,the package works fine on adminuser but fails to launch on testuser.
Also it self heals on each login on testuser but does not heal when the shortcut is clicked.
Pls help asap.need the solution urgently.
0 Comments
[ + ] Show comments
Answers (19)
Please log in to answer
Posted by:
murali.bhat
13 years ago
It might be an access issue. Run the tools FileMon and RegMon (or ProcMon which checks both) and look for "ACCESS DENIED". Application might be accessing files or registry keys where there is no permission.
After the login, check the event viewer and see which component is associated to the error. Check that component in your msi.
Are there any current user keys in your application?
After the login, check the event viewer and see which component is associated to the error. Check that component in your msi.
Are there any current user keys in your application?
Posted by:
timmsie
13 years ago
Posted by:
crazypackagers
13 years ago
I had checked with process monitor but could'nt get any "ACCESSED DENIED" but when i checked eventvwr. I got following warning:
Detection of product '{D9860634-FC03-4F49-B1B7-F716B21FF1D6}', feature 'GoogleDesktopNewFeature', component '{F4DF353E-98C3-4A8D-9832-A09294BF08F9}' failed. The resource 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\BrowseNewProcess - Google Desktop Backup\BrowseNewProcess' does not exist.
Detection of product '{D9860634-FC03-4F49-B1B7-F716B21FF1D6}', feature 'GoogleDesktopNewFeature' failed during request for component '{D8988958-7D07-4CCF-BACB-121454A1500B}'
Checked it in Installshield, components exist with correct files and key path.
Detection of product '{D9860634-FC03-4F49-B1B7-F716B21FF1D6}', feature 'GoogleDesktopNewFeature', component '{F4DF353E-98C3-4A8D-9832-A09294BF08F9}' failed. The resource 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\BrowseNewProcess - Google Desktop Backup\BrowseNewProcess' does not exist.
Detection of product '{D9860634-FC03-4F49-B1B7-F716B21FF1D6}', feature 'GoogleDesktopNewFeature' failed during request for component '{D8988958-7D07-4CCF-BACB-121454A1500B}'
Checked it in Installshield, components exist with correct files and key path.
Posted by:
murali.bhat
13 years ago
Posted by:
timmsie
13 years ago
your apps repairing because there is a current user key as the key path for that component.
The best way to handle this if you don't want a repair would be using Active setup, next question, what's active setup - http://www.etlengineering.com/installer/activesetup.txt
By the way when you say you packaged the app what did you do? Isn't it already in an msi format?
The best way to handle this if you don't want a repair would be using Active setup, next question, what's active setup - http://www.etlengineering.com/installer/activesetup.txt
By the way when you say you packaged the app what did you do? Isn't it already in an msi format?
Posted by:
crazypackagers
13 years ago
Posted by:
timmsie
13 years ago
My application does not get repair now as i have added the regisrty
have you just added it for you? what happens when you deploy it to other users?
Did you try the lua buglight tool I recommended
http://blogs.msdn.com/b/aaron_margosis/archive/2006/08/07/luabuglight.aspx
Posted by:
anonymous_9363
13 years ago
The best way to handle legacy installers is to always assume that you missed something and take a gap capture after installing your MSI, removing any trace of installation data and then runing the vendor install over the top. You then add any relevant changes to your package and re-test. I'm praying you're using VMs/VPCs/VirtualBoxes for packaging/testing...
Posted by:
crazypackagers
13 years ago
Posted by:
pjgeutjens
13 years ago
0) Snapshot your VM (to be repeated as needed)
1) Install your package
2) Take out all info relevant to your package from the registry (in HKCR/Installer and HKLM/Software/Microsoft.Windows/Currentversion/Uninstall)
3) start capturing
4) run the vendor's installer over your package install
5) stop capturing
6) look in this 'gap capture' for relevant changes made by the vendor's installer that you might need to put into your package
7) restore VM snapshot and do it all again
EDIT: added 0) and 7)
1) Install your package
2) Take out all info relevant to your package from the registry (in HKCR/Installer and HKLM/Software/Microsoft.Windows/Currentversion/Uninstall)
3) start capturing
4) run the vendor's installer over your package install
5) stop capturing
6) look in this 'gap capture' for relevant changes made by the vendor's installer that you might need to put into your package
7) restore VM snapshot and do it all again
EDIT: added 0) and 7)
Posted by:
anonymous_9363
13 years ago
I think you've captured the normal client, which downloads and installs from the web. There are MSI installs for the Google apps. Google for 'google desktop msi'.
Although not suitable for this app (as I say, there's already an MSI for it) please search AppDeploy for 'gap capture'. It's been done to death.
Although not suitable for this app (as I say, there's already an MSI for it) please search AppDeploy for 'gap capture'. It's been done to death.
Posted by:
pjgeutjens
13 years ago
as I say, there's already an MSI for it
look for a link at the bottom of http://desktop.google.com/ that says "business version" or something along those lines (it's in Dutch for me). That will give you the msi.
Posted by:
timmsie
13 years ago
Posted by:
crazypackagers
13 years ago
Posted by:
timmsie
13 years ago
Posted by:
anonymous_9363
13 years ago
I m using GOOGLE DESKTOP 5.9 which is an exe and not vendor msi.Holy friggin' cow...is that "crazypackagers" as in "totallyunabletoreadpackagers"?
Posted by:
crazypackagers
13 years ago
Posted by:
anonymous_9363
13 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.