Différences

Ci-dessous, les différences entre deux révisions de la page.

--- fr:error [2014/08/21 18:52] – [Autres] zatalyz
+++ fr:error [2018/03/29 22:56] – /* ping/traceroute */ merlin8282
@@ Ligne 1: / Ligne 1: @@
 ====== Erreurs du client ======
-<WRAP center round todo 60%>
+<WRAP center round todo 90%>
-Page en gros brouillon moche et à traduire ! Les infos sont à vérifier, il y a eu des mises à jours je crois.. Voir aussi comment présenter ça pour faciliter la recherche et la résolution (le tableau n'est sans doute pas la bonne idée).
+Les infos sont à vérifier, il y a eu des mises à jours je crois..
-Chercher aussi sur RC, je crois qu'il y a aussi une page qui résume.
+Vérifier dans le code si certaines erreurs ne sont pas plus détaillées sur où ça coince ; là, dans les descriptions, la plupart sont similaires.
 </WRAP>
 Page tirée entre autre de [[http://forums.ryzom.com/showthread.php?t=14746]].
-Les erreurs côté client sont notées de 1 à 99. Celles côté serveur sont noté de 1000 à 4999. Donc : avant 99, vous pouvez agir !
+Les erreurs côté client sont notées de 1 à 99. Celles côté serveur sont théoriquement notées de 1000 à 4999. Dans la pratique, ça reste mélangé.
-^ Code Erreur ^ Description ^ Solution ^
+^Code^Message^Description^Solution^
-| Error Code 1 | Pas de connection au serveur | Vérifiez le firewall, que les ports soient ouverts OU Le fichier ''client_default.cfg'' pointe peut-être vers le mauvais serveur (mettre à jour) OU  |
+| 1 |  | Pas de connexion au serveur | Vérifiez le firewall, que les ports soient ouverts (voir [[#ports_a_ouvrir]]) |
-- Can also happen when there are network problems along the path, so check local network and try doing a ping plot or tracert to 91.121.164.170 & 91.121.160.110.
+|  |  |  | Le fichier client_default.cfg pointe peut-être vers le mauvais serveur (mettre à jour) |
-- Your client may be too old; check this thread if you have a doubt.
+|  |  |  | Can also happen when there are network problems along the path, so check local network and try doing a ping plot or tracert to (ip ?) |
+|  |  |  | Votre client est peut-être trop vieux, vérifiez sa version. |
+| 2 | player already connected | Le compte n'a pas été bien déconnecté (souvent dans le cas des plantages) | Attendre 30 secondes avant de tenter de se reconnecter. |
+| 3 | Your client is unable to reach the server. Please check your internet connection and/or your firewall. |  | Voir le code 1, si désactiver le pare-feu ne suffit pas |
+| 4 | Client received an empty answer |  |  |
+| 5 | Bad reception of shard listings | The list of shard received by the client is invalid. The number of rows is incorrect. | Côté serveur, contactez le support |
+| 6 | Bad reception of shard listings | The answer from the server is wrongly formatted on the (shard list separator) | Côté serveur, contactez le support |
+| 7 | cannot connect to the selected shard | Connexion internet instable, perdue entre le login et le chargement | Se connecter à nouveau ; vérifier l'état de sa connexion internet |
+| 8 | login field is empty | Le login reçu par le serveur est vide. Peut être dû au redémarrage du client. | Se connecter à nouveau ; vérifier l'état de sa connexion internet |
+| 9 | password field is empty | Le mot de passe reçu par le serveur est vide. Peut être dû au redémarrage du client. | Se connecter à nouveau ; vérifier l'état de sa connexion internet |
+| 10 | client is incorrect | the client does not fit to the server. Usually comes from a change in the cfg | Vérifiez les versions des fichiers .cfg |
+| 10 | no mainland shard available | Le serveur est fermé. Cela peut être du à un crash, une maintenance… | Suivez les news et allez sur IRC pour savoir ce qui se passe et quand le serveur sera de nouveau up |
+| 11 |  | Voir erreur 1 |  |
+| 12 |  | Voir erreur 1, parent of error code 61 |  |
+| 14 | Invalid reply from the server | Le cookie envoyé par le serveur n'est pas valide.  | Côté serveur, contactez le support |
+| 15 | you can't connect to an offline shard | Le serveur est fermé. Cela peut être du à un crash, une maintenance… | Suivez les news et allez sur IRC pour savoir ce qui se passe et quand le serveur sera de nouveau up |
+| 20 | Failure in sending to the server the request HTTP GET StartupPage?command=ask&login=login | Échoue à envoyer les informations | Vérifier votre connexion internet, recommencez, demandez de l'aide si ça se reproduit. |
+| 29 | Cannot create the batch file for restart of client | Client is unsuccessful in creating the batch file (UpdateBatchFilename in the cfg) in order for the client to restart | Problème de patch ; lié à windows ? Sans doute obsolète. |
+| 30 |  | Cannot launch the batch process before client is closed | Laissez le temps au client de patcher ? |
+| 31 | Cannot decompress a patched file | Cannot decompress a patched file in order to apply it. | Problème de patch. Vérifiez qu'il reste de la place sur le disque dur et que l'application a les droits en écriture. |
+| 32 |  | During decompression of a patched file, cannot create it on the hard drive | Vérifiez qu'il reste de la place sur le disque dur et que l'application a les droits en écriture. |
+| 33 |  | Failure during decompression of a dowloaded patch file. | Relancer le patch, peut-être en ayant effacé le précédent fichier de patch ? |
+| 34 |  | During the decompression process, cannot write the file on the hard drive | Problème de patch. Vérifiez qu'il reste de la place sur le disque dur et que l'application a les droits en écriture. |
+| 36 | The launcher is out of date and won't allow to download the patch | Vous utilisez une version trop ancienne qui n'arrive pas à patcher | Téléchargez et installez le dernier client |
+| 37 | Cannot write a downloaded patch file | Impossible d'écrire le fichier du patch sur le disque dur. | Vérifiez qu'il reste de la place sur le disque dur et que l'application a les droits en écriture. |
+| 41 | Login Server is down | Un des éléments du serveur (service de login) est tombé | Contactez le support |
+| 52 | unknown login | Le login utilisé n'est pas enregistré dans la base de donnée | Vérifiez le login ou créez un compte |
+| 53 | not authorised to use the shard | Pas les bons droits pour se connecter ; souvent lié à des comptes désabonnés ou qui ne sont pas activés | Vérifiez le statut de votre compte (abonné/activé/lié au bon serveur), réabonnez-vous au besoin.  |
+| 55 | the player is already online and can't be disconnected | Voir erreur 2 ; contacter le support si le problème persiste |  |
+| 56 | bad password | Mauvais mot de passe | Vérifiez la saisie |
+|  |  |  | Sur certains serveurs/client, un bug limite le mot de passe à 8 caractères, uniquement alphanumériques (pas d'accents ni de symboles) |
+|  |  |  | Demandez la réinitialisation du mot de passe si nécessaire |
+| 60 | Your client is unable to reach the server. Please check your internet connection and/or your firewall.  | Voir erreur 1 | Vérifiez aussi que vous avez créé un compte (via l'interface web et pas le client) |
+| 61 | No answer from the server to the client from the request | Voir erreur 1 ; vérifier le pare-feu en priorité |  |
+| 62 | empty answer | Peut venir d'un joueur tentant de se connecter au mauvais serveur par rapport à son client (exemple : client Khanat pour se co sur Ryzom) | Vérifiez le client utilisé et le serveur auquel il cherche à se connecter |
+| 63 | Your client is unable to reach the server. Please check your internet connection and/or your firewall.  | Voir erreur 1 ; vérifier le pare-feu en priorité |  |
+| 64 | unknown login | Voir erreur 52 |  |
+|  |  |  |  |
+| 1000 | Unexpected error |  |  |
+| 2001 | There is no such login in the database |  |  |
+| 2002 | There is a matching login but the activation link has not been clicked yet |  |  |
+| 2003 | There is a matching login but the activation link has not been clicked yet |  |  |
+| 2004 | The password you have entered is not valid. Please retype it or contact a CSR. |  |  |
+| 2101 | Database consistency problem: user found in 'user' but not in 'ring_users' |  |  |
+| 3001 | Unexpected error |  |  |
+| 3002 | The client did not submit the required arguments |  |  |
+| 3003 | The Shard Unifier is down or does not reply |  |  |
+| 3004 | The DB server is down or misconfigured, or r2_login is misconfigured |  |  |
+| 3005 | The DB server or r2_login is misconfigured |  |  |
+| 3006 | The DB server or r2_login is misconfigured |  |  |
+| 3007 | There is no registered domain corresponding to the clientApplication |  |  |
+| 3011 | Either the account is no more subscribed, or the client tries to connect to a domain not granted to this account |  |  |
+| 3013 | Access is restricted at the moment (for example during a patch) |  |  |
+| 4001 | Technical problem on SU or WS |  |  |
+| 4002 | Technical problem on SU or WS |  |  |
+| 4003 | Technical problem on SU or WS |  |  |
+| 4004 | Technical problem on SU or WS |  |  |
+| 4005 | Randomly selected mainland shard is not reachable |  |  |
+| 4006 | Technical problem on SU or WS |  |  |
+| 4007 | Technical problem on SU or WS |  |  |
+| 4008 | Technical problem on SU or WS |  |  |
+| 4009 | Technical problem on SU or WS |  |  |
+| 4010 | No mainland shard available at the moment, or the user does not have privileges to connect to any mainland shard (ex: no rights on ATS) |  |  |
+| 4011 | Technical problem on SU or WS |  |  |
+| 4012 | Technical problem on SU or WS |  |  |
+| 4013 | Technical problem on SU or WS |  |  |
+| 4014 | Access is restricted at the moment (welcome service closed) |  |  |
+| 4015 | Technical problem on SU or WS |  |  |
+| 4016 | Technical problem on SU or WS |  |  |
+| 4017 | Technical problem on SU or WS |  |  |
+| 4018 | Technical problem on SU or WS |  |  |
+| 4019 | Technical problem on SU or WS |  |  |
+| 4020 | Technical problem on SU or WS |  |  |
-Error Code 2 - player already connected
+===== Messages d'erreurs sans code =====
-- Wait for 30 seconds then try logging in again.
+  * //Échec de la connexion, Si vous venez de quitter Khanat, veuillez patienter 30 secondes// : Si 30 secondes ne changent rien, vérifier que les [[fr:error?s[]=ports#ports_a_ouvrir|ports du parefeu local]] soient ouverts.
-Error code 3
+===== Autres =====
-Your client is unable to reach the server. Please check your internet connection and/or your firewall. ((Faut plus d'infos, à chercher))
+Vieilles résolutions, sans doute obsolète...
-error code 4
+To run Ryzom on windowed mode, the desktop must be set to 32 bit mode
-Client received an empty answer
+or
+Can't create a window display (1024x768 32 bits)
+- Check windows display settings and set desktop to at least 1024x768 resolution with 32 bits colour depth and that Direct3D or OpenGL are enabled.
+- You can also get this message if the computer does not have adequate video hardware (onboard video chips like SiS or Intel are prime examples of video systems that cannot run Ryzom).
+- NOTE: you can try to launch the game in 800x600 resolution but will not be able to see all the buttons as the launcher screens require at least 1024x768.
+- Detailed information here.
-Error Code 7 - cannot connect to the selected shard
+nel_drv_opengl_win_rd.dll is more recent than the application
-- You lost internet connection between the login/pw screen and the shard selection screen.
+- The video drivers may be too old for Ryzom to work with properly: obtain newer video drivers and install properly (remove current, reboot, run driver installer).
-- Try logging in again.
+- Or the launcher files may be too old for Ryzom to patch properly: delete UNPACK folder, run ryzom_recover.exe and then launch game again. Warning! At this time ryzom_recover.exe will render your game installation unusable, this will require you to redownload and re-install Ryzom. Do Not run ryzom_recover.exe until further notice.
-Error Code 10 - no mainland shard available
+Microsoft Visual C++ Runtime Library - Runtime Error
-- The shard is closed. This can be due to a maintenance reboot, patch day, or server crash.
+- Again, make sure that your desktop resolution is at least 1024x768 with 32 bit colour depth.
-- Go to Klients live support for up to date information, check also the Ryzom news and technical forum.
+- Make sure that your system is virus and spyware free. They can corrupt or interfere with executable files.
+- Everything that I can find on this and some experience by players with this error indicates a damaged IE install. Fixing IE or removing some of the extras usually will fix this error. In worst case the OS has to be reinstalled as IE is integrated into WinXP. Check out the Microsoft Knowledgebase article 318378 on how to repair Internet Explorer.
-Error Code 53 - not authorised to use the shard
+Error -1607: Unable to Install InstallShield Scripting Runtime
-- Check your billing status on the Account Management page to ensure that subscription is current.
+- Please visit the InstallShield site to diagnose and repair this problem.
-- If you can't manage to subscribe, contact the support staff on Klients, boards or by email.
-Error Code 56 - bad password
+Error patching files...
-- Check password spelling.
+- Delete the UNPACK folder and launch the game again.
-- If you subscribed before 2007, January 9, and changed your billing password since then, your game password became the same as the billing one as both accounts now use the same password. You may have to get a new billing password here and then change it in your profile if you forgot it.
-error code 60
+msg.xml and database.xml files are invalid (server version signature is different)
-Your client is unable to reach the server. Please check your internet connection and/or your firewall.
+- Delete the data_common.bnp file found in the DATA folder and then relaunch.
-error code 61
+==== Ports à ouvrir ====
-Your client is unable to reach the server. Please check your internet connection and/or your firewall.
+Tiré de [[http://forums.ryzom.com/showthread.php?p=78597#post78597|l'ancien forum Ryzom]] (nous n'avons pas forcément besoin de tout ça) :
-error code 62
+  * UDP 47851 to 47860 (game)
-Client received an empty answer
+  * TCP 80 (support)
+  * TCP 443 (account creation from launcher)
+  * TCP 40916 (login/patch)
+  * TCP 43434 (patch)
+  * TCP 48851 to 48860 (Ring)
+  * TCP 50000 (forum)
-error code 63
+Au 9 mars 2018, voici les ports à ouvrir côté firewall si vous avez configuré ce dernier dans une optique très sécurisée (ne rien laisser entrer et sortir en dehors des ports explicitement autorisés) :
-Your client is unable to reach the server. Please check your internet connection and/or your firewall.
+  * TCP 80 (trafic internet de base)
+  * TCP 443 (trafic internet sécurisé)
+  * TCP 50000 (lié aux "stats", probablement pas très utile à ce stade mais bon, il le faut pour que ça marche)
+  * TCP 43435 (serveur de jeu)
+  * TCP 40916 (login/patch)
-Error Code 64 - unknown login
-- Check login name spelling.
-Error - no response from shard unifier, try later
-- The shard is locked. Happens after a server reboot. The shard stays temporarily locked while we check everything is alright before reopening it.
-- Go to Klients live support for up to date information, check also the Ryzom news and technical forum.
-error code 1000
+==== Diagnostic ====
-Unexpected error
+=== ping, traceroute ===
+Dans un premier temps, on peut chercher à savoir si notre ordinateur parvient à joindre le serveur :
-error code 2001
+  ping lirria.khaganat.net
-There is no such login in the database
-error code 2002
+Résultat concluant :
-There is a matching login but the activation link has not been clicked yet
-error code 2003
+  PING lirria.khaganat.net (91.121.106.70) 56(84) bytes of data.
-There is a matching login but the activation link has not been clicked yet
+bytes from ns349745.ip-91-121-106.eu (91.121.106.70): icmp_seq=1 ttl=48 time=40.3 ms
+bytes from ns349745.ip-91-121-106.eu (91.121.106.70): icmp_seq=2 ttl=48 time=41.8 ms
+bytes from ns349745.ip-91-121-106.eu (91.121.106.70): icmp_seq=3 ttl=48 time=41.6 ms
+bytes from ns349745.ip-91-121-106.eu (91.121.106.70): icmp_seq=4 ttl=48 time=41.0 ms
+  --- lirria.khaganat.net ping statistics ---
+packets transmitted, 4 received, 0% packet loss, time 3004ms
+  rtt min/avg/max/mdev = 40.356/41.237/41.818/0.594 ms
-error code 2004
+En cas d'erreur (i.e. "le serveur n'est pas joignable") :
-The password you have entered is not valid. Please retype it or contact a CSR.
-error code 2101
+  PING lirria.khaganat.net (91.121.106.70) 56(84) bytes of data.
-Database consistency problem: user found in 'user' but not in 'ring_users'
+  --- lirria.khaganat.net ping statistics ---
+packets transmitted, 0 received, 100% packet loss, time 3078ms
-error code 2102
-You already have a character logged in. Please retry connecting later
-error code 3001
+Dans ce cas on peut essayer de voir à quel niveau cela coince, sur le réseau, avec la commande traceroute :
-Unexpected error
-error code 3002
+  traceroute lirria.khaganat.net
-The client did not submit the required arguments
-error code 3003
+Si la dernière ligne contient l'adresse IP de lirria.khaganat.net (91.121.106.70 au 29 mars 2018), c'est tout bon. Sinon, traceroute n'affiche plus que des lignes avec 3 étoiles ''* * *'' : un élément du réseau pose souci et le lien ne peut être établi.
-The Shard Unifier is down or does not reply
-error code 3004
-The DB server is down or misconfigured, or r2_login is misconfigured
-error code 3005
-The DB server or r2_login is misconfigured
-error code 3006
+=== Vérifier si les ports sont bien ouverts ===
-The DB server or r2_login is misconfigured
+Vous avez bien ouvert les ports de votre firewall, mais ça ne fonctionne toujours pas ? Il se peut qu'il y ait d'autres problèmes. Le plus simple est alors de vérifier si l'on peut ouvrir une connexion sur les ports TCP sus-cités, ou en termes plus simple voir si sa machine peut communiquer avec le serveur. En fonction du système d'exploitation il y a différentes méthodes :
-error code 3007
+== GNU/Linux ==
-There is no registered domain corresponding to the clientApplication
+On peut installer ''netcat'' si ce n'est pas déjà fait, et tenter d'ouvrir une connexion TCP sur les ports dont on a besoin :
-error code 3011
+  nc -vz lirria.khaganat.net 80 443 40916 43435 50000
-Either the account is no more subscribed, or the client tries to connect to a domain not granted to this account
-error code 3013
+En cas de succès, voilà à quoi cela ressemble :
-Access is restricted at the moment (for example during a patch)
-error code 4001
+  Connection to lirria.khaganat.net 80 port [tcp/http] succeeded!
-Technical problem on SU or WS
-error code 4002
+Sinon, on obtient un message d'erreur :
-Technical problem on SU or WS
-error code 4003
+  nc: connect to lirria.khaganat.net port 80 (tcp) failed: Connection refused
-Technical problem on SU or WS
-error code 4004
+Le message peut varier, en fonction de l'erreur. Il peut être affiché au bout d'un certain temps ("timeout" ou "délai d'attente") quand aucune réponse n'a été reçue.
-Technical problem on SU or WS
-error code 4005
-Randomly selected mainland shard is not reachable
-error code 4006
+== GNU/Linux et windows (peut-être aussi MacOS ?) ==
-Technical problem on SU or WS
+Si on n'a pas envie ou pas la possibilité d'installer netcat, on peut aussi utiliser ''telnet'' à la place :
-error code 4007
+  telnet lirria.khaganat.net 80
-Technical problem on SU or WS
+  telnet lirria.khaganat.net 443
+  telnet lirria.khaganat.net 40916
+  telnet lirria.khaganat.net 43435
+  telnet lirria.khaganat.net 50000
-error code 4008
+Si la connexion TCP est établie cela ressemble à ceci :
-Technical problem on SU or WS
-error code 4009
+  Trying 91.121.106.70...
-Technical problem on SU or WS
+  Connected to lirria.khaganat.net.
+  Escape character is '^]'.
-error code 4010
+Pour sortir il faut taper les trois touches ''Ctrl + AltGr + ]''
-No mainland shard available at the moment, or the user does not have privileges to connect to any mainland shard (ex: no rights on ATS)
-error code 4011
+Sinon en cas d'erreur, on obtient... un message d'erreur (qui peut varier en fonction du système d'exploitation) :
-Technical problem on SU or WS
-error code 4012
+  Trying 91.121.106.70...
-Technical problem on SU or WS
+  telnet: Unable to connect to remote host: Connection refused
-error code 4013
-Technical problem on SU or WS
-error code 4014
-Access is restricted at the moment (welcome service closed)
-error code 4015
-Technical problem on SU or WS
-error code 4016
-Technical problem on SU or WS
-error code 4017
-Technical problem on SU or WS
-error code 4018
-Technical problem on SU or WS
-error code 4019
-Technical problem on SU or WS
-error code 4020
-Technical problem on SU or WS
-===== Autre copie à comparer =====
-LOGIN RELATED
-Error code 1, 2, 3, 4, 60, 63
-Description: Cannot connect to the web server with data as set up in the StartupHost (port 80)
-Explanation: player do not have internet access, or the connection is blocked by a firewall. often happens when player has a firewall.
-Those 6 error code are the same but at various level of the problem.
-Error code 20
-Description:
-Explanation: Failure in sending to the server the request HTTP GET StartupPage?command=ask&login=login
-Error code 36
-Description:
-Explanation: The launcher is out of date and won't allow to download the patch
-Error code 41
-Description:
-Explanation: Login Server is down, contact Nevrax
-Error code 52
-Description: unknown login
-Explanation: the login of the user is not in the database which grant access to servers
-Error code 55
-Description:
-Explanation: the player is already online and can't be disconnected
-Error code 56
-Description: bad password
-Explanation: the player has entered an invalid password for the login he provided
-Error code 61
-Description: No answer from the server to the client from the request
-Explanation: prolly comes from a firewall
-Error code 62
-Description: empty answer
-Explanation: can be the result of a player trying to connect to the wrong for server for the client he uses
-SHARD LISTING
-Error code 5
-Description: Bad reception of shard listings
-Explanation: The list of shard received by the client is invalid. The number of rows is incorrect.
-Error code 6
-Description: Bad reception of shard listings
-Explanation: The answer from the server is wrongly formatted on the | (shard list separator)
-SHARD CONNEXION
-Error code 7
-Description: Cannot connect to the selected shard
-Explanation: The player has lost internet connection between the login/pw screen and the shard selection screen
-Error code 8
-Description: login field is empty
-Explanation: the login the server received is empty, prolly due to restart of client
-Error code 9
-Description: password field is empty
-Explanation: the password the server received is empty, prolly due to restart of client
-Error code 10
-Description : client is incorrect
-Explanation : the client does not fit to the server. Usually comes from a change in the cfg
-Error code 11
-Description : same as error code 60
-Explanation : request GET StartupPage?cmd=login&shardid=id&login=login&password=cryptedPass&clientApplication=app&cp=1
-Error code 12
-Description: same as error code 61
-Explanation: parent of error code 61
-Error code 14
-Description: Invalid reply from the server
-Explanation: Cookie sent by the server to client is invalid
-Error code 15
-Description: you can't connect to an offline shard
-Explanation: the user tried to connect to an offline shard
-Error code 53
-Description:
-Explanation: the account of the player is Unsubscribed. Needs to activate the account in order to log in. (former explanation: the player is using the wrong client for the server he is trying to connect to)
-PATCH
-Error code 29
-Description : Cannot create the batch file for restart of client
-Explanation : Client is unsuccessful in creating the batch file (UpdateBatchFilename in the cfg) in order for the client to restart
-Error code 30
-Description :
-Explanation : Cannot launch the batch process before client is closed
-Error code 37
-Description : Cannot write a downloaded patch file
-Explanation : Client cannot write on hard drive a file from the patch. Prolly due to a full hard drive
-Error code 31
-Description : Cannot decompress a patched file
-Explanation : Cannot decompress a patched file in order to apply it.
-Error code 32
-Description :
-Explanation : During decompression of a patched file, cannot create it on the hard drive
-Error code 33
-Description :
-Explanation : Failure during decompression of a dowloaded patch file.
-Error code 34
-Description :
-Explanation : During the decompression process, cannot write the file on the hard drive
-===== Autres =====
-To run Ryzom on windowed mode, the desktop must be set to 32 bit mode
-or
-Can't create a window display (1024x768 32 bits)
-- Check windows display settings and set desktop to at least 1024x768 resolution with 32 bits colour depth and that Direct3D or OpenGL are enabled.
-- You can also get this message if the computer does not have adequate video hardware (onboard video chips like SiS or Intel are prime examples of video systems that cannot run Ryzom).
-- NOTE: you can try to launch the game in 800x600 resolution but will not be able to see all the buttons as the launcher screens require at least 1024x768.
-- Detailed information here.
-nel_drv_opengl_win_rd.dll is more recent than the application
-- The video drivers may be too old for Ryzom to work with properly: obtain newer video drivers and install properly (remove current, reboot, run driver installer).
-- Or the launcher files may be too old for Ryzom to patch properly: delete UNPACK folder, run ryzom_recover.exe and then launch game again. Warning! At this time ryzom_recover.exe will render your game installation unusable, this will require you to redownload and re-install Ryzom. Do Not run ryzom_recover.exe until further notice.
-Microsoft Visual C++ Runtime Library - Runtime Error
-- Again, make sure that your desktop resolution is at least 1024x768 with 32 bit colour depth.
-- Make sure that your system is virus and spyware free. They can corrupt or interfere with executable files.
-- Everything that I can find on this and some experience by players with this error indicates a damaged IE install. Fixing IE or removing some of the extras usually will fix this error. In worst case the OS has to be reinstalled as IE is integrated into WinXP. Check out the Microsoft Knowledgebase article 318378 on how to repair Internet Explorer.
-Error -1607: Unable to Install InstallShield Scripting Runtime
-- Please visit the InstallShield site to diagnose and repair this problem.
-Error patching files...
-- Delete the UNPACK folder and launch the game again.
-msg.xml and database.xml files are invalid (server version signature is different)
-- Delete the data_common.bnp file found in the DATA folder and then relaunch.
 {{tag>Bug Brouillon}}