Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ConfigureIIS / "Failed to read IIsWebs table" #884

Closed
wixbot opened this issue Aug 23, 2006 · 5 comments
Closed

ConfigureIIS / "Failed to read IIsWebs table" #884

wixbot opened this issue Aug 23, 2006 · 5 comments

Comments

@wixbot
Copy link

wixbot commented Aug 23, 2006

I believe that there is a problem with the Server
Custom Actions (SCA) that causes a MSI to fail with a
message of “Failed to read IIsWebs table” during the
install.

I first noticed this problem with release 4221 and
have validate that it still occurs up to the current
release 4415.

I have attached a log output of from the Windows
Installer. I noted that it first reported a buffer
overflow ostensibly during
CommitMetabaseTransaction.

I do not know where the problem may have been
introduced, but release 3309 did not experience the
problem.

I was able to work around the problem locally by
copying the 3309 versions of the server custom action
wixlib and dlls into my bin folder with the 4221
executables. I have not tried this workaround for
any other releases.

This is a paste from the log file of the
[ConfigureIIs] section where it appears that the
error occurs.

Action 17:33:48: ConfigureIIs. Configuring IIS
Action start 17:33:48: ConfigureIIs.
Action 17:33:48: StartMetabaseTransaction. Starting
IIS Metabase Transaction
Action start 17:33:48: StartMetabaseTransaction.
1: Starting IIS Metabase Transaction
Action ended 17:33:48: StartMetabaseTransaction.
Return value 1.
Action 17:33:48: RollbackMetabaseTransaction. Rolling
back IIS Metabase Transaction
Action start 17:33:48: RollbackMetabaseTransaction.
1: Rolling back IIS Metabase Transaction
Action ended 17:33:48: RollbackMetabaseTransaction.
Return value 1.
Action 17:33:48: CommitMetabaseTransaction.
Committing IIS Metabase Transaction
Action start 17:33:48: CommitMetabaseTransaction.
1: Committing IIS Metabase Transaction
Action ended 17:33:48: CommitMetabaseTransaction.
Return value 1.
ConfigureIIs: Error 0×8007007a: Insufficient buffer
to track all sub-WebSites
ConfigureIIs: Error 0×8007007a: Failed to find web
root
ConfigureIIs: Error 0×8007007a: failed to read
IIsWebSite table
Error 26002. Failed to read IIsWebs table. (-
2147024774 )
MSI (s) (DC!74) [17:33:50:711]: Product: Crawford
RiskTech Interfaces — Error 26002. Failed to read
IIsWebs table. (-2147024774 )

Action ended 17:33:50: ConfigureIIs. Return value 3.
Action ended 17:33:50: INSTALL. Return value 3.

Originally opened by dmadam from http://sourceforge.net/p/wix/bugs/655/

@wixbot
Copy link
Author

wixbot commented Sep 15, 2012

[Note that I'm only referring to v3, I haven't built/used
v2 in a while.]

The previous comment about the file scaweb.cpp is correct,
though the line numbers have changed slightly. I just built
from source (2006-10-04 at about noon PST) and the error
still happens.

Opening scaweb.cpp (Rev. 1.9) and commenting out lines 689

  • 693 seems to fix this. Sweet! Maybe a dev can delete
    these for an upcoming weekely release:

if (cSubKeysFilled >= countof(rgdwSubKeys))
{
hr = HRESULT_FROM_WIN32(ERROR_INSUFFICIENT_BUFFER);
ExitOnFailure(hr, "Insufficient buffer to track all sub-
WebSites");
}

-mattyj2001

@wixbot
Copy link
Author

wixbot commented Sep 15, 2012

The code is supposed to dynamically allocate enough memory
for the number of keys extracted and only fail if there
isn't sufficient memory. However, at line 679 of
scaweb.cpp, there is a test against countof(rgdwSubKeys).
Because rgdwSubKeys is a pointer, this will evaluate to 1,
so the code will work if there is only one subkey but fail
otherwise.

I suspect the code at line 679 is a leftover from when
rgdwSubKeys was a static array. This 'if' statement should
now be removed - the code further down at line 689 should
handle expanding the array and reporting an error if there
is a failure to allocate memory.

@wixbot
Copy link
Author

wixbot commented Sep 15, 2012

Originator: NO

Thanks to the pointers below, I've fixed up the code. Should be in the next weekly release.

@wixbot
Copy link
Author

wixbot commented Sep 15, 2012

/Log output from MSIEXEC

@wixbot
Copy link
Author

wixbot commented Sep 15, 2012

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 15 days (the time period specified by
the administrator of this Tracker).

@wixbot wixbot added this to the v2.0 milestone Dec 20, 2015
@wixbot wixbot closed this as completed Dec 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
@wixbot and others