ONLINE HELP
 WINDEV, WEBDEV AND WINDEV MOBILE
This content has been translated automatically.  Click here  to view the French version.
Help / WEBDEV administrator / WEBDEV Application Server administrator / Tutorial: Configuring a machine in IIS
  • "Unable to add the programming" error during the remote setup of a site (via FTP)
  • Error "WDMetabase.dll: Meta_bInit failed" or meta database update failure with IIS7
  • Checking configuration
  • HTTP error 404 the diagnostic on AWP
  • In Windows 2008
  • Problem while displaying the images and the styles
  • The Active WEBDEV Pages do not operate
  • The URL rewriting of Active WEBDEV Pages does not operate
  • The short URLs of dynamic sites do not operate
  • The access to the network data does not operate
  • The URL with just the domain name does not start the WEBDEV website
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
Common problems
"Unable to add the programming" error during the remote setup of a site (via FTP)
The following error may occur during the remote setup of a site on a Windows 2008 server on which the UAC mechanism of Windows is enabled:
Unable to add schedule due to the following error:
Launching the executable 'C:\WEBDEV30\WD300Admin.exe /MAJDIFFEREE /DATE=201101260949 /CMD="/INSTALL/AJOUTALIAS/NOMSITE/domaine.com/"' failed for the following reason:
The requested operation requires an elevation.
When this error occurs, the site setup is performed at 95% on the server: only the setting of Web server (IIS) was not performed. If the WEBDEV administrator is manually started on the server, the name of your site will be displayed in the list of sites.
To fix this configuration problem, the setting of Web server must be "manually" forced for your site. To do so, see "Checking the configuration". The diagnostic of your site will detect this configuration error of Web server and it will propose to repair it automatically.
Reminder about the UAC mechanism (User Account Control):
With the UAC mechanism of Windows, each executable is run with the privileges granted to its parent without possibility to elevate these privileges. Furthermore, the shell (iexplore) is started with a "filtered token" (for the administrators), which means that it has the rights but not the privileges.
Therefore, an application started in an administrator session will not have the administrator privileges and it will not be able to write into the registry of "HKEY_LOCAL_MACHINE" branch. If the application start requires an elevation of rights (like the WEBDEV administrator), Windows displays a confirmation dialog box (mandatory), with eventually the input of a login and administrator password if the current account is not administrator. When the start is performed by another application, no dialog box is displayed but the start fails: this is what happens here.
To avoid this error, the UAC must be disabled. To disable the UAC, a simple method consists in running MSCONFIG.EXE (Start .. Run, then type MSConfig.exe). Then, in the MSConfig window, go to the "Tools" tab and select "Disable User Account Control" (Caution: you must reboot the computer).
Error "WDMetabase.dll: Meta_bInit failed" or meta database update failure with IIS7
This error occurs when the compatibility of metabase IIS 6 is missing from the IIS configuration.
To fix this error, see:
Checking configuration
For any problem, check the configuration from the interface of WEBDEV administrator in the "Advanced" tab.
  1. In the "Host name/IP" controls, specify the domain name of your site. The next operations will be performed on this address, make sure that it is the address of virtual server to check. If there is a single virtual server, leave "localhost" in the control in order for the test to use the default site.
  2. Click the "Diagnostic" button.
  3. To check the server configuration, check "General configuration of WEBDEV Application Server". Then, click "Start the check"
  4. To check the configuration of a specific site, select the name of site to check in the combo box and click "Start the check".
  5. The WEBDEV administrator detects the problems and proposes to fix them automatically.
HTTP error 404 the diagnostic on AWP
In the event of an HTTP 404 error on the AWP protocol (or on the URL HTTP://Server/WD300AWP/WD300Awp,exe/VERSION), check that WEBDEV CGIs are authorized.

In Windows 2008

In the IIS console (started by "Inetmgr" from the Windows Start menu), select:
  • the computer in the treeview (on the left),
  • the "Restriction of requests" icon (on the right).
    Make sure that the CGIs of WEBDEV Application Server are found in the list. These elements must be "Authorized". Otherwise, these elements must be added.
On the virtual site, check in the "Handler mappings" section whether the CGI executables are allowed. Otherwise, add these elements (during the addition, check "Execution" in the "Restriction of requests", "Access" tab):
Problem while displaying the images and the styles
Problem: Site launches but images are not displayed. The styles are not good: there are javascript errors on the pages. Some actions do not operate.
Solution: Site alias (virtual directory) not defined or incorrect. Use the site diagnostic from the WEBDEV administrator. You can also:
  • start the IIS console ("Inetmgr" from the Start menu of Windows)
  • check whether the alias named liked the _WEB site is found and whether it is not in error.
The Active WEBDEV Pages do not operate
Problem: AWP extension association with WEBDEV Application Server not defined.
Solution: Use WEBDEV Application Server diagnostics.
The URL rewriting of Active WEBDEV Pages does not operate
Problem: AWP extension association with WEBDEV Application Server is incorrectly defined.
Solution: Use WEBDEV Application Server diagnostics from WEBDEV Administrator.
Caution:
  • The site must have been deployed at least once by a setup (physical media or FTP) in order for the WEBDEV Application Server to have been configured (no simple manual copy).
  • In the directory corresponding to the path of the rewritten URL, a ".WDConfig.awp" file (which contains information on the site name, such as SITED * <NomDuSite>) must be present.
  • If the URL contains characters (such as +), some Web servers may consider that it is a double escape and trigger an HTTP 404 error (or an HTTP 404.11 error). In this case, the Web server must be configured to allow the double escape.
    For example, for IIS 7 (2008): On the website go to "Request filtering", then to the link on the right "Modify function parameters..." and check the "Allow double escape" box.
The short URLs of dynamic sites do not operate
Problem: IIS 6 on Windows 2000 or 2003 is not supported. The association between the AWP extension and the WEBDEV Application Server is not defined properly.
Solution: Use WEBDEV Application Server diagnostics.
The access to the network data does not operate
Problem: The site cannot access data on another machine. The Windows account that runs the site is a local guest account, therefore without any possibility to access the network shares.
Solution: To access network resources, change the Windows account associated with the virtual website to a domain account.
The URL with just the domain name does not start the WEBDEV website
Once the WEBDEV website is deployed, the URL with the domain name must directly redirect to the WEBDEV website.
With IIS 7 in Windows 2008, you can specify a redirection rule, for example the address of the desired dynamic WEBDEV website:
Special cases: Display of static or AWP pages with only the root domain:
  1. Modify the base directory of the virtual site (wwwroot). This base directory must point to the _WEB subdirectory of the desired WEBDEV website. If the site supports only one language, it is possible to point to the language subdirectory. Example with IIS 7 in Windows 2008:
  2. Specify the default page (Default.html or index.htm). Use:
    • a page that redirects to the URL of dynamic site
    • your static home page if you have one (the name given by WEBDEV is correct by default).
      Note: If your first page is an Active WEBDEV Page, make sure that its name corresponds to the name of a document of the Web site.
Let's see some methods to create a page that opens or redirects to a dynamic WEBDEV website:
  • In the static home page of WEBDEV website, type the following code in the onload code of the page:
    DynamicSiteDisplay("MYSITE")
  • Example of HTML code for a static "index.htm" page with FrameSet. With this type of page, the URL displayed by the browser will remain unchanged (only the domain name) even when navigating in the site. This example is not suitable for a site with .awp pages or for which a lot of SEO is required:
    <html>
    <head>
    <title>My site</title>
    <meta name="url" content="/WD300AWP/WD300AWP.EXE/CONNECT/MONSITE">
    <meta name="robots" content="all">
    </head>
    <frameset rows="100%,0" frameborder=no border=0>
    <frame name="SITE" src="/WD300AWP/WD300AWP.EXE/CONNECT/MONSITE">
    <frame name="NONE" src="" scrolling="no" noresize>
    <noframes>
    <body><a href="/WD300AWP/WD300AWP.EXE/CONNECT/MONSITE">
    Your browser does not support the frames, click here to start the site</a>
    </body>
    </noframes>
    </frameset>
    </html>
  • Example of HTML code for a static "index.htm" page for redirection by meta tag:
    <html>
    <head>
    <title>My site</title>
    <meta name="url" content="/WD300AWP/WD300AWP.EXE/CONNECT/MONSITE">
    <meta http-equiv="refresh" content="0;URL=/WD300AWP/WD300AWP.EXE/CONNECT/MONSITE">
    <meta name="robots" content="all">
    </head>
    <body><a href="/WD300AWP/WD300AWP.EXE/CONNECT/MONSITE">
          The site is loading, click here to force a reload</a>
    </body>
    </html>
Minimum version required
  • Version 23
Comments
Click [Add] to post a comment

Last update: 09/30/2024

Send a report | Local help