I can able to perform the Azure MVC web app publishing from external networks but the publishing fails when I do it from company network.Please let me know what network setting restricts the publishing. Please help. Below is the error message:
Severity Code Description Project File Line Suppression State
Error Web deployment task failed.
(Web Deploy experienced a connection problem with the server and had to terminate the connection.
Contact your server administrator if the problem persists.
Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CONNECTION_TERMINATED.)
Please let me know if you need more information reg this.
Thanks
AR_
If nothing has changed other than the external/internal network, my guess is that your company has blocked Web Publishing from inside the network.
I would recommend contacting your network team and asking them to unblock port 8172 which is used by Web Deploy.
I'm currently trying install a web application on win server 2012. After compiled the app, i'v deployed it in IIS. After the logging page the next page is not displayed and i see the error in the subject in the svclog file. I saw that this error could be caused because a missing dll but as the application run on another server, i compared the dll's in the bin directory and that's the same as on the new server. I'm newbee in web application. I'don't know how to debug it and i can't go further in my task to improve the application. Any help would be appreciate !
The application is silverlight + MVVM + RIA services + sql server
thanks
it COULD be due to win server configuration.
Make sure that WCF Services HTTP Activation is installed.
Errors messages and stack are the bare minimum in diagnosis. It's like symptoms for sickness.
Even if this would solve your problem, please reports them here, for future reference.
I have a WCF application which was working perfectly fine until recently when we introduced some SSL related settings and certificate requirements into our application. As soon as we turned out the SSL following started happening:
When I launch the service using my Visual studio it launches fine without any errors and With Https in the URL
As soon as I click on WCF URL to see the WSDL, it fails with SSL connection error.
Browser does not provide any more information on this. I have also installed WCF Trace utility and it traces most of the errors correctly BUT not this one(probably because it does launch the application fine but fails when we try to launch the WSDL)
Any suggestions on a good tool that can help me debug SSL errors any better?
One thing I found very very helpful while working with WCF in general is using Idiagnostic module. It does not relate to any specific SSL related issues but it helps debug issues in general
I deployed a web role in windows Azure, based on the following tutorial.
http://weblogs.asp.net/scottgu/archive/2013/10/22/windows-azure-announcing-release-of-windows-azure-sdk-2-2-with-lots-of-goodies.aspx
but when I try attaching the debugger I get the following message:
"there was a failure to launch the remote debugger"
apparently this is a known issue, and the suggested solution from Microsoft is to restart the visual studio and try again, which unfortunately didn't work for me
http://msdn.microsoft.com/en-us/library/windowsazure/dn459835.aspx
Remote debugging may fail to attach to an existing Cloud Service:
After deploying a new Cloud Service the debugger may fail to attach to
an existing cloud service with the error message “There was a failure
to launch the remote debugger”. To correct this problem, restart
Visual Studio and reattach the debugger to the new deployment.
So I thought to ask here in case anybody faced the same issue and found another solution other than restarting the visual studio!
I'm using visual studio 2012, with Azure SDK 2.2
Make sure that you deployed a Debug build to your web role and that you have checked "Enable Remote Debugging for all roles" on the advanced tab during deployment. Failure to do either of these could lead to the problem your seeing.
I was using Azure SDK 2.2, so as to use "Attach debugger", but unfortunately I needed to use SDK 2.1 as 2.2 needs some references that weren't included in 2.1, so I guess this is the problem.
Thank you all for your help
I tried all of the solutions above and found that none worked for me. My problem turned out to be stale or inaccessible certificates that the VS debugger uses to connect to the service. I discovered this was the problem by going to event viewer and found:
A fatal error occurred when attempting to access the SSL client
credential private key. The error code returned from the cryptographic
module is 0x8009030D. The internal error state is 10003.
I had had other problems with permissions on private keys and so I ended up deleting all of the certificates from my personal store (current user) with the "Issued To" equal to "Windows Azure Tools". When I redeployed my service VS created new certificates and uploaded them.
Voilà -- attach remote debugger works again.
I got the same exception trying to remotely debug a VM in Azure, following the guide in Debugging Azure Virtual Machines.
What worked for me was to simply install the remote debugging tools matching my version of Visual Studio (VS2013 Update2).
Further I had to add a new endpoint in the Azure portal. This didn't work initially but eventually using the same public and private port number did the trick. The default port of 4018 worked.
Start the remote debugger program on the client machine in adminstrator mode and remember to set to port number, e.g. to 4018. I chose Windows authentication as well.
From within Visual Studio: Debug menu -> Attach to Process -> [yourVMName].cloudapp.net:4018 or whatever port number you chose. You should now see a list of processes on the virtual machine.
In case its helpful for someone else, I've just spent 3 hours on this! In the end I gave up and using 'Cloud Explorer' (in VS 2013, after installing the Azure SDK) I selected 'Disable Debugging' and noticed it cleared out port rules in the Network Security Group for the VM.
I hadn't seen it set these up (which is where I'd spent hours guessing that these were the issue and trying to figure them out from patchy MS documentation, broken links, etc).
So, I 'enabled debugging' for the VM and saw it set up security rules - something it didn't do the first time!
At a guess this is because I had initially enabled debugging for my VM soon after I installed the Azure SDK into VS. Since then I rebooted the VS server, and that may have enabled something in the SDK.
Anyway - before spending hours figuring out ports, reboot the VS server and then disable/reenable debugging in Cloud Explorer - you should see a status message (in the Azure Activity Log) saying 'Configuring networking security group debugging port' - this is the magic step that it didn't do the first time around.
I think you should try lunching VS in administrator mode, and see if you always have the same problem.
Else I think you should put more details about your problem.
This is what I did to enable debugging on an Azure VM.
At the time of this writing my current setup is as follows
Windows Server 2012 R2 IIS 8.5 (Virtual Machine)
Visual Studio 2013 Update 4
Microsoft Azure SDK Tools 2.5
Update Visual Studio to the latest Azure SDK
go th the server window (server explorer)
Expand the Azure node
Expand the virtual machines node
Right click on the VM you want to debug
Choose "Enable Debugging" Visual Studio will begin to add a debugger extension to your virtual machine
Once complete, Right click on the virtual machine from the virtual explorer and choose attach debugger
I am interested in working with blob storage from a Windows Phone app.
The Windows Azure Toolkit for Windows Phone should enable this. http://watwp.codeplex.com/
They have a sample application on NuGet which you install in a default WP application from VS, by running the command:
PM> Install-Package Phone.Storage.Sample, in the Package Manager Console
http://www.nuget.org/packages/Phone.Storage.Sample
The only configuration needed to run the app is to change the default navigation page in WMAppManifest.xml to "/Pages/StoragePage.xaml".
But when I try to run this sample application in a default WP app from VS, I get the error:
"The value for one of the HTTP headers is not in the correct format. RequestId:38df4766-0da8-4212-84a1-3da0c994a876 Time:2012-06-06T14:50:02.0209600Z"
Any idea what to do to make it work?
As you just made one changes in your sample, I believe you are using Azure Storage Emulator. Have you verified if Azure Storage Emulator is running. Also be sure to have a physical network in your main machine rather then virtual network to connect as i have seen such problem with virtual network and loopback address.
It is very much machine specific issue as I just tried to exact same step with no error. There could be any random error for this issue and while you try to restart the machine, re-install sdk and other components and it will go away. I can help you to find some ways to trouble shoot it:
When you run this application in WP emulator, while using Development storage the HTTP request pass through localhost:PORT/storage_container means the network traffic is on localhost so you can run fiddler to capture traffic on 127.0.0.1 (by default it is not set so you need to configure it. Once you have network trace you can find the root cause however it would hard to find the fix, as i have seen in past.