Resources For IT Professionals
Post an article
Wikis - Page Details
  • First published by (8Microsoft Partne)
  • When: 29 Aug 2013 12:36 AM
  • Last revision by (aMicrosof)
  • When: 4 Sep 2013 7:12 PM
  • Revisions: 6
  • Comments: 3
Options
RSSSubscribe to Article (RSS)
Can You Improve This Article?
Positively! Click Sign In to add the tip, solution, correction or comment that will help other users.

Report inappropriate content using these instructions.
Wiki  >  TechNet Articles  >  BizTalk 2013: Installation and Configuration Error (Invalid Column id)

BizTalk 2013: Installation and Configuration Error (Invalid Column id)

BizTalk 2013: Installation and Configuration Error (Invalid Column id)

I just have faced an interesting error while configuring new BizTalk 2013 in the test environment. Actually it is not a complicated environment, it has BizTalk 2013 Enterprise edition on Windows 2012 Server and SQL Server 2012 on the same machine.
While configuring feature the Group I got this error:

SQL script file: "C:\Program Files (x86)\Microsoft BizTalk Server 2013\Schema\\BTS_Administration_Logic.sql"
SQL command batch: "CREATE PROCEDURE [dbo].[adm_Adapter_Delete]
@Name nvarchar(256)
AS
    set nocount ...";
2013-08-28 11:51:55:0496 [WARN] AdminLib GetBTSMessage: hrErr=c0c02524; Msg=Failed to create Management database "BizTalkMgmtDb" on server "MSK1-SQL-P0CT".
Statement(s) could not be prepared.
Invalid column name 'id'.

SQL script file: "C:\Program Files (x86)\Microsoft BizTalk Server 2013\Schema\\BTS_Administration_Logic.sql"
SQL command batch: "CREATE PROCEDURE [dbo].[adm_Adapter_Delete]
@Name nvarchar(256)
AS
    set nocount ...";

     
At first I thought that it is related to security problems but after that I realized that it is a different problem. BizTalk Server runs several sql files to configure stable platform and establish an integration framework in back process.
You can check those files in the folder C:\Program Files (x86)\Microsoft BizTalk Server 20XX\Schema.

As observing the problem I realized that the root of the problem is related to [dbo].[adm_Adapter_Delete] Stored procedure in the file BTS_Administration_Logic.sql
This procedure uses a query part as "select sh.id from adm_sendhandler sh where sh.AdapterId = @AdapterId" on line 4316. But if we check the table adm_sendhandler we will see that column name is "Id", not "id".
I mean problem is that SQL Server (Collation Turkish_CI_AS) doesn't interpret them as equal. In addition other procedures including BizTalk 2010 procedures don't use the query as adm_sendhandler.id so we don't face this error in another step.

Finally I had to change the query to solve the problem. We should change in the query the sh.id to sh.Id in BTS_Administration_Logic.sql on line 4316.

 It worked for me and I hope it will work for you too.
, , , , , [Edit tags]
Leave a Comment
  • Please add 8 and 8 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
  • 29 Aug 2013 8:13 AM

    Naomi  N edited Original. Comment: Minor corrections, more tags

Page 1 of 1 (1 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
Page 1 of 1 (3 items)