Trying to set up a WC app on a new server using the .NET handler. Basic operations seem to work, except I get a 401 error when I hit: /wconnect/admin/wc.wc?ModuleAdministration.wc

However, /wconnect/admin/wc.wc?wwmaint~showlog comes up fine, which tells me the .wc extension is mapped correctly. What else would prevent just that page from working?

FWIW, the legacy link /wconnect/wc.wc?_maintain~ShowStatus also throws a 401 error.

--stein

The URL is wrong. It should be:

/wconnect/admin/ModuleAdministration.wc

All of the admin links are routed to dedicated 'page links' - no wc.wc or wc.dll can be used with those routes.

The last link requires 2 underlines wc.wc?__maintain~ShowStatus. But you shouldn't use that anyway. Use ModuleAdministration.wc.

+++ Rick ---

Sorry, I did a poor cut and paste job when composing the message. For the actual test I was using the correct URL:

Make sure you're using a recent version of WebConnectionModule.dll and that .wc is mapped as a scriptmap.

+++ Rick ---

Webconnectionmodule.dll is dated 4/16/2018.

As I mentioned, other links on the admin page are working (e.g. wconnect/admin/wc.wc?wwmaint_showlogError)

..which implies that the problem is not tied to the .wc extension.

--stein

Not running in .NET Mode?

+++ Rick ---

Output of Request.ServerVariables("DLLVersion"):

Web Connection 6.20 (.NET Handler)

I don't know then.

Make sure the script maps are pointing at the right place and are defined at the right IIS level etc. - double check the .wc script map in IIS.

+++ Rick ---

Contents of web.config shown below. Handler mappings look correct to me - the .awp links to my app work fine, so don't see why anything would be different for .wc pages.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <configSections>
    <section name="webConnectionConfiguration" type="System.Configuration.NameValueSectionHandler,System,Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
  </configSections>
  <system.webServer>
    <rewrite>
      <rules>
        <clear />
        <!-- Insert rules for this application (if any) **below** the "clear" -->
      </rules>
    </rewrite>
    <httpErrors>
      <remove statusCode="404" subStatusCode="-1" />
      <!--			<error statusCode="404" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr\" path="404.htm" responseMode="File"/> -->
      <error statusCode="404" prefixLanguageFilePath=".\.\custerr\" path="404.htm" responseMode="File" />
    </httpErrors>
    <handlers>
      <add name=".AWP_wconnect-module" path="*.awp" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode" />
      <add name=".WC_wconnect-module" path="*.wc" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode" />
      <add name=".WCS_wconnect-module" path="*.wcs" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode" />
    </handlers>
  </system.webServer>
  <webConnectionConfiguration>
    <add key="MessagingMechanism" value="Com" />
    <add key="ComServerProgId" value="aw3.acewebServer" />
    <add key="ServerCount" value="2" />
    <add key="AutoStartServers" value="False" />
    <add key="ComServerLoadingMode" value="LoadBased" />
    <add key="TempPath" value="c:\temp\wc\" />
    <add key="TempFilePrefix" value="WC_" />
    <add key="Timeout" value="60" />
    <add key="UseCustomManifestLoading" value="False" />
    <add key="AdminAccount" value="" />
    <add key="AuthenticationMode" value="Default" />
    <add key="AdminPage" value="/wconnect/admin/admin.aspx" />
    <add key="ExeFile" value="C:\inetpub\aceweb\aw3.exe" />
    <add key="UpdateFile" value="" />
    <add key="LogDetail" value="False" />
    <add key="ValidateRequest" value="False" />
    <add key="PassAspNetContext" value="False" />
    <add key="MessageDisplayFooter" value="Page generated by Web Connection IIS Connector Module" />
  </webConnectionConfiguration>
</configuration>

I don't know then. If other .wc links are working I don't see why ModuleAdministration.wc isn't working unless the URL is incorrect or it's pointing at a virtual folder that's not configured. Check the IIS settings make sure your virtual is pointing at the right location and that you don't have the amdin folder configured separately. Something is screwy in the configuration if that file is not found.

Note that you can call ModuleAdministration.wc from anywhere - it doesn't have to be in the admin folder. So maybe try it in the same location the other wc.wc links are working.

+++ Rick ---

So maybe try it in the same location the other wc.wc links are working.

The other links work from the admin folder:

http://xxxxxxxxxxx/wconnect/admin/wc.wc?wwmaint~showlog

Or from the virtual root: http://xxxxxxxxx/wconnect/wc.wc?wwmaint~showlog

ModuleAdmin throws a 401 from either location: http://xxxxxxxxxxx/wconnect/admin/ModuleAdministration.wc http://xxxxxxxxxx/wconnect/ModuleAdministration.wc

Note that this is an unsecured test server - is there anything in the ModuleAdmin code that requires https?

How is that routine invoked? There does not appear to be a standalone file named ModuleAdministration.wc.

--stein

Wait - a 401 is an Authentication error.

Make sure Basic Authentication and Windows Authentication are enabled. You cannot access the admin links in the DLL without being authenticated.

Make sure AdminAccount is not empty.

+++ Rick ---