Shibboleth IdP 4.1.4 on Windows 2019 server

[Michael Grady]

> On Aug 4, 2021, at 7:17 AM, Rod Widdowson <rdw at steadingsoftware.com> wrote:
> 
> Running shibd_idp from the command line can sometimes also provide useful feedback (if the issue is lost dependencies).

Yes, I tried that, and all it gave me was this:

PS C:\Program Files (x86)\Shibboleth> procrun\amd64\shibd_idp.exe
%1 is not a valid Win32 application.
Failed to run service as console application.

procrun\shibd_idp.exe  would run fine.

After installation, this is what sc reported for the service entry:

PS C:\Program Files (x86)\Shibboleth> & sc.exe qc shibd_idp
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: shibd_idp
        TYPE               : 10  WIN32_OWN_PROCESS
        START_TYPE         : 2   AUTO_START
        ERROR_CONTROL      : 0   IGNORE
        BINARY_PATH_NAME   : "C:\Program Files (x86)\Shibboleth\ProcRun\amd64\shibd_idp.exe" service shibd_idp
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : Shibboleth IdP Daemon
        DEPENDENCIES       :
        SERVICE_START_NAME : LocalSystem

Until I change the binPath for that, it would not start from Service Manager. (I also had to lower the memory for Java, it says it can't allocate 2gig of object storage, starts fine with 1 gig.)

In Task Manager, if I display the Platform column, almost everything is running as 64 bit, only a very few entries list 32 bit (right now that includes shibd_idp.exe.)

--
Michael A. Grady
IAM Architect, Unicon, Inc.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20210804/66ad6cae/attachment.htm>