Latest windows 32-bit installer for salt-minion 2014.7.0 is broken

[TheBigBear]

I found that the 32-bit installer for salt-minion for windows installs the 64-bit binary of nssm.exe and therefore the windows service does not get created.

If I run the c:\salt\nssm.exe manually it reports:
This version of C:\salt\nssm.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the soft ware publisher.

I have also found that the key does not get deposited on the master and even a local call-up of

salt-call --local key.finger

does not result in the display of the fingerprint. not sure if this is anything to do with the above problem of nssm.exe being of the 64-bit variant?

[rallytime]

Thanks for the report @TheBigBear - the nssm.exe binary issue has been reported here: #18325, so that part of the issue is a duplicate.

However, the question about key.finger, I am not sure if that is related or not, but very well could be. I don't know very much about the windows packages. Maybe @UtahDave can weigh in here.

[TheBigBear]

@rallytime I copied a 32-bit binary in place to test if the key.finger issue is related and then ran the installer line to install the service and started the successfully created service and voila it uploaded a key to the master and the local salt-call --local key.finger also displayed the expected output.

So it was a related issue.

Thinking about it I guess the key get's only created upon the first startup of the salt-minion service and since nssm was not able to create the service using the 64-bit binary on a 32-bit windows the minion never got started up and hence the key did not even get created.
But evidently once the proper 32-bit nssm binary is in place from v 2.24 from http://nssm.cc/download all seems to be well.

[rallytime]

@TheBigBear Awesome! I am glad you were able to fix both problems by getting the correct 32-bit version of nssm. And that definitely makes sense with the key.finger command not working since there isn't a key yet.

I am going to close this issue as a duplicate in favor of the other issue. Thanks again!