Known issues, limitations, and workarounds

Workaround You can change the QMS port value to the IDOL query port to bypass QMS. To do this, follow these steps:

1. Edit the /opt/hp/propel/search/search.yml file.

   # vi /opt/hp/propel/search/search.yml

2. Search for "qms" in the "idol" section, and then modify the port value from the QMS port (16000 by default ) to the IDOL Server port (14000 by default) as in the following example:

   …
   qms:
      hostname: <IDOL server FQDN>
      port: 14000
      oemKey: <oemKey value>
      executionIsolationThreadTimeoutInMillis: 80000
      threadpool:
        threadPoolCoreSize: 10
        keepAliveTimeMinutes: 1
   …
   

3. Run the following commands to restart the search service:

   # service search stop
   # service search start
   

Workaround Set the module name again.

Workaround Set the Document ID field another non-editable and unique field.

Workaround Set the display list and value list of the columns in the relevant forms manually.

Workaround Link the new external knowledge manually.

Workaround Add "eml" to the Skip these extensions field on the Type information tab for the corresponding knowledgebase definition.

Workaround You can direct the JVM to use /dev/urandom with the following directive:

Add the following line to the Server's sm.ini file:

-Djava.security.egd=file:/dev/urandom

Alternatively, you can add the following line to the jre/lib/security/java.security file:

securerandom.source=file:/dev/urandom

For additional information, see the following important third-party information:

http://bugs.java.com/view_bug.do?bug_id=6521844

http://www.2uo.de/myths-about-urandom/

Workaround See the corrected configuration topic at:

How to configure TSL/SSL for two-way authentication between Service Manager and Smart Analytics

Workaround Refresh the browser.

Workaround Add either the “Service” field or the “Service Display Name” field to both the view and the list of group-by fields.

Note that the “Service” field is preferred because this field is populated with CI Display Name values. There is no need to add the second level field, Service Display Name.

Workaround Make a call to the API after you set up the SM Hybrid environment.

Workaround Drill down into the Knowledge Maintenance page for the library to synchronize the index status into the Knowledge Management knowledge base.

Workaround You can apply a workaround if the following error appears in the application.log of the content server:

[1] 70-Error: Error: Attempt to open [ =…)0] failed. (No such file or directory). The file open mode [rb] does not permit creation of a new file.

In this case, modify the following parameters in the configuration of the content server, and then restart the content server.

[Server] Threads=x [AsyncActions] Threads=y let x+y<32

Workaround Refresh the status in library configuration.

Workaround Use Chrome 43 instead.

Workaround Add the fields used in the match criteria of the predefined filter in context aware search into the form of the current working ticket.

Workaround The fsyslib link refers to URLs with the "file://" protocol in search results. However, Firefox and Chrome do not open such links when they are clicked in the result page or in the pages that are originated from outside the local machine. This is a design decision made by those browsers to improve security. Internet Explorer supports this functionality by default.

Workaround Refresh the page in this case, and the list will be displayed. You can then select an item and save the record successfully.

Workaround To see all list items, clean the combo field and click the drop-down button again.

Workaround Purge data and reload preupg.bin again after preupg.bin is loaded for the first time.

Workaround  

1. Make the following changes to the SQLServer SQL:

   ALTER TABLE [932].[dbo].[OPERATORM1]
ADD RECORD_KEY varchar(60) NOT NULL DEFAULT('a')
 
ALTER TABLE [932].[dbo].[OPERATORA1]
ADD RECORD_KEY varchar(60) NOT NULL DEFAULT('a')
 
...
 
ALTER TABLE [932].[dbo].[OPERATORA5]
ADD RECORD_KEY varchar(60) NOT NULL DEFAULT('a')
 
UPDATE [932].[dbo].[OPERATORM1]
set
[RECORD_KEY] = [NAME]
 
UPDATE [932].[dbo].[OPERATORA1]
set
[RECORD_KEY] = [NAME]
...
 
UPDATE [932].[dbo].[OPERATORA5]
set
[RECORD_KEY] = [NAME]

2. Log on to Service Manager, open the Operator dbdict, and then import this new column.

3. Add this new column as the unique key.

Workaround Resize the details page to make it wider or use the horizontal layout.

Workaround Change the first unique key to the primary key for the modules that have this issue.

Workaround Manually recreate the primary key.

Workaround Change the Primary Key of the patchrelresults and scmessage tables to a Unique Key before you perform the unload.

Workaround Use Internet Explorer or Chrome.

Workaround Manually change the display option ID.

Workaround Reload the record.

Workaround In Condition Editor, set the value of User Option UO1 = {"1"} instead of User Option UO1 = "1"

Workaround Close the current change model and open it again to update the changes in the change model other than the task editor changes.

Workaround Manually update the "Open in Phase" and "Close by Phase" in Task Planner.

Workaround Use the "assignment" table instead of the "cm3groups" table in Service Manager Codeless.

Workaround Use the Chrome browser instead of Safari.

Workaround Start Service Manager as an administrator.

Workaround Shorten the legend label.

Workaround Check the inbox size periodically, and control the size manually.

Workaround Refresh the dashboard before exporting a report.

Workaround Set a dedicated Service Manager instance for the reporting schedule.

Workaround Click Tailoring > Database Dictionary, search for "htmltemplates," click the htmlcode field, and then change the SQL RC value to "true."

Workaround Click Tailoring > Database Dictionary, search for "kmknowledgebaseupdates,"click the recdata field, and then change the SQL RC value to "True."

If you already have garbled data in your search results, perform a full index against that library.

Workaround Modify the "operator" dbdict manually to fix this issue. First, create a new "a6" table in the SQL Tables tab. Then, modify the value of the "secRole" field from "m1" to "a6" in the Fields tab for both fields (array field and child field).

Workaround Do not use duplicate user options for items in one service catalog bundle.