• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    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.

‎05-19-2020 12:19 PM

HP Recommended
Product: Web JetAdmin
Operating System: Microsoft Windows Server 2016

We've had Web JetAdmin running on a server with Windows Server 2016 for a while using the included SQL Express.  The server was basically underutilized with only Web JetAdmin on it, so it was decided to install some other things on the server.  Those other things required a full version of SQL rather than SQL Express.  So - our SQL admin exported the Web JetAdmin database, removed SQL Express, installed SQL 2017, and imported the Web JetAdmin database into SQL 2017.  SQL 2017 is running on the same server as Web JetAdmin, just as SQL Express was.

 

Web JetAdmin no longer works since this was done.  Web JetAdmin indicates that Microsoft SQL Server is stopped when we try to start Web JetAdmin.  SQL Server is not stopped.  I've logged in to SQL Server Management Studio and verified that the HPWJA database is in there.  I've verified that all necessary services are running.  I need to get this running ASAP, and the other option I've been given by my manager if I can't get it fixed is to remove and reinstall Web JetAdmin - basically starting all over again.  I really don't want to do that, because it's a TON of work to start over again because I'll have well over 100 subnets I'll have to add in and scan.  There's GOT to be some way to get it to recognize this existing database that got moved over to SQL 2017 - I just haven't been able to figure it out.

 

Can anyone please help me with this?

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 Terms of Use and Rules of Participation.

Didn't find what you were looking for? Ask the community

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