June 24, 2025 at 7:57 pm
Here's the complete error:
An error occurred during local report processing.
The definition of the report '/My Report' is invalid.
An unexpected error occurred while compiling expressions. Native compiler return value '[BC301791] class 'TextBox4_TextBoxExprHost' and class 'textbox4_TextBoxExprHost' conflict in class 'ReportExprHostImpl'
This is a relatively simple report, and the textbox in question contains a column header label as opposed to any kind of actual expression. There are 3 groups in the report, with PayorType, InvoiceNumber, and SegmentId as the groups. The first line is at the top of the outermost group and contains the PayorType field. The 2nd line is column labels, and is within the outermost group. The 3rd line is the Details line and is within all 3 groups. Am I doing something dumb here ? Any / all feedback appreciated. Also, it appears the SSRS forums haven't been touched in at least the last year, so I'm posting here for visibility.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
June 25, 2025 at 4:35 pm
Just to confirm, you get that error when trying to PREVIEW the report on your local computer, correct? If so, are you using the correct VS version for the SSDT and SSRS version? That is assuming you are using Visual Studio, if using report builder, then SSDT doesn't matter, but SSRS version does still.
If versions are good, do you get the same error if you deploy the rpt to your TEST report server? If it's local only, then it is an annoyance, but you could still test the report on your test report server and the problem is likely a problem with either the rpt file or a version of something is misbehaving. I say TEST report server as I don't recommend pushing anything to prod that is potentially misbehaving. I ALWAYS try stuff on test before pushing to live even if it is a trivial change. Never know when it MAY work fine on my local machine but break on the production server.
Next suggestions involve changing the report. I STRONGLY recommend you make a backup before you make any changes so you can undo everything in the event you make things worse.
If you remove that text box, does the report work? I've seen times (usually in C# or TSQL, not in SSRS/RB/VS SSDT) where an error message is misleading to the actual problem. So removing the text box MAY help you see the ACTUAL error and correct it then put the text box back. If the report works without the text box, does it still work if you re-create the text box (ie not "undo" but add a new text box with the properties you want)?
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.
June 26, 2025 at 1:59 pm
Turned out I just needed to recycle Visual Studio on my laptop. That solved the funky problem. Now I have to fight what seems like a silly problem. I have a multi-value capable parameter that I would like to display all the selected values in a text box on the Report Header, and I used the following expression:
=Join(Parameters!PayorTypes.Label,",")
This now produces the following errors:
In the Preview pane:
The server did not return a meaningful reply...
In the Error window:
Severity Code Description Project File Line Suppression State
Warning [rsInvalidExpressionDataType] The Value expression used in textrun 'Textbox7.Paragraphs[0].TextRuns[1]' returned a data type that is not valid. ...
BUT....
Then I recycle Visual Studio after changing the expression to include the CStr() function surrounding the Join() and the problem disappears... Going to recycle it yet again after adding a space within the quotation marks following the comma... and yet again, I ended up recycling Visual Studio on the laptop to get the changes to work. Really weird. BTW, Visual Studio 2019 CE. I also am behind on the version, as it turns out, so I'll need a LAN Admin to permit the update to occur. More of an FYI...
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
June 26, 2025 at 3:33 pm
If memory serves, SSDT for VS 2019 is an option during install, so it could be you need a patch update.
As a thought - can you use report builder instead of VS? If the report isn't complex, I find that report builder can handle it pretty well. Once the report gets complex though, I prefer to work with it in VS. BUT once VS starts giving me grief, I sometimes switch back to RB for that one report just so I can get it done.
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 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply