Wsaewouldblock resource temporarily unavailable sap ошибка

[ Script execution time: 0,0747 ]   [ 16 queries used ]   [ Generated: 29.01.23, 03:29 GMT ]  

SAP on single Windows Server.

For Me through VPN:

1. I can ping both the IP address and domain.
2. I can connect to SAPGUI.
3. When I telnet to IP Port 3200, get a black screen.
4. «netstat -a» is slow, but executes, but «netstat -an» is instantaneous.

My developer through VPN:

1. Can ping both IP and domain, but can’t connect through SAPGUI from two different machines.
2. Have tested with all firewalls (server and client) off — doesn’t work.

Hosts file on server correctly has entry for domain. Services file has entry for sapdp00:3200 .

Reviewed both 124562 Hostname resolution problems (DNS timeouts) and 23538 Problems due to inconsistent host name notation but don’t know that I’ve got a good answer.

I’m not a network guy (or really Basis). Hoping someone can give me some pointers of what to look for.

Thanks in advance.

SAP on single Windows Server.

For Me through VPN:

1. I can ping both the IP address and domain.
2. I can connect to SAPGUI.
3. When I telnet to IP Port 3200, get a black screen.
4. «netstat -a» is slow, but executes, but «netstat -an» is instantaneous.

My developer through VPN:

1. Can ping both IP and domain, but can’t connect through SAPGUI from two different machines.
2. Have tested with all firewalls (server and client) off — doesn’t work.

Hosts file on server correctly has entry for domain. Services file has entry for sapdp00:3200 .

Reviewed both 124562 Hostname resolution problems (DNS timeouts) and 23538 Problems due to inconsistent host name notation but don’t know that I’ve got a good answer.

I’m not a network guy (or really Basis). Hoping someone can give me some pointers of what to look for.

Thanks in advance.

SAPDHI:sapdp00 not reached and WSAEWOULDBLOCK : Resource Temporarily unavailable

I have installed a SAP ERP 6.0 on SUSE with Maxdb. The installation was concluded with successful. I have started SAP instance with the command startsap all and I could see that the Instance is look like working. 

From a workstation, I am getting to ping the server but when I try to use SAP GUI, I am getting an error saying : 

«SAPDHI:sapdp00» not reached 

Component : NI (Network Interface) 

Module : nibuf.cpp 

Line 4658 

Method NiBuf!ConnetÇ connection pending after 10000ms 

Return code : -10 

Error No : 10035 

Error Text : WSAEWOULDBLOCK : Resource Temporarily unavailable 

To check if the system is working I have executed the following command ps -ef | grep dw.sap  and the result was : 

SAPDHI:/ # ps -ef | grep dw.sap 
dhiadm 27676 27631 0 21:56 ? 00:00:02 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28023 27676 0 21:56 ? 00:00:02 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28026 27676 0 21:56 ? 00:00:00 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28030 27676 0 21:56 ? 00:00:01 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28036 27676 0 21:56 ? 00:00:00 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28039 27676 0 21:56 ? 00:00:01 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28080 27676 0 21:56 ? 00:00:00 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28081 27676 0 21:56 ? 00:00:01 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28083 27676 0 21:56 ? 00:00:04 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28086 27676 0 21:56 ? 00:00:01 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28087 27676 0 21:56 ? 00:00:05 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28093 27676 0 21:56 ? 00:00:00 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28103 27676 0 21:56 ? 00:00:00 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28109 27676 0 21:56 ? 00:00:00 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28110 27676 0 21:56 ? 00:00:00 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28117 27676 0 21:56 ? 00:00:01 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
dhiadm 28120 27676 0 21:56 ? 00:00:00 dw.sapDHI_DVEBMGS00 pf=/usr/sap/DHI/SYS/profile/DHI_DVEBMGS00_SAPDHI 
root 29089 5024 0 22:26 pts/0 00:00:00 grep dw.sap 
SAPDHI:/ # 

продолжатьTCPСетевое программирование, использованиеsend()Когда функция отправляет данные, она иногда встречаетWSAEWOULDBLOCKНеправильно, что это за хрень?

Пример кода

    iResult = send( ConnectSocket, sendbuf, (int)strlen(sendbuf), 0 );
    if (iResult == SOCKET_ERROR)
    {
       int nLastError = WSAGetLastError();
       if (WSAEWOULDBLOCK == nLastError )
       {
            ...
       }
        ...
    }

WSAEWOULDBLOCK

WSAEWOULDBLOCK
10035
Resource temporarily unavailable.
This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket.
It is a nonfatal error, and the operation should be retried later.
It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.

WSAEWOULDBLOCKЭто не фатальная ошибка, и соответствующие операции следует повторить позже.

Анализ причин

WSAEWOULDBLOCK is not really an error but simply tells you that your send buffers are full.
This can happen if you saturate the network or if the other side simply doesn’t acknowledge the received data. Take a look at the select() function, which allows you to wait until buffer space is available or a timeout occurs. There is also a way to bind a win32 event to a stream, which then allows its use with WaitForMultipleObjects in case you want to abort waiting early.

Буфер ядра окна, который должен быть отправлен, заполнен и может быть отправлен только при наличии свободного времени.

Решение:

• Перед отправкой поспите

while(nRet == SOCKET_ERROR && WSAGetLastError() == WSAEWOULDBLOCK)
{
    Sleep(50);
    nRet = send(...);
}

Этот тип мышления лучше всего складывать суждение о количестве раз, например, если более 20 раз, передача считается неудачной.

• Увеличиватьsocketизkernel buffer

SOCKET ConnectSocket = ...
...
int nRcvBufferLen = 1024*1024;
int nSndBufferLen = 4*1024*1024;
int nLen          = sizeof(int);
setsockopt(ConnectSocket, SOL_SOCKET, SO_RCVBUF, (char*)&nRcvBufferLen, nLen);
setsockopt(ConnectSocket, SOL_SOCKET, SO_SNDBUF, (char*)&nSndBufferLen, nLen);

При отправке аудио и видео, еслиSO_SNDBUFЕсли настройка слишком мала, когда сетевая среда плохая, экран будет размытым (данные будут отправлены слишком поздно), и это явление не произойдет, если сетевая среда хорошая.

References:

https://msdn.microsoft.com/en-us/library/ms740149(VS.85).aspx
https://msdn.microsoft.com/en-us/library/ms740668(v=vs.85).aspx#WSAEWOULDBLOCK
http://www.cnblogs.com/chengxin1982/archive/2009/12/24/1631067.html
http://stackoverflow.com/questions/14546362/how-to-resolve-wsaewouldblock-error
https://bobobobo.wordpress.com/2008/11/09/resolving-winsock-error-10035-wsaewouldblock/