I want to start my web application in Visual Studio 2013, but it is not starting. It is showing me an error Port "2729" is in use. Which is the port number of my Web Application. Please guide me. How can I start my application which has 2729 port number.
Related
Newly released Wakanda 2.7.0 Studio reports port 8080 in use (when it is not) when attempting to start the server from Studio with an existing solution.
"Impossible to find or start Wakanda Enterprise Server. Port 8080 might already be in use by another application.
Wakanda 2.6.0 does not have this issue with the same solution, no changes.
Please advise.
The license for Wakanda Enterprise was not present. The application does not report not finding a valid license key; rather generates the above cryptic error message.
I'm currently using visual studio 2017 and trying to attach the debugger to my web app. I've deployed my app and i've attached the debugger through VS. I've also ensure on the azure portal that remote debugger is turned on. I've also went to https://xxxxxxxx.scm.azurewebsites.net/ and checked the processes and w3wp is available. From Unable to start debugging in VS2015 for Azure web app and Remote Debugging - Web App Azure it indicated to me it could be a port being blocked. so i went ahead and set my firewall outbound to allow the connections from UDP 3702 TCP 4020 TCP 4021 and ports 4022 and the problem still persist. I'm unable to connect to my connection target.
I've tried xxxxxxxxx.azurewebsites.net:4022 and xxxxxxxxx.azurewebsites.net
I'm all out of ideas and suggestions from the web. If anyone else has tips, that'll be great.
unable to connect to my connection target.
Please refer to this article to configure the firewall to enable remote debugging for VS 2017.
Remote debugging works for me using VS 2017 with following steps:
Turn on Remote debugging and choose VS 2017
Find and attach to process
Please try to enter {your_web_app_name}.azurewebsites.net:4022 and click Refresh button to check if you can see available processes.
Besides, you can right-click your web app, and then click Attach Debugger to remote debug the web app in Server Explorer.
Updates:
Get publish profile on portal
I have Windows Azure SDK 1.6 installed along with Azure tools. I have one web role (with two endpoints, port 80 for http and port 443 for https) and only have one instance of the web role running (for testing purposes).
When I ran it from Visual Studio for debugging last week, it ran the emulator, attached it to IIS with a binding of 127.0.0.1:80 and everything was peachy.
But as of yesterday, as soon as I started it was trying to bind it to 127.255.0.1:82 and it stopped working with this error (from Visual Studio):
There was an error attaching the debugger to the iis worker process
for URL 'http://127.255.0.0:82'
Now if I manually go to IIS and change the bindings back, I can access the site through a browser but obviously I can't debug it via VS.
Why is Visual Studio doing this? What made it change from last week (I've only made code changes and I have commented them out)?
Edit: I know about this blog, but my issue seems to be different because for one reason I don't have errors in the event logs. And like I mentioned as soon as I change the bindings manually in IIS, I can access the site properly so the app pool is configured correctly.
Edit2: I have the following set:
<compilation debug="true" targetFramework="4.0" />
And my cloud project is set to startup project as well.
When I ran it from Visual Studio for debugging last week, it ran the
emulator, attached it to IIS with a binding of 127.0.0.1:80 and
everything was peachy.
I don't believe you ever debugged a Azure Emulator deployed project on 127.0.0.1:80 binding with IIS. There is a chance that what you've debugged is just the Web Application project and not the Azure Deployed one. Let me explain why:
Windows Azure Emulator uses internal emulated Load Balancer (LB).
This emulated LB binds to 127.0.0.1 port 80 (if port 80 is already
taken it uses port 81)
Windows Azure Tools are dynamically creating a virtual IP address
for every instance of a webrole you have. These dynamic IP Addresses
are 127.255.0.X, where X is the logical number of the instance (0,
1, 2, etc...).
Windows Azure tools creates a website in the local IIS, with binding
of 127.255.0.X and port 82
Step 3 is repeated for every instance you have defined.
When start debugging, your browser usually opens http: //127.0.0.1:81/ which is the address of the LB. But the request from this address is forwarded to the IIS and its binding to 127.255.0.X:82. You could not have debugged a Windows Azure Emulator deployed project by manually attaching debugger to 127.0.0.1:80, because, if everything was fine there is no w3wp process listening on that address:port, but Azure emulated LB.
When you only have the WebRole (no additional sites defined), Windows Azure Tools does know that it shall attach the debugger to 127.255.0.X:82 where a w3wp process is listening.
This is the clean working configuration of Azure Emulator & SDK & Tools v.1.6 (I think also 1.5 and even back to 1.3 where the Full IIS mode was introduced for first time)
Now if I manually go to IIS and change the bindings back, I can access
the site through a browser but obviously I can't debug it via VS.
Yes, you will be able to access the site, but in that way you are skipping the emulated LB, which is not the point when developing Windows Azure Applications.
If you are heving issues of that kind, I suggest that you clean your solution, restart the computer, and if the problem persist uninstall the SDK & Tools and perform clean full install of SDK & Authoring tols for Windows Azure v.1.6 using the Web Platform Installer.
I am working on Windows Server 2008, and I am wondering if it is possible to show my debugging server to a peer over my LAN? What would I need to configure?
Thanks
The answer is you cannot show the built in debugging server anywhere other than localhost. To get around this I just added an entry to IIS and configured my network.
Thanks
I have 2 wireless barcode scanners. I have created an application in C# which reads a barcode and sends data to a web service which then manipulates the data and do further processing. When I start aplication, it first tries to connect to web service and will proceed further only if connection succeded. The problem I am facing is, if I deploy the application through visual studio then it works fine and connects to web service. But if I just copy the contents (exe and config files) manually, then it gives error that unknown host name. Can someone please help me to understand how this connection works? Does it needs some special settings in scanner device which visual studio does automatically while deployment?
Thanks and Cheers.