Hi @saanah khan ,
Can you run the report via SSDT/Report Builder locally?
Double check you have both catalog and system level permissions on the report.
Try to modify the credentials used to datasource, maybe set to stored credentials to see if that works.
In addition, check the Execution log to see which period it spent most like here say.
Also see the error log for more details.
You may use SQL Profiler to catch the trace to do more analyze.
Regards,
Zoe
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
What can I do if my transaction log is full?--- Hot issues November
How to convert Profiler trace into a SQL Server table -- Hot issues November