Wednesday, August 03, 2005

Covast Engine Input File Locking (EIF)

Sympton: Build output:XSD2EDI failed to convert XSD: Can't lock repository because it is already lockedYou can google this but let me just quote it from one existing blog:http://weblogs.ilg.com/brumfieldb/category/54.aspxThe above blogger has some good HIPPA blog too.---QuoteWe've been using the Covast EDI Accelerator for BizTalk 2004 recently as part of a solution for a client. One issue we've run into and have just discovered the solution for is that the Engine Input File (EIF) file may get locked if your process is killed while compiling the EIF file.

There may be legitimate reasons for these to be locked (such as another user actually changing the EIF file), but if you are sure that no one else should be editing the file, you can remove the locking flag manually.

To do so, go to the Covast database. Find the parame table and set the value in repolock column to NULL (Ctrl-0 in Enterprise Manager). I believe there should only be one row in this table, so that will be the row you edit.--End Quote--