Troubleshooting

Cannot connect to Web service.

Verify the URL to the Web service was entered correctly, including the port number and the path.

Encounter SOAP errors when creating a Remedy application.

This typically occurs in the Web Service Element Definition window if you are using a WSDL file that is configured to not produce output. For example, if you are creating an update application, the WSDL file does not need to produce output. You can ignore the message and continue to the next screen in the wizard. If you can save the mobile application, it will be created.

Encounter CCL, SOAP, and Java errors when creating a Remedy application.

These are typically Remedy messages in SOAP format that are not processed by Unwired Accelerator. You can ignore these and continue the procedure. As long as you can save the application successfully, the mobile application is created. If you cannot save the mobile application later, it indicates another problem.

The namespace in XML returned by Remedy 7.0.x Web service is inconsistent with what is defined in the WSDL.

Verify that patch 4 is installed properly on Remedy AR system 7.0.x. See “Configuring for Remedy AR system version 7.0”.

You do not have write license

You do not have write permissions for one more Remedy fields. See the Remedy system or database administrator.

Entry does not exist in database

The default value you supplied for the input parameter does not exist in the Remedy database. Supply a valid value.

Cannot get the linked parameters to work.

It is important for parameters to use the same display name used in the Display_Name column in the data source table, or the linked parameters will not work. Check the Display_Name values used in your applications and the data source table to make sure values are consistent. Review “Using the linked parameters application in the update and insert applications”.

Some display names do not show up in the deployed application on a BlackBerry device.

If the display names of parameters do not match the output display name in the XSLT template definition, parameters will not show up in the mobile application on the BlackBerry device. Check the display names used in the XSLT template (see “Optional. Viewing the XSLT template definition”) against the display names in your applications, and make the appropriate changes.

The application created from a Remedy Web service does not preview correctly with the default JSP template.

You may need to develop a custom JSP template to handle special formatting requirements for a particular Remedy Web service. See the UA 8.0 Developer’s Guide for information on JSP templates.

Remedy mobile applications do not work after the Remedy AR system server was changed.

Try flushing the cache in the Remedy middle-tier server. See the Remedy documentation for instructions.

Remedy mobile applications do not work after a Web service was changed.

Try cleaning up the “generated” and “XSD” directories in %SYBASE%\tomcat\webapps\onepage\WEB-INF.