Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: Application Management|
Failed to apply changes to software installation settings. <failure consequence>. The error was <error message>.
|English: Request a translation of the event description in plain English.|
I tried every recommended solution and nothing was helpful. We have Win XP clients and 2008 R2 domsin controller. After a day of trying solutions I found the entry of giddyflea on EV100422 (Cannot open or run MSI files from network share) that there is a sysvol compatibility issue w/ Win XP and 2008 R2.
The solution is simple: Apply this GPO to your DCs --> Comp Config\Admin Temp\System\Net Logon\Sysvol Share Compat.
In my case, the solution was to go under Computer Configuration -> Software Settings -> Right-click Software installation -> point to New and then click Package. In the Open dialog box, type the full Universal Naming Convention (UNC) path to the shared folder that contains the MSI package that you want. For example: \\file server\share\file name.msi.
IMPORTANT: Do not browse to the location. Ensure that you use the UNC path to the shared folder.
As per Microsoft: "When Group Policy is configured to assign a software installation package to client computers, the administrator must specify a share path that hosts the software installation files. If the specified share is located on a Microsoft Windows NT 4.0 file server, the software installation policy may not be successfully applied. When programs are assigned to a computer, the computer tries to access the software installation share by using the credentials of the computer account. Microsoft Windows XP-based and Windows Server-based computers require Kerberos authentication. Windows NT 4.0 is not Kerberos-aware and can provide only NTLM authentication. Therefore, authentication is unsuccessful". See ME323304 to resolve this problem.
If this error appears when you try to install Windows 2000 Service Pack 3 (SP3) Finnish on your Windows 2000 Professional-based computer, see ME813807 for a hotfix.
- Error: "Not enough storage is available to complete this operation" - From a newsgroup post: "I've seen this problem reported a few times. This is caused when some of the appmgmt client's local state gets “corrupted” (for unknown reasons). You should also see a message something like this in the log: "Cannot initialize the data structure for local script <GUID>". The GUID will highlight the identifier for the app which is causing the trouble. It's failing out because a registry subkey can not be found. This was considered something that would indicate a catastrophic failure somewhere, which is why the lame out of memory error code was chosen (because we figured it would never be hit anyway). Possible way to fix this is to find the troubling key. This will be under HKLM (computer policy) or the user's HKCU key (user policy) Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\Appmgmt\\<GUID>.
It's failing because one of these named values under that key is not present: "Deployment Name", "GPO ID", "GPO Name", and “Product ID". All of these are the bare minimum the client code needs to proceed. One remedy is to simply remove the <GUID> key. The appmgmt client will forget about the app in that case. Or you could fix up the missing value (all reg_sz) manually".
- Error: "Access is denied" - From a newsgroup post: "Make sure the share and NTFS permissions on the deployment path are setup to allow "Authenticated Users" read access otherwise you will get this error". See the link to Error code 0x5 for more details on "Access is denied" errors.
- Error: “The installation source for this product is not available. Verify that the source exists and that you can access it” - From a newsgroup post: "This is the expected behavior on computers when Fast Logon Optimization is turned on. Configure the setting “Always wait for the network at computer startup and logon” to be enabled to resolve this problem. The system will always wait for network connections at startup (this is the same behavior as in Windows 2000).
Turning off Windows XP Fast Boot.
Create and link a GPO (preferable at the domain level) to simply enable the policy setting named "Always wait for the network at computer startup and logon". This policy can be found at Computer configuration -> Administrative Templates -> System -> Logon branch of Group Policy.
Remember, to force Windows XP machines to receive this policy (or any policy), the computer account must be within the site, domain or OU at which you set the policy. If you set the policy at the domain level, you are guaranteed that all Windows XP machines in your domain will get the policy.
After creating this policy you have to reset the computer in order for the policy to take affect. Then when you assign an application to a computer or user, the application will be installed after the first reboot".
- Error message: “Error applying transform“ - I resolved this problem by installing the Windows Installer 3.1 (v2) (see ME893803).
- Error: "There is no software installation data object in the Active Directory" - See ME315809.
- Error message: "There is no software installation data object in the Active Directory" - Try seeing if you get this error using different users/computers. I kept getting this error whenever I made a new GPO and pushed out software to my test user account. I finally deleted the account and recreated it with the same memberships and suddenly the GPOs worked.
- Error: "There is no software installation data object in the Active Directory" - This occurred after rebuilding group policies for the domain. After a few days of messing with policies, I finally figured out it was because the Default Domain Security Policy was linked to the domain in Group Policy. Once I corrected this, the errors went away and software installation continued normally.
- Error: "The installation source for this product is not available. Verify that the source exists and that you can access it" - As per Microsoft: "The machine account for the workstation does not have permissions to the share or file system that holds the source files for the package. When a workstation runs Group Policy, it does so in the context of the machine system account for the workstation".
We had the pleasure of finding out that this is not always the case, although it is in most instances. In the instance where a Group Policy prevents the DFS source server from updating its DNS automatically, we had an issue with its original build location pointing to a non-related DNS server of the domain. When moved into the domain that we were working in, the update of the servers DNS record was not complete as per the restriction of the policy. With no record, and no hard coded SPN CIFS for the DFS Service to direct the client to (our structure houses a DFS Store separate to the DFS service), the DFS Service could not find the source path for the application deployment. We manually created the SPN CIFS entry for the source server, which addressed the immediate needs, and then turned to our design for policies controlling the automatic update of DNS.
I had EventID 102 and 108 on a machine, when I tried to install the ISA Firewall Client from an assigned Software installation policy. All other computers in the domain installed fine; there was nothing different about the computer accounts. After I upgraded the machine from W2k SP3 to SP4 and this resolved the issue.
This error occurs on Windows XP Pro when you assign an application through Group Policy but you do not disable logon optimization, which is enabled by default. Also logs events 101 and 103 .To resolve, enable the policy setting "Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon". See ME305293 for more information.
Failure: "Software changes could not be applied. A previous log entry with details should exist", Error: "The group policy framework should call the extension in the synchronous foreground policy refresh". I often see this event the first time a Group Policy gets applied to a new computer. If I then reboot the computer, I get ID 308 "Changes to software installation settings were applied successfully". There must be something that trips it up the first time around.
Failure: "Software changes could not be applied. A previous log entry with details should exist", Error: "The installation source for this product is not available. Verify that the source exists and that you can access it". As per Microsoft: "The machine account for the workstation does not have permissions to the share or file system that holds the source files for the package. When a workstation runs Group Policy, it does so in the context of the machine system account for the workstation." See ME278472 for more details and resolution.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated