To restore the ALM tray icon:
set InstallLocation=<ALM Installation folder>
set TrayMain=com.hp.alm.platform.trayicon.ALMTrayIconMain
Run time error “Server Error in ‘LoadTest’ Application.” is observed when we click on scenario both in My Performance Center and DesktoClient version 12.56 .
The full error message is:
Server Error in ‘/LoadTest’ Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a “web.config” configuration file located in the root directory of the current web application. This <customErrors> tag should then have its “mode” attribute set to “Off”.
<!– Web.Config Configuration File –>
<configuration>
<system.web>
<customErrors mode=”Off”/>
</system.web>
</configuration>
The test can be edited but in the summary tab the error message appears.
The issue is observed when analysis template and/or resource monitors which were deleted from the project are used it the problematic test.
To overcome the issue the missing analysis template and/or resource monitors should be removed from the test.
1. If the test is using a deleted analysis template the options are in the test to choose another analysis template or the default analysis template by following the steps below:
Click on a problematic test
Click on Edit test button
In test window select Advanced-> Analysis Template Options
In the Analysis Template Options select:
Use default Analysis Template
Click on OK
Save the test
2. If the test is using a deleted monitor the missing monitor need to be removed from to test or substituted it with an existing monitor.
To delete a Monitor please follow the steps below:
Click on Associated Monitors tab
Select the missing Monitor
Click on Remove Selected
To add an existing monitor
Click on Associated Monitors tab
Select “Add Monitor Profile” or “Add Monitor OFW”
Select the Monitor from Select Monitors part of the screen.
Automated tests failing, usually due to object not found in application under test
The ALM Lab Service, using the auto-login functionality, will establish a remote session on the host machine.
The native resolution of the session is determined by the video drivers used on the physical machine or virtual machine.
In some cases this causes a lower than normal screen resolution such as 800×600 which causes UFT to not locate the objects on the screen of the application under test.
To fix this upgrade and/or configure new video drivers on the physical box or VM which support the screen resolution established when the automated test was recorded using UFT.
Make sure the native resolution provided by the video drivers supports the same resolution when the test was recorded.
To set the resolution use: https://social.msdn.microsoft.com/Forums/azure/en-US/1c215514-aeef-41d9-b47b-5c838a0bf83f/how-to-change-the-vm-default-screen-resolution?forum=WAVirtualMachinesforWindows
To rename Resource Type or Test Type in Application Lifecycle Management (ALM) 11.00
For example:
QUICKTEST_TEST to QTP_TEST
First of all, because this is a database (DB) change, it is highly recommended to make a back up of your project database before doing any changes on it.
Please follow these steps in order to change the name of resource type “Testing Activity”:
1. Login into your Site Administration
2. Navigate to your project in the tree
3. Expand its tables
4. Go to ENTITY_SUBTYPES Table
5. In the query box enter the following Query
For Test Type (QUICKTEST_TEST):
— this script will update the type visible in Test Plan
UPDATE ENTITY_SUBTYPES
SET EST_NAME=’QTP_TEST’ — the name you want to set
WHERE EST_ID = ‘QUICKTEST_TEST’ — you can check it in the same table
AND EST_ENTITY_TABLE_NAME = ‘TEST’
— this script will update the type visible in Test Lab
UPDATE ENTITY_SUBTYPES
SET EST_NAME=’QTP_TEST’ — the name you want to set
WHERE EST_ID = ‘QUICKTEST_TEST’ — you can check it in the same table
AND EST_ENTITY_TABLE_NAME = ‘RUN’
For Resource Type:
UPDATE ENTITY_SUBTYPES
SET EST_NAME=’Resource Type Name’ — the name you want to set
WHERE EST_ID = ‘Resource Type ID’ — you can check it in the same table
AND EST_ENTITY_TABLE_NAME = ‘RESOURCE’
6. Close your browser
7. Open your Temp folder (in windows explorer path enter %temp%)
8. Find and delete folder called “TD_80”
9. Open your browser again and load the HP ALM components
10. Login into the project and check the name of the type you have changed.
After creating some keyword mapping, in SAP Solution Manager, to synchronize some custom fields of SAP Blueprints with User Defined fields (UDF) of ALM Requirements, the synchronization does not seem to work.
For example, as illustrated in the two next screenshots, after setting the keyword mapping in SAP Solution Manager, the next synchronization does not update the requirements’ UDF in ALM:
•Setting keyword mapping in SAP Solution Manager:
•The UDF remains empty after next synchronization:
Apparently, the requirements’ User Defined Fields have been created in the customization of the ALM project but they were not set to be in the requirement type (each requirement type can be customized to contain or not specific UDFs and each new UDF created in an ALM project is, by default, not part of any requirement type).
In the Customization section of the ALM project, the “Requirement Types” option should be modified so each requirement type related to the SAP synchronization (if they are not known, modify every requirement type in the ALM project) is set to have the User Defined Fields in their definition as illustrated in the next screenshot:
•Customize the Requirement type to contain the UDFs:
•The UDFs should be successfully synchronized after this:
Messages:
Failed to Restore Project;
Stack Trace:
org.bouncycastle.crypto.InvalidCipherTextException: pad block corrupted
at org.bouncycastle.crypto.paddings.PKCS7Padding.padCount(PKCS7Padding.java:63)
at org.bouncycastle.crypto.paddings.PaddedBufferedBlockCipher.doFinal(PaddedBufferedBlockCipher.java:286)
at com.hp.sw.bto.ast.security.lwcrypto.LWBlockCrypto.decrypt(LWBlockCrypto.java:114)
wrapped in com.hp.sw.bto.ast.security.lwcrypto.LWCryptoException: Unable to finalize decryption for the following 16 bytes: [ -49, 70, 121, 104, -37, -48, -11, -24, 77, -2, -69, 17, 52, -16, -27, -102, ], 0 bytes were already precessed. Current configuration is: com.hp.sw.bto.ast.security.lwcrypto.LWBlockCrypto[ cipher: AES/CBC, Encoding mode: Base64Url, forEncryption: false, keysize: 256]
at com.hp.sw.bto.ast.security.lwcrypto.LWBlockCrypto.decrypt(LWBlockCrypto.java:118)
at com.hp.alm.platform.crypto.QcCipher.decrypt(QcCipher.java:168)
Issue happens since the password in the dbid.xml does not match with the data in Application Lifecycle Management (ALM).
Steps to fix the issue:
· Create a new project.
· Go to the repository of the newly created project.
· Open the dbid.xml file
· Copy the Password
· Open the dbid.xml file of the project we are trying to restore.
· Make sure the password is the same for both new and failed to restore project.
· If different change the password.
· Restore the project again.
The error message appears when trying to access Mtours from Application Lifecycle Management (ALM)
Error Message: HTTP 503
The cause of this problem is because Mtours is disabled by default if it was not enabled during the intallation of ALM.
To fix this issue and enable Mtours, follow these steps:
1. Open and edit the “start.ini” file located in the following location: C:\ProgramData\HP\ALM\server\conf
2. In the file locate the following line: jetty-testrealm.xml
3. Edit this line and remove the ‘#’ character at the beginning of the line.
4. Save and close the file
5. Restart the ALM server.
6. Check if the problem is resolved.
