Ending A Windows Installer Transaction Event Id 1042

Making statements based on opinion; back them up with references or personal experience.

This is MsiInstaller reconfiguring about a dozen products over and over, looping about every half-hour.

In essence this means that it will keep checking whether the files on disk and settings in the registry match what the respective package originally installed.

These checks are generally not performed for everything that the package installed, but for what is referred to as key paths.

Like the guy said, its like a humidifier and a dehumidifier fighting it out in the same room - or a dog chasing its own tail.

You dont get anywhere till the conflict is found and eliminated.

The MSI file will keep going this is my resource, I am changing it back over and over.

This path will not be found for another user logging on, and self repair results.

Another example is key paths set to folders that are not writeable for the System account.

Still another example is a key path set to a temporary file (which the system will delete eventually).

Unfortunately narrowing down which application is causing the problem is difficult.

But as documented in this other question below, you cannot use the Win32regAddRemovePrograms if you dont have SCCMSMS installed and even if you do would have to use Win32regAddRemovePrograms64 to get a list of 64bit programs.

I think the choice by Microsoft to do a repair check at the same time as responding to the query is just bad design.

A query should never cause changes to a system, that should be a different function (WMI method).

A sensible design could have included a periodic check into their system maintenance featrure of the newer operating systems, because thats also configurable and makes sense to usersadministrators.

But it did happen on all of our servers for many years (that was a major hit to performance now its confirmed).

So Ill have to check again on the newer 2008 R2 servers to see if this will be an ongoing production issue or not.

Weve got hundred of scripts and tools written by lots of different people for 1000s of packages.

So this behaviour should be fixed as a critical design fault by MS if its still occurring in 2008 R2 and other supported OS versions.

If you have sufficient reputation, you may upvote the question.

Alternatively, star it as a favorite and you will be notified of any new answers.

I dont have enough reputation to do any of the other things and had more useful information to add than just a comment.

Provide details and share your research But avoid Asking for help, clarification, or responding to other answers.

Ending A Windows Installer Transaction Event Id 1042