The DefaultValue expression for the report parameter 'UserTokenSIDs' contains an error: That assembly does not allow partially trusted callers.

Question

Started receiving the above error message in the last couple of weeks. This happens whenever I click on the View Report button of any of the canned reports in Configuration Manager. Has anyone seen this specific message? I have found many instances of the first part (up to the colon), but not anything relating to the "assembly" part of the message.

Answer 1

So just got off the phone with MS on this issue and I am back to working in both my environments.

Basically we made backups first via vmware snapshot.

Determined if the reporting services we're running under a service account - in my case yes. Made sure we had credentials / password etc

opened up the srsrpsetup.log and srsrp.log and kept them open

Then navigated to administration section within sccm and went to servers and site systems roles. Determined which server was running the reporting services - in my case it was the primary. Then we right clicked on reporting services -and looked at properties / took a screen shot.

Then removed reporting services

Then went into windows services and restarted the sms_executive service.

Then came back and reinstalled reporting services using same config as before.

Then restarted the sms_executive service a second time and waited about 2 min for the website to spin up etc.

Then tried to run some reports and all was good

We did get one error during testing about the site not being running but gave it another minute and all came up.

We also opened up report server configuration manager from the start menu, connected and then selected web service URL and verified that all was coming up etc.

One of my environments is http and the other is http / https.

He did say that if this did not work there was a reg key that needed to be adjusted but he did not share that key with me.

Anyways - hope this helps

Peace

Answer 2

I have an active case open with Microsoft that I opened yesterday. The tech I am working with acknowledged that they have received other calls for the same error message and are working on a resolution and may issue a bug notice.

I will be meeting with them again later this afternoon and will post any updates.

Questions for you Eric -

1. Are you running Sql Server 2019
2. Is your OS 21H2
3. Did you recently install SQL Server 2019 Reporting Services 15.0.9098.6826, 2025/01/06

I have 2 seperate sccm environments running the above and installed the reporting services patch last Friday night. Up until then all had been fine.

Answer 3

Problem fixed. We ended up just removing and then adding back the Reporting Services Point from the site server and that allowed all of the canned and custom reports to work.

I don't know of any changes that were made to any configurations prior to this blowing up as I am not the only person in there. We'll keep an eye out for anything else. Thank you all for your recommendations.

Answer 4

Is your account from a 1-way trusted domain?

Answer 5

This is NOT an answer or fixing it the right way. This is a POTENTIAL 'hide the problem' fix cough

Either...

• In each report, change the parameter for @UserSID to be the explicit value of DISABLED

OR

• Sitewide: in registry on your server hosting your reporting point, HKLM\Software\Microsoft\SMS\SRSRP, change “EnableRbacReporting’ from 1 to 0

Try the regkey and see if that works. I do not think you need to restart your reporting point service or reboot the server after adding that regkey.

If you just-so-happen to work in an environment where your reports ARE sensitive and you have setup RBAC roles specifically for reporting and collections to make it so that people get 'just the information they should see', then you may need to turn off that site-wide regkey (even if it worked, hopefully), and try to figure out what the real issue is.