I have a web application written in VB.NET. In my application I have a few RDLC reports that will be generated dynamically. Everything works fine during the development. But those reports are not working after I deployed my web application to IIS. Here are my problems.
(1) All the reports under my RDLC folder are not deployed, I think this is the reason why I got the error “error occurred during local report processing”
My question is why this folder was not published, and what should I set to publish this folder?
(2) If I manually copy those RDLC reports to the destination folder, I got another error “failure: unknown user name or bad password”
My authentication mode is set to Windows. Is there anything else I need to set in my web.config?
I am using IIS 5.1 and my web app has been upgraded from VS2005 to VS2010.
Your RDLC files are probably marked as "Embedded resource".
Right click on rdlc file and change it to "Content" and re-publish.
It will work this time.
Related
I have created an asp.net core mvc web application in visual studio 2019 professional edition. After a successful build when I run the application, I am getting a blank screen in the browser. It is not showing the contents of the index page.
I checked the iis by typing inetmgr in the command window. It is opening up the iis Window. I also cross-checked in the browser window by typing http://localhost/. I am able to get the welcome page in IIS.
I don't know what's the issue here. Any valuable help is appreciated.
Please find the screenshot below.
When I faced a similar issue, it was due to the Web.config file, when the run httpRuntime was set to an incorrect target framework. Maybe remove the targetFramework parameter and see if the auto resolver resolves it.
I have some question regarding VB 2019 RDLC report sharing to the client.
I am creating a setup .exe file for my application and install it locally, it works perfectly on my local PC.
Now I share the .exe to the local client PC, the client PC can access it with no issue
When I set the report reference, the client site is not able to access the report. What I have tried:
manually drag the .dll file to the .exe file location, but no work
manually add the .dll assembly file while creating the setup, but no work
remove the report reference, it works, but I want to use the report reference in order to generate barcode
Can I know any way to solve this problem or any way to know which file is needed to install in client side while I deploying the report with my application?
In my project i sent the barcode image from my code inside the list, table, etc. Along with all data
I have developed ASP.NET project in Visual Studio 2019. When I try to run the project with IIS Express, the webpage says “This site can't be reached” and "The connection was reset".
In taskbar I can see that IIS Express is working and I'm able to debug and step though my code till the very end successfully so I know the service is executing fine without any errors.
Site can`t be reached
I created a new project, just to ensure that there weren't any errors within my config or build files. When I run the new project, I get the same result.
I tried with other browsers as well, but still the same error.
I repaired the Visual Studio using the Visual Studio Installer, and reset everything to default, and had no success with that.
I tried to delete hidden vs. folder and had no success.
Any advice on how to resolve this would be greatly appreciated.
Thanks!
I fixed the issue by deleting Kaspersky Antivirus.
i am very new to SQL server Reporting Services.I have developed reports in SQL Server Reporting.now Where do i deploy them in order to use them into my asp.net web application?
To include the report in your ASP.NET application, here you will need to use a custom control however, Microsoft does not provide a custom control like crystal report viewer custom control, in fact you will find it deployed in the samples directory of Reporting service. The custom control is located at
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\Samples\Applications\ReportViewer
You can just go and open that project and compile it and use the ReportViewer DLL in your ASP.NET application. This can be done by opening your toolbox, then click Add/remove and click browse and select the ReportViewer.DLL I included the source and the DLL in the source in case you cannot find it or you didn't install the sample applications of reporting service. Anyway after selecting the DLL you have to select the custom control from the list.
You will find the name of the Custom Control ReportViewer "Microsoft Sample Report Viewer Application"
When you are done, just include the custom control in your ASP.NET page and change the following properties.
First you have to select the report path and this should be something
like :- My Reports/Report1 - exactly the sample folder you deployed
your reports in.
Second you have to edit the ServerURL and here you enter your
reporting service location http://localhost/reportserver/ this is the
reporting server location, while /reports is the report server web management so take care not to get mixed up.
Once both are done, you can start viewing your report by accessing your ASP.NET web page.
Now enter the location of your web application and choose the asp.net page that contains the custom control
I'm stumped. There are several threads out there that reference a similar problem, but not the same one. I'm trying to get a simple WCF service up and running in Azure, but my problem is happening before I even deploy. I'm following this article:
https://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-create-deploy/
Which says to create your project, build the "Hello World" service interface and class, and then start your project locally. I get a 403 error when I try to start my project.
The only step I'm not following exactly is that I don't have a "Start Without Debugging" option (I'm using Visual Studio Express Web Developer), so I just push "Start Debugging."
Why would I get a 403 error on my own machine? I am running Visual Studio as Administrator.
On the WebRole project right click on your .svc (Service1.svc) and choose "Set As Start Page" And then run the project. Make sure to do this on the WebRole project not the Azure Cloude Project.
Is the Azure project the default project or is the WCF Web Role? If it's the role itself, that may be your issue - it's trying to access the root of virtual directory containing the web service versus running the cloud app in the local emulator. If you browse to http://127.0.0.1:81/Service1.svc in a new browser window do you still get the 403?
It seems VS has lost the its project settings. Bring up "Properties" page on the web service in VS. Go to the "Debug" tab. Under Servers/Virtual Path: my configuration was set to just "/". Put the name of your server back in there "/Service1.svc" and it should work from the debugger now. This fixed the problem for me.
The problem went away when I upgraded to VS 2010 Pro. I never fixed it on Express, but after upgrading the problem was gone ... I had the "Start without Debugging" option in the Pro edition, so I suspect that the problem may have been specific to Express.