In This Section

Receiving Agent Running Message but Connection Fails in Testing

Receiving a Connection Failure Message

Experiencing a Channel Security Error within the PerfectForms™ Application

Error Codes are Showing Up in the Agent Log File

Problem Description:

When accessing the Agent URL after installation, user sees the "agent running" message as expected but receives a 'Connection Failed' message given when testing the connection from the Dashboard.

Resolution:

Edit Apache security settings.

For Apache servers behind firewalls, Apache's security settings prevent cross-domain transfers. On Apache, you need a .htaccess file in the /root folder that includes the following settings:

SecFilterEngine Off

SecFilterScanPOST Off

This issue is documented on the following URL for various backend set-ups: http://www.element-it.com/OnlineHelpMulti/Troubleshooting.html

Problem Description:

Receiving a Connection Failure message.

Resolution:

Possible resolutions include the following:

Problem Description:

The user is presented with a Connection Communication Error from within the PerfectForms™ application that looks as follows:

Agent communication error:

faultCode:Channel.Security.Error

faultString:'Security error  accessing url'

faultDetail:''Destination: DefaultHTTP'

Resolution:

Possible resolutions include the following:

Problem Description:

Error codes are showing up in the Agent Log file.

Resolution:

These errors are displayed in the agent's log files. Error messages offer valuable details in case of SQL exceptions. As these are specific error messages for each database server type and each database structure, the list will not include all possible errors. Along with these messages, more details are provided by the Java Virtual Machine based on which specific Java class crashed.

Example:

The following message occurred in a log file:

ERROR: SQLException:Invalid object name 'Orders'.                

    net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)                

    net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816)                

    net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254)                

A SQL exception message is displayed whenever and wherever an object is not found in the database structure. The above error occurred because a wrong name was entered for one required object ("Orders"). It cannot be determined if the required object was a table, a stored procedure, or some other object. What can be understood from this message is that a wrong name for one database object was entered into the connection action detail screen on the PerfectForms™ Connections Dashboard.

Reference additional error codes and their descriptions in the table below.

210

IP address is not allowed

Client's IP address is not allowed by a rule in the config.xml IP filters.

Special attention:  If Use Proxy was selected in the connection details screen on the PerfectForms™ Dashboard, the IP that will make the call to the agent and will be filtered by config.xml IP filter is the IP of the PerfectForms™ Application Server, not the client's computer IP.

When Use Proxy is enabled, the request to the agent is only made by the PerfectForms™ Application Server.

211

User not authenticated to the agent

Username/password from config.xml are not the same as the ones that user entered.

211

Not Authenticated

Username/password from config.xml are not the same as the ones that user entered.

212

NO Database permissions

Agent-authenticated user is not allowed to access the specified database from config.xml. Check the 'logins' attribute of <database ...> tag in config.xml

213

No permissions for accessing table ... from database ...

Agent-authenticated user is not allowed to access the specified database TABLE from config.xml. Check the “tables” attribute of <database ...> tag in config.xml

213

Permission denied for text file ...

Agent-authenticated user is not allowed to access the specified TEXT FILE from config.xml. Check the “tables” attribute of <database ...> tag in config.xml

216

Permission denied for distinguishedName ... from LDAP tree ...

Agent-authenticated user is not allowed to access the specified LDAP DN NODE from config.xml. Check the “tables” attribute of <database ...> tag in config.xml

217

Required Agent version ... is not installed

Agent version incompatibility. Client application version requires a specific agent version.

230

Invalid Context

There is a problem with the JVM (Java virtual machine) or Tomcat server.

231

Invalid connection parameters

Datasource type is not present in the request. This means the connection is not correctly configured in the connection details screen (if this occurs in ConnectionEditor when using

"Check" button) or the connection is not correctly saved (if this occurs in Player or MainEditor).

231

Invalid Request Parameters

Database ID and/or Datasource ID are not in the request. This means the connection is not correctly configured in the connection details screen (if this occurs in ConnectionEditor when using

"Check" button) or the connection is not correctly saved (if this occurs in Player or MainEditor).

231

Datasource type not defined

Request to the agent does not contain a datasource type. This occurs when the connection

details are not correctly saved.

231

No parameters in request

Request to the agent does not contain any send or return parameters. This may be a Flash player problem or bad connection action configuration.

232

Datasource NULL

Datasource was not found in the config.xml file. This means the connection is not correctly configured/saved or config.xml file has changed without synchronizing connection actions details.

233

Database NULL

Database was not found into config.xml. This means the connection is not correctly configured/saved or config.xml file has changed without synchronizing connection actions details.

234

DatabaseList NULL

Databases list of the specified datasource was not found into config.xml. This means Connection is not correctly configured/saved or config.xml file has changed without synchronizing connections/actions details.

235

Invalid Database Type

Database type was not found. This means the connection is not correctly configured/saved or config.xml file has changed without synchronizing connection actions details.

237

SQLException ...

Specific SQL error. Database server problem or connection action parameters are not correct.

238

Invalid SQL statement

A SQL statement that was executed contains syntax errors. This means that connection actions are not correctly saved or that the user changed the connection action details but didn't synchronize those changes with the form's Connect command. The original SQL statement is described in log files just above the error entry.

238

Exception in BaseRequestProcessor

Error occurred in class BaseRequestProcessor.java. More details should be provided by the entire error log message.

238

Exception in SqlRequestProcessor

Error occurred in class SqlRequestProcessor.java. More details should be provided by the entire error log message.

239

Invalid SQL statement

A SQL statement (used in the LDAP jdbc driver) that was executed contains syntax errors. This means that connection actions are not correctly saved or that the user changed the connection action details but didn't synchronize those changes with the form Connect command. The original SQL statement is described into log files just above the error entry.

239

Exception in LdapRequestProcessor

Error occurred in class LdapRequestProcessor.java. More details should be provided by the entire error log message.

243

ExecuteStartTransaction: NO TRANSACTION REQUESTED!

No specific request for this transaction was made from the client side. Transaction will not be started.

244

ExecuteCommitTransaction: NO TRANSACTION REQUESTED!

No specific request for this transaction was made from the client side. Transaction will not be committed.

245

ExecuteRollbackTransaction: NO TRANSACTION REQUESTED!

No specific request for this transaction was made from the client side. Transaction will not be rolled back.

246

No SQL statements to execute transaction!

No SQL statements to be executed in the transaction. Check if there are any Connect commands between the Start Transaction command and Execute Transaction command for the same transaction.

247

Invalid SQL statement

A SQL statement (used in the CSV jdbc driver) that was executed contains syntax errors. This means that connection actions are not correctly saved or that the user changed the connection action details but didn't synchronize those changes with the form Connect command. The original SQL statement is described into log files just above the error entry.

248

Exception in GetCsvColumnNames service ... FILE NOT FOUND ...

The file specified into config.xml for Text File connection was not found under specified location. Check if the file exists and has read/write permissions.

249

Text file is empty or cannot be opened

Text file used by the connection doesn't contain the HEADER line or file doesn't have Read permissions.

NO ERROR CODE

... Network connection error ....

There is something wrong with the database server. Check if server accepts TCP/IP requests.

NO ERROR CODE

... IO Exception ....

There is something wrong with the database server. Check if server accepts TCP/IP requests.

NO ERROR CODE

... Unknown server host name ...

Database Server not found on the available network connection or it is a server instance which is not supported yet.