package not installing due to error 1406

getting the following error in the event viewer when trying to install a package from patch manager. I have verified that administrators has full access to software in the registry and the username I use for patch manager is an administrator.

I can install other applications from patch manager. also I can install the msi directly on the pc.

Find more posts tagged with

Accepted answers

All comments

KMSigma.SWI

Alan - it's unclear to me - is this message on the client or on the server? How are you sending this package? Did you create a custom package, approve it, and then publish it for the clients? Are you sending the package directly from the Patch Manager console?

alan.dunne

I’m getting this error on the client machine.

It’s a custom package. I’ve published it to my wsus server band I’m using update management to download and install it on a couple of computers before I approve it for general install.

Each client machine gets the same error message.

KMSigma.SWI

What are the chances that this particular application cannot be installed as the "SYSTEM" user and needs to interact directly with the user profile on the computer?

I also did some quick digging around about the BigHand client. Are you passing "ALLUSERS=2" as part of the custom strings to the installer? (Reference)

LGarvin

Alan, this is an issue with the product installer, not WSUS or Patch Manager.

For whatever reason, the product installer is unable to create a Registry Value in the specified Registry Key (HKLM\Software\BigHand\TotalSpeech\v3).

The Administrators group, and the PM Credentials, will have no impact here. At this point the installer is executing in the SYSTEM context, inherited from the Windows Update Agent. This, itself, could be part of the problem. If the installer creates the HKLM\Software\BigHand registry subkey(s) without the proper ACLs (i.e. they've assumed that a *user* will be doing the installation), that would result in a write failure.

If that is the issue here (inspect the ACLs on the keys to be sure), you could use PackageBoot to pre-create the registry subkeys (which should also ensure that SYSTEM has the appropriate level of access since it would then be CREATOR).

alan.dunne

Thanks Lawrence

I had a look and system has full control over the keys. this package is an upgrade to software that is already installed if that makes a difference.

I have installed previous versions of the software with a group policy

alan.dunne

I am not passing "ALLUSERS=2" as part of the custom strings to the installer. would this work if I do?

alan.dunne

I have contacted bighand about the msi package and they have seen this before.

they recommend deleting the bighand key in the register.

Is there a way to do this with the package boot editor and if so can you please point me in the right direction

LGarvin

Great news that the vendor had useful information to share.

Yes, you can pre-delete the registry key by using a "Run a program" action in the "Before applying package" section:

Program Name: REG.EXE
Command-line parameters: DELETE {KeyName}
Select "Run program from specified directory" and choose the %SYSTEM% environment variable from the dropdown.
Select "Stop processing further actions if this action fails", since failure to delete the registry key would presumably cause an installation failure.