unable to deploy application thru GP
I created an MSI using the repackager, and it works as a stanalone install with no issues. Since runas doesnt work with the MSI and my users arent local admins, I figured I could deploy using GP. I set up a test policy, and created the package thru the computer settings, and then tried to install. I get 3 errors in the eventlog.
Event 101 - The assignment of application (app) from policy (GP) failed. The error was : fatal error during installation
Event 103 - The removal of ....... (Same as above)
Event 108 - Failed to apply changes to software installation settings. software changes could not be applied........
I tried as an standard user and as an administrator same issue and errors. The share where the msi is located is open, and all users can access, I even gave everyone full access to test. I am not sure of why this is happening, I searched, but couldnt find anything relevant. Any thoughts?
Event 101 - The assignment of application (app) from policy (GP) failed. The error was : fatal error during installation
Event 103 - The removal of ....... (Same as above)
Event 108 - Failed to apply changes to software installation settings. software changes could not be applied........
I tried as an standard user and as an administrator same issue and errors. The share where the msi is located is open, and all users can access, I even gave everyone full access to test. I am not sure of why this is happening, I searched, but couldnt find anything relevant. Any thoughts?
0 Comments
[ + ] Show comments
Answers (12)
Please log in to answer
Posted by:
dvdzonenz
14 years ago
does it install manually (using an admin account)?
try using xp sp3 (Assuming you are using xp sp2). It happened once to me.
try using xp sp3 (Assuming you are using xp sp2). It happened once to me.
Posted by:
DeployTech
14 years ago
Do you have a current\new version of Windows installer (I think 4.5 is the latest) installed on your clients?
Posted by:
anonymous_9363
14 years ago
Neither XP SP3 or WI 4.5 will make any difference.
Enable the MSI logging policy and re-try the install. The engine will deposit a bunch of MSI log files in %SsytemRoot%\TEMP which you'll need to search through. Once you locate the log file, look for the text 'Return value 3.' The dozen or so lines above and below will highlight where the error is actually occuring and you can work back from tehre.
This policy is an all-or-nothing policy so remember to turn it off when you're done, as it logs ALL MSI activity.
Enable the MSI logging policy and re-try the install. The engine will deposit a bunch of MSI log files in %SsytemRoot%\TEMP which you'll need to search through. Once you locate the log file, look for the text 'Return value 3.' The dozen or so lines above and below will highlight where the error is actually occuring and you can work back from tehre.
This policy is an all-or-nothing policy so remember to turn it off when you're done, as it logs ALL MSI activity.
Posted by:
aschwartz
14 years ago
Thanks -
It does install manually using an admin account.
SP3 is installed.
I enabled logging, and then logged in again, and the same errors came up in the event log.
I checked the temp folder, and found 2 msi*.log files. they both have the same contents:
=== Verbose logging started: 6/22/2009 11:55:42 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: \??\C:\WINDOWS\system32\winlogon.exe ===
MSI (c) (6C:80) [11:55:42:984]: User policy value 'DisableRollback' is 0
MSI (c) (6C:80) [11:55:42:984]: Machine policy value 'DisableRollback' is 0
1: 2905 2: C:\WINDOWS\system32\appmgmt\MACHINE\{f2353a9b-fc01-4d7a-9890-58b473223ffb}.aas
MSI (c) (6C:80) [11:55:43:015]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (c) (6C:80) [11:55:43:031]: DoAdvertiseScript is returning: 1603
=== Verbose logging stopped: 6/22/2009 11:55:43 ===
Any idea what this means?
It does install manually using an admin account.
SP3 is installed.
I enabled logging, and then logged in again, and the same errors came up in the event log.
I checked the temp folder, and found 2 msi*.log files. they both have the same contents:
=== Verbose logging started: 6/22/2009 11:55:42 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: \??\C:\WINDOWS\system32\winlogon.exe ===
MSI (c) (6C:80) [11:55:42:984]: User policy value 'DisableRollback' is 0
MSI (c) (6C:80) [11:55:42:984]: Machine policy value 'DisableRollback' is 0
1: 2905 2: C:\WINDOWS\system32\appmgmt\MACHINE\{f2353a9b-fc01-4d7a-9890-58b473223ffb}.aas
MSI (c) (6C:80) [11:55:43:015]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (c) (6C:80) [11:55:43:031]: DoAdvertiseScript is returning: 1603
=== Verbose logging stopped: 6/22/2009 11:55:43 ===
Any idea what this means?
Posted by:
cub1c
14 years ago
Any news on that because I have the exact same thing! It's a problem with package created with AppDeploy because package made with WinINSTALL LE work perfectly.
Posted by:
anonymous_9363
14 years ago
Does the GP package have 'Ignore language' set? If not, GP will check the MSI's ProductLanguage property and will abort the install if that language isn't present on the target. I think, though, that you should see an error in the Event Log to indicate that.
Posted by:
cub1c
14 years ago
Ignore language is on and it doesn't work.
There is the error with Event ID 101, 103 and 108 in the application logs, that just says error during installation and nothing more. And no information in the MSI logs either.
There is the error with Event ID 101, 103 and 108 in the application logs, that just says error during installation and nothing more. And no information in the MSI logs either.
Posted by:
anonymous_9363
14 years ago
Ignore language is on and it doesn't work.What does this mean? That it was not set and that setting it made no difference?
Is this a User or Machine GP?
Does it install OK from the command line when run on a user machine but with an account which has admin-level privileges?
Posted by:
revizor
14 years ago
Test your package under local System account: Schedule interactive task "cmd.exe" under "at" command:
[font="courier new"]at HH:MM /interactive "cmd.exe"
Call unattended install of your MSI. If it fails, attempt attended install to see if it provides you with more clues...
[font="courier new"]at HH:MM /interactive "cmd.exe"
Call unattended install of your MSI. If it fails, attempt attended install to see if it provides you with more clues...
Posted by:
cub1c
14 years ago
Ignore language is on means that the check box for the Ignore language is checked. Check or unchecked, it doesn't change anything. It's a simple package for testing (Flash Player 10). I tried other small software and it doesn't work either. It's a Machine GP.
Like I said, the exact same package with WinINSTALL LE installs perfectly. I really doubt it's a GP problem. Why would a MSI done with WinINSTALL works but not the one done with AppDeploy?
Like I said, the exact same package with WinINSTALL LE installs perfectly. I really doubt it's a GP problem. Why would a MSI done with WinINSTALL works but not the one done with AppDeploy?
Posted by:
anonymous_9363
14 years ago
Well, in my previuos response I was tempted to add what I'm going to say now. That is, with regards to tools, you get what you pay for.
If you used proper tools (no offence to AD's author, BTW), you would find a utility to compare two MSIs (or MSI to MST). As it is, you're probably stuck with opening both in Orca or InstEdit and going through the tables one by one to see where the differences are.
If you used proper tools (no offence to AD's author, BTW), you would find a utility to compare two MSIs (or MSI to MST). As it is, you're probably stuck with opening both in Orca or InstEdit and going through the tables one by one to see where the differences are.
Posted by:
cub1c
14 years ago
Ok thank you very much. I understand what you mean. But in rather small deployment and the small number of package to deploy, or even just for beginners, free solution are always a good start. But yes, I can see why I wouldn't recommend those for advance/big deployment.
I'll continue making some tests see if I can come with a solution for others experiencing the same issue.
I'll continue making some tests see if I can come with a solution for others experiencing the same issue.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.