Troubleshooting

Here are some solutions to some problems that you might experience when you try to log on to a generated web page.

TIP: You are advised to set the Log Level attribute to INFO in the publication configuration. This results in error messages that are more elaborated and informative.

Problem

Error message after log on attempt:

Failed to create Socket connection. Connection refused: connect Try again

Solution

Install and start the Rules Service with at least one Rules Engine running.

Problem

In the Rules Service configuration pages, I cannot enter an application name because the dropdown list for the <Application Name> field is empty.

Solution

In the Authorizer, change the Owner for the application that you want to start to the user name for the database account.

Only those applications are listed in the <Application Name> dropdown list.

Problem

Error message after log on attempt:

Failed to connect to Engine. The application "APPNAME" is not known

Solution 1

(Re-)configure the Rules Service. Reset application name to APPNAME, and click Run.

Solution 2

Check if the publication (in the Web Designer) has the correct Connection Specifier:

jdbc:jrec:APPNAME@localhost:7777

If not, change this Connection Specifier and re-publish. The application for the Rules Service must be the same as the application in the Connection Specifier string.

Problem

Error message after log on attempt:

No suitable driver. Internal Error.

Solution

Check the Security Settings for the publication folder. This folder must be readable by Everyone.

Problem

Error message after log on attempt:

Object Required

OR:

HTTP 500.100 - Internal Server Error - ASP error

Internet Information Services

Error Type: Server object, ASP 0177 (0x800401F3)

/Persons.asp, line 12

Unspecified error

Solution

After installation of USoft Series, the USoft Page Engine must be registered with Microsoft Component Services.

See also Help topic: "How to Register the USoft Page Engine On Windows".

Problem

Error message after log on attempt:

com.usoft.XMLParser.USXMLDOMException:

Cannot create a Microsoft DOM Document : Class not registered.

Solution

For the USoft Web Server you require the Microsoft XML Core Services 4.0

When installing USoft Series, you will be asked to install the Microsoft XML Core Services 4.0 SP1.

Problem

Error message after log on attempt:

006~ASP 0177~Server.CreateObject Failed~800401f3

Solution

The cause of this problem may be that the published ASP page contains a different version number in its content than the installed component, e.g.

Set USComVM = Server.CreateObject("USoftComJavaCall.ComJavaCall.6")