« 回到Technical Questions and Installation

[alogin-22] Login Error

組合檢視 平均檢視 瀏覽樹狀資料
相關串連 [ 前一個 | 下一個 ]
toggle
[alogin-22] Login Error
webinar installation faq
答覆
2017/7/11 下午 1:16
I used Adoxx three month ago for a projekt. Today i want to use this again, but this time there is a error when i login in. The error shows "A character set error has been detected with the selected database! ". I choosed the same database like i used before. Could you tell me, what should I do to solve this problem?

.
附件

附件: aloogin22.jpg (46.8k)

RE: [alogin-22] Login Error
答覆
2016/6/3 上午 8:33 作為回覆給匿名
The error message means that there is a mis-match between your non-unicode settings and the database collation used. The non-unicode setting of your "Language for non-Unicode programs" needs to be the same as the instance collation used for ADOxx. There are two possibilities to solve this problem:

a) Adapt the non-unicode settings to collation:
Please have a look at the collation of the database instance. By default, ADOxx creates a new instance called ADOXX15EN with collaction "Latin1_General_CS_AS". In the PCs control panel, you can switch from "Non-Latin" to a Latin codepage (e.g. English), performt the required restart and re-run the installation. The drawback of this approach is that ADOxx won't store "Non-Latin" characters properly.

b) Remove current instance installation and create a new instance ADOXX15EN with "Non-Latin" collation:
Alternatively, and in case you want to be able to enter "Non-Latin" characters properly, please remove the instance ADOXX15EN using the "Remove  software" functionality in the Control panel. After removal has completed, setup a database instance with "Non-Latin" collation manually using ADOXX15EN as an instance name and (detailed steps are available here:http://www.adoxx.org/live/installation-guide-15-other-collation) and re-run the ADOxx installation.

NOTE: If you go for solution (b), you will loose all the content of the SQL server instance ADOxx15EN (e.g. libraries, models, ...). Therefore if there are some work, which you want to save before than please perform first solution (a), do a backup, and switch to solution (b).