System.Net.Sockets.SocketException in external code? Source not available - c#

Scratching my head here...
I am using VS 2022 with 4.8 Framework
I am getting a System.Net.Sockets.SocketException: 'An invalid argument was supplied' error when I try to launch my app.
It doesn't show me the line it's caused by or anything. I don't use any networking in my application however I do connect to SQL and Active Directory and am thinking that could be causing it? Not really sure. I am at a total loss is there anything I can do to further identify what's going on?
Thanks

Related

Cannot connect to database after installing Nuget Package Microsoft.Asp.Net.Webhelpers

I am having an issue with connecting to any of my databases after installing Microsoft.Asp.Net.Webhelpers. I have uninstalled it and still having an issue:
SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was
not found or was not accessible. Verify that the instance name is
correct and that SQL Server is configured to allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)
My live site uses this database and is up and working. It does the same thing when I use my local machine connection. Does anyone know what this package may have changed in my project to cause this? I appologize if this is not the correct place to put it, I really do not know what code needs to be posted because everything was working fine before installing this package..
Thanks for your help!
UPDATE:
I am now showing an error that I need to restore with nuget package manager. Something is missing. It is set to automatically update missing packages but for some reason it doesn't. So I closed the program and will reboot my system and see what happens when I reopen and try to rebuild. I will do a clean first.
UPDATE:
The Problem package appears to be Microsoft.AspNet.Webpages.data which is a dependancy of `Microsoft.AspNet.WebHelpers. As soon as I install this package I loose database connectivity. I have not found any information on this issue anywhere. It seems strange to me because Microsoft has it under the latest version of .net. Which i am using..

Unable to run the application from VS 2015 [duplicate]

This question already has an answer here:
"The underlying connection was closed: An unexpected error occurred on a send" after installing VS 2015 update 2
(1 answer)
Closed 4 years ago.
I am running my application using VS 2012 initially, That time it's working fine. After that we installed VS 2015 update 3. Now we are not able to run the application.
Getting Unable to start the debugging server on the web server. The Underlying connection was closed.An unexpected error occur on a send.
My application hosted in IIS, host entry fine with host file. I am able to run the application from IIS. And get the Verbosity -Diagnostic output. There is no conflicts between the packages. Firewall port is enabled as well as there is no Anti virus blocking.
Before installing VS 2015 it's working fine, Please let me know what is the issue here. Is there any .netframework conflicts, Please help to resolve the issue.
Try these:
Try changing the port being used to something other than 80 which may being used by another application.
Check to make sure the app pool has the right privileges.
Are VS2015 components installed on the remote to allow for VS2015 debugging? See Installing Remote Tools

unhandled exception has occurred in your application error comes when installing setup

This is my first question. if happens any mistake please ignore.
We develop an inventory system using C# in visual studio, database design by MS server management and create a setup file. To access database we use ODBC.
The problem is started when we installing the setup file into another computer. After the installation clicks on the .exe file, the error will appear as shown in the image.
Most of the time it may happen because doesn't set correctly connection string, can anyone please be of any assistance,

Latest MonoTouch 4.0 problem when trying to access a WCF service

My MonoTouch application is calling to a SOAP WCF Service using CustomBinding with HttpTransportBinding and TextMessageEncodingBinding and everything is working fine with MonoTouch version 3.2.6. I'm updating my system to use MonoTouch version 4.0.0 and the call to my SOAP WCF Service is no longer working. I keep getting the System.Net.WebException
"The remote server returned an error: 400 Bad Request";
What is causing this problem, and how do I to fix it?
If I re-install MonoTouch version 3.2.6 again, then my application works correctly, but as soon as I update to MonoTouch 4.0, I run into the same problem.
Your question lacks many details to help us help you, but here's two things you should try:
1) Some fixes made for WCF inside MonoTouch 3.x were (sadly) missing from MonoTouch 4.x. It's possible that your application depended on them. If you use MonoTouch 4.1 then you can replace your System.ServiceModel.dll (see comment #6 of the above link), rebuild your application and see if this fix solves your issue.
2) Several fixes were made in the HTTP stack for MonoTouch 4.2 (soon to be released, but most are not in the 4.1 beta). They are not exactly WCF-related but it's not clear if your 400 error message is a WCF failure (or not).
If both updates do not solve your issue then please fill a bug report at http://bugzilla.xamarin.com and attach a self-contained test case so we can investigate this further. Thanks!

.net 3.5 simple win application error

I have a .net win app that seems to work for all our of test machines but the client is getting this error after installation. So the install seems to be working but the app running creates an issue.
The exception unknown software exception (0xc06d007e) occured in the application at location 0xfd96aa7d
Any ideas how to fix or troubleshoot without going back to the customer for techie debug
Idea for troubleshooting - there may be an entry in Administrative Tools->Event Viewer (look inside Windows Logs->Application) that could help you narrow down the reason for the failure.
The issue was that some of the resources where being blocked by the end user downloading from the web. FTP solved it

Categories

Resources