Ошибка сокета 10038 citrix

Go to Top

[{«Business Unit»:{«code»:»BU059″,»label»:»IBM Software w/o TPS»},»Product»:{«code»:»SSMRTZ»,»label»:»IBM Cognos Controller on Cloud»},»ARM Category»:[],»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»All Versions»,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

Нравится ресурс? Помоги проекту!

[ Script execution time: 0,0403 ]   [ 16 queries used ]   [ Generated: 12.02.23, 04:29 GMT ]  

Ошибка socket error 10038

Please contact us if you have any trouble resetting your password.

The problem is that you increment the client count *before* you assign to the array. This causes assignment to the wrong slot, which means you pass a not-a-socket value into select(). 10038 means «not a socket» which makes sense.

Also, incrementing the counter first means that you have a potential buffer overrun. And, just because listen() takes 9 as a parameter, doesn’t mean that the number of potential connections will be limited to 9 — the *backlog* may be limited to 9. You could get 100 connections, and you’d totally crash your server. Or, worse, someone might exploit it as a remote code execution vulnerability.

Is this what you mean my ‘client count’:

If so, couldn’t I just put an if around it? Like this:

Quote: Original post by Azjherben
couldn’t I just put an if around it? Like this:

The if statement doesn’t do anything. If numclients is less than or equal to zero, the loop won’t execute (0 Cancel Save

You did not actually show the area where you increment the client count.
Specifically, you keep the client count in the «numclients» variable.

This is meant as good advice, not as a put-down: If you can’t figure out this simple problem from the information we’ve already given you, you should not be writing network code in C++ yet — you need to first learn the language really well, because distributed concurrent programming is hard as it is even when you’re fully fluent in developing in the language of your choice.

Quote: Original post by hplus0603
The problem is that you increment the client count *before* you assign to the array. This causes assignment to the wrong slot, which means you pass a not-a-socket value into select(). 10038 means «not a socket» which makes sense.

Also, incrementing the counter first means that you have a potential buffer overrun. And, just because listen() takes 9 as a parameter, doesn’t mean that the number of potential connections will be limited to 9 — the *backlog* may be limited to 9. You could get 100 connections, and you’d totally crash your server. Or, worse, someone might exploit it as a remote code execution vulnerability.

Okay, looking at what you said, I realize that I should have it check for the lowest number available out of the maximium amount (9) and set it to that. And have clients br removed from the array when they disconnect. (Making that number available again) As for the main error, I’ll try to fix that first. If I get a completly new error, or it works, I’ll post. Also, that for right after the while, that is what you mean by ‘client count’ right.

Источник

Why do I receive «FLEXlm error: -15,570. System Error: 10038 Winsock: Specified socket is invalid» when I try to start MATLAB?

Direct link to this question

Direct link to this question

Accepted Answer

Direct link to this answer

Direct link to this answer

0 Comments

More Answers (0)

See Also

Categories

No tags entered yet.

Products

Find the treasures in MATLAB Central and discover how the community can help you!

An Error Occurred

Unable to complete the action because of changes made to the page. Reload the page to see its updated state.

Select a Web Site

Choose a web site to get translated content where available and see local events and offers. Based on your location, we recommend that you select: .

You can also select a web site from the following list:

How to Get Best Site Performance

Select the China site (in Chinese or English) for best site performance. Other MathWorks country sites are not optimized for visits from your location.

Americas

Europe

• Belgium (English)
• Denmark (English)
• Deutschland (Deutsch)
• España (Español)
• Finland (English)
• France (Français)
• Ireland (English)
• Italia (Italiano)
• Luxembourg (English)

• Netherlands (English)
• Norway (English)
• Österreich (Deutsch)
• Portugal (English)
• Sweden (English)
• Switzerland
  • Deutsch
  • English
  • Français
• United Kingdom (English)

Asia Pacific

• Australia (English)
• India (English)
• New Zealand (English)
• 中国
  • 简体中文 Chinese
  • English
• 日本 Japanese (日本語)
• 한국 Korean (한국어)

Accelerating the pace of engineering and science

MathWorks is the leading developer of mathematical computing software for engineers and scientists.

Источник

How Socket Error Codes Depend on Runtime and Operating System

Rider consists of several processes that send messages to each other via sockets. To ensure the reliability of the whole application, it’s important to properly handle all the socket errors. In our codebase, we had the following code which was adopted from Mono Debugger Libs and helps us communicate with debugger processes:

In the case of a failed connection because of a “ConnectionRefused” error, we are retrying the connection attempt. It works fine with .NET Framework and Mono. However, once we migrated to .NET Core, this method no longer correctly detects the “connection refused” situation on Linux and macOS. If we open the SocketException documentation, we will learn that this class has three different properties with error codes:

• SocketError SocketErrorCode : Gets the error code that is associated with this exception.
• int ErrorCode : Gets the error code that is associated with this exception.
• int NativeErrorCode : Gets the Win32 error code associated with this exception.

What’s the difference between these properties? Should we expect different values on different runtimes or different operating systems? Which one should we use in production? Why do we have problems with ShouldRetryConnection on .NET Core? Let’s figure it all out!

Digging into the problem

If we run it on Windows, we will get the same value on .NET Framework, Mono, and .NET Core:

10061 corresponds to the code of the connection refused socket error code in Windows (also known as WSAECONNREFUSED ). Now let’s run the same program on Linux:

As you can see, Mono returns Windows-compatible error codes. The situation with .NET Core is different: it returns a Windows-compatible value for SocketErrorCode (10061) and a Linux-like value for ErrorCode and NativeErrorCode (111). Finally, let’s check macOS:

Here, Mono is completely Windows-compatible again, but .NET Core returns 61 for ErrorCode and NativeErrorCode . In the IBM Knowledge Center, we can find a few more values for the connection refused error code from the Unix world (also known as ECONNREFUSED ):

• AIX: 79
• HP-UX: 239
• Solaris: 146

For a better understanding of what’s going on, let’s check out the source code of all the properties.

SocketErrorCode

These values correspond to the Windows Sockets Error Codes.

NativeErrorCode

In .NET Core, the native code is calculated in the constructor (see SocketException.cs#L20):

The Windows implementation of GetNativeErrorForSocketError is trivial (see SocketException.Windows.cs):

The Unix implementation is more complicated (see SocketException.Unix.cs):

TryGetNativeErrorForSocketError should convert SocketError to the native Unix error code. Unfortunately, there exists no unequivocal mapping between Windows and Unix error codes. As such, the .NET team decided to create a Dictionary that maps error codes in the best possible way (see SocketErrorPal.Unix.cs):

Once we have an instance of Interop.Error , we call interopErr.Info().RawErrno . The implementation of RawErrno can be found in Interop.Errors.cs:

Here we are jumping to the native function SystemNative_ConvertErrorPalToPlatform that maps Error to the native integer code that is defined in errno.h. You can get all the values using the errno util. Here is a typical output on Linux:

Note that errno may be not available by default in your Linux distro. For example, on Debian, you should call sudo apt-get install moreutils to get this utility. Here is a typical output on macOS:

Hooray! We’ve finished our fascinating journey into the internals of socket error codes. Now you know where .NET is getting the native error code for each SocketException from!

ErrorCode

Writing cross-platform socket error handling

There was a lot of work involved in tracking down the error code to check against, but in the end, our code is much more readable now. Adding to that, this method is now also completely cross-platform, and works correctly on any runtime.

Overview of the native error codes

We executed this program on Windows, Linux, and macOS. Here are the aggregated results:

Источник

Why do I receive «FLEXlm error: -15,570. System Error: 10038 Winsock: Specified socket is invalid» when I try to start MATLAB?

Direct link to this question

Direct link to this question

Accepted Answer

Direct link to this answer

Direct link to this answer

0 Comments

More Answers (0)

See Also

Categories

No tags entered yet.

Products

Find the treasures in MATLAB Central and discover how the community can help you!

An Error Occurred

Unable to complete the action because of changes made to the page. Reload the page to see its updated state.

Select a Web Site

Choose a web site to get translated content where available and see local events and offers. Based on your location, we recommend that you select: .

You can also select a web site from the following list:

How to Get Best Site Performance

Select the China site (in Chinese or English) for best site performance. Other MathWorks country sites are not optimized for visits from your location.

Americas

Europe

• Belgium (English)
• Denmark (English)
• Deutschland (Deutsch)
• España (Español)
• Finland (English)
• France (Français)
• Ireland (English)
• Italia (Italiano)
• Luxembourg (English)

• Netherlands (English)
• Norway (English)
• Österreich (Deutsch)
• Portugal (English)
• Sweden (English)
• Switzerland
  • Deutsch
  • English
  • Français
• United Kingdom (English)

Asia Pacific

• Australia (English)
• India (English)
• New Zealand (English)
• 中国
  • 简体中文 Chinese
  • English
• 日本 Japanese (日本語)
• 한국 Korean (한국어)

Accelerating the pace of engineering and science

MathWorks is the leading developer of mathematical computing software for engineers and scientists.

Источник

I am testing out a Socket Server application in c and I am getting an error on the bind function with code 10038. I looked this up and MSDN says it means:

An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.

Here is the code:

// I have the correct include files such as include , but stackoverflow displays it weird when i put #include winsock2.h

int main()
{
WSADATA         wsaData;
SOCKET          ListeningSocket;
SOCKET          NewConnection;
SOCKADDR_IN     ServerAddr;
int             Port = 5150;


if(WSAStartup(MAKEWORD(2,2),&wsaData) != 0)
{
    printf("Server: WSAStartup failed with error %ldn",WSAGetLastError());
    return -1;
}
else
{
        printf("Server: The Winsock dll found!n");
        printf("Server: The current status is: %s.n",wsaData.szSystemStatus);
}

if(LOBYTE(wsaData.wVersion) != 2 || HIBYTE(wsaData.wVersion) != 2)
{
    printf("Server: The dll do not support Winsock version 
           %u.%u!n",LOBYTE(wsaData.wVersion),HIBYTE(wsaData.wVersion));
    WSACleanup();
    return -1;
}
else
{
    printf("Server: The dll supports the Winsock version %u.%u!n",LOBYTE(wsaData.wVersion),HIBYTE(wsaData.wVersion));
    printf("Server: The highest version this dll can support: %u.%un",LOBYTE(wsaData.wHighVersion),HIBYTE(wsaData.wHighVersion));
}

ListeningSocket == socket(AF_INET,SOCK_STREAM,IPPROTO_TCP);

if(ListeningSocket == INVALID_SOCKET)
{
    printf("Server: Error at socket(), error code: %ldn",WSAGetLastError());
    WSACleanup();
    return -1;
}
else
    printf("Server: socket() is OK!n");

ServerAddr.sin_family = AF_INET;
ServerAddr.sin_port = htons(Port);
ServerAddr.sin_addr.s_addr = htonl(INADDR_ANY);

if(bind(ListeningSocket, (SOCKADDR *)&ServerAddr,sizeof(ServerAddr)) == SOCKET_ERROR)
{

    printf("Server: bind() failed! Error code: %ld.n",WSAGetLastError());
    closesocket(ListeningSocket);
    WSACleanup();
    return -1;
}
else
    printf("Server: bind() is OK!n");

if(listen(ListeningSocket,5) == SOCKET_ERROR)
{
      printf("Server: listen(): Error listening on socket %ld.n", WSAGetLastError());
      closesocket(ListeningSocket);
      WSACleanup();
      return -1;
 }
 else
      printf("Server: listen() is OK, I'm waiting for connections...n");

 printf("Server: accept() is ready...n");


 while(1)
 {
      NewConnection = SOCKET_ERROR;

      while(NewConnection == SOCKET_ERROR)
      {
          NewConnection = accept(ListeningSocket, NULL, NULL);
      }

      printf("Server: accept() is OK...n");
      printf("Server: Client connected, ready for receiving and sending data...n");

      ListeningSocket = NewConnection;

      break;
 }

 if(closesocket(NewConnection) != 0)
     printf("Server: Cannot close "NewConnection" socket. Error code: %ldn", 
            WSAGetLastError());
 else
      printf("Server: Closing "NewConnection" socket...n");

 if(WSACleanup() != 0)
      printf("Server: WSACleanup() failed! Error code: %ldn", WSAGetLastError());
 else
      printf("Server: WSACleanup() is OK...n");


 return 0;

}

I am testing out a Socket Server application in c and I am getting an error on the bind function with code 10038. I looked this up and MSDN says it means:

An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.

Here is the code:

// I have the correct include files such as include , but stackoverflow displays it weird when i put #include winsock2.h

int main()
{
WSADATA         wsaData;
SOCKET          ListeningSocket;
SOCKET          NewConnection;
SOCKADDR_IN     ServerAddr;
int             Port = 5150;


if(WSAStartup(MAKEWORD(2,2),&wsaData) != 0)
{
    printf("Server: WSAStartup failed with error %ldn",WSAGetLastError());
    return -1;
}
else
{
        printf("Server: The Winsock dll found!n");
        printf("Server: The current status is: %s.n",wsaData.szSystemStatus);
}

if(LOBYTE(wsaData.wVersion) != 2 || HIBYTE(wsaData.wVersion) != 2)
{
    printf("Server: The dll do not support Winsock version 
           %u.%u!n",LOBYTE(wsaData.wVersion),HIBYTE(wsaData.wVersion));
    WSACleanup();
    return -1;
}
else
{
    printf("Server: The dll supports the Winsock version %u.%u!n",LOBYTE(wsaData.wVersion),HIBYTE(wsaData.wVersion));
    printf("Server: The highest version this dll can support: %u.%un",LOBYTE(wsaData.wHighVersion),HIBYTE(wsaData.wHighVersion));
}

ListeningSocket == socket(AF_INET,SOCK_STREAM,IPPROTO_TCP);

if(ListeningSocket == INVALID_SOCKET)
{
    printf("Server: Error at socket(), error code: %ldn",WSAGetLastError());
    WSACleanup();
    return -1;
}
else
    printf("Server: socket() is OK!n");

ServerAddr.sin_family = AF_INET;
ServerAddr.sin_port = htons(Port);
ServerAddr.sin_addr.s_addr = htonl(INADDR_ANY);

if(bind(ListeningSocket, (SOCKADDR *)&ServerAddr,sizeof(ServerAddr)) == SOCKET_ERROR)
{

    printf("Server: bind() failed! Error code: %ld.n",WSAGetLastError());
    closesocket(ListeningSocket);
    WSACleanup();
    return -1;
}
else
    printf("Server: bind() is OK!n");

if(listen(ListeningSocket,5) == SOCKET_ERROR)
{
      printf("Server: listen(): Error listening on socket %ld.n", WSAGetLastError());
      closesocket(ListeningSocket);
      WSACleanup();
      return -1;
 }
 else
      printf("Server: listen() is OK, I'm waiting for connections...n");

 printf("Server: accept() is ready...n");


 while(1)
 {
      NewConnection = SOCKET_ERROR;

      while(NewConnection == SOCKET_ERROR)
      {
          NewConnection = accept(ListeningSocket, NULL, NULL);
      }

      printf("Server: accept() is OK...n");
      printf("Server: Client connected, ready for receiving and sending data...n");

      ListeningSocket = NewConnection;

      break;
 }

 if(closesocket(NewConnection) != 0)
     printf("Server: Cannot close "NewConnection" socket. Error code: %ldn", 
            WSAGetLastError());
 else
      printf("Server: Closing "NewConnection" socket...n");

 if(WSACleanup() != 0)
      printf("Server: WSACleanup() failed! Error code: %ldn", WSAGetLastError());
 else
      printf("Server: WSACleanup() is OK...n");


 return 0;

}