Troubleshooting

🩺 Troubleshooting

A drive that does not come up almost always says why. This page collects what those answers mean, starting with the number Windows returns when it refuses a mapping.

Tip

TL;DR — A red icon with Offline or Maintenance is not an error and needs nothing from you. Anything else carries either a status word from the status vocabulary or an error number from Windows. Look the number up in the table below. If it is not there, the number itself is what a search engine and the Windows event log understand, and the diagnostics report is what makes an issue answerable.

• What is not a problem
• The mapping error codes
• Symptoms without a number
• Collecting a diagnostics report

😌 What is not a problem

Three states look alarming and are not:

What you see	Why it is fine
Offline	the server did not answer. NcDavTray unmaps the drive cleanly and remounts it by itself as soon as it does
Maintenance	the server answered and said it is in maintenance mode. Same handling
Waiting for a free connection slot	both logins Windows keeps for that host are taken. The mount stays in the list and connects on its own as soon as one of them is released. See Server identities

Watching a server come back on its own is what the application is for. The only reason to act is when a drive stays down while the server is demonstrably up.

🔢 The mapping error codes

When Windows refuses to map the drive it returns a number, and NcDavTray shows it. Only the codes with a remedy of their own get a message of their own; the rest carry the number.

Code	Windows name	What NcDavTray says	Where to look
1219	ERROR_SESSION_CREDENTIAL_CONFLICT	a dialog naming the two drives that hold the logins for that server	Server identities
5	ERROR_ACCESS_DENIED	did not accept the credentials	the credentials
1326	ERROR_LOGON_FAILURE	did not accept the credentials	the credentials
1244	ERROR_NOT_AUTHENTICATED	did not accept the credentials	the credentials
53	ERROR_BAD_NETPATH	could not be reached	the server field
67	ERROR_BAD_NET_NAME	could not be reached	the server field
31	ERROR_GEN_FAILURE	unexpected network error	the diagnostics report
59	ERROR_UNEXP_NET_ERR	unexpected network error	the diagnostics report
85	ERROR_ALREADY_ASSIGNED	nothing	nothing to do, see below
anything else		the number, as it came from Windows	the number is what the event log and a search engine speak

🔑 The credentials group: 5, 1326, 1244

The server was reached and turned the login down. For an account mount the usual cause is the wrong kind of password: an account mount needs an app password created in Nextcloud under Profile → Security, not the password you log in with. For a share link it is the share's own password, which is a different thing entirely — see Share links.

An app password that was revoked on the server gives the same answer. Nextcloud lists every one of them with its last activity under Profile → Security, so a mount that worked until recently is quickest to check there.

🌐 The reachability group: 53, 67

Windows could not resolve or reach the path at all. The server field of a mount holds a host name and nothing else — no https://, no port, no path. A full URL pasted in there produces exactly this. Only https on the standard port 443 works, so a server behind a different port cannot be mounted.

A server that is genuinely back can still look unreachable for a while, because Windows caches the fact that it did not answer. The lifetime of that cache is adjustable, see WebClient service.

🧱 The unexpected group: 31, 59

The server answered, but the redirector could not make a WebDAV session out of what came back. These two are the codes without a remedy of their own, and the ones worth collecting a diagnostics report for: what Windows saw is the only thing that narrows it down.

🔁 85, and why you never see it

ERROR_ALREADY_ASSIGNED means the drive letter is still taken. Right after a mapping was taken down that is not a failure but a matter of waiting: NcDavTray releases the letter, waits for Windows to let go of it, and maps again. Only if that second attempt fails does anything reach you.

🧩 Symptoms without a number

Symptom	What it is
The application icon says needs setup (service deactivated)	the WebClient service is disabled and cannot start on demand, so no WebDAV drive works. See WebClient service
Drive {letter} is already in use while adding a mount	another mount or another program holds that letter. Pick a different one
A share link is refused with a message rather than a number	the server, the link or the password. The messages are listed on Share links
Large files fail, or a big folder behaves erratically in Explorer	redirector limits, not NcDavTray. See WebClient service
A mount shows No drive letter	the entry has no usable letter configured. Edit it in the Shares tab

📋 Collecting a diagnostics report

The repository ships a script that writes the relevant Windows state into one text file: tools/diagnostics/.

1. Copy NcDavTray_diag.ps1 and Run_NcDavTray_diag.cmd into any folder on the affected machine.
2. Leave NcDavTray running as you normally use it, if you can.
3. Start Run_NcDavTray_diag.cmd and answer the prompts: the profile, installed or portable, and whether to include UI/DPI and reachability information.
4. It writes NcDavTray_diag_<date>_<time>.txt next to the scripts.

Important

For a report you are going to post publicly, pick the profile Public issue / GitHub. It anonymises host names, user names and mount labels for you. The other profile keeps them, which is what you want when you are only reading it yourself.

Paste the full file into the issue inside a fenced code block. A report answers in one go what a conversation otherwise needs a dozen questions for.