I have a web application developed on ASP.NET 4.0, SQL SERVER 2008 and Crystal Report 2008. When running on VS2010 it works fine but when i deploy it on IIS 7 reports are not working.
Application logins successfully.
Database is Correct.
Connection on reports are correct.
I gave full permission to IIS and Windows\Temp folder
I googled it and found many solution but non of them working.
Please tell me the solution. Furthermore the reports are working on IIS6.
The error is in the below image
I'm running IIS7 with Crystal with no issues. Out of the blue, certain reports started failing and creating lock files in c:\windows\temp. The only fix, so far for me, was to open each report and perform the following:
File > Page Setup > Check off the following option "No Printer
(optimize for screen display)"
Afterwards I stopped the application pool, cleaned up the c:\windows\temp directory and started the application pool again. All issues have since been resolved.
This assumes you have a working IIS7 environment to begin with
Finally, I got the solution*. I was using ODBC and it was the problem.
I deleted the connection from the User DNS and created in System DSN.
*I got that a year ago but it is for people who are searching. It might help.
Related
I must preface this post by saying that I am not an experienced developer, I am in the process of learning through trial and error and a lot of google searches so detailed (step-by-step) feedback would be greatly appreciated. I created a website, which does not use a database, using visual studio 2015 and I am attempting to host it locally on a Windows 2008 R2 server.
I installed IIS and loaded the asp.net v4.0 framework. The site works fine, produces no errors when I test it and works after being published only if the visual studio is still running.
However, when I close the Visual studio and open my browser window to http://localhost:50044 (which is the URL listed in properties menu in VS), I also tried using port :80 and nothing. When trying to add Web Site via the IIS management utility I receive the following authentication error: ”Cannot verify access path (C:\Inetpub\wwwroot).”
I checked the permissions and windows authentication is enabled with read access, and all other permissions seem to be correct. I am at a loss, I'm sure it is probably something simple that I am missing due to my lack of knowledge and experience. Any help would be appreciated.
It's sounds like you are running on IIS express which in your case stops running when you close visual studio. Normal process is create a new website in IIS and point to the folder where your web.config is. You can then hack your host file (C:\Windows\System32\drivers\etc) so DNS works. Add an entry like "127.0.0.1 mytestwebsite.com". I hope that helps
So I figured out part of what was happening. I didn't realize that visual studio has built in IIS and was using that by default.
I ran VS as an admin, created a new project, then attempted to create a virtual directory thru VS under the project/properties/web tab. I selected local IIS and entered http://localhost/boc and it returns an error: unable to create vd. Web server http://localhost... Could not be found.
I then went in to the IIS manager and set up a virtual directory with no issues. However, when I attempt to reference it thru VS I again receive an error message.
Any ideas?
this is a bit of a shot in the dark but I am truly stuck here.
I have an asp.net MVC app that spits out some PDF reports.
This works great on production Windows Server 2003 / IIS6, Local Dev Server, and Win 7 / IIS7
When I go to production IIS 7.5 / Server 2008, some reports hang indefinately without an error or a trace written. They just continue to spin seemingly forever, there is never a failed request back from the server.
Some reports do this, some do not, we've had multiple folks look at the reports and can find no discernable differences.
Does anyone have any tips on:
Why I never get an error/timeout?
Why some crystal reports would fail, and others are fine?
This works 100% fine in all other environments. I did some SQL tracing and the database commands are being run and terminating pretty much instantly, there is no hang there.
I have the 64 and 32 bit crystal runtime installed on the server. (Allow 32-bit is set to true for the app pool).
I have the same setup elsewhere and it works with no issues on Win 7 / IIS 7.
I've temporarily added the app user to Local Admins, and given him full access to both databases
As per dotjoe's suggestion, a default printer that is not present on the system caused this issue. Make sure you a) have the printer installed on the server, or b) have "no printer" for default.
Thanks, Stackoverflow!
Selected the printer 'Microsoft XPS Document Writer'.
To do this go to the report in the designer->Design->Page-Setup and select.
A mate of mine has recently deployed a site of theirs to a Windows 2008 sp1 Server with IIS 7. The app itself runs fine with no problems, however when they try launch a Crystal Report they get a 404 error.
If they manually try access the path using the IP of the server instead of the server name the report loads fine though.
Can anyone point us in the right direction to sort this issue out? I would assume that there is a setting we missing in IIS 7 since this ran perfectly in IIS 6 on a 2003 server.
Thanks
We got the issue pinpointed to SQL 2008 Reporting Services. It creates a virtual directory called Reports. This clashed with the site folder also called Reports.
Sounds a bit like another question I answered, where the problem had to do with the execute permissions on the special "CrystalReportViewers115" folder (exact folder name changes with the version of Crystal). The solution in that case was to execute permissions on the folder to "scripts & executables".
I have a question regarding IIS (version 7.5) and ASP.NET (.NET Framework 4) . I am trying to debug ASP.NET web application which is stored on IIS. Now, I have done this in past and everytime it worked perfectly.
But now when I try to do same, **Visual Studio 2010** always gives me error, **"unable to start debugging on the web server. the iis worker process for the launched URL is not currently running" ...** even the application I had created in past (& stored in IIS) can't debug using Visual Studio. But all applications (new & old) can be accessed if I type their path in Browser, and they work fine too.
I did search on internet about my problem and I found many posts, but almost every post talks about activating **Windows Authentication** in IIS for the application in question. But, I am using Windows 7 home premium and the IIS shipped with this version doesn't support option for Windows Authentication. Also, if this is the only reason then why my old applications were working just fine till now without this Authentication method?? I found MSDN help about this error but it is not much helpful to me. I also checked APPLICATION POOL selection in IIS and my Application (both are using V.4.XX.XXX)... I have also checked **BINDING** , which is *:80 to Default Website, that means all requests to port 80 will be directed to default website (where my all applications reside)
As a side note, I have SharePoint Server 2010 installed. Which has its own website (which I have disabled while debugging) ...
I think there is something is changed in my IIS configuration, but I cant figure out what it is. And I am sure that it has something to do with SharePoint installation (may be because of more than one website on IIS for same port ??). Because I am using IIS for first time after installing SharePoint and I am having this error.
I will really appreciate if any one has answer ...
Thanks,
Jack
UPDATE: As I suspected ... having more than one site in IIS was root cause of trouble, Once I uninstalled Sharepoint Server 2010 and its web sites from IIS, my Visual Studio 2010 debugger was able to "Auto-Attach" w3wp.exe process while debugging any application ... ( I really don't see any reason that even after disabling all other websites why still it was giving me error at first place ?? )
I know its not a solution, because I have to remove Sharepoint Server ... but at present its more important for me to work on that application then Sharepoint Server.
But I am still open for any suggestions which might help me to run both together ....
Thanks,
Jack
Check the Bug fix for this issue in the Microsoft's Connect site.
.
Is it with .NET 3.5 in Visual Studio 2010 , if yes , then check http://www.ginktage.com/2010/08/fix-for-visual-studio-2010-hangs-when-debugging-asp-net-3-5-web-application/ for information
I'm trying to debug an ASP.NET webapp that's configured to "Use Local IIS Web Server" on WinXP. When I start the debugger, the compile succeeds, and then the following error is displayed in a dialog:
Unable to start debugging on the web
server. The COM+ registry database
detected a system error
The webapp never launches in my browser. How can I get rid of this message and debug this webapp?
I tried the usual stuff, and my exact scenario ended up being described a post in the MSDN forums. Its answer worked for me, despite my environment (VS2008, .NET 3.5) being more modern:
Here are the steps I followed (basically a summary of the link above -- "ASPNET" being significant because that's the user running the IIS instance on my development box):
Close VS
Shutdown IIS
Add ASPNET to the local Administrators group
Start IIS
Start VS and successfully debug ASP.NET webapp
Close VS
Shutdown IIS
Remove ASPNET from the local Administrators group
Start IIS
Start VS and continue debugging ASP.NET webapp without error
My development workstation's security settings/situation is regularly managed by our security folks here, so something must have upset my ASP.NET/IIS/etc environment.
I am using the Visual Studio 2002 and I had the same problem, with tha same Error Message. To solve it, I did only the first 5 steps of the solution recommended before.
I am starting in VS 2002 because I use it in my work. I have the basic concepts, but I never develop in this program language, so I am a begginer.
The most important point in this solution I believe it is understand that ASPNET is a user in the development machine, as Administrator, as "Name.LastName" or any other user that access the machine. When I search for ASPNET to add in the Administrators Group and found it, made a lot more sense because I don't know exactly how the .NET architecture works.
So, if you have the same problem, I here confirm this solution solved my problem, even when I reboot my machine:
Close VS
Shutdown IIS
Add ASPNET user of the Machine to the local Administrators group
Start IIS
Start VS and successfully debug ASP.NET webapp
Thanks for the solution!!