I'm having troubles enabling remote debugging on sharepoint online. I have 2 machines, my local machine (Windows 8.1) and my development server(Windows Server 2008 R2). On my development server I first tried remote debugging using Visual Studio 2012 Update 4, as described here: http://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-troubleshoot-visual-studio/#remotedebug.
When this didn't work I tried doing exactly the same thing on my local machine, which has Visual Studio 2013 (Ultimate) update 1 and the latest windows azure sdk (2.3). This worked perfectly. Thinking upgrading to visual studio 2013 would solve my problem I've installed 2013 (Premium) on my dev server, next to 2010 and 2012. After installing and updating everything for 2 hours however, I came to the conclusion that I received the same error as on VS 2012.
Googling came up with a few interesting causes for this bug: sitenames longer than 20 characters or sitenames containing hyphens. This is not the case. Then I verified port settings, the dev server has no active firewall but I wanted to exclude any possibilities. And low and behold, both telnetting from my local machine as my dev server to ports 4016 and 4018 of my azurewebsites.net url worked.
Are there any other solutions for this bug? Since debugging locally is not an option (sharepoint provider hosted app for project online) this is very inconvenient.
Thanks,
UPDATE: Deploying the site as a cloud service works, and so does remote debugging them. However, we would like to stay with azure web sites for now..
I know this is a duplicate of Azure Remote Debugging: Failed to enable remote debuggingException from HRESULT: 0x89710023; but none of the solutions there or on twitter were of any use.
Check out Azure Remote Debugging: Failed to enable remote debuggingException from HRESULT: 0x89710023
I think this has to do with blocked ports 4016 and 4018
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?
I hit an issue on IIS and it bothers me for many days. After I searched all over the web, I still cannot find the right answer so it is time to post on StackOverflow to seek help.
I created a Windows Server 2016 VM on Alibaba Cloud and an SMB file share on Alibaba Cloud. Then I followed this instruction (https://github.com/AlibabaCloudDocs/nas/blob/master/intl.en-US/Best%20Practices/Use%20Windows%20IIS%20and%20NAS%20to%20provide%20Web%20and%20FTP%20services.md) to put my website on the file share and load it to IIS. The problem is this setting works on Windows Server 2012 R2 or lower versions, however, it shows dll load failure on Windows Server 2016. Error looks like this:
Dll load failure: 0x8007003a
I have tried a bunch of settings
<runtime>
<loadFromRemoteSources enabled="true"/>
</runtime>
and searched online but none of the tricks work. I have also tried to use Process Monitor to check the details of w3wp.exe and got this difference between 2012 and 2016:
Windows Server 2012's w3wp.exe gives CreateFile: Success
Windows Server 2016's w3wp.exe gives CreateFile: Invalid Network Response
Comparison between the stacks of 2012 (Left) and 2016 (Right):
Left: 2012, Success; Right: 2016, Invalid Network Response
Another interesting thing is Windows Server 2016 doesn't really send out any SMB packet for this dll open request.
My concern is this is a bug of Windows Server 2016 Kernel.
After writing all the words above, the question is pretty clear: Does anyone know what really happened and is there a solution to load remote dll on Windows Server 2016 for IIS?
Check the root permissions in the IIS server
Reduce the security level permissions
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.
I am working on getting web deploy set up on IIS 7.5. I have followed the steps exactly in this article:
http://www.iis.net/learn/publish/using-web-deploy/configure-the-web-deployment-handler
I have tested importing and exporting applications on the server and all work perfectly. Now I would like to set up remote access to ms deploy so I can install web applications by publishing in visual studio 2012 with publish profiles.
Here is where I am confused, what is the url I include in this for the service url (ie. msdeploy.axd)? Where I can find it on the servers iis (server is located on different machine than visual studio)? I have read about access is over port 8172, how can I check that this is open for communication?
Thanks for any help
First up, the installation instructions you want are Installing and Configuring Web Deploy in the "Install" section of the site. The instructions you linked are from 2008.
Once you've installed MSDeploy v3 as per the newer instructions, the MSDeployServiceURL value will be https://webserver:8172/msdeploy.axd. You'll also probably need to set <AllowUntrustedCertificate>true</AllowUntrustedCertificate> if you don't have a cert on the server.
The user in question will need to be an administrator unless you have setup non-administrator deployments (instructions in the same link).
I have upgraded my 2011 Lightswitch app to 2012 RTM and it works fine locally. However, when I try to Publish it to my web server it fails (http://blogs.msdn.com/b/bethmassi/archive/2011/03/23/deployment-guide-how-to-configure-a-web-server-to-host-lightswitch-applications.aspx).
I checked the Web Platform Installer on the live server and it does NOT have "Visual Studio LightSwitch 2012 Server Runtime without Local SQL" (http://msdn.microsoft.com/en-us/library/Gg481779(v=vs.110).aspx) - it only has the 2011 version.
Where do I get the 2012 version from? There is very little info about it on the web.
Ok, I am going to summarise my experience here as it might help others who are upgrading. My app uses the Telerik RadgridView control and Forms authentication. It runs OOB:
1) Firstly, I upgraded to the RTM LS2012 version and rebuild my app - all works fine on Dev.
2) I then tried to deploy to my Win2008 Server with no changes (note: it was running the LS2011 version with no problems). This failed with an "Unknown" message during the publish process. To get around this I unchecked the flag on the Publish wizard "IIS Server has the Lightswitch Deployment Prerequisites".
3) Next problem: The Silverlight App would show "loading" and then show a blank screen. At one point I received a message saying "Debugging resource strings are unavailable". The problem here was that the IIS site that the publishing wizard created had Windows and Forms Authentication (under the IIS Authentication icon). Disabling Windows Auth solved this problem. I was finally able to log on to my app.
4) Hardest problem: The app would log in and work fine for about 20 seconds. Then it would throw a Silverlight unhandled exception: "Unhandled exception at 0x5ceed700 in sllauncher.exe: 0xC0000 094: Integer division by zero". After a lot of Googling someone asked if I was using a VM - the server IS a VM and they suggested I run as a single processor (ie. it was a threading error). I did not try this, instead I tried running from a different PC as a client OOB (I was testing on the server). This then worked.
After all this my app is now up and running as Lightswitch 2012.... hope this helps someone!
Notes: I did NOT install .NET 4.5 (my projects target .NET 4) OR the Lightswitch 2012 requisites on the server. It works with the Silverlight 4 Telerik dlls.
I think all you need is change of .NET framework from 4.0 to 4.5 in your application directory.
It is called "LightSwitch for Visual Studio 2012 - Server Configuration with(out) local SQL Express" and available at the Web Platform Installer.