Vb.net how to solve - specified argument was out of the range of valid values."parameter name: size"

Question

0.00/5 (No votes)

See more:

Visual Studio 2019, VB.Net. Just getting back into coding after many years and thought I would start by setting up a simple chat app in VB.Net. I've downloaded many examples of UDP and TCP/IP, including here, from Code Project, and all have the same error - Specified argument was out of the range of valid values."Parameter name: size", in the following line: serverStream.Read(inStream, 0, buffSize)

Private Sub getMessage()
        For infiniteCounter = 1 To 2
            infiniteCounter = 1
            serverStream = clientSocket.GetStream()
            Dim buffSize As Integer
            Dim inStream(10024) As Byte
            buffSize = clientSocket.ReceiveBufferSize
            serverStream.Read(inStream, 0, buffSize)
            Dim returndata As String =
            System.Text.Encoding.ASCII.GetString(inStream)
            readData = "" + returndata
            msg()
        Next
    End Sub

Every example I've tried has the same error, even the example from Microsoft.

What I have tried:

From various sites it seems that the ReceiveBufferSize is different from serverStream Length. However, I can't seem to find a resolution to the problem. Many sites say it shouldn't be coded like that but don't off a fix for it. I'm not understanding why every example fails in the same way. What am I doing wrong? Any help would be appreciated.

Posted 26-Jun-23 8:49am

Member 15070471

Updated 26-Jun-23 10:42am

v2

Add a Solution

Comments

Richard MacCutchan 26-Jun-23 15:11pm

The first thing to do is step through this code with the debugger and see what actual value is being returned into buffSize. That should give an idea as to why the following call is failing.

Ralf Meier 26-Jun-23 15:36pm

when reading your code I stuck at the dimension of the array - did you really want to have it ten thousand bytes large ? or do you originally want to size it 1024 bytes ?

Member 15070471 26-Jun-23 18:50pm

Thank you Richard, that game me the correct value

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2023-06-26T10:42:00

Solution 1

RecieveBufferSize is not the same as the number of bytes in the buffer itself: it's likely to be considerably bigger.
So when you try to read RecieveBufferSize into your array:

Dim inStream(10024) As Byte
buffSize = clientSocket.ReceiveBufferSize
serverStream.Read(inStream, 0, buffSize)

It looks at the siize of the buffer and the number of bytes you asked it to read and throws an error because one will not fit into the other.
Use the size of your array, and it should go away.

Posted 26-Jun-23 10:42am

OriginalGriff

Comments

Member 15070471 26-Jun-23 18:48pm

Thank you. On running the code and checking the error, the number of bytes in the buffer was 65536.
Changing the RecieveBufferSize to 65536 fixed the problem. Still not sure why every example I downloaded had the same error though. Perhaps a chnage in .Net from older versions or something?

OriginalGriff 27-Jun-23 0:37am

No, that's the wrong approach - you pass the length of the barray you want to recieve in, not the max length of the buffer that supplies the data!
Your way is like fitting a fuel tank to your car that is the size of the underground tank at the gas station, and always trying to fill it completely! It may work, but you end up with a huge tank of fuel attached to the roof of your car with a dribble of fuel in it because the pump will only allow you £100 at a time ...

Ask for what is in the buffer, not what could be in the buffer!

Member 15070471 27-Jun-23 7:07am

lol, thank you, I've never really understood the relationship between the two, but your analogy makes it clear.

OriginalGriff 27-Jun-23 7:30am

You're welcome!