EIM Task Using .IFB File on Different Machine, Box, Fails with SBL-EIM-00105: Operating system error and Error SBL-EIM-00204: Failed to load configuration file (Doc ID 511385.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Enterprise Integration Manager - Version 7.0.4.15 FINS [14078] to 16.0 [IP2016] [Release V7 to V16]
z*OBSOLETE: Microsoft Windows 2000
Version: 7.0.4.15 [14078] Fin Svcs

Database: MS SQL Server 8 (2000)

Application Server OS: Microsoft Windows 2000 Advanced Server SP 2

Database Server OS: Microsoft Windows 2000 Advanced Server SP 2



This document was previously published as Siebel SR 38-843356551.

Symptoms

We are currently trying to run EIM processes in our integration environment. This environment consists of 3 machines (1 database server, 1 application server and one web server).
We are trying to run EIM processes having all files resident in the Database Server (including the server manager exec.).
We've a problem while running the processes that consists in server manager reporting the following errors:

GenericLog    GenericError    1    2002-10-25 08:39:35    EIM: Integration Manager v7.0.4.15 [14078] LANG_INDEPENDENT failure log (pid 2484).
GenericLog    GenericError    1    2002-10-25 08:39:35    
GenericLog    GenericError    1    2002-10-25 08:39:35    Error 105: Operating system error.
GenericLog    GenericError    1    2002-10-25 08:39:35    
GenericLog    GenericError    1    2002-10-25 08:39:35    Error 204: Failed to load configuration file
GenericLog    GenericError    1    2002-10-25 08:39:35    "\\egcintsql\Interfaces\scripts\CONTACT\V02\ifb\CONTACT.ifb".
GenericLog    GenericError    1    2002-10-25 08:39:35    (compmain.cpp 16(1552) err=100204 sys=0) EIM-00204: Invalid configuration file to load initially.
GenericLog    GenericError    1    2002-10-25 08:39:35    (smisched.cpp 17(791) err=100204 sys=0) EIM-00204: Invalid configuration file to load initially.
GenericLog    GenericError    1    2002-10-25 08:39:35    
GenericLog    GenericError    1    2002-10-25 08:39:35    Recorded 2 errors (no failure information)

This happens whenever the ifb file is on a server other than the application server, although if you are on the application server you can "see" the file using explorer or a command prompt.
We've already tried mapping a drive, using the default share, sharing to everyone, etc.
FYI : the servers are not on a domain but on the same workgroup, and have the same user/password configuration.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms