ALM error – Failed initializing plugin ‘Sprinter’. Could not load file or assembly
Question ID: 108587

I have a user reporting that when they are logging into ALM, they experience a "Failed to initialize. Please contact system administrator for help. Description: Failed initializing plugin ‘Sprinter’. Could not load file or assembly ‘HP.Sprinter.lSprinter.lProxy. Version=, Culture=neutral. PublicKey Token=null’ or one of its dependencies. The module was expected to contain an assembly manifest." The affected user is using a virtualized Windows 10 machine. They have been using HP ALM on this VM successfully for months. This issue just started about a week ago. Other users access HP ALM from this machine and do not have a problem. I cannot recreate the issue. It appears to be unique to the one user on that one machine. The user does not have any HP ALM access issues on other Windows 10 VMs they have access to. Please advise what may be at issue here and what can be done to fix.

Marked as spam
Posted by (Questions: 239, Answers: 31)
Asked on August 2, 2018 5:15 pm
Answers (1)
Private answer

Hello. It is possible that the users ALM Client has somehow become corrupt. We may be able to resolve this issue by removing the ALM client from the machine, then reinstalling it. First, I would like for you to run the ALM Client Cleanup Tool on the affected machine (You can download the ALM Client Cleanup tool by clicking the link below). Download the tool to your desktop, unzip the tool, then right click and select 'Run as an administrator'. Leave the 'Extended Cleanup' option selected and click the 'Cleanup' button. Once the cleanup process is complete, reboot the machine. Once the machine is back up and running, open a 32-bit version of Internet Explorer as an admin (Right-click and run as administrator), reconnect to the ALM server and reinstall the ALM Client platform. Once the client platform has been successfully reinstalled, have the affected user try logging into ALM to see if issue still occurs.

[Download the ALM Client Cleanup Tool][1]

[1]: /storage/temp/

Marked as spam
Posted by (Questions: 2, Answers: 300)
Answered on August 2, 2018 5:17 pm
Uninstalling and re-installing the HP ALM client did the trick. Thanks!
( at August 2, 2018 5:18 pm)

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

Scroll to Top