BTS2006 EDI Base Adapter – Error Occurred in the File System Connector

I installed the BizTalk 2006 base EDI adapter for the first time last night to investigate the differences between the Covast EDI Accelerator and the Base EDI Adapter (the base adapter technology is produced by Covast).

While working through the XML-to-EDI tutorial it became apparent that things were not quite right with my configuration – I was constantly receiving the following error:

Error encountered: ERROR (120) :
An error occurred in the File System connector. Check the details.Cant make a connection to \TITANAEEDIDocsHomeDocumentsPickupEDI. Errormessage: The operation cannot be performed because a network component is not started or because a specified name cannot be used.Foldername: \TITANAEEDIDocsHomeDocumentsPickupEDI, Errormessage: The operation cannot be performed because a network component is not started or because a specified name cannot be used.

It would appear that on installation, a share is created that points to C:Documents and SettingsAll UsersApplication DataMicrosoftBizTalk Server 2006EDISubSystem. The SubSystem folder contains all of the goodies required to make the Base EDI Adapter work – esp.ini, the engine input file (EIF) and Documents directory which provides a message store while the adapter is doing its magic.

The error above however is a little misleading, as it has nothing to do with a network component or the specified name being incorrect. Instead, the EDI Subsystem Users group is not granted access on this share under the default installation. Simply adding the group (with full control) will resolve this error.

It does make me wonder why the installation insists on creating a share to point to the aforementioned location as this directory information is actually held in the SQL Server database. The only reason I can see for using this method is on multi-server installations, where the EDI SubSystem resides on a network share, rather than a local directory. This makes sense, but I’m not too sure behind the reasoning on a default [local] installation.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s