We needed a modification to a Sales Order Form, so in Pilot (cloud) we made the modification to the RDD (copy) and the SSRS RDL and tested it (with the same Sales Order). Once approved we moved it to Live (both RDD and RDL) but in Live the report does not render and gives the following error in the System Monitor:
The SSRS server returned the status code 500 (InternalServerError) with the following error text:
Default value or value provided for the report parameter ‘RptLanguageID’ is not a valid value. —> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportParameterException: Default value or value provided for the report parameter ‘RptLanguageID’ is not a valid value.
I’ve tried the export/import from Pilot to Live both with classic UI and Kinetic UI, both yielded the same result.
I even exported the ‘not working’ items from Live and imported into Pilot and the report works fine in Pilot.
This doesn’t make sense. What could possibly be going on here? Any ideas for troubleshooting?
Did you leave a default value in the GUID parameter?
The connection setting in the RDL pointing to the correct server
The query expression in the RDL does have any “cheats” with direct references to ERP tables.
If you run the report as “generate only”, does it make an entry in Sys Monitor? If so do the temp tables in the report data database with the GUID from sys Mon show?
No - I don’t test that way… but I checked anyways, it’s clear.
This may be part of the problem - it is specifying the PilotSSRS root, unlike Live that just references ‘SharedReportDataSource’ So I corrected that and tried again, and got the same error.
-None I can find
It does, and gives the same error. This is a cloud instance, so I cannot check the database.
I did change the RDD to Output as XML so I can confirm that the RptLanuageID is generated in the OrderHed table in the XML and it is there an it’s a valid value.
Just to clarify, the issue isn’t with the value of the GUID parameter, but the error is about the RptLanguageID.
I just don’t understand why this RDL works in Pilot but not Live.
I’ve seen errors mentioning “RptLanguageID”, so often - but having nothing to do with that specific piece of information. So I typically just took that as a red herring. Something that would regularly appear as a ‘symptom’, but not really the root of the problem.
Being cloud based obviously impacts your ability to diagnose this. I’d try the following few things
Make a new report that is blank but uses the imported RDD (not really blank, just not using anything the rdd generates). If it runs,then the RDD is processing properly.
If the blank report runs with without error, start editing the RDL’s query expression, using one table at a time. For s#!ts & giggles, try the RptLanguage table first.
Thans Calvin… all good points… many I had forgotten but I have found to be the case as well… (meaning the error message indicates the error in the wrong place but the error is actually somewhere else).
What I find interesting though, that I still can’t shake (haven’t gotten back to investigating this mess) is that the report works fine in Pilot but not Live.
I really though that data source value was it… but apparently there is something else that is environment specific.