Web Jetadmin install fail

[JW24]

I'm attempting to install Web Jetadmin 10.4 on a Windows 7 SP1 x64 client. I receive the following error as it appears the install is almost complete:

Product: HP Web Jetadmin 10.4 -- Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action WjaHttpCfg8140Add, location: C:\Program Files\HP Inc\Web Jetadmin 10\bin\WjaHttpCfgSilent.exe, command: -a http://+:8140/ "NetworkService"

Any ideas on what I can do to prevent this from happening?

Thanks for your help.

[DGoode]

I'm getting the same message when I try to install on my print server that is running Server 2016. I know this is an old post, but any solution to the issue? Thank you.

[JW24]

Unfortunately no, I have not yet resolved the issue. I've moved on, but still open to getting it fixed.

[DGoode · Accepted solution]

I was able to get the software to install by installing a fresh version of Server 2016 on the server without any "STIGS". I'm not sure what kind of environment you're in, but we have to comply to certain settings that need to secure the system. So in this case, we installed the OS then installed the software, then applied the STIG settings/group policies, and was successful that way.

[JW24]

Similar environment here. Makes sense that would be the issue. I don't need it that bad though. Thanks for the info.

[Rhasputin]

I ran into this same issue as well in regards to STIG settings and found a fix for it without reimaging.  I had delete a key that was put in place by applying the STIG so if this key does not exist on your system already, then the fix won't work or be applicable for you.

Navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework

And delete the registry key: AllowStrongNameBypass

Hope this saves you a reimage.

[BrianD92]

This fix worked for me however I had to make an exemption in group policy for my server prior to it actually working. Once the installation was complete I was able to re-enable the policy and everything was in working order. Thanks for the tip!