Receiving Error "1721" When Trying to Install Shibboleth IdP

[Omar E. Ramos]

Thanks Rod,

I ended up figuring out what the problem was yesterday.

Initially, I had added the JAVA_HOME system variable and set it equal to the Java Path " C:\Program Files (x86)\Java\jre7" (including the quotes).

The quotes around the path are what caused the issue, but it took me a while to realize this and what I had to do was to kill the process before it rolled back the updates, and then I tried running the install.bat that was in the IdP install folder and that gave me the error message due to the path (since it was concatenating the path above with the quotes to another relative path and that created an invalid path).

Once I noticed that I went back in and removed the quotes and the install went fine after that.

The reason the quotes were added initially is because in order to test the System Variable I typed %JAVA_HOME% at the command line and without the quotes it was showing an incomplete path "C:\ Programs " like it was cut off, so I assumed the quotes were needed since I've had to do similar stuff for paths in PowerShell, but it looks like in this case it wasn't needed.

Omar Ramos
Online Services Architect
Imperial Valley College
760-355-6500

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Rod Widdowson
Sent: Tuesday, March 05, 2013 2:41 AM
To: 'Shib Users'
Subject: RE: Receiving Error "1721" When Trying to Install Shibboleth IdP

As far as the OP question goes:

I'd suggest you grab a log from the install

C:\>  msiexec <whatever.msi> /lvm LogName.log

And see what is provoking the failure.  It's usually easiest to look at the log just before you click on OK to roll-back the install.

Something you might want to try is to run the installer from an elevated command line.  The toolkit used to build these installers predates vista and sits slightly uncomfortably alongside LUA.  I've not seen this error but it might be involved.

Taking another tack and looking at the error returned I don't know whether it is a hex number or decimal (I know it won't be octal):

kd> !error 0x1721
Error code: (Win32) 0x1721 (5921) - An error occurred while reading from a stream of data. An unexpected number of bytes was returned.
kd> !error 0n1721
Error code: (Win32) 0x6b9 (1721) - Not enough resources are available to complete this operation. 

For the former , check that the msi is intact via the SHA or signature, for the latter I have no real input beyond "add more resources...".

As far as the x64/ia386 debate goes:

The QuickInstaller (which is targeted at getting people, particularly generalists,  going quickly), deploys a system service stub which is linked against the 32bit java DLL, so we require the 32bit JVM (and test for it).

There were good reasons for this which I'll not go into.  In V3 I'll be writing a proper WiX Installer and many of these issues will go away.

Rod

> -----Original Message-----
> From: users-bounces at shibboleth.net [mailto:users- 
> bounces at shibboleth.net] On Behalf Of Peter Schober
> Sent: 04 March 2013 19:34
> To: users at shibboleth.net
> Subject: Re: Receiving Error "1721" When Trying to Install Shibboleth 
> Idp
> 
> * Paul Hethmon <paul.hethmon at clareitysecurity.com> [2013-03-04 20:28]:
> > As far as 32 bit vs 64 bit, I would never deploy anything on 32 bit 
> > anymore. Any hardware less than 4 or 5 years old should be 64 bit
capable.
> > Windows 32 bit Java has that 1.5 gig (roughly) limit. As you noted, 
> > 32
bit
> > can handle quite a bit of usage. Again, depending on the OP's 
> > circumstances, a few different choices now (while initially 
> > deploying), might make life easier later.
> 
> Sure. The afforementioned machines have been running like that for 
> years, I certainly wouldn't build any like that now.
> -peter
> --
> To unsubscribe from this list send an email to users- 
> unsubscribe at shibboleth.net

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net