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=184.108.40.206, 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
Please log in to participate..