error calling socket()

Posted on 2004-09-06
Last Modified: 2008-02-26
My code is as follows:

      /* Create the socket */
      if(s == INVALID_SOCKET)
            FILE *f = fopen("c:\\temp\\lsp.txt","a");
            fprintf(f,"socket() error: %d\n",WSAGetLastError());
            return 0;

The error number returned by WSAGetLastError() is 183.  I looked in the winsock2.h header file, and I cant find any sort of reference to 183.  I'm hoping someone here can help me figure out this error.
Question by:lwinkenb
LVL 15

Expert Comment

ID: 11987955
First, you should capture the value from WSAGetLastError before calling fopen, because fopen can change the value.  Just save the value in a variable and use the variable after fopen to put out the value.

Second, do you have a call to WSAStartup before the code you showed?  It's necessary to initialize the library before you try to create a socket.

LVL 86

Expert Comment

ID: 11989644
Do you call 'WSAStartup()' before calling 'socket()'?

WORD wVersionRequested;
WSADATA wsaData;
int err;
wVersionRequested = MAKEWORD( 2, 2 );
err = WSAStartup( wVersionRequested, &wsaData );
if ( err != 0 ) {
    /* Tell the user that we could not find a usable */
    /* WinSock DLL.                                  */

Apart from that, try

     /* Create the socket */
    s = socket(AF_INET,SOCK_STREAM,0);

Author Comment

ID: 11991284
I was already calling WSAStartup(), so that isnt the problem.  I moved the WSAGetLastError() to a new line before the called to fopen(), and now it is giving me a legitamate error.  The error is WSAEPROVIDERFAILEDINIT.

I'm not sure exactly why I'm getting this error, but I think it's due to the fact that Im making the socket() call in DllMain() of a Layered Service Provider DLL.  

Accepted Solution

jonathan6587 earned 500 total points
ID: 12004973

Error 183 is:

"Cannot create a file when that file already exists."

Probably something to do with your "lsp.txt"

I suspect it is your use of fopen, specifically "a"

"a" opens the file for appending, but does not remove the end of file marker before writing new data -- thus if this is any type of loop or you've appended the file previously without closing the fclosing the file -- you would probably get an error like this.  I suggest you use "a+" -- it removes the end of file marker before new data is written and restores the marker after your done writing.

You can use the FormatMessage function to convert error number to the error message.

I'm not sure you care about this now, but it's good to know.

Also, you can type "net helpmsg 183" on the command line and it will convert the error number to a meaningful message.




Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

An Outlet in Cocoa is a persistent reference to a GUI control; it connects a property (a variable) to a control.  For example, it is common to create an Outlet for the text field GUI control and change the text that appears in this field via that Ou…
Preface I don't like visual development tools that are supposed to write a program for me. Even if it is Xcode and I can use Interface Builder. Yes, it is a perfect tool and has helped me a lot, mainly, in the beginning, when my programs were small…
Video by: Grant
The goal of this video is to provide viewers with basic examples to understand and use for-loops in the C programming language.
The goal of this video is to provide viewers with basic examples to understand opening and reading files in the C programming language.

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question