Forum Discussion
remove data source created on report server
hello,
i created two datasource on the report server they were created succssfully , I messed up while working on the security of the second datasource and endedup deleting both builtin administrator & myself
Now i am unable to view home folder of the report as it showing empty where as in reality it show one folder and atleast one data source as i did mess with security of the first data source
currently my view
where as i am able to access the folder which i have created at home and also the first datasource as shown in screens below
and when it try to access the second datasource i given error mentioned in below screenshot
http://XXXXXXXXX/reports/manage/catalogitem/security/conventional?_pk=s1crz700
is the link access the security setting of 1st datasource tried to the same for the second but was met with an error
http://XXXXXXXXX/reports/manage/catalogitem/security/takaful?_pk=s1crz700
i can view both sources in my report builder aswell meaning both of them are on the server.
is there a way that i can reset the the security settings or delete the second datasource ?
Thanks
Thanks. i fixed the issue using MS sql server management studion and going into [Catalog] table of the report server and updated the [policyid] column of the 2nd data source same as 1st data source as it had all the correct privileges assigned.
4 Replies
- d_gosbellSuper User
If you've removed all content management rights from the home folder and data source I am not aware of any supported way of getting those back other than restoring a backup of the Report Server database from before you made the security changes.
It might be a good idea to raise an official support ticket as the support engineer may know of a work around to fix this without resorting to restoring a database backup.
- SSWADOODHelper I
Thanks. i fixed the issue using MS sql server management studion and going into [Catalog] table of the report server and updated the [policyid] column of the 2nd data source same as 1st data source as it had all the correct privileges assigned.
- LaxmikanthGNew Member
Perfect, it worked like a charm. I was having trouble accessing an old data source and this policy ID update made it possible to access it. Thanks a lot for posting this solution here. Saved lot of time.