Invalid column name 'IBVERSION'

This forum is intended for cases when a problem can not be solved due to restrictions of the platform: a bug or lack of functionality.

#1
People who like this:0Yes/0No
Just came
Rating: 1
Joined: Nov 5, 2011
Company: DND Yazılım

When creating a new database on 1C:Enterprise 8.2.17.xxx version or When switching from an older version to a version higher 8.2.17.xxx; We got the following error;

"Microsoft OLE DB Provider for SQL Server: Invalid column name 'IBVERSION', HRESULT=80040E14, HRESULT=80040E14, SQLSrvr:SQLSTATE=42522, state=1, Severity=10, native=207, line=1 SQLSrvr:SQLSTATE=42522, state=1, Severity=10, native=207, line=1"

 
#2
People who like this:0Yes/0No
Just came
Rating: 0
Joined: Apr 20, 2013
Company:

Try latest 8.2.18.x

 
#3
People who like this:0Yes/0No
Just came
Rating: 1
Joined: Nov 5, 2011
Company: DND Yazılım

We already tried 8.2.18.xxx but still same error.

 
#4
People who like this:0Yes/0No
Timofey Bugaevsky
Guest

Joined:
Company:

Which versions of MS SQL Server and 1C:Enterprise do you use?
To reproduce an error please prepare an infobase without of sensitive data to our developers.

 
#5
People who like this:0Yes/0No
Just came
Rating: 1
Joined: Nov 5, 2011
Company: DND Yazılım

Microsoft SQL Server 2008 Enterprise Edition (64-bit)
Version 10.50.1777.0
Server Collation Turkish_CI_AS

 
#6
People who like this:0Yes/0No
Active user
Rating: 4
Joined: Nov 19, 2012
Company:

(5) I found this bug in version 8.2.17 and 8.2.18 in the list of planned for the correction.
May be it's your situation?

Quote
20012669 Creation of the information base in Client/server mode. The problem is:
If table in master database MSSQL established case-sensitive locale (for example, Cyrillic_General_CS_AS), then when you create the information base error occurs "Invalid column name 'IBVERSION'".
Date of publication:
2012-12-25

I don't know how you can work around this.
Try to check the collation in MS SQL for whole server and system databases. If it's not correct, I think, you must reinstall MSSQL.

Download 1.png (24.81 KB)
Edited: Aleksey Bochkov - Jun 25, 2015 05:10 AM
 
#7
People who like this:0Yes/0No
Interested
Rating: 27
Joined: Apr 5, 2012
Company: 1TÇ Şirketi - Merv Bilgi İşlem Otomasyonu Yazılım Ltd. Şti.

Emre I had such problem too. u can pass over this problem like that.
1. do not configure your sql for  Collation Turkish_CI_AS. Let it be
2. create empty infobase by tools of platform with usual settings (for sql is Language (Country) - English (United States)). It will create easily.
3. open in designer mode.
4. restore your dumped database. And collation settings will automatcally change.

Thats all. ))

in turkish click here.

Edited: Murat Yazlıyev - Apr 29, 2013 01:44 PM
 
#8
People who like this:0Yes/0No
Timofey Bugaevsky
Guest

Joined:
Company:

This error was fixed in the upcoming 8.3.3 release of 1C:Enterprise platform.
It occurs when the collation is used where IBVersion and IBVERSION are equal, for example in Cyrillic_General_CI_AS.
The workaround is to create a database in DBMS with the desired collation manually, after that the 1C:Enterprise platform should use this database to create an infobase.

 
#9
People who like this:0Yes/0No
Just came
Rating: 1
Joined: Nov 5, 2011
Company: DND Yazılım

Thank you for your help. Will be waiting to see in 8.3.3

 
Subscribe
Users browsing this topic (guests: 1, registered: 0, hidden: 0)
Be the first to know tips & tricks on business application development!

A confirmation e-mail has been sent to the e-mail address you provided .

Click the link in the e-mail to confirm and activate the subscription.