Struck on wait EXE stage

[jmajeti]

We have performed the sppatchify on couple farms and both times it struck when executing the exe . we wait for couple hours to see if the executed finishes, but no luck.

Any recommendations

[jmajeti]

Its sitting idle in the background.

[spjeff]

Thanks for screenshot. Looks good overall. I have a few ideas:

1. Path contains spaces "D:\Software\SPPatchify (1)\" Try renaming folder to remove spaces. Should be supported OK, but helps rule out any folder path confusion.
2. PACKAGE.BYPASS.DETECTION.CHECK might be the reason why it gets stuck. Was in older releases. https://github.com/spjeff/sppatchify/blob/master/SPPatchify.ps1#L189

Please download the current latest ZIP.

https://github.com/spjeff/sppatchify/releases

[MarcoFi2]

I faced exact the same issue with version 0.67. The script got stucked at the bypass.detection.check. @jmajeti , just run the script with the parameter -bypass to run the package insatllation without the bypass check.

[spjeff]

Sounds good. Yes, I ran into the same issue.

I believe this was inadvertently added while troubleshooting a partial EXE install (force install, by pass check, and that's how it made it's way here.)

[jmajeti]

Hi Jeff,

Should I have to run the new version with any parameters ? I have tried the new version you have provided it passed the exe , but I think it just bypassed the exe installation but never installed . Later it struck at the get-spproduct command and never passed to the next step .

SPPatchify-2017-07-21-08-43-28.txt

[spjeff]

Are there any LOGs available in the folder on the remote machine "SP-DEVAPP1" under the "..\SPPatchify\LOG\" folder?

That's odd for sure. The EXE should be visible on Task Manager with CPU % moving (to show activity).

[zaarin2k]

I also have this issue with 0.67 trying to patch SharePoint 2013.

As with Triaxout above, using the -bypass argument allowed it to proceed.

[spjeff]

Thanks zaarin2k.

Please download the latest release and run a fresh new test. Should resolve any issues.