SQL Server

Troubleshooting SQL Server 2014 Roles

Troubleshooting SQL Server 2014 Roles

If you have problems with SQL Server 2014 roles, review this troubleshooting checklist to find
potential solutions.

1. Install the latest SQL Server 2014 service pack.

Because many SQL Server 2014 roles bugs were fixed in SQL Server service packs, you should
install the latest SQL Server service pack.
At the time this article was written the latest SQL Server 2014 service pack was service
pack 1. You can download the SQL Server 2014 service pack 1 at here:
https://www.microsoft.com/en-us/download/details.aspx?id=46694

2. User obtains incorrect data when two users in the same security role run a client
report in SQL Server 2014 Analysis Services (SSAS 2014).

This is SQL Server 2014 bug. This bug was first fixed in Cumulative Update package 4 for
SQL Server 2014. You can download the Cumulative Update package 4 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/2999197

3. Non-admin role cannot receive correct ChildCount estimates for parent/child
dimension leaf members in SSAS 2014.

In this case, all hierarchy members display a drilldown symbol, even if you are looking
at leaf members with nothing to drill down. This bug was first fixed in Cumulative Update
package 6 for SQL Server 2014. You can download the Cumulative Update package 6 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3031047

4. The error 920 may occur when you modify the database script level.

This error indicates that only members of the sysadmin role can modify the database script
level. To resolve this problem, ensure that user, who modify the database script level,
belongs to the sysadmin fixed server role.

5. You can get the error 923 when access the database.

This error indicates that database is in restricted mode. To access this database you must be
a database owner or member of the dbcreator or sysadmin roles. Ensure that you have appropriate
permissions when access the database.

6. The error 2762 may occur when you activate the application role in the current database.

This error indicates that you activate the application role by executing the sp_setapprole system
stored procedure with incorrect parameters. To resolve this problem, check the sp_setapprole
procedure parameters and resubmit the procedure again.

7. You can get the error 4602 when grant or revoke the CREATE DATABASE permission.

To grant or revoke the CREATE DATABASE permission the user must be a member of the sysadmin
fixed server role. To resolve this problem, ensure that you have appropriate permissions.

8. The error 9939 may occur when you try to change the database owner.

This error indicates that current user or role does not have the required permission to set
the owner. To change the database owner, the user must have TAKE OWNERSHIP permission on
the database.

9. You can get the error 14366 when you try to change the owner of a schedule.

To modify the owner of a schedule, the user must be a member of the sysadmin fixed server role.
To resolve the error 14366, ensure that you have appropriate permissions.

10. The error 14391 may occur when you try to detach a job schedule.

This error indicates that only owner of a job or members of sysadmin fixed server role can
detach a schedule. To resolve this problem, ensure that you have appropriate permissions.

11. You can get the error 14392 when you try to purge history of the job.

The user must be the owner of the job or member of the sysadmin fixed server role or
SQLAgentOperatorRole fixed database role to purge history of the job. To resolve the
error 14392, ensure that the user have appropriate permissions.

12. The error 14393 may occur when you try to start or stop the job.

This error indicates that only owner of a job or member of the sysadmin role or SQLAgentOperatorRole
role can start or stop the job. To resolve this problem, ensure that you have appropriate permissions.

13. You can get the error 14394 when you try to modify or delete the job schedule.

The user must be the owner of the job or member of the sysadmin fixed server role to modify
or delete the job schedule. To resolve the error 14394, ensure that the user have appropriate
permissions.

14. The error 14396 may occur when you try to modify multi-server jobs.

This error indicates that only members of the sysadmin fixed server role can modify multi-server
jobs. To resolve this problem, ensure that the user tried to modify multi-server jobs is a member
of the sysadmin fixed server role.

15. You can get the error 14525 when you try to update or delete jobs owned by a different login.

The user must be the member of the sysadmin fixed server role to update or delete jobs owned
by a different login. To resolve the error 14525, ensure that the user have appropriate permissions.

16. The error 14586 may occur when you try to create new versions of DTS Package.

This error indicates that only the owner of the DTS Package or a member of the sysadmin fixed
server role may create new versions of it. To resolve this problem, ensure that the user have
appropriate permissions.