Since we moved to a new server we get the following error:
We made an exact copy of all files of the site from the previous server (Server 2003 with IIS) and put it on the new server (Server 2012 with IIS). The application has been written in Silverlight 4.
The information the ReportViewer has to show is for really important daily analyses.
If you need more information please let me know.
The problem is solved.
It was the version of the ReportViewer where we first had version 10 and 11. Version 10 wasn't installed anymore. We fixed it by changing the web.config.
Related
We had a classic ASP application that had to be migrated to a new Windows Server (Windows Server 2012 R2 Datacenter). IIS was already setup and we migrated the files configured the URL and DNS, as well as setting up the classic ASP components for IIS. The web application initially opens okay but the error below pops up on the server continually.
We checked the relevant site was configured to run 32bit and we ensured that in the sites "Debugging properties" the "Enable Server-side Debugging" was set to false. Also, all those testing the site we ensured in Internet Options >> Advanced the two values of "Disable script debugging" were checked. But this did not resolve the error. I believe we have all the necessary components setup in the server roles
I then followed this URL and deleted certain registry entries and restarted the server.
https://learn.microsoft.com/en-gb/visualstudio/debugger/just-in-time-debugging-in-visual-studio?view=vs-2015
This seemed to take away the above error but then the relevant application pool continually stops. I checked the application logs and at each time the application pool stops there is an error stating below
Since creating this ticket I installed DebugDiag 2 and set up a rule for IIS "Crashing". Ran the application until the relevant IIS Application Pool stopped and examined the Dump files created by the rule. All of them appear to have one error concerning "VCRUNTIME140.dll". See image below.
I found that this was a common issue and related to Visual C++ Redistributable 2015. I looked at installed programs and there was versions 2010, 2013 and 2017 installed. Microsoft state that after version 2013 subsequent versions incorporate the last. So I installed the latest version of Visual C++ Redistributable and restarted the server. This made no difference. So I uninstalled the latest version and installed version 2015 and restarted but again the application pool still stops after several actions on the web application.
Does anyone know how do I resolve this please?
My environment:
Windows 10 Creator (1703 with current updates to this date)
Visual Studio 2017, Enterprise, 15.3 with most of the goodies turned on.
Windows 2016, again with all current updates.
iis 10 with WebDeploy installed (that's a whole other installation nightmare, suffice it to say that SO helped there and the answers are already out there so I won't go into it here). Turned on ASP.NET 4.6, otherwise mainly accepted the defaults.
My process:
As per the NuGet.Server documentation, create a new ASP.NET MVC project using the "Empty" template and download and install NuGet.Server as specified. I'm using .NET 4.7 as my framework.
Compile and configure as desired (at least ensure you have an api key in place).
Deploy to iis using the "Publish" | Web Deploy option
Try to get in touch with the NuGet.Server on the website and fail miserably!
My bindings are 192.168.1.25 (yes, the server has a fixed IP address), port 80. The name of the site is AWENuGet and the desired url is www.awenuget.com.
To be sure, all of this works just fine if you take the same project as described above, assign a local port number (creating the project will do that anyway) and then simply running the application in Visual Studio works just fine.
But, when I took that self-same project and simply deployed it to iis, miserable failure.
I tried to open the host file (Windows\System 32\drivers\etc) and added the following:
192.168.1.25 www.awenuget.com
to said file and it still failed.
...and the answer, for me, was to take that same hosts file entry that I made on the server so that the server could see it and install it in my dev machine's hosts file and voila! NOW it works just fine.
My office just gave me a new machine with Windows 10 and both VS2013 and VS2015 installed. I transferred an existing VS2013 project to the machine, but when I attempt to run, I get a ERR_SSL_PROTOCOL_ERROR error in Chrome. There doesn't appear to be a Repair IIS Express application in Win10. I considered uninstalling IIS Express 10 and install 8, but I'd need to get permission for that and it wouldn't be an easy sell. What else can I look at?
I couldn't find a solution anywhere online that would help me out until I removed the bindings that I was trying to access via the IIS site bindings in IIS manager - see below :
This was the only binding I kept - I removed the other bindings which were pointed at the ports that I needed.
Windows 10 comes with IIS 10, and ColdFusion 10 doesn't seem to like it. ColdFusion 10 installs fine, but when it comes time to create connectors (either during installation or by using the tool at C:\ColdFusion10\cfusion\runtime\bin\wsconfig.exe), it fails. The error message I get is that it doesn't support IIS 10.
This connector is required to set up the CFIDE and jakarta virtual folders in IIS.
Any way around this?
An already deleted blog post from blogs.coldfusion.com (http://blogs.coldfusion.com/post.cfm/configuring-connectors-manually-for-iis-10) once stated the following
With Windows 10 out, there is a problem that most of the ColdFusion
customers will face, configuring connectors for IIS 10. Wsconfig, the
connector configuration tool, only supports till IIS 8.x. While the
ColdFusion team is working on this issue and will try to provide the
fix for it as soon as possible, there is already a KB article which
can be referred for configuring the connectors manually. Although the
article was originally written for CF10, it can be used for CF11 also.
After following all the steps in the article, you need to do one more
thing. Add index.cfm as default document for your website in IIS.
This solution is only recommended for development environments as
through testing of the connectors with IIS 10 is still going on. So
for production machines, you should wait for the actual release from
Adobe.
UPDATE
Important update: Note that ColdFusion 10 and 11 have been updated to
support Windows 10, a couple months after this blog post was first
written. Consider applying that update rather than this manual
configuration.
If you are running Windows 10 Pro, you also have the option of running a Virtual Machine in the included Hyper-V offering. Instructions on how to enable Hyper-V are found here: http://blogs.technet.com/b/canitpro/archive/2014/10/02/step-by-step-creating-and-running-a-windows-10-vm-on-windows-8-1.aspx
Simply spin up a version of Windows required.
apply latest hotfix for cf 11 hotfix_019.jar. that will fix the issue above
We're in the process of moving from 2003 IIS6 Web servers to 2008 R2 with IIS 7.5.
We also have a Windows 2008 server running IIS7 and everything works fine on this server.
On the new servers when we go to our crystal reports viewer page we get prompted for windows authentication, then if you type in valid credentials or not you get the following error in firefox:
XML Parsing Error: no element found
Location: http://192.168.10.112/Reports/ReportViewer.aspx?id=49
Line Number 1, Column 1:
^
In IE you just get a blank screen.
The same code runs fine in debug mode on the server in Visual Studio 2010, and works fine on our other servers
Thanks
I know that the answer is too late, but to be a reference for other users.
I faced this problem too in IIS 7.5, and after 5 days investigation, I found that the problem is because the Crystal Reports Viewer running as 32-bit, to solve this issue:
in IIS, go to Application Pools
Select pool that you are using it for your application, normally its "ASP.Net v4.0".
Click on "Advanced Setting..." in the right panel.
set the value "Enable 32-bit Application" to "True"
Also, note that you have to install the oracle client 32-bit version too.