Author Archives: Abdul Rahim

About Abdul Rahim

MCA professional with more than a decade experience with proven expertise in Project Management, Performance Testing, Performance Engineering, Product Benchmarking, Project Estimation, Project Plan, Test Strategy preparations, Pre-Sales Support.

Use rdp_sync_on_window for a partially changing window title

To use rdp_sync_on_window for a partially changing window title for the following scenario

rdp_sync_on_window(“StepDescription=Window Synchronization 1”,

“Snapshot=snapshot_12.inf”,

“WindowTitle=I am static XXXX YYYYY ZZZZ”,

“WindowState=ACTIVE”,

RDP_LAST);

Need to use sync on the portion of the window name that doesn’t change where XXXX YYYYY ZZZZ change, but the first part (I am static) stays the same.

To achieve this the windowTitle argument comes with regular expression

WindowTitle/RE=

In the above example, we can keep the first part static(I am static) and exclude the 2nd part (XXXX YYYYY ZZZZ)using Regular expression.

Advertisements

LR Controller throws Microsoft Visual C++ Runtime Library Runtime Error

Using LoadRunner (LR) 11.00 Patch 4 on a machine that was previously running LR 11.50. When trying to open a scenario the wlrun process crashes and the following message is displayed:

Unsupported operation was attempted

Microsoft Visual C++ Runtime Library

Runtime Error!

Program: C:\\Software\\HP\\LoadRunner\\bin\\wlrun.exe

abnormal program termination

This happens on every attempt to open an LR scenario. Uninstalling and re-installing LoadRunner 11.00 or and 11.04 patches does not resolve the problem. Upgrading LoadRunner to version 11.50 is not possible on this machine as it currently has to run with an LR 11.00 license key.

In certain cases uninstalling of LR 11.50 may leave registry keys enabled for the LR 11.50 version that are incompatible with LR 11.00 and therefore cause the 11.00 wlrun process to crash. To resolve the problem try the following steps on a Windows 7 64 bit machine:

Back up the registry.

Run Regit and go to HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{6B2455C3-CAF8-4578-BBA4-B7566F89EBAA}\InprocServer32

Delete any 11.5x subfolders.

On a Windows XP 32 bit machine the invalid 11.5x entry will be found in

HKEY_CLASSES_ROOT\CLSID\{6B2455C3-CAF8-4578-BBA4-B7566F89EBAA}\InprocServer32\11.5x.0.0

Error: “Object doesn’t support property or method ‘indexOf'” when saving the “Speed simulation” run-time settings of a TruClient script

An error is received when trying to save the “Speed simulation” Run-time settings of a TruClient script:

“Script Error: An error has occurred in the script on this page.

Error: Object doesn’t support property or method ‘indexOf'”

As a result the settings are not saved and the “Save” button becomes disabled.

The issues is caused by missing default values for the speed simulation settings.

To fix the issue for the current script:

1.Open the default.cfg file in the script folder.

2. Go to the [ModemSpeed] section

3. Add values for the ModemSpeedUpload, ModemSpeedDownload and ModemSpeedDownloadAndUpload settings.

For instance:

[ModemSpeed]

ModemSpeedMode=1

ModemSpeedUpload=0

ModemSpeedDownload=0

ModemSpeedDownloadAndUpload=0

4. Save the file and reopen the script in TruClient

5. Go to the Run-time settings > Network > Speed simulation. Changing and saving the values should work now.

To fix the issue for any new scripts, modify the run-time settings templates for TruClient IE and Firefox:

Apply the above changes to the following default.cfg file:

<LoadRunner installation>\template\WebIE\default.cfg

<LoadRunner installation>\template\Web2UI\default.cfg

After saving the changes, any new TruClient script will have the default runtime settings for “Speed simulation”

Unable to turn off Adaptive Learning for Smart Search in Service Manager

Disabling Adaptive Learning in the Knowledge Management Environment Record does not prevent adaptive learning records from being created in the kmadaptive learning table. This problem only occurs when using Smart Search/Smart Analytics and IDOL for Knowledge Management. The problem does not occur when using the SOLR Search Engine.

There is a defect within the IDOLAssistantUseSolution ScriptLibrary record.

The following steps below will disable Adaptive Learning for Smart Search:

1. Login to Service Manager

2. Go to System Administration > Ongoing Maintenance > Environment Records > Knowledge Managment Environment Record

3. Uncheck (i.e. set to false) Use Adaptive Learning to Enhance Search Results

4. Save

5. Logout then back into Service Manager

6. Go to Database Manager and access the ScriptLibrary table

7. Inside ScriptLibrary access the following script: IDOLAssistantUseSolution

8. Find this section of code:

function useSolution(record, solution, library, reference, keyword) {
var mapping = funcs.filename(record);
logger.debug(‘applying solution ‘ + solution + ‘ onto ‘ + record);

KMSearch.useSolution(mapping, solution, record);

var database = library.kbname;
// XXX: reference has to encode twice …
reference = encodeURIComponent(reference);
updateRanking(database, reference);
IDOLGlobalSearchAdaptiveLearning.appendPhrase(library, solution, keyword);
return record;
}

9. Comment the following line: IDOLGlobalSearchAdaptiveLearning.appendPhrase(library, solution, keyword);

10. The function should now look like this:

function useSolution(record, solution, library, reference, keyword) {
var mapping = funcs.filename(record);
logger.debug(‘applying solution ‘ + solution + ‘ onto ‘ + record);

KMSearch.useSolution(mapping, solution, record);

var database = library.kbname;
// XXX: reference has to encode twice …
reference = encodeURIComponent(reference);
updateRanking(database, reference);
// IDOLGlobalSearchAdaptiveLearning.appendPhrase(library, solution, keyword);
return record;
}

11. Save, Compile

12. Adaptive Learning is now disabled for Smart Search

Load files into Service Manager from the OS command line

1. Copy the unload file (eg unload_file.unl) into the <SM INST>\RUN directory

2. Open the terminal and navigate to Go to the <SM INST>\RUN directory

3. Execute the command:

For Microsoft Windows: sm -bg file.load <unload_file.unl> NULL NULL winnt

For UNIX: sm -bg file.load <unload_file.unl> NULL NULL unix

Where <unload_file.unl> is the name of the file to be loaded

4. A message will indicate the load succeeded.

SM 9.40: SURVEY MODULE: Configure Survey for Mobility Client

1. In SurveyParameterMapping, there is not predefined mappingValue for Mob

So add one in global list (List Name: SurveyPredefinedParameters) {“{$EMAIL}”,”{$NAME}”,”{$LANGUAGE}”,”{$WEBURL}”,”{$ESSURL}”,”{$EXURL}”,”{$EXTSID}”,”{$SURVEYURL}”,”{$MOBURL}”}

{“Recipient Email”,”Recipient Name”,”Language”,”Web URL”,”ESS URL”,”External URL”,”External Survey ID”,”InternalSurvey URL”,”MOB URL”}

2. Then add Mob URL for Interaction module for the particular Connector ID. In this example adding the parameters for Internal Connector.

Add mobURL in Survey Connector (for interaction parameters) as highlighted in below snapshot.

3. ScriptLibrary: Survey_TaskProducer, add below line at Line: 117:

paramMap[“$MOBURL”] = url.mob;

4. ScriptLibrary: Survey_Utilities. Add below lines:

Line 134: var url = {“web”:””, “ess”:””, “mob”:””};

Line 172: url.mob = lib.urlCreator.getMobilityURLFromQuery(record_id);

5. System Information Definition:

Add a testing value for “mobility.url” field:

http://mob-url.google.com

6. Schedule the Survey Interation record: S00003

7. Enable the SMSurvey in SMIS:

8. Make sure the Repeat Interval of Survey_Service_Agent within a few minutes:

9. Make sure the Repeat Interval of SMSurvey1 within a few minutes:

10. Now close any one of interaction record:

11. Check the record generated in eventout table:

Now we can see that the mobility.url has been displayed in the email message.

Forms Designer ‘Output Conversion’ property work for Export To Text/Excel

In Forms Designer there is a Property named “Output Conversion”. When used it can change the display of data in the GUI (i.e. display just the date of a record instead of the full date/time). However, the parameter will not extend to exporting the data of the Service Manager record to Excel or Text.

This property is used by RAD subroutines that mask the display of data on an output field, or check and validate the entry of data into an input field. If specified, the routine is called at runtime to convert the contents of the field before it is displayed on the screen. This only works within the client and does not extend to the export of data feature.

Note that at the time of this writing Enhancement Request QCCR1E137853 exists within Development to look into extending the capabilities of this Property to the Export To Text/Excel feature