I am currently working on a project via my visual studio 2019 software. i have the correct coding and the design for the project. however, whenever i run the program, it shows that there are no issues at all but I do not receive an output. my txtbox or lstbox (depending on the project) is blank and there are no error messages. I have a total of 6 projects due and all 6 projects are showing the same result. i am new to this and have minimal knowledge.
Related
I'm battling with a strange one. I've created a report using Visual Studio and deployed it successfully (so I thought). When I run it from within Visual Studio it displays data perfectly. But when I try and run it from online directly it allows me to select the parameters, it goes through the motions but returns no data. What could the issue be? I tried refreshing the fields in the Query Editor but this didn't work either.
In Microsoft Visual Studio when i run a Report using a Preview the data is showing and when the same report i run from server side its not showing the same data as per the Visual Studio Preview
please suggest
Visual Studio caches locally data in order to reduce the generation time for design puroposes, it will only update the data if you change the parameters values so if your report doesn't have any parameter you will get old data.
To refresh Visual Studio data preview the report and press the refresh button inside the generated report.
Let me know if this can help you.
I had a very similar problem. When I previewed on VS 2015, everything displayed perfect, but when I deployed to my server successfully, only one field wasn't showing up.
What ended up working was changing my report data sets from shared to embedded. Even though they were referencing the same query, somehow there was a disconnect when referencing the shared data set rather than embedding it directly in the report.
I have some users intermittently receiving this error 'Unable to read data from the transport connection—The connection was closed' when viewing an ssrs report through the ReportViewer control.
The user can access the SSRS via web browser and not replicate the error
On multiple pages reports the first page loads and where it states 'Page 1 of totalPages' this totalPages counts up as the rest of the pages are loaded. Half the time it doesn't display an error but not all pages are loaded.
We are running SSRS express within a windows application.
SQL Express installation is a named instance
When it happens the screen hangs for around 2 minutes
It occurs on a couple of reports but not others different reports. It's not data amount related, sometimes 50 page reports come through OK and sometimes 2 page reports fail.
If it fails the user can run the report again and it usually works the next time. Sometimes it takes 3-4 goes.
Nothing has changed recently, I'm told this was always the case but they never reported it.
I tried giving the single shared ssrs datasource sa user credentials - no change
Some reports appear to load OK everytime while others error out or only load a couple of pages.
What I have tried so far:
I cannot replicate this error from our remote client, I just ran 20 successful reports no dramas from within another client installed on the same network. But I can replicate it from the users computer with both my account and their account.
I cannot see anything relevant in 'C:\Program Files\Microsoft SQL Server\MSRS10_50.MyInstance\Reporting Services\LogFiles'.
Thanks in advance for tips on where to look for clues and ways to resolve this issue..
I have resolved this by removing the ReportViewer UI control and we are now creating a pdf of the report using ReportViewer.ServerReport.Render() and opening with Process.Start(). The client only wants a pdf or a print out so we don't need the report viewer as such.
I'm not sure why the connection was closed at times, maybe it's network related as I couldn't replicate on a machine located physically next to the server. Either way this is resolved, onto the next project!
VS2008 / TFS Build 3.5 / Ent Lib 4.1
I have a rather large solution that contains several apps. They are all currently using Enterprise Library (v.4.1) for their data access layer.
I added and locally tested a new data access layer that uses LINQ to SQL- it was fast and easy to add and the test went fine. But...
When I checked in the project, it would not complete the build - I get a "Partially Succeeded". There are some warnings, but those exact same warnings were there prior to the build failing.
I took the data access class back out (along with the code that calls it) and rebuilt and it builds fine.
I then added an empty new class and put a single variable in it and referenced it from the code. That built. I then created a new LINQ to SQL class in that new project and did not even reference it. When I checked that in, the build failed again with the "Partially Succeeded" message. No extra errors or warnings.
I love LINQ to SQL, I have used it in a few projects outside of this system, but I now have many hours into attempting to get this to build with no success.
Are all the same tools/libraries installed on the build server as on your desktop - Perhaps the server doesn't have the same vs or .net service pack level? Try running the build "manually" on the build server - load up the solution in Visual Studio on the server and execute the build within the IDE rather than under the TFS build system - this may report problems that you don't see so easily in the automated build.
Check the build log. Visual Studio often reports errors in the output pane text or build-server log text that are not picked up by the GUI error windows. So you will think a build succeeded but an output file has "quietly" not been generated. TFS build logs are usually huge so they are a pain to work through, so start by searching for keywords like "error" or the name of the project that fails rather than trying to read through line by line.
OK, we found it. The issue is on stack overflow elsewhere at
Visual Studio Setup and Deployment build fails with no errors
The issue is a bug in MS setup and deploy that breaks when it hits a line in the project that uses Linq. You have to comment out a line in the project to get it to work. Amazing, ridiculous, and no surprise.
Thanks for the input, it was that input that helped us get to the eventual answer (already on StackOverflow, but didn't have Linq in the title).
I am trying to print a report that contains a bar graph using the report viewer, but running into an error. My reporting server is running SQL Server 2005 Reporting Services SP3 on Windows Server 2003 SP2.
Here are some steps that will reproduce the problem (at least for me)...
On a clean machine, I open up the
report, and it displays fine.
I then click the print button, and I
am prompted to install the
RSClientPrint ActiveX control. The
control downloads and installs fine.
I then click the print button again,
and the print dialog appears.
I select a printer, and click "OK".
A message box appears that has the
following text (including the
spelling error)...
An error occured during printing.
(0x80004005)
Any other report I try to print works fine. The only difference between this report and the other ones is that it contains a bar graph. If I remove the graph from the report, redeploy it, and then re-run it, it prints without getting that error.
As far as I know, it is not isolated to a specific machine. It happens to every customer I have talked to, and a variety of machines here in the office.
Has anyone seen anything like this? I have seen similar posts on the web suggesting to uninstall video drivers on the reporting server (thinking the GDI dlls have become corrupt ), install service packs, etc. I have tried every suggestion, but haven't found a good solution yet.
Thanks.
I ended up having to use a paid Microsoft incident on this, but it is resolved now. The issue was that I had a matrix in my report that had dynamic columns. Depending on exactly which date range you picked, the report could have n number of columns. In my case, when a date range was chosen that produced three or more of these dynamic columns, it would cause the matrix to become too large and run outside of the margins of the report.
The report would run and display fine with the matrix being too large, but the incredibly non-descriptive error would display whenever the report was printed or exported.
I resolved the issue by reducing the size of other columns and the overall font size in the report. This prevents the matrix from running off the page in the case of date ranges that produce three dynamic columns. It doesn't solve it in the general case (four or more columns will make it fail), but is good enough for my current purposes.
Microsoft didn't have a fix for the general case (such as a way to make the matrix fixed width).
I figured I should answer this in case anyone else runs across it.
-David