The sort order set for databases is different from the system one. Database error “The sort order is different from the system one”: how to fix it? 1c sql sort order is different from the system one
There are times when the program cannot be launched 1C, and a window appears 1C with a message "The sort order set for the database is different from !".
After closing the window, the program closes (you can run it in the mode Configurator).
Cause of error and solutions
Reason for error – mismatch between settings and settings 1C.
By the way, if the operating system is localized and the regional settings are set correctly, then during installation 1C its settings will be brought into line with .
Checking the settings are correct
I. settings(for localized Russified version Windows)
1. Open Start – > Settings –> Control Panel –> language and regional standards.
2. On the tab Regional settings there should be in the dropdown list – Russian.
3. On the tab Languages – > More details… – window Text input languages and services –> tab Options – > Input language there must be – > Russian-Russian.
4. On the tab Additionally there must be –> Russian.
II. 1C settings
1. Launch the program 1C. In the window Launch 1C
2. In the dropdown list In mode select Configurator –> OK.
3. Start Configurator. Select menu Administration –> Code page of information security tables…
4. In the window there should be in the dropdown list –> 1251 – > Russian, Belarusian, Bulgarian and Serbian languages.
Notes
1. If you use the component (distributed infobase management), – when disabling sort order checking, – You SHOULD NOT use characters from any alphabets other than Latin in the three-letter identifier of infobases that are part of a distributed database.
2. Be aware that disabling sort order identity checking may result in unexpected – for the 1C program! – the order of lines, for example, when generating reports.
Fixing the error in Windows Vista and Windows 7+
If you use Windows Vista And Windows 7+ , then get rid of the message "The sort order set for the database is different from the system one!" the above methods will not work.
You'll have to go another way:
1. Launch the program 1C. In the window Launch 1C select the required information base.
2. In the dropdown list In mode select Configurator – >OK.
3. Start Configurator. Select menu Administration – > Code page of information security tables…
4. In the window Code page of infobase tables select from the drop-down list + Current installation – >OK.
You recently bought a new computer, installed 1C:Enterprise 7.7, transferred the database from the old computer, and your expectations for more comfortable work were overshadowed by the inscription on the screen:
This error occurs when the NT6 and 1C code tables do not match. There are 2 main ways to solve this problem.
1. If you work locally, on one computer and you do not need to periodically transfer the database to other computers, then the easiest way is to change the code page of the infobase, as shown in the figure below.
To do this, launch 1C:Enterprise in configurator mode, then select the item “ Administration» - « IS code page" And in the window that opens, select from the list, at the very bottom “ +Current system installation " and click " OK».
We wait for re-indexing, close the configurator and you can continue working, your data will not change or be lost.
2. This method should be used if in 1C:Enterprise 7.7. work on a network, and also use different versions of Windows (for example, Windows XP and Windows 7), or you work with one database on different computers, for example, at home and in the office, in the case where the database is located on removable media.
The solution is also quite simple, you need to create a file “ ordnochk.prm"in any editor, for example in the same notepad. This file may be empty or may contain the line “Hello”, in this case it does not matter, the main thing is the correct file name.
It must be placed in the root folder with 1C:Enterprise installed (by default it is “ C:\Program Files\1Cv77\BIN\"). This file will disable sort checking.
If you have a network version and 1C:Enterprise is installed on each computer, then you need to place this file on each one, this is important.
That's it, enjoy your work.
Despite the reluctance of corporate users to say goodbye to Windows XP, it is becoming obvious that this will still have to be done in the near future. Therefore, there will be a need to run 1C Enterprise 7.7 in a Windows 7 (Vista) environment. In this article, we decided to look at “typical” problems that arise when working with 1C in a new OS environment, and ways to solve them.
Error: "The data sort order is different from the system one"
Only the lazy probably don’t know about this error, as well as the way to solve it. However, not everything is as simple as it seems, so let’s look at this issue in more detail.
The reason for the error is trivial - a mismatch between the code pages of the NT6 and 1C family of operating systems. There are two ways to solve this problem:
- Bring the information security code page into line with the system one. To do this we launch Configurator - Administration - IB code page and at the very bottom of the drop-down list select + Current system installation. This is the most correct way, but having brought the database into compliance with the Windows 7 (Vista) code page, we will begin to receive the same error when launching the database in Windows XP.
- Disable sort order checking. To do this, create a signal file with the name ordnochk.prm(). Being placed in a directory with information security, it disables checking the sort order for this database when placing it in the directory BIN(in the 1C installation folder) sorting check will be disabled for all databases on this PC. This method works only with release 26 and higher. In addition, 1C warns:
"The use of this feature can be recommended only in extreme cases, when it is not possible to coordinate the system sort order with the sort order set for the infobase. When disabling sort order checking in the application conditions, distributed infobase management components SHOULD NOT use characters of any alphabets except Latin, in the three-letter identifier of the information bases that are part of the distributed one. It should be borne in mind that 1C:Enterprise uses the sorting capabilities of both mechanisms when working, and disabling the order identity check in them can lead to an unexpected row order for the user, for example, when generating reports."
Which method should you choose? If you have a homogeneous OS fleet, i.e. All machines run Windows 7 (Vista), then you should definitely use the first option. The second option should be used if it is necessary to simultaneously work with databases under both OS families. In this case, it is advisable to locate the databases on a machine with Windows XP, and ordnochk.prm place it in the BIN folder on a machine with Windows 7 (Vista). This will allow you to avoid potential problems with the operation of such components as the URIB. Please remember that a machine running Windows 7 (Vista) can be used only for working in 1C Enterprise mode. Any changes in the Configurator mode must be made only on a machine with Windows XP. When locating databases on a machine with Windows 7 (Vista) Necessarily the information security code page should be converted to the system one (according to the first method), and ordnochk.prm use already on machines with Windows XP, otherwise working with URIB or simply loading previously uploaded data into the information security will be impossible.
Error when creating from component V7Plus.dll (CLSID is missing)
This problem occurs when UAC is enabled, when accessing external processing or other actions that require a library V7Plus.dll(uploading data, reports, etc.), while V7Plus.dll present in the directory with the database. The reason for the error is that 1C Enterprise registers this library dynamically when the need for use arises. When UAC is enabled, 1C works with user rights and therefore cannot register the library. The solution is simple - register V7Plus.dll manually, for this we recommend copying it to the BIN folder (so as not to be tied to a specific database), run Command line with administrator rights and run the command:
Regsvr32<путь к 1С>\BIN\V7Plus.dll
the result of execution should be a message about successful library registration.
Error "To access the database, an ODBC driver for MS SQL Server version 3.50.0303 or older is required
The error occurs when you try to run SQL version 1C Enterprise 7.7 on Windows 7 (Vista) and is due to the lack of support by these operating systems for versions of SQL server lower SQL Server 2005 SP2. Excerpt from the official Microsoft press release:
For enhanced security, Microsoft Windows Server 2008 and Microsoft Windows Vista operating systems will support SQL Server 2005 Express SP1, and all other editions of SQL Server will require SQL Server 2005 SP2. or later. Earlier versions of SQL Server, including SQL Server 2000(all editions including Desktop Engine, also known as MSDE), SQL Server 7.0 and SQL Server 6.5, Windows Server 2008 and Windows Vista operating systems will not be supported.
Solutions for today does not exist(and it is unlikely to appear). The “solution” found on the Internet involving replacing ODBC driver files with files from Windows XP should not be seriously considered and its use is strictly not recommended.
As an alternative, we recommend running 1C Enterprise on Windows Server 2003 in terminal mode; we also recommend the same option for 1C file mode on a network with different versions of Windows.
1C: what to do if the message “The sort order set for the database differs from the system one!” appears
The cause of the error is a mismatch between the system settings and the 1C settings.
By the way, if the operating system is localized and the regional settings are set correctly, then when installing 1C its settings will be brought into line with the system ones.
Checking the settings are correct
I. System settings (for localized Russified version of Windows)
1. Open Start - Settings - Control Panel - Regional and Language Options.
2. On the Regional Settings tab, the drop-down list should be Russian.
3. On the Languages tab – More details... – Languages and text input services dialog box – Options tab – The default input language should be Russian-Russian.
4. On the Advanced tab there should be – Russian.
II. 1C settings
2. In the drop-down list In mode, select – OK.
4. In the Code page of infobase tables window, the drop-down list should contain – 1251 – Russian, Belarusian, Bulgarian and Serbian languages.
Notes
1. If you are using the DIMB component (distributed infobase management), - when sort order checking is disabled - you SHOULD NOT use characters of any alphabets other than Latin in the three-letter identifier of infobases included in the distributed database.
2. It should be borne in mind that disabling the sort order identity check can lead to unexpected results - for the user of the 1C program! – the order of lines, for example, when generating reports.
Troubleshooting Windows Vista
If you are using Windows Vista, then get rid of the message “The sort order set for the database is different from the system one!” the above methods will not work.
For this:
1. Launch the 1C program. In the Launch 1C window, select the desired information base.
2. In the drop-down list In mode, select Configurator – OK.
3. The Configurator will launch. Select menu Administration – Code page of information security tables...
4. In the Code page of infobase tables window, in the drop-down list, select + Current system installation – OK.
5. In the Configurator window with the message “When changing the code page, the indexes of all infobase data tables will be rebuilt! Do you want to change the code page?" click Yes.
6. After a certain period of time, depending on the size of the information security, the Configurator window will appear with the message “Code page has been changed!”, click OK.
7. Close the Configurator, you can work with the infobase.
8. To work with other information security systems, change the code page of information security tables in the same way.
