Error MessagesOn this page, you can find descriptions of the error messages that Haxial programs display from time to time. If the error message or code you are looking for is not here, you can contact Haxial and ask for it to be added. Contents:
Operation is unimplemented. (ID 1/4)This most likely means that the feature you tried to use has not been finished -- it is still being programmed/made and will be completed in a future version of the program. This should only happen in an alpha or beta (unfinished) version of a product.
Access Denied. (ID 1/20)If a KDX Server reports this error to you, it means that the server administrator has not given you access to do what you tried to do. In other words, the person that runs the server is not allowing you to do that, for whatever reason. The only solution is to contact the server administrator and ask for access. Only the server administrator or other authorized people can grant you access. Note that Haxial cannot grant you access because Haxial does not run the server that you are trying to use. Alternatively, you could simply go to a different server where the access rules might be different. If you see this error on your own KDX Server, then it is probably because you connected to your server using the guest account, or an account other than your admin account. When you first start KDX Server, it asks you to choose an admin login and password. This is what you should use when connecting to your server in order to gain full access. If people trying to upload to your KDX Server see this error, check their upload access privileges in (a) their Account Class, (b) their Account, and (c) the Folder Access for "UL" ("Commands" -> Your Server -> "Folder Access"). Also check where the people are trying to upload to -- most server administrators only allow people to upload to a special "Uploads" folder and no-where else, and this "Uploads" folder must have been created with the "UL" Folder Access item specified (which causes the real name of the folder to end with "[UL]", thus linking it with the "UL" Folder Access item). If the folder is linked with a different Folder Access item other than "UL", then you need to check the privileges in that other Folder Access item. If the folder specifies no Folder Access item, then it uses whichever the parent folder uses (or the parents parent etc). If none of the parents specify a Folder Access, then it uses the Default Folder Access item.
An unknown operating system error has occurred. (ID 1/27)This happens when the Operating System that you are using (such as MS Windows or MacOS) reports an error code/number that the Haxial program does not recognize. If the error code is displayed like this example: "(ID 1/27 [-3205])" Then the number -3205 is the error code that the Operating System reported. You could try to find a description of this error code, but unfortunately, the descriptions that Microsoft and Apple provide for their error codes are often unhelpful. If you contact Haxial, we may be able to guess what the Operating System is trying to tell you.
Not enough memory. Try closing some windows. (ID 2/101)This means that the program needed to use more memory to complete its current task, and it asked the Operating System to allocate it more memory, but the Operating System denied the request. The type of memory being referred to here is RAM, not hard disk. On MacOS 9, this error can occur even if the computer has sufficient RAM (because of the poor memory architecture in MacOS 9). All programs that run in MacOS 9 can potentially run into this error. The solution is to quit the program, then find the icon of the program file in the Finder, click once to select it, then click the "File" menu, then "Get Info", then "Memory" (alternatively you can control-click the icon). The Info window appears. Where it says "Preferred Size", you need to increase this number. The number is in kilobytes, so if you increased it by 1024, you would be adding an extra 1 megabyte of memory to the program. If your computer has plenty of RAM, you could even double the "Preferred Size" to make sure the program has plenty of memory available to it. You can also go the Apple menu, then "About This Computer" to see how much memory is allocated to each running program, and how much it is using (you can also turn on Balloon Help in the "Help" menu and move the mouse over the bars). On any Operating System other than MacOS 9, you are much less likely to see this error. If you do frequently encounter it, you could try buying more RAM for your computer.
WARNING: Damaged File SystemsOccasionally, someone reports a file system related error code that just does not make sense considering the circumstances. If this happens to you, try running a disk repair/verification utility on your hard disk. A few people have done this, the disk repair utility fixed problems in the file system, and then the error message / problem disappeared, indicating that the error was caused by a damaged file system.
Access denied because the file/folder is open. (ID 3/117)When a program opens a file (in order to read or modify it), it can prevent other programs from opening or modifying the file. Why would it want to do this? So that the 2 programs do not interfere with each other. For example, if the original program is expecting the file to remain unchanged, but another program comes along and changes the file behind its back, then this might cause problems for the first program because this sudden external change to the file was unexpected. You can usually solve this error by finding which other program has the same file opened, and either close the window in that program, or close the whole program. For example if you are trying to open a document that is already open in another program. If you cannot find which other program has the file open, then you could try restarting your computer.
Invalid file/folder name. (ID 3/118)This means that the operating system could not complete your request because the file or folder name that you were trying to use contains some characters/symbols that the operating system does not permit. The following characters are not permitted in file names in MS Windows:
The following characters are not permitted in file names in MacOS:
Access Denied by file system. (ID 3/119)Most operating systems support having access controls on individual files and/or folders, for example the ability to prevent certain users or programs from accessing a file/folder for security reasons. If you see this error message, it means that the program tried to access a file/folder, but the file system part of the operating system denied access. This might be because you are logged in to the computer as user X and you are trying to access files owned by user Y, and user Y has not granted access to user X. If this error occurs every time you try to download a file using KDX Client, then perhaps KDX has no access to your Downloads folder. Find the folder named "Downloads" which is located in the same folder as the KDX Client program, and then delete that folder or move it somewhere else, and create a new fresh folder named "Downloads" to replace it.
Maximum folder levels exceeded, check for an alias loop. (ID 3/121)When this happens, it is usually while cataloging the files on a disk. Cataloging involves looking inside a folder, and all folders inside that folder, and all folders inside those folders, and so on, until every folder and sub-folder has been inspected. If the cataloging process follows aliases/shortcuts/links to folders, then it is possible to arrange the aliases/shortcuts/links in such a way that a loop is formed. An alias loop is where if you keep following the folders, you will go around in circles forever. For example, folder A contains a folder B, which contains an alias C that points to folder A. Alias loops thus prevent cataloging from ever finishing. Instead of running forever, the program has alerted you to the situation with this error message. You must examine where you have used aliases/shortcuts/links in order to determine where you have created a loop, and then you must break it by deleting the offending alias/shortcut/link. If you cannot find the alias which is causing the problem, then try temporarily removing everything, and then add back some of the folders. Try again. If it works, then add back some more folders. Try again. If it still works, add back some more folders. By a process of elimination, you can find which alias/shortcut/link is causing the problem.
Invalid network address. (4/103)This means you tried to connect to a computer but the address you used is incorrect -- it is like you tried to post a letter to Santa Claus, 1 Christmas Lane, North Pole. It is simply wrong. Check whether you made a spelling/typing mistake. For example, if you try to connect to an address of xcnqwuic.com then you will see this error (at least the last time I checked, that's an incorrect address). If you are sure the address is correct and it did work previously, it is possible that there is a temporary internet fault or a problem with your internet connection. Check that your internet connection is working properly, or try again later.
Remote host terminated connection. (4/106)This means that there was an established connection between your computer and the remote/other computer (for transferring data), but the remote computer deliberately decided to terminate the connection. It is not possible for the Haxial program to determine the exact reason why the remote host terminated the connection -- only the remote host knows why it terminated the connection, and it usually does not say why unfortunately. But here are some reasons why you may see this error message:
Remote host refused connection. (ID 4/107)This means that the program contacted the remote/other computer, and asked for a connection (in order to transfer data), but was refused. It is not possible for the Haxial program to determine the exact reason why the remote host refused the connection -- only the remote host knows why it refused the connection, and it usually does not say why unfortunately. But here are some reasons why you may see this error message:
Connection timed out. (ID 4/108)There is a time limit on how long certain actions can take. If something takes too long, it is considered to have failed or "timed out". This is to stop you from waiting forever because if it has not worked by this time, it is most likely not going to work at all. If you see this error while trying to connect, then please see "Remote host refused connection. (ID 4/107)" above because the reasons for this error message are much the same. If you see this error sometime AFTER you have successfully connected, then here are some reasons why you may see this error message:
Connection aborted for unknown reason. (ID 4/109)This means that there was an established connection between your computer and the remote/other computer (for transferring data), but it was aborted/cancelled for a reason that the Haxial program is unable to determine because there is not enough information available to it. Here are some reasons why you may see this error message:
No route to remote host. (ID 4/111)This means that your computer is unable to send data to the remote/other computer, probably because you tried to connect using an incorrect address, or because of a temporary Internet fault. Please see "Remote host refused connection. (ID 4/107)" above because the reasons for this error message are much the same.
Incorrect login and/or password. (ID 4/112)A login and password is the standard method used on the Internet to securely identify and authenticate yourself to a server or service. Usually, you have an account somewhere, then before you can access it, you must enter the correct login and password. This prevents other unauthorized people from using your account, or impersonating you, or accessing your private information etc. Alternatively, you do not have a personal account, but nevertheless you are required to enter the correct login and password before you will be allowed to access the service. So this error message simply means that the login and/or password that you supplied was incorrect. For security reasons, you will not be told whether it was the password, or the login, or both that was incorrect. Here are some reasons why you may see this error message:
Please note that Haxial cannot tell you what the correct login and password is because Haxial does not have this information. Haxial is not the person or company who is running the server that you are trying to access. You will need to contact the administrator or owner of the server that you are trying to access, and ask them to tell you what login and password to use.
The network protocol is unknown. (ID 4/113)This means you tried to connect to another computer such as a server (or someone tried to connect to you) but the program that is running on the other computer is using a different protocol. A network protocol is a special procedure that allows 2 programs to communicate with each other. Programs can only communicate if they speak the same language/protocol, or at least understand each others protocol. The reason why you are getting this error is probably because the program on the other computer is a completely different program to the program that you are using, and thus your program cannot understand the other program (for example, if you tried to connect KDX to a Telnet program, rather than KDX to KDX). Alternatively, maybe it is the same program on the other computer, but it is an older or newer version of that program that is incompatible -- make sure you are using the same version of the program on both computers.
The protocol version of the remote host is too OLD. (ID 4/114)This happens when you use a program to connect to a computer running an older incompatible version of the program. Please update both computers to the most recent version of the software.
The protocol version of the remote host is more recent. (4/115)This happens when you use a program to connect to a computer running a newer incompatible version of the program. Please update both computers to the most recent version of the software.
Failed to open sound output. (5/101)The program attempted to open the sound/audio output in order to play some sound, but the Operating System refused to do it. Here are some reasons why this can happen:
Failed to open sound input. (5/102)The program attempted to open the sound/audio input in order to record some sound/audio, but the Operating System refused to do it. Here are some reasons why this can happen:
Cannot view display, maybe because no user is locally logged into the computer. (100/6)MS Windows: Unfortunately, we have so far not been able to discover how to capture the display when no user is locally logged into the computer. This problem also occurs when running KDX Server as a Windows Service (even if a user is logged in), and again we have not yet discovered how to make MS Windows allow the server to capture the display under these circumstances. (Sep2004)
|
