Exporting Crystal Report - asp.net

Alright, I've been racking my brain for days here. I have a VB.NET Web Application using Crystal Reports. Its been running smoothly until I moved it to a new server.
The problem is, when I try to export the report, this shows up at the bottom of the page and won't prompt the save dialog box.
Any ideas is sincerely appreciated. Thank you.

This took me days to troubleshoot. As it turns out, Crystal Report for 32bit and 64bit was installed on the server. Just had to uninstall 32bit and disable the Enable 32bit Applications option for the Application Pool.
Just in case someone stumbles upon here with the same predicament. :)

Related

MS Visual Studio 2017 problem with ASPX publishing a website

I'm quite new in ASPX development, as I was a desktop application developer for the past 18 years.
I am creating this ASPX / VB.NET application and when I build it and run it shows all the changes I did without any problem, but when I publish it shows the results in the attached picture.
Could you please help me by guiding me in the right settings and I will be very much appreciated?
Thanks in advance.
You are running the application from IIS? Set default page to view to your required page.

"unable to start debugging on the web server" MSVSMON.EXE failed to start. VS2010 error

having a real problem getting VS2010 to debug IIS.
I've searched on the internet for a few days now and tried every single solution I can. VS2008 works perfectly but I've installed VS2010 and when trying to debug an IIS site (by pressing F5 on a project that uses IIS) I get the error message
"unable to start debugging on the web server. Microsoft Visual Studio Debugging Monitor (MSVSMON.EXE) failed to start. If this problem persists, please repair your Visual installation via "add or remove programs" in the control panel."
when i try attaching the process manually, i get the same message.
I've tried repairing the software. I tried it, it failed, so I uninstalled using the Microsoft Visual Studio 2010 Uninstall Utility (http://archive.msdn.microsoft.com/vs2010uninstall/Release/ProjectReleases.aspx?ReleaseId=4321), then reinstalled and it still has the same problem. With the SP1 update this still happens. I can run the website fine when running "start without debugging" and it runs fine.
I've gone through all the guides I can and all tried all the settings on IIS I can and still no luck. I'm using Windows 7 64bit if that means anything. I can detail much more about all the things i've tried.
also have a laptop and have done the same, installing VS2010 and TFS (also on win7 64bit), and this works perfectly for debugging. Didn't have to mess around at all. I can't see any difference between this and my PC with the problem. I'm scratching my head here and thinking I might have to format my PC and try again from a fresh install (which would be seriously annoying!)
Thanks to anyone that reads this,
Dan Gent
I had a HOSTS file entry resolving the project URL to a DEV server instead of local machine. Changing the entry to point to 127.0.0.1 fixed the problem.
Are you installing from a purchased disc or did you download it? Either way, you need to download a fresh copy and install that (sounds like original is corrupted).
Also, make sure you have all the IIS & Web components installed on your machine. Is your OS home or basic?
http://technet.microsoft.com/en-us/library/cc731911.aspx
i've fixed it now. ended up formatting machine, reinstalling windows 7, and then taking backups everytime i installed a new program so i could roll back. installed VS2010 first, F5 worked. then installed VS2008 & everything else and debugging still works on VS2010. not sure what happened as the above problem happened on a fresh install. something must have corrupted something somewhere
thanks for all your help and narrowing this problem down to something that was worth formatting my PC to fix.
cheers,
Buswell
This can also be caused if you are using a host name in IIS and make a mistake in your hosts file.
Check that the hosts ip is set to the local machine 127.0.0.1 and not somewhere else. In my case I had accidentally set it to the development server.
Have you tried starting MSVSMON manually? I had the same problem you are and found the service was stopped. So I tried enabling the service and made sure that it was using the correct credentials.
I hope this helps!
Thanks!
Don
The only thing that worked for me after I tried practically every solution on the Web is to right-click the project on the solution explorer, and select Debug->Debug as Administrator.
Right click on Project, "Use Custom web server" checkbox will be selected, select check box "Use local IIS web server".
I resolved this issue with this and its working.
Managed to resolve this error by At solution explorer-> right click the project->select Debug->Start new instance.
I think it was because i had copied the project folder from another server.

VS2010 Ultimate - Unable to launch ASP.NET Development Server

I've worked with ASP.NET once before and had a project where it was potentially useful, so I started creating an ASP.NET website as part of a solution that contained several C# class libraries.
I'm using Visual Studio 2010 Ultimate Edition and Windows 7 Professional x64. The issue is that when I try to debug my website project, I get the following error message:
Unable to launch the ASP.NET Development Server
There's no other information (it seems a popular variant is the "port in use" error).
Interestingly, I can run single pages on the application by right-clicking on the ASPX and selecting "View in Browser". This does not allow me to debug into my breakpoints, though.
I have no clue what the problem could be. I'm running VS2010 in Administrator mode. One of the questions that popped up here suggested I uncomment the "127.0.0.1 localhost" line from my HOSTS file, which I did, and restarted VS with no luck. I also tried both setting a static port for the web server to run on as well as let it dynamically generate one. Both do not help the situation.
Any help?
Thanks.
Added on 5/20/2010 at 9:25 CT
I can debug by attaching to the process. However, this is still a painful way to debug quickly so I'd still like a solution to the problem.
There are some things to check before listed here
Please eliminate issues on the link and check whether you may debug
Hope this helps
Myra
The problem was I had a InstallShield Lite project which was apparently causing problems. Once I unloaded that project, I can launch the development server in debugging mode.

Why can't I attach the debugger?

I'm using Visual Studio 2008 SP1 and trying to debug a website created in ASP Classic. I have read numerous tutorials, however nothing seems to be working (PEBKAC?). I have enabled server-side debugging in IIS and am attaching the debugger to dllhost.exe. When I open my page in Google Chrome, set breakpoints and set VS to debug, nothing happens. I don't get any errors so I'm not sure what else to post.
Any ideas?
Thank you. :)
Attach to either w3wp.exe or aspnet_wp.exe - depending on your OS and IIS version.
Are you attaching to the w3wp process in your IDE? If your IIS site is running on your local host, then this SHOULD do the trick.

Asp.net Microsoft ReportViewer using rdlc page never loads

I have installed the Visual Studio 2008 sp1 Report Viewer Redistributable on the web server. I had to download it from microsoft, because the location I've seen other people post does not exist on my install of visual studio. I downloaded the one that is located here: http://www.microsoft.com/downloads/details.aspx?familyid=BB196D5D-76C2-4A0E-9458-267D22B6AAC6&displaylang=en.
I think the location people say ReportViewer.exe is in, is usualy: C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\ReportViewer\ReportViewer.exe. I have Visual Studio Team Suite Development Edition 2008 and the v2.0 directory under SDK does not exist. That may be some of my problem, I do not think so though.
I say all that to say that I can design the Microsoft Report, and I can run the page with the report viewer locally just fine. It seems to work really great, and could help out the company quite a bit.
However when I deploy to the webserver the page that host the reportviewer control will allways either say "This page does not have a precompiled..", or something like that. It usualy doesn't say anything and just sits there trying to load.
Other pages in the same website do not exhibit these symptoms. I have also successfully gotten crystal reports to display it's viewer, by installing the redistributable on the web server.
There must be something going on with one of our web servers. I finally got the report to load and it came up with an error message that said the same thing that this forum post talks about http://social.msdn.microsoft.com/Forums/en-US/vsreportcontrols/thread/b237dbab-7670-4c7a-b9af-70c5be7101d9.
I was then able to check the box that says allow precompiled site to be updatable. That fixed my issue. I now have both crystal and microsoft reports working correctly. Maybe this post will help someone else.
edit 2/18/2010 8:18am cst I thought it was fixed apparently not, as soon as I published to the web server again, the page will not load anymore. I am going to try and setup a completely new server in a virtual machine, to try and do more testing.
edit 2/19/2010 8:17am cst I spent alot of yesterday setting up a brand new virtual machine with server 2003, visual studio 2008, and sql 2005. I ran the same report page, all it has on it is the report viewer control. It still will not load. I figure there is something you have to do with IIS configuration to get it to work, since it won't load with default settings.
edit 2/19/2010 9:47am cst I have created a new web application with only the report in it, brand new web.config file. Something about my web.config file is causing the problem. This new web application is apparently working. I am now going to try and see if any new pages can be added to the previous web app at all. Maybe something is causing all new pages to not load.
edit 2/19/2010 10:12am cst Bizarrely the report sometimes loads. This happens on both the test environment, and the production environment. I did find a somewhat funny angry bug report to microsoft that explains the problem with the rdlc files compiling. That is what produces the following error:
**
An error occurred during local report processing.
The definition of the report 'Main Report' is invalid.
The report definition is not valid. Details: Data at the root level is invalid. Line 1, position 1.
**
The Bug report url: http://connect.microsoft.com/VisualStudio/feedback/details/468068/rdlc-files-are-build-into-resources-during-publish-this-is-a-marker-file
The blog post url that fixes it: http://weblogs.asp.net/stephensonger/archive/2008/09/10/deploying-rdlc-files-in-local-mode-for-asp-net-applications.aspx
As you can tell, possibly you don't find it funny, but there is a bug that causes rdlc files to compile for some reason. You can also fix it by having your site be updatable, which is one of the check boxes you can check when you publish in visual studio.
edit 2/19/2010 10:51am cst My next step is to snapshot the current virtual machine, go back to the point I installed sql 2005. At that point I'll install visual studio 2010 rc and see if it exhibits the same problem.
edit 3/3/2010 9:15am cst I don't know what fixed it, but both crystal and microsoft reports have been displaying correctly for awhile now. I made no changes other than what I have mentioned here.

Resources