Copyright (C) 1994-2019 Tricentis US Corp. All rights reserved.
These Release Notes contain the most recent information relating to the installation, configuration and operation of the LiveCompare software. Please read through them carefully, and we advise that you keep a hardcopy with the Installation and Configuration Guide for your reference.
Please read this post:
about changes to LiveCompare technical support.
Before Installing LiveCompare 3.9.3 please ensure that all Windows updates are installed on your LiveCompare server. If they are not, you may see a ‘missing api-ms-win-crt-runtime-l1-1-0.dll’ error when trying to configure LiveCompare.
If you have upgraded to LiveCompare 3.9.3 from an earlier release, please note the following:
LiveCompare 3.9.3 normally requires the version 3.9.3 transports to be installed on each SAP system that is used with LiveCompare. If you are running LiveCompare 3.9.3 using SAP systems that have LiveCompare 3.9.2 (or earlier) transports installed, please note the following:
Tosca Workspaces and Quality Center Projects have been replaced by Test Repositories in this release. If you have any standard LiveCompare App variants that use Tosca Workspaces or Quality Center Projects, you will need to create new variants for these Apps using the ‘Based on [app]’ option.
If you have any standard templates that use Tosca Workspaces or Quality Center Projects, these will need to be replaced with update workflows from the Data/Templates hierarchy folder. If you have any custom Apps or workflows that use Tosca Workspace or Quality Center Project parameters, these will need to be updated to use Test Repositories.
Upgrading to LiveCompare 3.9.3 resets any object links caches that have been generated for your RFC Destinations. An object links cache will be reset by the Where Used, Uses What and Find Object Links actions, if these actions identify that the cache was generated by a previous LiveCompare release.
LiveCompare 3.9.3 normally requires the version 3.9.3 transports to be installed on each SAP system that is used with LiveCompare. If you are running LiveCompare 3.9.3 using SAP systems that have LiveCompare 3.9 (or earlier) transports installed, please note the following:
The Run Web Service action no longer creates a dataset named Raw Results Xml. The Raw Results Xml dataset no longer used and will not be populated in existing workflows. If you have an existing workflow that processes the contents of the Run Web Service action's Raw Results Xml dataset, then this workflow may need to be redesigned.
LiveCompare 3.9.3 normally requires the version 3.9.3 transports to be installed on each SAP system that is used with LiveCompare. If you are running LiveCompare 3.9.3 using SAP systems that have LiveCompare 3.8 (or earlier) transports installed, please note the following:
LiveCompare 3.9.3 normally requires the version 3.9.3 transports to be installed on each SAP system that is used with LiveCompare. If you are running LiveCompare 3.9.3 using SAP systems that have LiveCompare 3.7 (or earlier) transports installed, please note the following:
The Get Transport Objects action has a new parameter in this release named Expand Views. Its default value is false. If the parameter is set to true and the action is run against an SAP system with LiveCompare 3.7 or earlier transports, the action will fail with an RFC error. This occurs because the underlying RFC-enabled function (/ICORP/RFC_GET_TRANSPORT_OBJS) was changed in LiveCompare 3.8, adding the new parameter. A call to the old function with fail if the Expand Views parameter is supplied.
Retrieval of Tier 2 details for CLAS objects has been reimplemented in this release. If you use the Quick Compare Wizard on a CLAS object, or run a workflow like Compare Objects to compare CLAS objects, no Tier 2 data will be returned from an SAP system with LiveCompare 3.7 or earlier transports.
LiveCompare 3.9.3 includes the following new features:
In some cases, an unknown termination error may occur when running the Code Guard App. On investigating the problem, we found that it was caused by two competing threads attempting to read the same Excel External Data Source. A workaround for this problem is to replace the App’s External Data Source with one of the same name that uses a different type of data file (for example, a .CSV file).
The Fix My Code App only supports atomic object types, and container object types, such as Function Groups (FUGR).
If an Excel spreadsheet opens in Protected Mode, the charts may not reflect the data in the actual spreadsheet. You must switch the spreadsheet into Editable Mode to see the correct values in the charts. This issue was noticed for the Upgrade Assessment Summary Excel report, however it may occur for other Excel reports.
A runtime error may occur when opening the Apps Home screen; an error page is shown with the title 'Server Error in ‘/livecompare/apps’ Application.'. This problem is caused if the IIS Session State feature value on the LiveCompare server is set to Read Only. To resolve this problem, carry out the following steps on the LiveCompare server:
In some cases the Upgrade Assessor Data Extract program may hang when run using SAP GUI 750, with the ST22 short dump file including either of the following errors:
In each of these cases, a workaround is to run the Data Extract program as a background job. See the ‘Running the Data Extract Program as a Background Job’ Help topic for details.
If you have edited the contact details displayed in the Administration page, these details will be used in place of the default contact details when upgrading to LiveCompare 3.9.2. If you have Administrator privileges, the ‘Restore Default Contacts’ button on the Administration page may be used to restore the default contacts provided with LiveCompare.
If a workflow is run, and then its workspace is reregistered (i.e. deleted without removing its database files and then registered again), the workflow will not be displayed when it is selected in the LiveCompare hierarchy. To resolve this problem, restart the RNSERVER service after first making sure that no users are logged into LiveCompare, and that no workflows are currently running.
In LiveCompare 3.6, the selecting the ‘Remove Database?’ option on the Delete Workspace screen unregistered the workspace, but did not remove the workspace database when using Chrome. This problem has been resolved, however if you are using Chrome and have upgraded from LiveCompare 3.6, you may have some unwanted workspaces on your LiveCompare server. You can check this in LiveCompare by selecting ‘Register Workspace’ from the Workspaces folder in the LiveCompare hierarchy and reviewing the list of unregistered workspaces. Workspaces that you no longer need may registered in LiveCompare 3.9.2 and then deleted as normal by selecting the ‘Remove Database?’ option.
If you have upgraded to this release from LiveCompare 3.8 or earlier and you have any workflows that are registered as Web Services, these will need to be reregistered in LiveCompare 3.9.3 using the Register Workflow as Web Service Wizard.
If an RFC timeout error occurs while running the Analyze Object Links action, this can be resolved by means of a registry entry on the LiveCompare server.
The Create Object Link Cache (COLC) action was improved in version 3.8. If only a few changes have been made to objects in an SAP system, for the most part it will only retrieve changes made to those objects and store them in the local cache. This greatly speeds up the COLC action (and any analyses that depend on it) by an order of magnitude, typically.
Note that if the EU_INIT job is run on an SAP machine, it also updates its SAP-resident cache regarding the SAP objects on the system. However, we have observed that it also regenerates all of the CLAS objects associated with WAPA objects. This can be 50K objects or more. The first time a COLC is run after the EU_INIT job is run, the COLC action will discard the current cache and completely rebuild the OLC cache.
The suggestion to users: if you have a regularly scheduled EU_INIT job, then schedule a COLC job to run after it, thereby making later COLCs run much faster.
This release contains new patterns in the Custom Object Naming Patterns External Data Source that classify objects whose names begin with SAPLY, SAPLZ, SAPMY or SAPMZ as custom objects. Customers who are installing LiveCompare for the first time will automatically receive this update. However, customers who are upgrading from an older release of LiveCompare will not automatically receive it. This policy exists because we do not wish to overwrite updates that customers have made to their External Data Source files.
If you are upgrading to LiveCompare 3.9.2 from LiveCompare 3.1 or earlier, the Add New Custom Object Naming Patterns workflow in the Tools template package should be run once only to update the External Data Source with the new patterns. Please see the workflow’s template help file for more details.
For SAP functions with ordinal parameters of type CHAR or DEC, if the direction is CHANGING, and there is no non-blank parameter value, the Generic RFC Call’s output dataset will not be populated by the remote function call. In this case, please contact Tricentis Technical Support for assistance.
The Read HTML Table action does not support URLs that begin with https:.
The Analyze ABAP Quality action may return ‘error in ABAP’ as the ABAP code’s complexity category, if the ABAP source includes long lines of code that run across several on-screen lines. For example, data declarations of long strings that exceed 4 on-screen lines and are literals may cause ‘error in ABAP’ to be returned.
In some cases, the ‘Create Hierarchy Report’ action may run out of memory when generating a report from IMG Comparison results. This problem may occur when large IMG areas are compared, for example ‘Payroll Accounting’. To resolve this problem, use IMG Select List parameters to generate a number of different reports, each for a smaller portion of the IMG.
In order to be able to compare application data from two systems with different client numbers, LiveCompare ignores the MANDT field when comparing table contents. Since MANDT is the only key field in table T000, LiveCompare has no way of matching up rows from the two systems. T000 is the only table known to manifest this problem.
In some cases, a timeout error may occur when using the Read SAP Table action to read large cluster tables. If this happens when comparing a list of objects, a workaround is to exclude the cluster table from the comparison, then read it separately from each system using the Read Large SAP Table action. The cluster table may then be compared using the Compare Tables action.
LiveCompare is not able to read or compare table data from SAP tables that contain variable-length string fields. ENHHEADER, T7XP_TEXT and N2GL_DES_STRING are examples of such tables. If the contents of these tables are compared using the Quick Compare Wizard, the following error occurs:
Message: UNSUPPORTED DATA TYPE - TABLE CANNOT BE READ FROM SAP. Internal Error Number: 30.
LiveCompare dynamically allocates the structures used to pass table contents from SAP. In the case of these tables, the structure contains a field of type STRG (variable-length string). Unfortunately, SAP does not allow dynamic allocation of structures with this type. At the time of writing, there is no workaround to this problem.
In Hierarchy datasets, the hyperlink that opens the ‘Row Details’ screen for Table Contents results displays a new a new window listing the table field names, the field values from each system and the field descriptions. However, the ‘Row Details’ screen displayed for Table Key results shows no data.
If a runtime error occurs when opening a WSDL file in the Web Services hierarchy folder, this may be resolved by deleting the <LiveCompare user data dir>\Cache\webservices folder.
Google Chrome is the preferred web browser for workflow development.
If a remote function is bound to a Generic RFC Call action and then modified to include an additional input parameter, the Generic RFC Call action retains the function’s original definition even after the RFC Signature Builder Wizard is rerun. This issue occurs because the SAP RFC Runtime maintains a cache for each SAP system ID, which is not controlled by LiveCompare.
A workaround for this issue is to restart the RNSERVER service on the LiveCompare server, first making sure that no users are logged into LiveCompare, and that no workflows are currently running. After the RNSERVER service has been restarted, the RFC Signature Builder Wizard may be used to bind the Generic RFC Call action to the updated function.
If a ‘Not enough memory to run Microsoft Excel’ error occurs when opening an Excel report from LiveCompare, this may be resolved by adjusting Excel’s Protected View settings as follows:
When you export a Table dataset to Microsoft Excel, LiveCompare displays a dialog asking whether you would like to open or save the Excel file. If you click ‘Open’ Excel displays the following warning message:
The file you are trying to open is in a different format than specified by the file extension. Verify that the file is not corrupted and is from a trusted source before opening the file. Do you want to open the file?
This warning occurs because the table contents are exported in HTML format, tagged to be opened using Excel. To display the table contents in Excel, choose ‘Save’ in the initial dialog, and save the file with an .xls extension. When opening the .xls file, click ‘Yes’ when the warning message is shown to display the table contents.
If a workflow takes longer than three seconds to reset, the hourglass cursor that is displayed during the reset operation is replaced with an arrow cursor. This suggests that the operation has finished, however the workflow renderer will remain unresponsive until the reset has completed. This problem may occur for workflows that call a large number of sub workflows.
When working with an IMG that has been downloaded from an SAP system it is possible that you’ll see items in the hierarchy with indecipherable names. The items may be selected and used in an IMG selection, and are being returned from SAP when we query for the IMG hierarchy. We expect to filter or transform these items in a future release.
A bug in the underlying library requires a workaround for graphic output from the ggplot() function. For example the following script results in a blank image:
library(ggplot2)library(extrafont)windowsFonts(Monoton=windowsFont("Monoton"))butterfly=function(x) 8-sin(x)+2*sin(3*x)+2*sin(5*x)-sin(7*x)+3*cos(2*x)-2*cos(4*x)opt=theme(legend.position="none",panel.background = element_rect(fill="black"),panel.grid=element_blank(),axis.ticks=element_blank(),axis.title=element_blank(),axis.text=element_blank())ggplot(data.frame(x = c(0, 2*pi)), aes(x)) +stat_function(fun=butterfly, geom="density", fill="#FC0C54", colour="#FC0C54") +coord_polar(start=-pi) +geom_text(x=.5, y=-14, colour="turquoise2", family="Monoton", label="Butterfly", size=12) +opt
This can be resolved by modification like this, note the assignment of the plot to a variable and the use of print():
library(ggplot2)library(extrafont)windowsFonts(Monoton=windowsFont("Monoton"))butterfly=function(x) 8-sin(x)+2*sin(3*x)+2*sin(5*x)-sin(7*x)+3*cos(2*x)-2*cos(4*x)opt=theme(legend.position="none",panel.background = element_rect(fill="black"),panel.grid=element_blank(),axis.ticks=element_blank(),axis.title=element_blank(),axis.text=element_blank())gg <- ggplot(data.frame(x = c(0, 2*pi)), aes(x)) +stat_function(fun=butterfly, geom="density", fill="#FC0C54", colour="#FC0C54") +coord_polar(start=-pi) +geom_text(x=.5, y=-14, colour="turquoise2", family="Monoton", label="Butterfly", size=12) +optprint(gg)
If a table containing Unicode character is read into the Execute R action and written to a result dataset, the table’s Unicode characters are replaced with ‘?’. This is a limitation of the underlying library used to run R scripts.
In some cases using Internet Explorer 8, the tabs shown for Hierarchy datasets may not be displayed correctly. If this occurs, select ‘Compatibility View Settings’ from the Internet Explorer ‘Tools’ menu, and deselect the ‘Display intranet sites in Compatibility View’ check box.
When a workflow is registered as a Web Service, the first output parameter found in the workflow is selected by default in the Register Workflow as Web Service Wizard’s ‘Choose Output Parameter’ screen. If the output parameter contains any spaces or non-alphanumeric characters, the resulting Web Service will be invalid, and in the case where this is the workflow’s only output parameter, no other parameters will be available for selection. Before registering a workflow as a Web Service, you should make sure that there are no spaces or non-alphanumeric characters in the name of the node that will be used for the Web Service’s output parameter.
If you are upgrading from LiveCompare 3.1 and are using an existing Web Service that is called by an external program or third-party application, it may be necessary to re-register the Web Service using the Register Workflow as Web Service Wizard in this release. The new WSDL must then be used by the calling program. This is due to changes in the Web Service Definition Language expected in later LiveCompare releases.
If you start a second LiveCompare browser window or tab (for example, to log in using the ‘admin’ account), the new browser window or tab shares the same session information as the first one. This means that if you log into LiveCompare using the second browser window or tab, then the first session will be lost. It also means that logging out from one LiveCompare session will log out the other session. To start a new session for a second LiveCompare login, choose ‘New session’ from Internet Explorer’s File menu.
LiveCompare uses Unicode internally to read, write and store text, and therefore supports all major languages. However, the display of Unicode text may require some additional client configuration steps.
See http://www.unicode.org/help/display_problems.html for information on setting up Internet Explorer to view Unicode characters.
In LiveCompare, the grid control that is used to display tabular data requires additional configuration in order to display non-Western European language text:
When IIS is configured to accept only authenticated access to LiveCompare, you may see this error message:
Invalid root in registry key"HKEY_LOCAL_MACHINE\SOFTWARE\Tricentis\LiveCompare\3.9\Settings\RootUrl"
This error occurs because the authenticated user has insufficient privileges to write to the Windows registry. The solution is to use REGEDIT and grant the authenticated user account ‘Full Access’ to the HKEY_LOCAL_MACHINE\SOFTWARE\Tricentis\LiveCompare\3.9 registry key.
The following message may be displayed if you try to export a table dataset to Microsoft Excel 2007 using the ‘Export to Excel’ button in the Details window. It may also be displayed if you use the ‘Export Header to Excel’ or ‘Export Attributes to Excel’ links and try to view the resulting spreadsheet.
The file you are trying to open ‘[Filename.xls]’ is in a different format than specified by the file extension. Verify that the file is not corrupted and is from a trusted source before opening the file.
Files exported from LiveCompare are safe to open. The message is displayed because LiveCompare data is exported in HTML format, and we are using an ‘.xls’ file extension. Excel 2007 uses a security measure called ‘extension hardening’ which requires that the format of a file’s contents matches its extension. To prevent the message from being shown, set the following registry value on your LiveCompare client machine:
See the MSDN blog entry at http://blogs.msdn.com/vsofficedeveloper/pages/Excel-2007-Extension-Warning.aspx for further details.
Generic RFC Call actions may not work in some 700 kernel release systems for functions that have tables with numbers on odd-byte boundaries.
The ‘Report View’ action in the APO Analysis ‘Macros’ workflow may generate an unknown error if the workflow is run repeatedly. If this happens, it may be necessary to restart the ‘Tricentis LiveCompare Application Server’ service on the LiveCompare server before running the workflow again. Before restarting the service, log into LiveCompare as an Administrator and select the Administration > Users folder in the hierarchy to make sure that no other users are logged in.
If the Deconfiguration Wizard Summary screen reports an ‘Access is denied’ error for any DLLs, please contact Tricentis Technical Support for assistance.