I use stimulssoft report mvc for generating a report in an Visual studio 2015 website.
There is no problem with the local host and all the records in the report are displayed.
But when the software is uploaded to the server there is no record in my StimulSoft Report to my users.
There is this problem for 2 days there is not this problem before.
Related
Here are the details:
OS: Windows 2016 server accessed over RD
Dev tools: VS 2022 17.1.6 & VS 2019 16.11.11. I run VS in Admin mode (both)
IIS Express version: 10.0.22489.1000, 64 bit
Browser Chrome: 100.0.4896.127 (Official Build) (64-bit)
App:.net 4 webforms application that uses ExtJs 6.6.0 classic as front end
Antivirus: CrowdStrike, version 6.36.15005.0.
I have a form with a file field. This link has more information on how the upload works, it basically uses an iframe under the hood.
Now, in VS 2019 the upload works. In VS 2022 the upload doesn't work anymore and it returns the error: "Blocked a frame with origin "http://localhost:38991" from accessing a cross-origin frame." (the error is returned in the client JavaScript code). Just to be clear, I open exactly the same project in VS 2019 and it works, then I open the project in VS 2022 and the uploads don't work anymore.
Both use the same IIS Express process (64 bit). And one minor detail, the upload operation when run from VS 2022 kills IIS Express, it basically evaporates.
Any idea on how to fix this in VS 2022? For now, I have to use VS 2019 in order to be able to test uploads.
Thanks in advance.
Update:
I installed VS 2022 version 17.1.6.
Initially I thought IIS express evaporates upon uploading the file. It actually exits when I select the file in the Open dialog.
The program '[19000] iisexpress.exe' has exited with code 4294967295 (0xffffffff).
When I run the project without debugging, it works fine!
I changed the title of the post from:
ExtJs file upload getting: "Blocked a frame with origin "http://localhost:38991" from accessing a cross-origin frame." when run w/ VS 2022 IIS Express
to
IIS Express w/ VS 2022 crashes when debugging web app and selecting file via file html input on page w/ ExtJs
ok, found the answer here: IIS Express stops suddenly when I click on a text box in my web app.
This did the trick:
The checkbox was clear in VS 2019, a colleague confirmed the uploads work in VS 2019 even with the checkbox selected.
I am using Visual Studio 2012 to develop an MVC 4 web application. I have also created a virtual directory on my local IIS 7 server which points to my MVC application. Both IIS and Visual Studio 2012 point to the same source code.
I usually edit JavaScript files and hit refresh on my browser to reload the JavaScript file.
For some reason whenever I edit the JavaScript via Visual Studio 2012 it is write protected (by IIS) so I have to touch the web.config file in order for IIS to release the file in order to overwrite the file. This is really annoying when debugging because I have to reload the application every time I make a minor change to a JavaScript file.
Has anyone had this issue and how did you resolve it.
Any help would be greatly appreciated. Thank You
Hey everyone.. This is my first time writing an ASP.NET MVC web app, and it's going good. I have no problems there. What I don't have any experience in is SSRS though. Ultimately I want to be able to render reports on my ASP.NET MVC app.
I got the report server installed and running, and it's visible within SQL Server Management Studio.
I created a test report (.rdl) via Business Intelligence Development Studio, and published it to my report server. It's now there, I checked.
My question is how do I tie that into my main application? Do I have to add a reference in my main application to be able to retrieve the report I created? I'm totally lost- I have my main database and my report server both visible within SQL Server Management Studio. That's as far as I got... help???? Thanks in advance..!
Try this: http://geekswithblogs.net/stun/archive/2010/02/26/executing-reporting-services-web-service-from-asp-net-mvc-using-wcf-add-service-reference.aspx
Failing that, if you are new to ASP.NET MVC and you do not specifically require MS Reporting Services (.rdl) created through BI Development Studio, but are satisfied with a standard Visual Studio Report (.rdlc) (This simply means the report may be more or less linked only to the single app. You create these via Visual Studio Project - Right Click -> New Item -> Reporting -> Report) take a look at this link (http://www.danielroot.info/2009/06/how-to-render-reporting-services.html), even though it states how to link Reporting Services, he actually means standard reporting .rdlc files. In essence it publishes simply the output from an .rdlc report as a .pdf and stream it to your user, I have found it to be incredibly simply and a powerful way to quickly publish reports.
Failing that a hybrid of both implementations might allow you to stream your Reporting Service .rdl correctly.
Good luck.
We recently upgraded a major application to Visual Studio 2010.
Unfortunately, we are still using several database servers that are still running SQL Server 2000 (8.0.2055 to be precise).
According to this article (Link), "Since mainstream support for SQL Server 2000 ended on 04/08/2008, Visual Studio 2010 will only support debugging SQL Server 2005 and SQL Server 2008.
We have a lot of stored procedures that we keep in Source Control and execute them from within Visual Studio whenever we need to update them.
Is there any way around this restriction? 3rd-party tool, anything.
While researching this, I saw a few sites that indicate an ODBC connection could be used to get to the SQL2000 box. I was able to create a System DSN and then a Data Connection within VS2010, but am unable to connect to it.
Any help would be greatly appreciated.
Thanks.
Chris
The only way I've found so far is to extract our data library out of the project and keep it in VS 2008 targeted at 3.5 while we're building it. Once it's complete and ready, we open up the primary project in VS 2010, check out the changed files and then use the file system to copy the changed files over.
We then keep the supplementary 3.5 project in source control parallel to the primary project.
They will still build and function in .Net 4.0, but we have found that the IDE will not accept any connections or commands to them.
I have an existing RDL report that I want to convert to an RDLC report for use in an MVC application.
According the the MSDN Site the way to convert it is to rename the .rdl file to .rdlc, include it in the project and then use a ReportViewer control to select the datasource.
Being MVC I don't have a ReportViewer control on my page, I was using this post to help me render the report into the Response stream.
I've renamed the rdl to rdlc and included it in my project but I get the following error when trying to open it:
The report definition is not valid.
Details: The report definition has an
invalid target namespace
'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition'
which cannot be upgraded.
Any ideas how I can convert the rdl to rdlc without having to re-write it?
You cannot convert a SQL Server 2008 Reporting Services report .RDL into .RDLC - Microsoft only knows why.....
See Bill Vaughn's Retraction: The ReportViewer Control does NOT support SQL Server 2008 RDL in Local Mode for some expert insight.
In short: right now, Microsoft doesn't have a working story for converting RDL to RDLC in Reporting Services 2008.
To correct the earlier answer: you cannot render an SSRS 2008 RDL file with the VS 2005 or VS 2008 ReportViewer control in local mode, because the schema has changed in SSRS 2008, but the control was not brought up to par. VS 2010 comes with a ReportViewer control that apparently supports the SSRS 2008 schema.
If the schema were supported, no conversion would be necessary (other than renaming the file from RDL to RDLC, which is how it worked in a VS 2005 environment).
See my question on MSDN about this issue.
Actually, you can convert an .RDL to .RDLC. Copy the report to your report folder on your project, rename the extension from .RDL to RDLC. Just make sure you have the Microsoft.ReportViewer.Webforms reference. I have created a ton of reports, using the Report builder, built and tested them there, then copied them to my project (MVC). Just my 2 cents.