Feedback
Did this article resolve your question/issue?

   

Article

Shutting down a database fails with error 541 when started by the AdminService or a local administrator account.

« Go Back

Information

 
TitleShutting down a database fails with error 541 when started by the AdminService or a local administrator account.
URL NameP4177
Article Number000172017
EnvironmentProduct: Progress
Version: All supported versions
Product: OpenEdge
Version: All supported versions
OS: Windows
Question/Problem Description

Attempting to shut down the database using proshut or _mprshut.
Database started from ProControl or via the local administrator account.
Domain Administrator is unable to shutdown a database that was started as a local system account, even though the domain administrator account is a member of the local administrators account.
Steps to Reproduce
Clarifying Information
Error MessageInvalid shutdown request from <user-id> on <tty>. (541)
Invalid shutdown request from <user-id> on CON. (541)

User <username> cannot disconnect user <username> . (2258)
User <username> cannot disconnect user SYSTEM. (2258)
Defect Number
Enhancement Number
Cause
Error (541) indicates that the user who is attempting to shutdown the database did not start it.  The user, therefore, does not have the authority to shut it down.
The user needs to have local administrative rights to shutdown the database.  

Even a user who is part of a domain admin login account, who by default, belongs to the local administrator's group, does not inherit all of the rights and privileges of the local administrator.

This applies to any action that involves a Windows service.
EXAMPLE: ProService or AdminServer, under the System account, started the database.
Resolution
Add a local user account with the same name and password as the domain login account.  Add the new users to the local administrator's group.  This will allow the user to stop any database started by ProService or the AdminServer.  

The reason this resolution works is that is allows for checking of the user name and not the fully qualified ID as it should.  Even if we expand this to cover Active Directory Domains, we still need to interact with the Windows UAC (User Account Control).  Need a way to test for a Windows administrator by being in one of the enabled local or domain admin groups.

It was determined that the Progress Product is functioning as designed.
 
An enhancement to the product can be requested through the Progress Community via an Ideas submission.  Customer feedback is valuable and Idea submissions are monitored by our Product Management team.  Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release.  Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea.
 
An enhancement request has been submitted as an Idea on the Progress Community.  To promote the Idea, click on this link:  https://community.progress.com/community_groups/products_enhancements/i/openedge_database_enhancements_-_tell_us_what_youd_like_to_see/allow_local_administrators_group_including_domain_administrators_to_run_jobs_against_databases.aspx

For detailed information on how to submit an Idea, please refer to Knowledge Base article  How to submit an idea for a Progress product enhancement (embedded video)
Workaround
Notes
Last Modified Date11/20/2020 7:14 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.