Security Issue with Installing PSQL Client Remotely on User's Workstation

Q - I tried to install PSQL Client remotely on a user's workstation, when I received the following message:

          Pervasive PSQL requires administrative privileges or elevated privileges

See the following sample screen.



I recognize that this means I need to run the PSQL installation package as an administrator.  So I did a right click on the PSQL installation package and chose "Run as Administrator."  See sample screen below.



But I still got the exact same error message.  Why didn't the  "Run as administrator" option work?

A - As you know, installing PSQL Client requires administrator or equivalent privileges on that workstation. If you already logged in on the workstation as the administrator or an equivalent user, then the right click to "Run as Administrator" procedure should work.  

The issue is that when you help a user remotely, your user often does not have administrator rights to his or her workstation. Since you are trying to help the user through a remote access utility such as GoToSupport or TeamViewer, you are running in their security context.  In a scenario like this, it is not suitable for you to ask your user to log out and reveal your administrator account information to your user so he or she can login on your behalf.

In this case, the proper solution for you is to hold down the "Shift" key on your keyboard, and do a right click on your mouse for the PSQL installation package.  When you do this, one more option -- "Run as different user" -- will appear in the popup menu.  See sample screen below.



When you choose this "Run as different user" option, the system will prompt you for the username and password.  Enter the administrator or equivalent username and password.  See sample screen below. Then PSQL installation package will work.








Pervasive PSQL

  1. Btrieve Error Codes 001 - 199
  2. Btrieve Error Codes 3000 - 3099
  3. Btrieve Error Codes 3100 - 3199
  4. PSQL Version Required by Each Elliott Version
  5. Do I Need to Change PSQL Server Engine Default Parameters After Installing It?
  6. New Elliott PSQL Server Processor and RAM Suggestions
  7. Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?
  8. Received "Your Computer Does Not Have PSQL 10 or 11 Client " Even though PSQL Client Is Just Installed
  9. Btrieve Error 161 on Password File When Starting Up Elliott
  10. Problems with Using Pervasive Rebuild Utility on APOPNFIL and AROPNFIL Tables
  11. Security Issue with Installing PSQL Client Remotely on User's Workstation
  12. PSQL and Distributed File System (DFS)
  13. How Do I Turn on PSQL Relational Engine Security?
  14. An Example of Debugging NOTE_ORD_VIEW PSQL Expression Evaluation Error
  15. Btrieve Error 025 on COP Open Order by Salesman Report
  16. What Is the *.^01 File for My PSQL Btrieve Table?
  17. Suggested Files to be Monitored by Audit Master
  18. Pervasive Backup Agent Is Not Compatible with Creating Work Files
  19. Hardware Recommendations for Your PSQL Database Server
  20. How to Optimize SQL SELECT Statement When Retrieving Data from Invoice History
  21. New User-Defined Functions in Elliott DDF
  22. How to Improve Query Performance When Retrieving Data from Notes & Invoice History
  23. How to Retrieve Tracking Number for an Order from Notes
  24. Actian PSQL Not Started Automatically After Server Reboot
  25. Create a New Database in the PCC for Relational Engine Access
  26. Slow PSQL Relational Engine Performance
  27. IPV6 May Cause Problem for PSQL 11 Relational Query
  28. DDF Files in DATA Folder May Confuse PSQL
  29. What to Do When PSQL 11 License Is Disabled
  30. Quick Installation Guide for Audit Master
  31. Quick User Guide for Audit Master

Feedback and Knowledge Base