Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Unable to generate Patch Manager reports and access Managed Computers

Unable to generate Patch Manager reports and access Managed Computers

Overview

When you run a report or expand the Managed Computer group, both attempts fail. 

Environment

  • All Patch manager versions
  • MS SQL - All supported versions

Cause 

SQL permissions are not assigned to ewreportuser.

Resolution

  1. Open SQL Server Management Studio.
  2. Navigate to Eminentware db > Security > Logins and select ewreportuser.
  3. Right-click > Delete.
  4. Open the Server Security > Logins and select the ewreportuser.
  5. Right-click >Delete.
  6. Right-click Logins > New Login.
  7. Name the new login:
    ewreportuser,
    No password is required.
  8. Set the default schema to Master.
  9. Go to User Mappings and select Eminentwaredb.
  10. Assign Eminentwaredb with public and db_owner permissions.
  11. Go to the Eminentware db logins.
  12. Make sure the account displays and has the proper permissions.
    You can now run the reports.
 

 

Last modified

Tags

Classifications

Public