I have Main SSRS report with few drill down reports calling same main report with parameters. It works fine in Regular SSRS. When I upload the same report on Azure the main report works fine without problem. When I click on the drill down links it keeps on giving error saying The Item "reportname" cannot be found. Tracing id is : (rsItemNotFound). What change I need to make in the SSRS to have the drill down report work in Azure environment.
There shouldn't be a need to change anything between between regular SSRS and Azure Reporting.
I had a simular problem once. In my case it happened since I renamed the report at one point, but the drill down action was still using the old report name. Maybe you have a simular problem?
Also, check out the Azure Reporting limitations over here (in case your report happens to use an unsupported feature like RDCE)
Related
Something really strange is happening with SSRS. I have a report which is powered by a stored proc which uses a lot of TSQL and CTE's to set variables ect... I know that there's no problem with the procedure as it runs in SQL and also runs within Visual Studio and returns a full data set. The issue I'm having is on deployment, I can't seem to get the report to return data when running it from the reporting server. The headers of the table and parameter are displayed but just no data.
I've tried the following:
- Deleting the .DATA file
- Clearing cache
- Checking for data source errors
- Checked the report server error log
- Rebuilt RDL and created a different report with the code
I'm clueless on this one, it's something I've never seen before.
Please help.
Much appreciated,
Thank you
Ri
I have created Web performance testing using visual studio 2017, Most of the pages are data driven by Login, Change of lists etc is there
I have added extraction rule, and when i do load test of the same WPT it gives me errors 403 and fail's the test
My question here is how should I make it work
Thanks in advance
A 403 error usually means that your VS script is failing at login. It is most likely happens due to one or several dynamic values that VS plays back as recorded. To fix it you need to find and manually correlate them by creating extraction rules and parameters somewhere at the beginning of your script.
It looks like you already created some extractors, but if your script is still failing, chances are that you did not create all of them. Try the manual correlation technique described in my article.
Or check our Web Test Builder for Visual Studio referenced here to automatically create missing extractors and parameter.
We've setup some different load tests and need to generate/send the result pr. e-mail, a link, pdf or similar. The output and metrics are saved to a database (resultstore), but I haven't been able to find too much information on how to generate a report without having visual studio. One thing that comes into mind, is creating a custom report in reporting service (any one know of existing reports I could use?).
Any thoughts?
Thanks
Ended up with creating a report myself using reporting services. If I can make generic enough, I'll post it here.
My company participates in Windows Error Reporting via Winqual. We'd like to add some additional data to our crash reports, using WERRegisterMemoryBlock. Obviously we'd like to make sure this is working before we ship our next version. How can we test it?
Is there a way to locally preview precisely what is going to be sent? Does this realistically reproduce what we are going to be able to retrieve from Winqual?
Alternatively, can we generate a real report from a developer machine, then retrieve the report from Winqual? How would we distinguish this test case from the rest of our Winqual data?
[...] can we generate a real report from a
developer machine, then retrieve the
report from Winqual?
build a special test version of your application
upload a product mapping for this test version to WER
crash the test version on a machine with error reporting enabled
check Winqual, after a couple of days a report should show up
if the report does not come with CAB data already, enable additional data request (in Winqual)
crash the test version again on a machine with error reporting enabled
check Winqual, after a couple of days a report with CAB data should be waiting for you
download the CAB data and check if/that it contains what you need (you will need to use WinDbg to get the full picture, VS is not as thorough with minidumps as WinDbg)
How would we distinguish this test
case from the rest of our Winqual
data?
give the test version a special name and version (EXE name and *.rc)
just using a different "product name" and "product version" (=WER friendly names) is not enough to get an extra event ID / bucket, but an extra EXE name plus "Product Name" for the application mapping should do the trick
The best test would be to map a test only version of your product. You can verify that the expected information is present and then make sure you change the version and upload a new product mapping file before shipping
I can run all my reports from report studio just fine. So its not a question of query or data or even report specs.
When i call them from URL i am getting no data in the report. There obviously should be data.
We had just upgraded from 8.2 to 8.3 and it is not all the reports... only a select few.
This is serious problem since our users can no longer run these reports.
please help.
-k
This was worked around by recreating the reports from scratch in 8.3 by copying over all the contents using the clipboard and saving it over the old one. There must be something wrong with our reports and the cognos upgrade engine.
This fixes 90% of our reports. we still have some that do not behave correctly.