Getting a strange ”Value cannot be null. Parameter name: type” error in HP ALM?
Question ID: 105727

We are getting the above stated error "Value cannot be null. Parameter name: type" in a pop up message box after connecting to our HP ALM installation.

What could it be?


Marked as spam
Posted by (Questions: 379, Answers: 35)
Asked on November 13, 2014 1:08 pm
Answers (2)
Private answer

Hi HomerJ,

This issue could be occurring due to the client being registered for the older patch (some files will need updating due to the newer patch being installed). I have seen this where projects have certain add-ins that require registration and after the patch it caused the issues as the re-registration is needed for this particular user's system. You can try some of the following suggestions to fix the issue:

1) try to re-run the connectivity and the client registration add-ins from the add-in/tools page (label depends on the version) 2) Remove the client installation and temporary files and then reconnect to the server to download the files again Open file Explorer and delete the following folders (may vary dependent upon OS versions and ALM versions in use (you may have to show hidden files and folders to see these as they are hidden by default): C:USERSAppDataLocalHPALM-Client (delete the ALM-Client folder) C:Program DataHPALM-Client (delete the ALM-Client folder) C:USERSAppDataLocalTempTD_80 (delete the TD_80 folder) 3) Obtain a copy of the HP Client Uninstaller and run it on the affected system and make sure to select the ''Full Clean UP'' option in the lower left side of the initial screen, and run the uninstaller on the system.

I hope these suggestions help.

Thanks, Dan

Marked as spam
Posted by (Questions: 0, Answers: 770)
Answered on November 13, 2014 1:26 pm
Thanks, the re-registration did the trick. Yes the one project did have some extensions that weren't on other projects and this is probably the cause of the issue. Thanks!!!
( at November 13, 2014 1:27 pm)
Private answer

Hi @HomerJ and @Dan,

We were having the same error show up for only one of our projects. In our case this was being cause by an enabled Project Extension that was not found on any other projects. The extension was the Application Model extension version 2.6. We were able to resolve this error following these steps:

1. Open Internet Explorer and go to Internet Options
2. Click on the Advanced Tab
3. Scroll down to the security section and uncheck ''Check for publisher's certificate revocation'' and ''Check for server certificate revocation*'' options
4. Restart Internet Explorer and try to login again

Thanks to @KevinHedgecock for determining the project extension was enabled for this particular project.

Marked as spam
Posted by (Questions: 0, Answers: 1)
Answered on May 6, 2015 8:57 pm

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top