When debugging HP Performance Center connectivity, determining if ports are opened is a key step. In the past I’ve used Netstat -A to identify what ports on the target host are listening. While it is useful, it only shows the ports the local host is listening for, it doesn’t indicate if the port is truly open through the firewall. Using TelNet is much more effective as it allows you to see if port is open from source to destination. Enjoy.
How to use:
Google has released a new JPG encoder that reduces file sizes up to 35%. This could mean slimmer pages and faster response times. Yay.
Check it out here!!!
Canadian Immigration Website Crashes with Donald Trump victory in the election.
I wonder if this will create demand for performance testing service(s) and if so, there could be significant demand moving forward prior to each election season.
The SuperBowl effect:
It’s become so common, some companies are now predicting which sites are most likely to crash before the event even occurs.
Situation: Someone on your team has accidentally deleted Test Cases / Scripts / Results / etc. from ALM.
Just in case you aren’t familiar with the structure HP ALM stores data, here are the basics. All of the data stored in ALM (test cases, runs, defects) live in a database on a SQL Server. A unique DB exists for every ALM project.
Usually when you suffer this kind of event, you have only a few options:
- Restore the specific DB impacted. Now, if your lucky the SQL server routinely backs-up all DBs stored on it. (That ALM is configured to use) If that is the case, here is what I think the best solution is. Completing Step 2 reduces the impact to only one project and allows you reconcile differences from the impacted project and the restored one. It also protects other teams if the Server is a shared system vs. doing a complete restore of a Drive in totality. Following the steps below will create a new project in ALM with the restored data from a back-up.
- Login to HP Site Admin
- Create a new Empty Project (Project X)
- Note the DB name for this new project. (I.E. NewProject_DB)
- De-activate the New project in Site Admin
- Open SQL Server, and Re-name the DB you just took Note of (NewProject_DB) and append it with _Old (NewProject_DB_Old)
- Identify the DB of the Project that lost the data (I.E. SomeoneDeletedME_DB)
- Restore and rename the DB (SomeoneDeletedME_DB) from back-up to the one created in the new project. (NewProject_DB)
- Activate the new project (Project X) in Site Admin
- Assign an Admin user to the project
- Login and verify procedure was successful
- Restore the entire System (via many means). While this will do the ‘trick’ it will also wipe out all progress from all Projects in ALM. Meaning, if you have multiple teams using ALM, everyone will be impacted. Also, if this is a shared server, you could impact many other teams. If restoring a system, ideally if you can specify the drive that will help to a certain extent. This should only be done as a last resort.
- Do Nothing. If you don’t have any back-ups then you better get to work….
HP ALM 12.50 Administrator Guide
PC Host Installation Error Solved.
My team and I were struggling to get a PC Host added to the LAB. We knew the issue was caused by an access issue, but nailing down the exact problem was quite difficult. Now, I’ve generalized the error by indicating the Domain\User as most PC installations use custom user names instead of the generic IUSR_METRO account.
Failed to create process [C:Program Files (x86)\HP\Performance Center Host\al_agent\bin\alagentservice.exe] with user [DOMAIN\USER] windows error code 
How to Solve It:
The PC service account must have rights to Logon Locally to the system in question. In my team’s instance, we saw that our PC Service Account was failing to login and the Logon Type = 2 was viewable in the Event Viewer. Once this restriction was removed from the user, we were able to successfully add the system to the PC Lab.
The HP requirements for access for the PC Service Account aren’t ironclad. Meaning, in our instance we were able to determine that the Logon Locally right is only required to add the system in the LAB and isn’t required afterwards.