Error netname deleted

User-1809261048 posted

Greetings,

I’m not 100% sure this is performance related but the other subforums felt even less adequate. We have a site that is accessed both at an intranet and a remote level via a static IP. At certain intervals of days (sometimes it’s less than 5, sometimes it’s
up to three weeks) the site just crashes and until the app pool is restarted, IIS just can’t serve the page.

Trying to isolate issues, we separated the app pools, so we left one for the intranet access and another for the remote one, the intranet never crashed again (we are talking about 6+ months without a crash) whereas the remote one still faces the same issue
mentioned above.

IIS list this at the end of the line where things start going awry: 500 0 64 7 , the error 64 means ERROR_NETNAME_DELETED but for the life of me I couldn’t find what it really means and how to deal with it. Initially I thought this happened because of rapid
fail protection but the executable set to run when it triggers never does, so now I’m unsure about that. That executable restarts that one app pool, if I run it manually then everything goes back to normal.

So… in a nutshell, anyone has any idea of how to deal with this situation? Is it related to rapid fail protection or not? If it is, why isn’t the executable running? If it isn’t, is there any way to get a better description of the situation
/ error? Moreover, why would this happen only with the app pool that serves the site remotely when they are the same version of the site with the exact same files loaded for use?

Any kind of help will be greatly appreciated.

I’m writing a tcp server in Windows NT using completion ports to exploit asynchronous I/O.
I have a TcpSocket class, a TcpServer class and some (virtual functions) callbacks to call when an I/O operation is completed, e.g. onRead() for when a read is completed. I have also onOpen() for when the connection is established and onEof() for when the connection is closed, and so on.
I always have a pending read for the socket, so if the socket effectively gets data (the read will be completed with size > 0) it calls onRead(), instead if the client closes the socket from the client side (the read will be completed with size == 0) it calls onEof(), and the server is aware of when the client closes the socket with closesocket(server_socket); from its side.

All works gracefully, but I have noticed a thing:

when i call closesocket(client_socket); on the server’s side endpoint of the connection, instead of the client side, (either with setting linger {true, 0} or not), the pending read will be completed as erroneous,
that is, the read size will not only be == 0, but also GetLastError() returns an error: 64, or ‘ERROR_NETNAME_DELETED’. I have searched much about this on the web, but didn’t find nothing interesting.

Then I asked myself: but is this a real error? I mean, can this really be considered an error?

The problem is that on the server side, the onError() callback will be called when I closesocket(client_socket); instead of the onEof(). So I thought this:

What about if I, when this ‘ERROR_NETNAME_DELETED’ «error» is received, call onEof() instead of onError() ?
Would that introduce some bugs or undefined behavior?
Another important point that made me ask this question is this:

When I have received this read completion with ‘ERROR_NETNAME_DELETED’, I have checked the OVERLAPPED
structure, in particular the overlapped->Internal parameter which contain the NTSTATUS error code
of the underlying driver. If we see a list of NTSTATUS error codes [ http://www.tenox.tc/links/ntstatus.html ]
we can clearly see that the ‘ERROR_NETNAME_DELETED’ is generated by the NTSTATUS 0xC000013B, which is an error, but it is called ‘STATUS_LOCAL_DISCONNECT’. Well, it doesn’t look like a name for an error. It seems more like `ERROR_IO_PENDING’ which is an error, but also a status for a correct behavior.

So what about checking the OVERLAPPED structure’s Internal parameter, and when this is == to ‘STATUS_LOCAL_DISCONNECT’ a call to the onEof() callback is performed? Would mess things up?

In addition, I have to say that from the server side, if I call DisconnectEx() before calling
closesocket(client_socket); I will not receive that error. But what about I don’t want to call DisconnectEx() ? E.g. when the server is shutting down and doesn’t want to wait all DisconnectEx() completions, but just want to close all client’s connected.

Categories: Troubleshooting, Error Codes, XenServer, Hyper-V, Physical Systems, Alike v3, Alike v4

Introduction

The following list of common error codes are separated into three categories: Windows systems, Alike Backup Delegate (ABD), and miscellaneous Alike errors. Get a description of each and when possible, a resolution.

Service/Windows Error Codes

Error 1219

(ERROR_SESSION_CREDENTIAL_CONFLICT)

This is a very common, and confusing, error but fortunately easy to fix. Windows throws an error 1219 when you try to login to a resource, such as a network share, with two different user accounts within the same session. The most common cause is when a Windows Explorer window is opened to a network share (e.g. the ADS folder), causing a conflict with Alike’s session.

Error 86

(ERROR_INVALID_PASSWORD)

“The specified network password is not correct.”

Error 1326

(ERROR_LOGON_FAILURE)

Error 1727

(RPC_S_CALL_FAILED_DNE)

“The remote procedure call failed and did not execute.”

Error 71

(ERROR_REQ_NOT_ACCEP)

“No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.”

Error 3

(ERROR_PATH_NOT_FOUND)

“The system cannot find the path specified.”

Error 64

(ERROR_NETNAME_DELETED)

Symptoms:

• “ERROR_NETNAME_DELETED” appears and crashes the active program window.
• Your PC frequently crashes with Error 64 when running the same program.
• “The specified network name is no longer available” is displayed.
• Windows runs sluggishly and responds slowly to mouse or keyboard input.
• Your computer periodically “freezes” for a few seconds at a time.

These 64 error messages can appear during program installation, while a Microsoft Corporation-related software program (eg. Windows Operating System) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your ERROR_NETNAME_DELETED error occurs is a critical piece of information in troubleshooting the problem.

Error 67

(ERROR_BAD_NET_NAME)

“The network name cannot be found.”

Error 87

(ERROR_INVALID_PARAMETER)

“The parameter is incorrect.”

ABD Related Error Codes (linux errno.h codes)

Error 22

• Example: Seek failed on file /dev/nbd0 with error code : 22

This is most often caused by networking related issues between the source and destination ABDs. Often, this is due to aggressive idle settings in firewalls or network devices which forcibly close the network connection between the two devices. It can also be caused by network intermittencies or a generally unreliable connection between the two locations.

• Resolution: If this is the case, simply close the offending explorer window and try again. You can also check the output of the command, net use, and close any conflicting sessions.

Close the sessions with the following syntax: net use /DELETE \path.tosession

Error 137

• Example: “failure for device: X. Output: 137”

This is caused by the ABD running out of memory during the course of the job (usually a restore job).

• Resolution: It can be resolved by assigning additional memory to the ABD template for the pool in question (i.e. going from 128MB to 512MB ram), and re-running the job.

PLEASE NOTE: This problem typically affects only older versions of Alike (pre v3.0). However, this error can occur in newer versions. If a newer installation of Alike encounters this issue, please open a support ticket.

Error Message: ABD Failed to mount ADS. mount: Cannot allocate memory

This misleading error may mean that the ABD appliance cannot fully connect to your CIFS network share, usually due to a permissions problem.

• Resolution: Double-check the NTFS and CIFS Sharing permissions on the Alike Data Store (ADS) allows full access by the user account defined in the Alike Manager under Settings–>Storage.

Miscellaneous Errors

Error Message: “Failed to copy databases”

• Resolution: Change the “Archive internal databases every___hours” setting under Tools–>System Settings–>Show Advanced Settings.

The default is undefined. Change this setting to archive every 6 to 8 hours.

Final Notes

If you didn’t find what you’re looking for here, or need help troubleshooting, please open a support ticket. See the KB article, “How to Use Quadric Support,” for instructions and tips on making your support experience as efficient as possible.

Scott

|

Published: October 24, 2017

Error 1611: 64. Failure
Error 1620: 64. Failure
Error 1611: 2250. Failure
Error 1620: 2250. Failure