Not enough credits on dispose() about smblibrary

[TalAloni]

Not Enough Credits and STATUS_INVALID_SMB are two different issues.
In both cases it means the client is doing something it should not do. (it can be the library code or how the library is used)
In most previous cases it was due to incorrect usage of the library (e.g. multi-threading, multiple requests)
This can be investigated though a WireShark capture of the session.
Are you based on the latest v1.5.0?

[smarsh-gregj]

Thanks for the response. I understand they are different issues, but in our case, we get STATUS_INVALID_SMB and throw an exception which causes the FileStore to Disconnect() and throw "Not enough credits". (This Disconnect would count as a multiple request at this point).
So my question would be... If/When we get STATUS_INVALID_SMB, what is the proper way to handle that status? If the answer is "Don't get that status" then we can certainly look deeper into that too.

Unfortunately I have no way to get a wireshark capture due to the problem happening seemingly randomly and we haven't been able to reproduce in production. And yes we are on v1.5.0

[TalAloni]

Yes, the answer is "Don't get that status". it means the client is behaving in some way it shouldn't so the server is telling the client so.