• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
HP Recommended

After applying latest MS Security patches (Feb. 2013) on a Windows 2008 R2 WJA-server, HPWSProAdapter service failed to start.

 

"The HPWSProAdapter service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

 

"A timeout was reached (30000 milliseconds) while waiting for the HPWSProAdapter service to connect."

 

This error is leaving me with some newer HP printers in status "Device Communication Error" because they are depending on this HPWSProAdapter service.

 

Any idea's?

1 ACCEPTED SOLUTION

Accepted Solutions
HP Recommended

Open the registry, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HPWSProAdapter

Edit Multi-String Environment

Insert COR_PROFILER={03191964-0505-1966-BD0E-E92B0C04964F}

so it will look like this;

 

COR_ENABLE_PROFILING=1
COR_PROFILER={03191964-0505-1966-BD0E-E92B0C04964F}
SystemRoot=C:\Windows

 

Mr Kim

View solution in original post

10 REPLIES 10
HP Recommended

I work for HP, but my posts and replies are my own. .....

 

 

Hi Lars,

 

This is an old post but it has no replies.  So, I would like to ask -- were you able to resolve this issue?  I am not a regular participant on HP Forums and am looking at mainly  Web Jetadmin related details here because I am working at HP Expert Days.  Please let me know if you still need help or if you were able to get an answer.  Thanks!

 

Best Regards,

 

BikeRider

HP Recommended

Hi BikeRider

 

Thanks for your time. Unfortunately I have not found a solution to this problem yet.
We have two WJA servers, (one in a lab environment), both showing the same issue.


I've been searching around a lot, but it seems like I'm the only one in the whole world to experience this problem (as usual 😉

 

I'm 99% sure the HPWSProAdapter problem started after applying Feb. 2013 Microsoft Security Patches.
(I was thinking of uninstalling them one by one to see if it helps, but I have not managed to get that time yet...)

 

The security patches applied in Feb. 2013 were:

 

Security Update for Windows Server 2008 R2 x64 Edition (KB2778344)
Security Update for Windows Server 2008 R2 x64 Edition (KB2790113)
Security Update for Windows Server 2008 R2 x64 Edition (KB2790655)
Security Update for Windows Server 2008 R2 x64 Edition (KB2799494)
Security Update for Internet Explorer 8 for Windows Server 2008 R2 x64 Edition (KB2797052)
Cumulative Security Update for Internet Explorer 8 for Windows Server 2008 R2 x64 Edition (KB2792100)
Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2789645)
Windows Malicious Software Removal Tool x64 - February 2013 (KB890830)

HP Recommended

Open the registry, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HPWSProAdapter

Edit Multi-String Environment

Insert COR_PROFILER={03191964-0505-1966-BD0E-E92B0C04964F}

so it will look like this;

 

COR_ENABLE_PROFILING=1
COR_PROFILER={03191964-0505-1966-BD0E-E92B0C04964F}
SystemRoot=C:\Windows

 

Mr Kim
HP Recommended

Hi KPITT

 

Your suggested solution did the trick!

(Even if I don't understand how this issue arose)

 

A million thanks!

HP Recommended

Hi,

 

The Multi String was exactly as you mentioned on my system!

Do you have other solutions in order to fix the service startup?

 

Dann

HP Recommended

When FIPS policy is enabled .That could cause the (HPWSProAdapter ) service not to start.

  1. Run the Group Policy Editor (gpedit.msc ).
  2. Browse to Computer Configuration , Windows Settings , Security Settings , Local Policies , Security Options .
  3. Locate the policy named, System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing .
  4. If the policy is enabled, disable the policy and then stop and restart the HPWJA Service.

or 

Edit the registry 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy

Enable value set to 1

Disable value set to 0

 

This policy blocks the use of all network communication encryption standards (such as SSL) except for TLS and since WJA uses WS which is encrypted to communicate with these devices, it could cause us problems.

HP Recommended

Thank you for the previous suggestions. The 2 registry keys mentioned in previous posts (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HPWSProAdapter and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy) already have the suggested values. Still, the HPWSProAdapter service would not start either automatically or manually.

 

This is a fresh install of HP Web Jetadmin server 10.3 SR4 on a Windows 7 Enterprise platform.

 

When trying to run an alert template, we get a "Communication Failure" error on the alert subscription attempt. The Status tab for the printer shows: "Device Communication Error: HPWSProAdapter Service is not started"

 

As stated before, when we go to Services through the Control Panel we can see the HPWSProAdapter service has not started, and we cannot start it manually. The error we get is: "Windows could not start the HPWSProAdapter service on Local Computer."

 

Below it says: "Error 1053: The service did not respond to the start or control request in a timely fashion".

 

Any suggestions will be welcome.

HP Recommended

After migration from windows server2008 R2 to server2012 I did a fresh install of HP Web Jetadmin server 10.3 SR4 on th new server platform.

 

In order to use a remote SQL datbase I installed the Database Connectivity Licence once again.  After server restart HPWSProadapter service failed to start.

The problem was : I took the old licence. The licencees are node-locked to an IP adress. It seems, a separate licence ist needed for each new HP web jetadmin installation although IP adress didn't change. I ordered a new license and since I installed this one, HPWSProadapter service runs.

HP Recommended

Remote SQL datbase  Database Connectivity module Licence was re-called from Web Jetadmin 10.3 SR 3 version.
So there is no need to install the license going forward.

Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.