Component | Issue | Description | Affected version | Addressed in |
BMC Remedy Approval Server | SW00523776 | When you create a Change Approval request, maximum 4000 characters are allowed in the Approver field. The characters are truncated if the limit exceeds. | 18.08 18.05 9.1.04 9.1.03 9.1.02 9.1.01 | |
BMC Remedy Approval Server | SW00524531 | There might be performance issues with the Approval server, for example, the Request Entry Console takes a long time to load data or the SQL queries take a long time to run on tables for the AP:Signature and AP:Detail-Signature forms. Workaround: To improve the query performance, you can add an index for the Approvers (13207) field on AP:Signature form using BMC Remedy Developer Studio. However, this option cannot be used on the Microsoft SQL Server database, as the composite index has a restriction of 900 bytes and the data from this field can cross the 900 bytes limit. Note: To improve the query performance on an Oracle database, you can use the option of adding indexes as there is no length restriction on Oracle database for creating index. | 18.08 18.05 9.1.04 9.1.03 9.1.02 | |
BMC Remedy AR System Server | SW00549518 | Bulk entry creation for MFS (multiform search) enabled field fails due to unique index violation on the ft_pending table. The following error is displayed: Error: com.bmc.arsys.domain.etc.ARException: ERROR (9713): The attempted bulk entry transaction failed due to an error in one of the individual operations. ERROR (552): The SQL database operation failed.; Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.2.v20130514-5956486): | 18.05 9.1.04 | 18.08 |
BMC Remedy AR System Server | SW00549254 | When you create a custom distributed mapping between two forms, a new entry is created instead of updating the existing entry on forms. |
18.05
9.1.04
| 18.08 |
BMC Remedy AR System Server | SW00549215 | The FTS scan interval function causes multiple indexer threads to index the same record at the same time. |
18.05
9.1.04
| 18.08 |
BMC Remedy AR System Server | SW00549103 | An error occurs when you use a case statement and add a financial field in the report. |
18.05
9.1.04
| 18.08 |
BMC Remedy AR System Server | SW00549061 | Cross communication between the server groups can occur because of the following reasons: When the backup of one Remedy environment is restored to another Remedy environment without cleaning the server group back end tables. When there is a network connectivity between two server groups. |
18.05
9.1.04
| 18.08 |
BMC Remedy AR System Server | SW00549019 | The ARDBC LDAP query fails due to malformed query when the distingushedName contains "\," embedded in the data. | 18.05 9.1.04 9.1.03 | 18.08 |
BMC Remedy AR System Server | SW00548869 | When you upgrade from BMC Remedy AR System version 8.1 to version 9.1.04, the date and time format behavior for time fields in set fields actions is different. | 18.05 9.1.04 | 18.08 |
BMC Remedy AR System Server | SW00548846 | On Oracle case insensitive database, a combination of bind variable and literal in SQL query causes a performance issue. |
18.05
9.1.04
| 18.08 |
BMC Remedy AR System Server | SW00548823 | When you process any custom filter on any field with the $ DEFAULT $ setting, the $ DEFAULT $ setting sets the actual values of Remedy Developer Studio. |
18.05
9.1.04
| 18.08 |
BMC Remedy AR System Server | SW00548738 | The Jackson databind libraries have some known vulnerabilities. | 18.05 9.1.04 9.1.02 9.1.01 9.1 | 18.08 |
BMC Remedy AR System Server | SW00548713 SW00549578 | On the AR System Report console, any non-admin user can edit the AR System report created by another user. |
18.05
9.1.04
| 18.08 |
BMC Remedy AR System Server | SW00548511 | AR System Server version 9.1.04 does not start with a Read-Only database when you have Remedy Smart Reporting installed. |
18.05
9.1.04
| 18.08 |
BMC Remedy AR System Server | SW00549299 | In a server group environment, the following error is displayed in the arerror.log file when the server points to a read-only database: Error in failover monitor ERROR (552): Message not in catalog; Message number = 552; Failed to update database "ARSystem" because the database is read-only. Workaround: Perform the following steps: 1. Backup and restore the AR Server database. 2. Point the secondary server to the restored database. 3. Login to the secondary server and delete entries of the primary server from the AR System Service Failover Ranking form. 4. Make the database read-only. 5. Start the AR System Server. | 18.08 18.05 9.1.04 | |
BMC Remedy AR System server | SW00535782 | The normal search operation does not work on the Vendor form if you have enabled a multi-valued attribute for any field. | 18.08 18.05 9.1.04 9.1.03 | |
BMC Remedy AR System server | SW00515753 | In a server group environment, when the Admin server is down and the secondary server has not picked up the admin server operations, requests pending from Hierarchical Group might accumulate. | 18.08 18.05 9.1.04 9.1.03 9.1.02 | |
BMC Remedy AR System server | SW00516587 | When you install the AR System server in a server group and the server has multiple IP addresses, the server group JSM signing does not work. | 18.08 18.05 9.1.04 9.1.03 9.1.02 9.1.01 9.1 9 | |
BMC Remedy AR System server | SW00417387 | An email message is sent to all the users registered on the People form (users belonging to a particular group) under either of the following circumstances: A user on the People form has an email address such as "00000", group IDs, or some garbage characters, and an incident is created for this user. The user who is creating a ticket for the customer for whom the incident is being created replaces the value in the Email address field with zeros (for example, 000000) or the group ID and submits the incident. | 18.08 18.05 9.1.04 9.1.03 9.1.02 9.1.01 9.1 9 8.1 8 7.6.04 7.5 7.1 | |
BMC Remedy AR System server | SW00494703 | If you enable the Always Logging ON with default settings, the Java plugin server heap memory consumption is high. Workaround: Open the armonitor configuration file. (On Windows) The armonitor.cfg file located at <ARSystemInstallDir>\ARSystem\Arserver\Conf folder. (On UNIX) The armonitor.conf located at /etc/arsystem/serverName folder. Locate the Java plug-in server command and add the following parameters: 1. -XX:+UseConcMarkSweepGC 2. -XX:+UseParNewGC For example: "C:\Program Files\Java\jre1.8.0_51\bin\java" -Xmx512m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -classpath "C:\Program Files\BMC Software\ARSystem\pluginsvr;C:\Program Files\BMC Software\ARSystem\pluginsvr\arpluginsvr91_build001.jar;C:\Program Files\BMC Software\ARSystem\approval\bin\armaskingImpl91_build001.jar;C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arcmnapp91_build001.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x <SERVER NAME> -i "C:\Program Files\BMC Software\ARSystem | 18.08 18.05 9.1.04 9.1.03 9.1.02 9.1.01 9.1 | |
BMC Remedy AR System server | SW00495468 | If you are using an Oracle database and you use a JDBC query with the LPAD and RPAD functions, the following error occurs: ERROR (552): The SQL database operation failed.; ORA-00932: inconsistent data types: expected CHAR got NUMBER The LPAD and RPAD functionality is supported for character fields only and not supported for integer fields. | 18.08 18.05 9.1.04 9.1.03 9.1.02 9.1.01 9.1 | |
BMC Remedy AR System server | SW00550473 | The FTS Indexing stops working due to lack of disk space in Collection folder. | 18.05 9.1.04 9.1.03 9.1.02 | 18.08 |
BMC Remedy AR System server | SW00550447 | When you use mid tier version 18.05 to connect to the AR System Server version 18.05 and earlier to open the data dictionary menus, a Caught exception occurs and data dictionary menu does not open. | 18.05 | 18.08 |
BMC Remedy AR System server | SW00549928 | Cross data center communication between the server groups is not working with external IP addresses. | 18.08 | 18.08 |
BMC Remedy Developer Studio | SW00548625 | BMC Remedy Developer Studio version 9.1.04 has a performance issue. When you try to delete a large number of active links such as 3000 the operation takes longer time and eventually, a timeout occurs. | 18.05 9.1.04 | 18.08 |
BMC Remedy Developer Studio | SW00515529 | When you create a character field on a form and set an attribute property to $LOWER$,the value does not fall within the limits specified for the field and the following error occurs: (Field ID - , Pattern - $LOWER$) (ARERR 306).d | 18.08 18.05 9.1.04 9.1.03 9.1.02 9.1.01 9.1 | |
BMC Remedy Developer Studio | SW00475891 | When you create an association between the main form and its audit form and you have chosen this to follow this association during archiving, all the related audit entries are also archived with that form. However, after archiving, when you delete the archived records from the main form, an audit entry gets added for deletion in the audit form and it is not archived. Workaround: You can choose to archive those entries in your audit form which were created due to deletion on the form by archive user. 1. Define an archive on your audit form. 2. Select Appear in Archive Policy check box. 3. Add the qualification as 'User'='AR_ARCHIVER' & 'Action'='Delete'. 4. Save the form. | 18.08 18.05 9.1.04 9.1.03 9.1.02 9.1.01 9.1 9 | |
BMC Remedy Email Engine | SW00548062 | When an outgoing email has an attachment with a background image, the email is not sent and the following message is displayed in the Email Engine logs: "Invalid Value. m_EntryMap. Email ID: <ID>" | 18.05 9.1.04 | 18.08 |
BMC Remedy Email Engine | SW00548060 | When you add an attachment to an email, the real file name of the attachment is changed to "some text" and the attachment becomes zero KB. |
18.05
9.1.04
| 18.08 |
BMC Remedy Email Engine | SW00548974 | Inline images in an email are not visible if you send an email using the email template, which uses an attachment that has a name different than the name of the image file attachment. Workaround: Ensure that the attachment name and image name are the same for inline images. | 18.08 | |
BMC Remedy Email Engine | SW00550438 | When the AR System Email Messages form is populated with a large number of outgoing emails, the outgoing emails are stuck. |
18.05
9.1.04
| 18.08 |
BMC Remedy Email Engine | SW00549923 | When the AR System Email Messages form is populated with a large number of outgoing emails, the outgoing emails are stuck. |
18.05
9.1.04
| 18.08 |
BMC Remedy Flashboards | SW00438995 | If you manually deploy version 9.1 flashboards on the same computer and in the same path and folder where you have an earlier version of the flashboards binaries already deployed to support remote flashboards, the BMC Remedy Flashboards 9.1 installation fails. Workaround: Perform either one of the following actions: 1. Stop the earlier flashboards service before installing BMC Remedy Flashboards version 9.1. 2. Install BMC Remedy Flashboards version 9.1 in a different location. | 18.08 18.05 9.1.04 9.1.03 9.1.02 9.1.01 9.1 9 8.1 8 | |
BMC Remedy Mid Tier | SW00548925 | When you log in to mid tier and open any form with Set Fields to default values option, the form values are not set. | 18.05 | 18.08 |
BMC Remedy Mid Tier | SW00548866 | (Microsoft Edge) A caught exception occurs when you access BMC Remedy AR System 9.1.04 using the new Microsoft Edge EDGE 42.17134.1.0 browser. | 18.05 9.1.04 | 18.08 |
BMC Remedy Mid Tier | SW00548618 | In Remedy AR System version 9.1.04, Null pointer exception occurs sporadically on mid tier when you try to add or display attachments. |
18.05
9.1.04
| 18.08 |
BMC Remedy Mid Tier | SW00548348 SW00548349 | (Firefox) On the Work Order console, a caught exception occurs intermittently if you open any existing work order or switch between work orders. |
18.05
9.1.04
| 18.08 |
BMC Remedy Mid Tier | SW00547874 | When you log in to mid-tier and enter more than 30 characters in Username and Password field, sensitive information such as the web server version present on the server is displayed instead of an authentication failed error. |
18.05
9.1.04
| 18.08 |
BMC Remedy Mid Tier | SW00549151 | Apache Tomcat version disclosed in application web server's HTTP response. This information can help an attacker gain a greater understanding of the systems in use and potentially develop further attacks targeted at the specific version of Apache. | 18.08 18.05 | |
BMC Remedy Mid Tier | SW00541707 | (Google Chrome) When you perform global search, the global search internal elements are collapsed to the left side and the results are not displayed as expected. | 18.08 18.05 9.1.04 | |
BMC Remedy Mid Tier | SW00544617 | On the AR System Deployment Management console, when you click Manage Package > Create, all fields are read-only and you cannot create a package. Workaround: 1. Login to mid tier. 2. Click Cache Settings. 3. Click the Flush Cachebutton. |
18.08
18.05
| |
BMC Remedy Mid Tier | SW00527721 | In the AR System Report console, the following error occurs if you create a web report that contains double quotation marks (" ") in the report name: ARERR [9246] Cannot find report. Workaround: Do not use double quotation marks (" ") in the report name. | 18.08 18.05 9.1.04 9.1.03 | |
BMC Remedy Mid Tier | SW00528996 | When you have Mid Tier installed with Apache Server and Tomcat as a web server, the login page is not displayed. Workaround: Enter a forward slash (/) at the end of the Mid Tier URL. For example http: //<server_name>:port/arsys/ | 18.08 18.05 9.1.04 9.1.03 | |
BMC Remedy Mid Tier | SW00529534 | If you apply underlining in the pop-up editor, the underline color is black regardless of the font color that you select. | 18.08 18.05 9.1.04 9.1.03 | |
BMC Remedy Migrator | SW00550007 | When you migrate an overlay object such as a form, active link, or filter using the Migrator Tool, the migration process is successful but the following error is displayed in the migration report. Thread Error : 2004 An Unknown error occured within the thread. | 18.08 18.05 9.1.04 | |
BMC Remedy Single Sign-On | SW00550591 | When you install BMC Remedy Mid Tier with Web Sphere, install Remedy Single Sign-On, and then configure Remedy Single Sign-On with Mid Tier, the Remedy Single Sign-On login page is correctly displayed. However, when you log in using your credentials, the AR System login page is incorrectly displayed instead of directly logging in. | 18.08 | |
BMC Remedy Single Sign-On | DRRS0-948 | The User ID field in the certificate-based authentication does not behave as expected. If a user selects Custom Attribute in the User ID field while configuring certificate-based authentication, the User ID Attribute field does not become visible. Workaround: The user must save the configuration and edit the realm to enter a value in the User ID Attribute field. The User ID Attribute field remains available even if the user selects any value other than Custom Attribute in the User ID field. Workaround: The user must enter some value in the User ID Attribute field, but BMC Remedy SSO ignores this value and considers the one entered in the User ID field. | 18.08 18.05 9.1.04 9.1.03 9.1.02 9.1.01 | |
BMC Remedy Single Sign-On | | If ADFS use self-signed signing certificate and "AutoCertificateRollover" option is enabled, new sign certificate will be generated 20 days prior to expiration of old certificate and ADFS starts to sign responses with new certificate. This will result in user's log in failure. Response signature isn't verified" error and SAML authentication failure. Possible fix could have been to re-import Idp metadata but the problem is that Idp metadata contains both new and old certificate and RSSO server extracts old certificate instead of new one. Workaround: Manually update the signing certificate to a new signing certificate in BMC Remedy SSO. | | |
Remedy online documentation portal | SW00550388 | In the Remedy online documentation portal, when you click on any link that is pointing to another Remedy component’s online documentation, sometimes an earlier version of the page opens. Workaround: After the page opens, from the left pane, select the latest version from the Product version drop-down menu to open the page for that version. | 18.08 | |