PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Error messages
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Error messages that can be displayed in the browser
Overview
This help page presents the different error messages that can be displayed in the browser.
Error messages
The error messages that can be displayed in the browser are as follows:
ErrorsDesignation
Error opening access log. Check setupThis message is displayed when starting a WEBDEV site.

This message is displayed by the OmniHTTPd server. This message can have several causes:
  • the OmniHTTPd server is installed in a directory that is using long names.
    Solution: Re-install the OmniHTTPd in a directory that does not use long names.
  • several OmniHTTPd servers are opened.
    Solution: Close all the opened servers and restart a single instance of OmniHTTPd.
  • the "Log file" directory does not exist.
    Solution: In the control panel of the server, disable all the "Log File" directories and restart the server.
HTTP/1.0 404 Object not found or Resource not foundThis message is displayed in the Internet browser when starting the site.

This message is caused by a bad configuration of the Internet server. It means that the server cannot find the CGI protocol manager.

Solution: Check the configuration of the Internet server used, especially:
  • the virtual directory (or alias) pointing to the directory containing the CGI protocol manager, WD230AWP.EXE
  • the registry key of CGI protocol manager must be equal to WD230AWP.EXE.
Reminder: The information regarding the WEBDEV setting is saved in the registry, in the following entry: "HKEY_LOCAL_MACHINE\SOFTWARE\PC SOFT\WEBDEV\23.0".
Internet Explorer cannot open the Internet site...This message is displayed by the Internet browser when running a WEBDEV site if no Internet server is started when running the site.

Solution: Start an Internet server before starting the WEBDEV site.
Could not resolve local name, Error code: 11004This message is displayed when starting the OmniHTTPD server.

Solution:
  1. Open the properties of the OmniHTTPD server (right-click the icon of the server in the taskbar).
  2. Display the "Server" tab.
  3. Uncheck "Lookup Site Address (Dynamic)".
  4. Validate and restart the server.
RunTime Error .WDD missing or invalid JW06 nameIf you are using a WEBDEV site in development mode:
  • Open your project in WEBDEV.
  • Save your project.
If you are using a site installed on the WEBDEV application server:
  • Recompile your project ("Project .. Compile the project").Recompile your project: on the "Project" pane, in the "Project" group, expand "Recompile and synchronize" and select "Recompile the project".
  • Regenerate the library.
  • Re-create the setup of your site.
  • Re-install the site on the server.
Note:
  • In all cases, check whether the setup directory of the example corresponds to the directory used by the WEBDEV administrator ("Applications" tab).
  • Otherwise:
    • delete the site of the administrator.
    • in the development version, open your project in WEBDEV and click the "GO" icon.
    • in the deployment version, re-install the site.
1, ERR_MISSING_PAGEThe request is incomplete. It contains no information about the context.

This error message is displayed during a click on a link that uses an invalid syntax or that points to an HTML page that does not exist.

Solution: Check the syntax used for the link and the existence of the page called.
4, ERR_BUTTON_EXPECTEDThe request is invalid. The action to perform is missing.

This error message can be displayed in several cases:
  • a link is specified in the HTML page with the [%URL()%] syntax without button name in the parameters.
    Solution: In the parameters of a link, specify the name of the button in the WEBDEV page corresponding to the action to perform.
  • a click was performed on a button that only exists in the HTML page. This button does not exist in the page.
    Solution: The buttons found in the HTML page must have an equivalent in the corresponding WEBDEV page.
  • a form validation is performed without using a button (JavaScript code) or a validation is performed via the ENTER button.
    Solution: A button must be used to perform the validation of a form.
    Tip: To allow the Web user to validate a form via the ENTER key, define a button whose type is "Send the value of controls to the server" in the WEBDEV page and associate this button with the ENTER shortcut ("Details" tab of the control).
5, ERR_NO_CURRENT_PAGEThe site did not operate properly because no page was returned (EndProgramm may have been called without returning a page).

This error message occurs when a WEBDEV site is closed without using the HTML page indicating the end of connection.
To avoid this message, a page indicating the end of connection must be displayed by PageDisplay or EndProgram.
6, ERR_PARSERSyntax error in the HTML file named <FILE_NAME>, line <LINE_NUM>.

An invalid syntax was used in the HTML page displayed.
Check the code found in the HTML controls or the HTML code inserted into the controls of your WEBDEV site ("Advanced" tab in the description window of the controls).
7, ERR_BAD_ACTIONThe special action named <ACTIONNAME> is unknown.

A specific action was defined by the WD_ACTION_ parameter in the HTML page but invalid parameters have been used. You must correct the syntax used to define the action.
This error can occur when implementing a link used to open or close a secure transaction. Check and correct the syntax used.
8, ERR_NO_PAGEYou want to work on the <PAGE_NAME> page. It does not exist or it is hidden by an object of another type (a control for example).

The WEBDEV page used is hidden by another object on the server: the corresponding HTML page cannot be displayed.
This error can occur when using the "Back" and "Next" keys of the browser.
Solution: Check the management mode of the browser "Back" key in your site.
9, ERR_BAD_PARAMETERThe <COMMAND_NAME> command does not contain the proper parameters.

A specific action was defined by the WD_ACTION_ parameter in the HTML page but invalid parameters have been used. You must correct the syntax used to define the action.
This error can occur when using a custom action defined for a button or for a link, or when using a link to open or close a secure transaction. Check the syntax used.
10, ERR_BAD_FILEThe <FILE_NAME> file cannot be opened (and therefore returned).

The HTML file that must be displayed in the browser does not exist.

Solution: Check the presence of the file in the site directory.
11, ERR_WWADMIN_EXISTThe WEBDEV administrator was already started. A single one is allowed on each computer.

Several sessions of the WEBDEV administrator (WD230ADMIN.EXE) cannot be started on the same computer.
12, ERR_NO_WWADMINThe management program of WEBDEV was not started.

The access to a dynamic WEBDEV site can be performed only if the WEBDEV administrator (WD230ADMIN.EXE) is started and run on the Internet server.

Solution: Check whether the WEBDEV administrator is started on the server.
13, ERR_OUT_OF_MEMORYInsufficient memory to perform the operation.

Insufficient memory to run the program.

Reminder: The resource required per connected Web user:
For each connected Web user, you must plan for:
  • about 400 KB of RAM per connection, in addition to the memory required by the server.
  • about 1 MB of disk space per connection.
For example, for 20 parallel connections, you must plan for:
  • RAM: 67.8 MB (7.8 MB of RAM for the site, 60 MB for the NT server)
  • Virtual memory: 84 MB (20 MB for the connections, 64 MB for the NT server)
14, ERR_MAX_CONNECTIONThe connection is refused because the maximum number of connections (<NB_CONNECTION>) allowed by the Webmaster for this site has been reached. Retry later.

This message is displayed on the Internet browser when the number of connections to the dynamic WEBDEV sites installed at the hosting company is greater than the total number of authorized simultaneous connections.

Solution: Check the configuration of the WEBDEV administrator at the hosting company.
15, ERR_BAD_COMMANDLINEThe command line passed to the (<ENGINE_NAME>) engine is invalid. The >SWITCH_NAME> switch is missing.

A WEBDEV site is started from an incorrect command line (bad arguments, ...).

Solution: Check the command line used to start your WEBDEV site.
17, ERR_BAD_CONFIGThe configuration of the <SITE_NAME> site is incorrect for the <VALUE_NAME> value.

This error is caused by a wrong setup of the site in the registry. You must:
  • re-install the site.
  • correct the configuration of the site in the registry.
Reminder: When installing a WEBDEV site, a new entry is created in the registry. This new entry is created in the following key:
"HKEY_LOCAL_MACHINE\SOFTWARE\PC SOFT\WEBDEV\23.0\<ProjectName>".
The name of the project and its directory are specified.
18, ERR_BAD_WEBDEV_CONFIGWrong overall configuration of WEBDEV. The <KEY_NAME> key is missing or incorrect.

The WEBDEV setup was not performed properly in the registry.

Note: The information regarding the WEBDEV setting is saved in the registry in "HKEY_LOCAL_MACHINE\SOFTWARE\ PC SOFT\WEBDEV\23.0".
An entry is created for each new WEBDEV site.
19, ERR_BAD_CONTEXTThe context to which this request refers (<CONTEXT_NAME>) does not exist (or does not exist anymore). You may have been disconnected.

This message is displayed by the Web browser when the WEBDEV engine is not active anymore.
The WEBDEV engine is not active anymore in several cases:
  • the idle time was exceeded: the Web user was disconnected.
    Solution: Reload the site and configure (if necessary) a longer idle time before disconnection in the options of the administrator.
  • the HTML page was not refreshed (in test mode only)
    Solution: Refresh the display of the page via the "Refresh" button in the Internet browser.
20, ERR_BAD_URLThe <URL_NAME> URL is not valid.

This message is displayed when an invalid URL is used in the HTML page.

In WEBDEV, a URL is valid if it starts with:
  • the following syntax: [%URL()%] for example:
    <a hRef="[%URL()%]?Table=[%TABLE%]&RESULT">
  • a "/" sign: for example:
    <a hRef="/Img_WEB/Hello.gif">
  • the http protocol: for example:
    <a hRef="http://flop.www/pages/Index.html ">
21, ERR_INTERNALInternal error: <ERROR>

A very rare error occurred.
Solution: Try to establish a reproduction protocol for this error and contact the Free Technical Support.
22, ERR_TIMEOUT_REQUESTThe request did not respond within the time-out (<TIMEOUT> seconds).

An action was requested from the Internet server and the response time has exceeded the time-out specified in the WEBDEV administrator (WD230ADMIN.EXE). The Web user was disconnected.
Solution: Check whether the response time is long enough.
23, ERR_SESSION_CLOSEDYou have been disconnected.

The Web user was disconnected by the WEBDEV administrator.
Reminder: From the WEBDEV administrator, you have the ability to disconnect:
  • a Web user from a WEBDEV site.
  • all the Web users from all the WEBDEV sites available at the hosting company.
24, ERR_CLOSED_PAGEThe request refers to the <PAGE_NAME> page that does not exist anymore. (it may have been closed by the process).

This error means that the page corresponding to the HTML page is not available anymore. During a process, the current page may have been closed by a procedure.
Solution: Check the code of your site, especially the existence of the context for the page used (with ContextExist for example).
25, ERR_MSG_BOXThe site has generated the following error message <ERROR_MESSAGE>.

A dialog box was displayed on the server, locking the site. WEBDEV automatically closes the message box and the corresponding message is displayed in the browser.
Solution: Correct the site according to the error message displayed. In most cases, the error corresponds to a programming error found in the site.
26, ERR_BAD_SERIAL_NUMBERThe serial number is invalid.

The serial number used for WEBDEV is invalid.
27, ERR_SYSCALLFAILEDThe call to the <FUNCTION_NAME> system function failed.

The site tries to use a WLanguage function. The resources required by this function (WEBDEV DLL) are not accessible.
Solution: Check whether all the DLLs required by your site are installed on the Web server.
28, ERR_CANNOT_OPEN_FILEThe <FILE_NAME> HTML file cannot be opened.

The HTML file corresponding to the WEBDEV page or requested by PageDisplay is not accessible and it cannot be opened.
30, ERR_NO_PROJECTThe <PROJECT_NAME> project does not exist (in WDP or in WDL).

Check the configuration for this project.
The site is not installed properly (corresponding files not copied onto disk or invalid corresponding entry in the registry). Re-install the site and/or check its configuration in the registry.

Reminder: When installing a WEBDEV site, a new entry is created in the registry. This new entry is created in the following key:
"HKEY_LOCAL_MACHINE\SOFTWARE\PC SOFT\WEBDEV\23.0\<ProjectName>".
The name of the project and its directory are specified.
32, ERR_NO_APPLICATIONThe <SITE_NAME> site is unknown: it was not configured for WEBDEV.

The site is not installed properly (invalid correspondence with the registry). Re-install the site and/or check its configuration in the registry.

Reminder: When installing a WEBDEV site, a new entry is created in the registry.
A new entry is created in the following key:
"HKEY_LOCAL_MACHINE\SOFTWARE\PC SOFT\WEBDEV\23.0\<ProjectName>".
The name of the project and its directory are specified.
33, ERR_BAD_DLLEXEThe <DLL_NAME> DLL is not compatible with this version of WEBDEV.

This message is displayed if:
  • a conflict occurs between the DLLs installed on the computer.
  • the WEBDEV DLLs are not installed properly. Reinstall WEBDEV.
34, ERR_NO_DLLEXEUnable to load the <DLL_NAME> DLL.

Some of the WEBDEV DLLs required by the WEBDEV administrator and by the WEBDEV engine have not been copied onto the setup computer.
Solution: Reinstall WEBDEV.
35, ERR_CANNOT_LAUNCHThe engine was not started for the following reason: <REASON>.

The WEBDEV engine was not started.
36, ERR_UNKNOWNUnknown error.

A very rare error occurred.
Solution: Try to establish a reproduction protocol for this error and contact the Free Technical Support.
37, ERR_NO_TABLEThe <COMMAND_NAME> command operates with tables and <CONTROL_NAME> is not a table.

The WD_ACTION_ parameter was used on a control other than a TABLE control.
Solution: Check the custom actions found in your page.
38, ERR_ALREADYCONNECTEDThe connection is refused because you are already connected to this site.

The maximum number of connections for the same Web user on a WEBDEV site has been reached. The Web user must disconnect from one of the sites.

Reminder: the maximum number of connections for the same Web user to a WEBDEV site is configured in the WEBDEV administrator.
39, ERR_NOTACTIVATEDThe module was not enabled (it must be reinstalled).

WEBDEV was not installed properly. Reinstall WEBDEV.

Reminder: There is:
  • WEBDEV Development Version, used when developing a WEBDEV site.
  • WEBDEV application server. This server must be installed at the hosting company when deploying a WEBDEV site.
40, ERR_NOTAVAILABLEThis command is available in development mode only.

WEBDEV "Deployment Version" is used to deploy a WEBDEV site.

Solution: Install the "WEBDEV application server" to deploy a WEBDEV site.
41, ERR_NOTADEVVERSIONThis version cannot be used in development.

The WEBDEV application server is used to develop a WEBDEV site.

Solution: You must install WEBDEV Development Version to develop a WEBDEV site.
42, ERR_LOADMOREDLLThe <COMPONENT_NAME> user component cannot be loaded.

A user component was defined in the registry by the MOREDLL entry (to optimize the management of AS/400 for example). This registry key is not valid.
43, ERR_TIMEOUTINITThe engine was not initialized within the time-out (<TIMEOUT> seconds).

This error, that occurs when starting the WEBDEV engine, can have several reasons:
  • using a response time that is not long enough between two requests.
    Solution: Modify the setting of the administrator.
  • the server is saturated.
    Solution: Use a larger server or use parallel servers.
46, ERR_UPDATING_SERVERA server update is in progress. Please retry later.

This error message signals to the Web users that they cannot connect to their site because an update is currently performed on the server.
To display this message on the computer of the Web users during an update and to avoid any new connection to a server site, check "Lock the server (for an update)" in the WEBDEV administrator.
47, ERR_TEST_WDPThe test mode cannot operate without the project (.WWP) and its pages.

Note: The test mode does not use the WDL.
A test of the site built by WEBDEV "Development Version" requires the presence of the project on the computer (.WWP file). If this file is not found, the test cannot be run.
48, ERR_SYNCHRONIZATIONThe requested action cannot be performed. Indeed, the [BACK] or [NEXT] button of the browser was used on a page containing dynamic data. The visible data is no longer synchronized with the data processed on the server. The server is going to return the latest data. Check the page displayed and retry your request.

Technical note:
  • this message can be configured (synchronization code).
  • to avoid this message, a specific process must be found in the synchronization code.
The page context found on the server and the page displayed in the browser on the computer of the Web user are out of synch: the data displayed does not correspond to the data found on the server.

This message is displayed when the "Back" key of the browser was pressed by the Web user.
We recommend that you thoroughly run the test of a WEBDEV site before deploying it, especially the use of the browser "Back" key. WEBDEV proposes an automatic method for managing the "Back" key of the browser.
49, ERR_BAD_APPLICATIONThis site is not allowed to be used with this WEBDEV version.

You are trying to use a WEBDEV site with a limited server.

To use your WEBDEV site, you must own the WEBDEV application server.
50, ERR_NO_END_TAGSyntax error in the <FILE_NAME> file. The end tag for the <NAME_HTML_TAG> tag is missing.

An error was found in the HTML file that must be displayed: a beginning tag is found without an end tag. The HTML page cannot be interpreted by the WEBDEV engine. You must correct the corresponding code. This error can occur when using:
  • HTML controls
  • JAVA controls
  • FLASH controls
  • HTML code inserted into the WEBDEV controls ("Advanced" tab)
  • HTML code inserted into the page ("Advanced" tab)
Check the HTML code found in these controls.
51, ERR_LAUNCH_FAILEDError while starting the site.

The site cannot start because it is automatically closed.
Solution: Check whether EndProgram is not used in the initialization code of the project (or any other function or process that stops your site).
52, ERR_CANNOT_CREATE_TMPUnable to create the temporary file named <FILE_NAME>. Test canceled.

This error occurs when running the test of a WEBDEV site on a development computer. This error occurs because:
  • no temporary directory is found on the development computer.
    Solution: Create a C:\Temp directory for example.
  • the space is not sufficient on the development computer.
    Solution: Free some space on the development computer.
53, ERR_CANNOT_RUN_EXPLORERUnable to start the application associated with .htm, File: <FILE_NAME>, Code: <CODE>.

This error occurs when running the test of a WEBDEV site in the following cases:
  • the browser was closed as soon as the test of the site was started (by a GO of the project for example).
  • when running the GO of the project (or page), WEBDEV cannot start the default browser associated with the HTML pages.
Solution: Check whether a browser is associated by default to the ".HTM" files.
54, ERR_BAD_CONTEXT_INVALIDThe context to which this request refers (<CONTEXT>) is unknown. The server may have restarted since your last request.

This error can occur when the WEBDEV administrator was stopped then restarted or if the Web server was rebooted. These actions may have been performed by the monitoring tool (WWSURVEILLANCE).
55, ERR_BAD_CONTEXT_INTERNALInternal error: Invalid context (<CONTEXT>). (status = <STATUS>)

This error occurs when the context corresponds neither to the current site nor to the current page.
56, ERR_DISCONNECTED_BY_ADMINYou have been manually disconnected by the WEBDEV administrator. {RECONNECT}

This error occurs on the browser of the Web user when:
  • the Web user was disconnected from the site by the WEBDEV administrator ([Disconnect] or [Disconnect all] button)
  • the Web user was disconnected from the site by the remote WEBDEV administrator.
By default, the Web user is automatically reconnected to the site after 3 seconds.
57, ERR_DISCONNECTED_TIMEOUTYou have been disconnected because your last request is too old (time-out = <TIMEOUT> sec) {RECONNECT}

This error occurs on the browser of the Web user when the response time of the last action performed is greater than the time configured in the WEBDEV administrator. By default, the Web user is automatically reconnected to the site after 3 seconds.
58, ERR_DISCONNECTED_RELOGThe context to which this request refers is not valid anymore, it was replaced by a new context during your last connection to the site {RECONNECT}

This message is displayed when the Web user clicks the "Back" key of the browser for example: the Web user is positioned an old site page and the corresponding context does not exist anymore.

By default, the Web user is automatically reconnected to the site after 3 seconds.
59, ERR_BAD_CONTEXT_FOUNDThe context to which this request refers (<REFERENCE>) is invalid (your session was ended for an unknown reason). {RECONNECT}

This message is displayed when the Web user clicks the "Back" key of the browser for example: the Web user is positioned on an old page of the site, coming from a previous connection.

By default, the Web user is automatically reconnected to the site after 3 seconds.
60, ERR_DISCONNECTED_ERRORThis session was ended further to the following error: <ERROR>

This message is displayed when the Web user tries to reconnect to a WEBDEV site that ended by an error for example.

By default, the Web user is automatically reconnected to the site after 3 seconds.
61, ERR_DISCONNECTED_EXECThe session does not exist anymore (you have exited from it or it was ended 'normally') {RECONNECT}

This message is displayed when the Web user tries to use a WEBDEV site that is already ended for example. For example, the Web user clicks the browser "Back" key to go back to a site page while he previously clicked the [Exit] button to exit from this site.

By default, the Web user is automatically reconnected to the site after 3 seconds.
62, ERR_BAD_VERSION_RQSInvalid version number of dialog structure. This problem comes from a mix of incompatible versions of WD230Session/WD230AWP/WD230Admin.

To fix it, reinstall WEBDEV.
The versions of the different elements found in the WEBDEV application server are not compatible: reinstall WEBDEV.
63, ERR_DISCONNECTED_UPDATEYou have been disconnected because the site was updated on the server. {RECONNECT}

This message is displayed when the Web user was disconnected for an update.

Reminder: when updating a WEBDEV site remotely, the Web users connected to this site are automatically disconnected.

By default, the Web user is automatically reconnected to the site after 3 seconds.
64, ERR_FORBIDDEN_UPDATEWEBDEV is configured to forbid the remote update.

This message is displayed when trying to perform a remote update. The administrator is not configured to allow the remote update.
65, ERR_FORBIDDEN_INSTALLWEBDEV is configured to forbid the remote setup.

This message is displayed when trying to perform a remote update. The administrator is not configured to allow the remote setup.
Minimum required version
  • Version 10
Comments
Click [Add] to post a comment