A client has a Sharepoint 2013 farm consists of 2 servers acting as frontend and app and 2 SQL server (SQL14) all with windows server 2012.
My application is a windows application that calls sharepoint with CSOM requests.
All the environment was late by 10 min from the real time and for years everything was working, suddenly after fixing the time on the Domian sever so that it is fixed on all the severs and client machines, all the CSOM requests to sharepoint severs throws exception request aborted request timeout. Nothing is logged on the server and I couldn't find any reason.
Suddenly and by chance when I changed the IP on one of the PCs that holds my windows application to a one that was not in use, things started working again and I continued the same on all PCs.
But the client wants a clear justification on what was the problem.
Does anybody know how time is related to sharepoint and client.svc and is there any way the time keep cached on any level of the network
Actually it was not a problem of sharepoint.
The client was using a new NSX system and for unkown reason it was causing packets loss. Basically net tcp requests packages.
Related
I have a site that is used by a local company now for many years. In the last week, every time a user connects.... about 30 seconds after a data stream appears that fills their internet connection (Upload bandwidth since they are hosting the app internally) with 7Mbits of data.
The browser (Chrome or Edge) is not reporting any of this traffic. Just shows that the Web socket connection is established, and that it is listening. If I do something in the app to transfer data through the websocket, I see it in the debug window with the size at the bottom. The browser does not see all of this data coming to it....
With WireShark I can capture the data but it looks to just be all binary and can't make heads or tails of it....
It is hosted on Windows 2019
IIS
the site is .Net 4.8
The issue started without any site updates on my part....
Has anyone heard of something similar to this? Was their a Windows patch recently involving websockets? What can I include for anyone to help...?
I have ASP.NET MVC website that runs on my local sever and I need to check mobile area.
So I decided to connect to it via Android Emulator (AVD)
As I read IIS server reject incoming requests from remote devices.
So from this thread I think I found solution
Post
I make all described on his github and get this
So as I understood it can receive external requests now.
And I tried to make request from AVD (192.168.2.106:3000)
And I get this
So as I understood it got path, but IIS still not receive external request.
Maybe someone faced this problem and can help me solve it?
We recently migrated a site to a new server. This site integrates with Barclaycard ePDQ, and was working fine on the old server.
Since migrating, however, ePDQ is unable to hit our Postback Url (which is an ashx handler). They are seeing a response http code = -1, which we're told means it's either exceeding the maximum timeout (20 seconds) or the url simply can't be accessed.
We checked the firewall on the new server, and it is allowing incoming traffic over ports 80 and 443.
I am also able to mimic the POST with the same request data to the Postback Url using Fiddler, and this works fine. So no timeouts, and it is accepting POST requests over port 80.
The site was migrated several days ago, and running a DNS propagation tool against the domain shows it universally resolving to it's new IP.
We're running Windows server 2012 on the new server. The old server was running Windows 2008 R2.
Does anybody have any ideas why ePDQ is unable to hit our postback url?
Thanks in advance
I create Asp.net WS and host it on the IIS.Now i want to consume it from remote computer or another computer.When i insert the URL of the WS on the remote computer an error message appears inside internet explorer browser page says
This program cannot display the web page
i work on Visual studio 2008, windows 7 and the client application is Asp.net website.
i don't know what is the problem??
have i connect the two computers with LAN(make network between them) or just enough each one connect to the internet??
Your computers need to be able to connect to each other.
If they on LAN, then You need to specify LAN address for asp.net WS.
Also check Your firewall for blocking connections, need to be sure that port were IIS hosted is available for connection
If nothing helps, then provide us more information about problem.
Really i don't know what is the problem.When i do the same thing in another computer it runs but on my laptop doesn't run.
I have an Azure web role that accesses an external WCF based SOAP web service (port 80) for various bits of data. The response from this service is highly erratic. I routinely get the following error.
There was no endpoint listening at
http://www.myexternalservice.com/service.svc that could accept the message. This is
often caused by an incorrect address or SOAP action.
To isolate the problem I created a simple console app to repetitively call this service in 1 second intervals and log all responses.
using (var svc = new MyExternalService())
{
stopwatch.Start();
var response = svc.CallService();
stopwatch.Stop();
Log(response, stopwatch.ElapsedMilliseconds);
}
If I RDP to one of my Azure web instances and run this app it takes 10 to 20 attempts before it gets a valid response from the external service. These first attempts are always accompanied by the above error. After this "warm up period" it runs fine. If I stop the app and then immediately restart, it has to go back through the same "warm up" period.
However, if I run this same app from any other machine I receive valid responses immediately. I have run this logger app on servers running in multiple data centers (non Azure), desktops on different networks, etc... These test runs are always very stable.
I am not sure why this service would react this way in the Azure environment. Unfortunately, for the short term I am forced to call this service but my users cannot tolerate this inconsistency.
A capture of network traffic on the Azure server indicates a large number of SynReTransmit's in 10 second intervals during the same time I experience the connection errors. Once the "warm up" is complete the SynReTransmit's no longer occur.
The Windows Azure data center region where the Windows Azure application is deployed might not be near the external Web Service. The local machine you're trying (which works fine) might be close to the web service. That’s why there might be huge latency in Azure which would likely cause it to fail.
Success accessing WSDL from a browser in Azure VM might be due to browser caching. Making a function call from browser would tell you if it is actually making a connection.
We found a solution for this problem although I am not completely happy with it. After exhausting all other courses of action we changed the load balancer to Layer-7 Load Balancing from Layer-4 Load Balancing. While this fixed the problem of lost requests I am not sure why this made a difference.