• ×
    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
We have new content about printers, Click here to check it out!
Check some of the most frequent questions about Instant Ink: HP INSTANT INK, HP+ PLANS: INK AND TONER.


Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs AND MORE.
HP Recommended

Hi!

 

We're trying to set up HP Jetadmin 10.5SR2 with remote SQL server, however we've ran into some issues.

We've tried to use the following documentation: 

https://kaas.hpcloud.hp.com/pdf-public/pdf_3017812_en-US-1.pdf

https://kaas.hpcloud.hp.com/pdf-public/pdf_6642757_en-US-1.pdf

 

However, the documentation seems to contain outdated information, like referring to "WjaSetup.exe" when the file you can download is called "HP_Web_Jetadmin_10.5_SR2_64_bit_SW_J6052-10613".

 

Also the described option "/V"WJA_SKIP_DB_INSTALL=1" does not seem to work.. atleast there is a Microsoft SQL Server folder in Program Files

 

Also, we could not find any information in the documentation if a MS SQL Always-on Availability Group database are supported.

 

 

Even so, we "soldiered on" and tried to configure a remote SQL server, and we used SQL Authentication, and we can see that the server connects to the SQL server, and we also saw that the service did modify the DatabaseSetting.config.xml file to create a "hash" value of the password in that file.

 

However, when the service "HPWJA Service" starts, and we try to start the HP Web Jetadmin application, it just hangs on "Waiting for service start"..... and when checking the eventlog/application log we find a Warning message that states "The HP Web Jetadmin service startup is delayed due to database initialization failure."

 

So, anyone have any clues as to what could be the issue here ?

 

 

Edit:

 

It seems it did not support using Always-On Availability Groups, and once we removed that from the equation, we got Jetadmin Working with a remote SQL server.

† 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>.