Script of Siebel Open UI application is failing during replay

Script of Siebel Open UI application is failing during replay on the first or the second iteration due to not captured correlation values.

Siebel correlation library need to be used to allow successful correlation of Siebel specific dynamic values.

The issue could appear if not all needed steps are performed to enable correlation with Siebel correlation library.

For example if the library file ssdtcorr.dll is copied into the bin folder of the product installation but but Siebel correlation rules file WebSiebel77Correlation.cor is not imported in recording option’s correlation node this can lead to correlation values not being captured correctly.

Siebel has released a correlation library file as part of the Siebel Application Server version 7.7. This library is available only through Siebel. The library file, ssdtcorr.dll, is located under the siebsrvr\bin folder for Windows and under siebsrvr/lib for Linux installations.

The library file, ssdtcorr.dll, must be available to all machines where a Load Generator or Controller reside.

Please follow all of the steps listed below to enable correlation with Siebel correlation library.

1. Copy the DLL file into the bin folder of the product installation.

2. Open a multi-protocol script using the Siebel-Web Vuser type.

3. Enable UTF-8 support in the Recording Options > HTTP Properties > Advanced node.

4. Open the recording option’s Correlation node and click Import. Import the rules file,

WebSiebel77Correlation.cor, from the \dat\webrulesdefaultsetting folder. If you are

prompted with warnings, click Override.

To apply Siebel correlation library rules for existing script, the script need to be regenerated.

Advertisements

Not able to upload the scripts to ALM 11 UI

The Upload script functionality is throwing an error "Script upload failed. Error: Object reference not set to an instance of an object " when trying to upload the script thru ALM-PC UI.

Patch 18 was installed on top of ALM 11 and the relevant ALM client was downloaded on PC server. Upon running the System Health check, the issue was identified as OTA Client version mismatch. The PC server has OTA client related to patch 18 and the PC Host has OTA client related to patch 10.

Run the ALM Client uninstaller on PC server. The utility can be downloaded from KM1400068. Re run the System Health check after ALM client is uninstalled from PC server. This should fix the script upload issue.

Bookmarks and Breakpoints are lost after “Save As” operation in VuGen 12.01

VuGen script bookmarks and breakpoints are lost after executing a "Save As" operation in VuGen 12.01.

This issue appears on Windows Server 2012 R2 and Windows 8.1 Operating Systems.

The problem is related to McAfee antivirus running on the machine on which VuGen is installed.

Please disable McAfee antivirus to overcome this issue.

Message which suggest to reload a script file appears after code generating in VuGen 12.01

An unexpected message which suggest to reload a script file appears after code generating in VuGen 12.01. This issue appears on Windows Server 2012 R2 and Windows 8.1 Operating Systems.

The problem is related to McAfee antivirus running on the machine on which VuGen is installed.

Please disable McAfee antivirus to overcome this issue.

“The file … Action.c has been changed externally. Do you want to reload it?” message wrongly appears in VuGen 12.01

"The file … Action.c has been changed externally. Do you want to reload it?" message wrongly appears in VuGen 12.01 which is installed on Windows 8.1 Operating Systems.

The problem is related to McAfee antivirus running on the machine on which VuGen is installed.

Please disable McAfee antivirus to overcome this issue.

SiteScope – Supported browsers

As of SiteScope 11.24, the list of supported browsers is as follows
(taken from SiteScope Deployment Guide -> Installation Requirements -> Client System Requirements)

SiteScope client is supported on all Microsoft Windows operating systems using the following:

Supported Browsers: SiteScope UI

– Microsoft Internet Explorer 7, 8, 9, 10

Note for Internet Explorer 10:
+ Alert, Monitor, and Server-Centric Reports are supported in compatibility mode only.
+ There is no support for add-ons, like Java, when Internet Explorer 10 is used from the Start screen.
To use SiteScope in Internet Explorer 10, you must switch to Internet Explorer desktop mode and install java.
For details, see http://windows.microsoft.com/en-us/internetexplorer/install-java#ie=ie-10.

– Mozilla Firefox (latest certified version: 24.0 ESR)

– Safari (7.0.4) on Mac OS (10.9.3)

Supported Browsers: Unified Console (Multi-View, Event Console)

– Google Chrome (latest certified version: 34.0.1847.137 m)

– Mozilla Firefox (latest certified version: 24.5. 0 ESR)

– Safari (latest certified version: 5.1.7 for Windows; 7.0.3 for Mac OS)

– Internet Explorer 9, 10, 11

Note:
+ Internet Explorer 9 is supported with the following limitations:
– It is not supported on Microsoft Windows 7 N Edition.
– It is not supported on Microsoft Windows Server 2008.
+ SiteScope Multi-View is no longer officially supported in Internet Explorer 8, and we recommend switching to one of the supported
browsers. The tab functionality in the Web Dashboard does not work in Internet Explorer 8.

– iPad 3 with Safari (iOS 7 with latest updates)
– Android tablet with Chrome 34.0.1847 (Full HD display)

Supported Browsers: SiteScope Multi-View Page in MyBSM
– Internet Explorer 8, 9, 10

SQL Server monitor counters cannot be accessed

Add the objects to the PerfMon counters on the remote machine

SQL Server objects need to be accessable via PerfMon (Windows Performance tool) for SiteScope to get the counters.

Add the objects to the PerfMon counters on the remote machine and the SQL Monitor in SiteScope will work.

There are many cases where SQL Server’s counters are missing. In this FAQ, it is assumed that the installation of SQL Server 2000 is a default installation.

There are many reasons for which the SQL Server counters will disappear, such as Permission, Server Crash, Registry Modification, and Virus. To work around these symptoms, please take the following actions:

1. Check if you have full permissions to access the local folder C:\Program Files\Microsoft SQL Server\MSSQL\. Make sure that you can access this folder or your current account is located in local administrator group.

2. Make sure there is no third-party application that add keys to the registery to disable the performance counters. You can open the registry to check if there is a key named “Disable Performance Counters” valued “1” in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER\Performance. If it exists, delete it.

3. Under the registery key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER\Performance, make sure the following keys with these values do exist. If not, create a new one and add the value.

“Library”=” C:\PROGRA~1\MICROS~3\MSSQL$~1\BINN\SQLCTR80.DLL”
“Collect”=”CollectSQLPerformanceData”
“Open”=”OpenSQLPerformanceData”
“Close”=”CloseSQLPerformanceData”
“Last Counter”=dword:

Note:
The “Last Counter,” “Last Help,” “First Help,” “WbemAdapFileSignature,” “WbemAdapFileTime,” and “First Counter” values can vary between SQL Server installations.