December 2, 2021 at 5:43 pm
Looks to me like your data source is configured wrong on the report server. The error (if I am reading it right... I only know english, so I am just guessing) is that the anonymous logon is not allowed to log into the SQL instance. This is a good practice and I would NOT add it to the instance, but that is one fix.
The other (better) fix is to change who the report server connects to the SQL instance as.
Opening the report in Visual Studio and running it runs the report as whoever is configured to run the report on the visual studio side of things.
The above is assuming you are using a shared data source (which is a practice I recommend as it makes things easier if you ever need to change connection strings). If you are using a connection baked into the report, I think similar logic would apply, but I've not built reports that way as it always seemed like a lot of technical debt...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply