EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB487202: Error "Failed to delete schedule for trigger" occurs when modifying LDAP synchronization schedule in both LDAP Connectivity Wizard and MicroStrategy Developer


Yating (Tiffanie) Zhai

Senior Cloud Support Engineer III • MicroStrategy


Error "Failed to delete schedule for trigger" occurs when modifying LDAP synchronization schedule in both LDAP Connectivity Wizard and MicroStrategy Developer

Symptom

Open LDAP Connectivity Wizard, any changes to the LDAP synchronization schedule throws the "

Failed to delete schedule for trigger
" error.

ka0PW0000004qT3YAI_0EMPW00000ITp6P.jpeg

Open Developer > Strategy Intelligence Server Configuration > LDAP > Schedules, and changes to schedules throws error "

You do not have DssPrivilegesScheduleAdministration (i.e, Administer Subscriptions) privilege(s) to perform the task
".

ka0PW0000004qT3YAI_0EMPW00000ITp81.jpeg

Error in DSSError.log


[MSISchedulerUtil.cpp:1322] MSIScheduler::Unschedule(): Unauthorized attempt to unschedule: ProjectID=<00000000000000000000000000000000>, UID=<E930C892504DB451C8C4CA971444C811>, TriggerID=<297A791FAA5A462EA92F925FC507521E>, HR=-2147213784.

Cause

The "Administer Subscriptions" user-level privilege is required to add or remove schedule triggers for LDAP configuration. The user with this privilege inherited from Security Role is not allowed to do such configuration.
This is because LDAP settings are configured at Intelligent Server level and not bound to any specific Project. In contrast, privileges inherited from Security Roles are tied to individual Projects, that's why it needs the user-level privilege.

 

Solution

Add the "Administer Subscriptions" privilege to user level.


Comment

0 comments

Details

Knowledge Article

Published:

March 3, 2025

Last Updated:

March 3, 2025