If your SSRS setup similar to the one below. You're likely running into a common SSRS Reporting Service Double Hop (aka Negotiate / SPNego / Kerberos/ SSO) issue.
Clients e.g. PCs -> SQL Server A (Hop 1) with SSRS -> SQL Server B (Hop 2) contains DBs where your SSRS data sources are pointing to.
There're 2 solutions to this. Solution 1 is to hardcode credential in each Data Source. Solution 2 is to configure Kerberos Authentication (SPN + Account Delegation). There 3 places need to be configured correctly in order for it to work properly. May be easier to watch the following video which explains things a bit better.
- SPN & Service Account Delegation on Domain Controller
- Authentication Type in SSRS Configuration File rsreportserver.config on the SSRS Server
- App/Script such as Browsers, Web Apps, Python, PowerShell, etc. Integrated Authentication Settings, Additional Modules, Add-ons, etc.
SSRS SQL Reporting Double Hop (aka Negotiate / SPNego / Kerberos/ SSO) ANONYMOUS LOGON Issues