Troubleshooting : Solutions to problems
  
Solutions to problems
These are some solutions to problems that might occur when using Focal Point®.
A “transaction rollback” error occurs
In the user interface, a message indicates that a business rule stopped responding.
The input parameters to the business rule might be wrong. Also, the attribute or element that triggered or is referenced from the business rule might be broken or contain unexpected data.
Solution: Reproduce the steps that lead to the error. Obtain the stack trace that is in the log file, and then send the file to UNICOM Systems, Inc. Support.
A “null pointer exception” error occurs
A null pointer exception is a runtime error.
Solution: Reproduce the steps that lead to the error. Obtain the stack trace that is in the log file, and then send the file to UNICOM Systems, Inc. Support.
A “batch indexing failed” error occurs
A “batch indexing failed” error message is written to the logs when the search index fails to be updated.
This failure usually occurs when data cannot be accessed in a workspace. The index queue might contain references to elements, a workspace, or attributes that do not exist or that contain unexpected data.
This error might occur if you add an attribute to a module and delete that attribute before the search index is updated with the new attribute.
Solution: Obtain the stack trace that is in the log file, and then send the file to UNICOM Systems, Inc. Support. You might need to provide UNICOM Systems, Inc. Support with additional information from SQL queries.
Information is displayed inconsistently in Focal Point®
When you save a filter or load the tree view, information might be displayed inconsistently.
Focal Point® uses Java applets and runs JavaScript to display the information in the browser. The inconsistencies might be caused by corrupted caches in the browser and Java. Also, the Java might be corrupted.
Solution
1 At the command prompt, run this command:
java -version
Focal Point® 6 supports Java 1.6.
2 Clear the Java cache: click Start > Control Panel > Java > Delete files.
3 Clear the browser cache:
In Microsoft Internet Explorer, click Tools > Internet Options > Delete Files (Delete all offline content), and then click Delete cookies.
In Mozilla Firefox, click Tools > Clear Private Data.
4 If the issue persists, uninstall and reinstall Java.
Generated files, such as workspaces and Microsoft Excel files, cannot be downloaded in Focal Point®
When this error occurs, a message states that the files cannot be downloaded from the Focal Point® server.
This error occurs because cache policies conflict between the files that are generated by Focal Point® and the web server or proxy that is used by the browser.
Solution: The default cache control policy for downloading files is set to public.
You can change the cache control policy by running an SQL query.
Restriction: In the SQL query, the CC parameter value must be supported and defined by w3c protocols. For more information, see:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9
1 In Focal Point®, click the Settings menu icon, and then, from the Advanced group, click SQL.
2 Enter this SQL query:
set value=CC where name = 'cache.control'
3 Clear the browser cache.
While using the search function, a message indicating that the search index is not created is displayed
By default, the search index is created or updated when elements are added or modified. But sometimes you might get this error.
Solution: The global administrator can recreate the search index when only a few users have logged in. To recreate the search index:
1 Log in as a global administrator.
2 In the Workspaces menu, select the View All link.
3 Click the Actions menu corresponding to the workspace that has the search issue.
4 Select Recreate search index, and click OK.
Note The duration of the indexing operation is based on the size of the workspace.
During the indexing operation, you cannot use the search feature. Also, the server performance is affected
The pop-up window to select the work item type hangs and the integration fails.
After editing the Integration Link attribute, when you click Create New r use a view command to publish elements, the pop up window to select the work item type hangs.
Solution: If the Title or Description attributes contain more than 2000 characters, they are not automatically populated to the title and description fields of work item type. Copy the content of Title and Description manually.
Report generation in Focal Point® using Rational Publishing Engine found impacted on upgrading Focal Point®
After upgrading Focal Point® from version 6.5.2 to version 6.5.2.2, the Focal Point® reports generated using Rational Publishing Engine are found to be blank.
Solution: New parser has been introduced to fix this problem. The following workaround can also be tried:
1 Log in as a global administrator.
2 From the user menu, click Administration.
3 Select Application > Data access. The Data Access Settings page is displayed.
4 Click the Edit icon for the Enable REST field selection field, and specify No to disable the setting.
“An error occurred” message is displayed randomly when Microsoft Internet Explorer is used as the browser for IBM Focal Point®
An error message is displayed when the proxy settings enabled in the browser prevents some of the Java applets and JavaServer Pages (JSP) from displaying the content.
Solution: The proxy settings in Microsoft Internet Explorer can be modified to resolve this issue:
1 Click Tools > Internet Options.
2 Click the Advanced tab.
3 Under HTTP 1.1 settings, select Use HTTP 1.1.
Note Do not select the Use HTTP 1.1 through proxy connections.
The Edit icon disappears and an “Unable to edit fields under Applications ->Mail in Internet Explorer" message is displayed
The application settings in Focal Point® cannot be configured when Microsoft Internet Explorer is used as the browser. The Edit icon disappears and an “Unable to edit fields under Applications ->Mail in Internet Explorer” message is displayed when a field in the Application > Mail page or the Application > Support and Contact page is selected.
Solution: To resolve this issue, enable the Native XMLHTTP support in Microsoft Internet Explorer:
1 Click Tools > Internet Options.
2 Click the Advanced tab.
3 Under Security, select Enable native XMLHTTP support.
.xslx files are downloaded as .zip files when Microsoft Internet Explorer is used as the browser for Focal Point®
.xslx files in Focal Point®are downloaded as .zip files.
Solution: Modify the security settings for the internet, the local intranet, and the trusted sites in Microsoft Internet Explorer:
1 Click Tools > Internet Options.
2 Click the Security tab.
3 Select Internet from the section Select a zone to view or change security settings.
4 Click Custom Level.
5 Select Disable for Open files based on content, not file extension.
6 Click OK to change the setting, and then click Yes when asked to confirm.
7 Select Local intranet from the section Select a zone to view or change security settings.
8 Repeat steps 4 through 6.
9 Select Trusted sites from the section Select a zone to view or change security settings.
10 Repeat steps 4 through 6.
11 Click OK.
12 Restart the computer.
See also
Troubleshooting Focal Point®