Is the Web Server Working?
The first thing to check is to see whether the Web Server and Web Connection are running.
The following assumes you're working with the Web Connection sample application at http://localhost/wconnect, but these steps can apply to your own applications in your own virtual directory and/or server.
First of all make sure that your Web server is running and that you can bring up a static page in your Web application.
and make sure that this page comes up. For the Web Connection demo the page to check is:
If this page doesn't come up your Web server is not functioning correctly. Check the IIS setup and configuration page first.
Next, check to see whether the Web Connection module is actually working. You can do this by hitting the Web Connection Module Administration link from the Administration page.
The URL for this operation is:
If the page comes up, the Web Connection module is working. Note that the .NET module and ISAPI pages look slightly different, but if it comes up the Web Connection server component is working.
Login Security Most likely you will have to provide credentials in order to access this page - use a valid server username and password to gain access to the admin and related links. Note that if you are on the actual server you might have to configure Loopback Protection on Windows Server.
In order for Web Connection to serve requests, make sure that the FoxPro server is actually running. In File mode this means you have to ensure that the server is started either via the EXE itself or from the FoxPro IDE by running the application.
If unsure that your EXE is running check Task Manager for your EXE. If it isn't, start it manually from Explorer or the Command Line.
You can use the
ServerCount(.NET Module web.config) or the
FileStartInstances(ISAPI wc.ini) configuration options to automatically launch Web Connection servers when IIS starts.
If you are running in COM mode you should hit one of the Admin links on the Admin page that returns the Web Connection Server status. These pages hit the Web Connection server and return various pieces of information from the Web Connection server.
For the sample application:
If this request comes up your COM server is loading and working.
If the COM server does not come up check task manager to see if the server EXE is listed. If it is the server might be coming up in COM but crashing during initialization. If that's the case, check the startup log
If your COM server doesn't come up you need to look at the COM error messag that is likely to display which might give more information.
Comment or report problem with topic