Siebel Remote Errors – Solutions

Often, when using Siebel Remote application, users face error messages. Out of my experience, below are the solutions for these errors. Note that these are based purely on my experience working with Siebel Remote, if anybody have different solutions for these errors, please share the same here with wider audience.

  1. If you are seeing below error while upgrading the Siebel Remote client or related to configuration file or DLL errors, follow the below steps:

Unable to initialize the upgrade wizard possibly due to an error reading the configuration or driver file. Please look at the upgrade log for details               Solution:

  1. Please navigate to the “C:\Program Files\Siebel\7.0\WEBCLI~1\Bin” directory through Windows Explorer and rename upgwiz.ucf file if it exists.
  2. Restart the Siebel remote client and continue with the synchronisation.

2. If you are seeing below error while installing the Siebel Remote client: “Class not registered”                                     Solution:

  1. Browse to C:\Program Files\Common Files\InstallShield\engine
  2. Delete the engine folder
  3. Install the latest version of the iKernel engine from the below link.
    1. Download iKernel engine update and save it to your Desktop. (
    2.  Install the ikernelupdate.exe, downloaded in the above step.
      1.  Once the above steps are completed, try the installation of Siebel remote from                     the setup.exe file
      2. If you are seeing the errors like, “..Node is already servicing this client” the solution would be to re-extract this user on the server again.

Differences between Siebel Remote and Handheld

Siebel Remote and Siebel Handheld are two different types of Siebel Clients used for accessing the Siebel application by end users. Even though both are used for accessing the Siebel application remotely without having the need to be connected to the Siebel server/database, below are primary differences betweeen them:

1.Mode of Synchronisation:

Siebel Handheld client use a separate Handheld Object Manager for synchronization.

Siebel remote Client does not have a object Manager but uses component Synchronisation Manager on the server for synchronization and has its own local database.

2. Local DB size:

 Siebel HH uses a smaller database with data filters compared to Remote client.

Siebel Remote has a larger database and data on it is controlled by filters set on the server side.

3. Scheduled Sync:

Siebel sync cannot be scheduled on the HH client, whereas it can be scheduled on the Remote client using Trickle Sync functionality.

4.DB Extract:

Siebel HH client does not database extract job to be executed.

A DB extract job for the Remote client user need to be executed to extract the data for the remote user.

5. Applications available:

Siebel HH does not support but only few industry applications like ePharma, eMedical, eConsumer, etc.

Siebel Remote supports all Siebel Industry and Business applications.

Siebel Remote Architecture

          Siebel Remote enables the use of disconnected Siebel access on the user’s local PC without the need to be connected with the Server database for accessing the Siebel applications. The user needs to connect to the server database regularly to get the latest data from the server and to send the local data to the server so that corporate database is up-to-date with latest field data from the users.

Now, let us look into major Siebel components of the Siebel Remote:

  1. Transaction Processor
  2. Transaction Merger
  3. Transaction Router
  4. Synchronization Manager
  5. Generate New Database
  6. Database Extract

Below is the flow of Siebel Remote: 

 Siebel Remote Architecture

 Siebel Remote works in the following way:

1.Every Transaction (TXN) in the Siebel application is logged into a master log table, S_DOCK_TXN_LOG

2. Transaction Processor Component picks these and creates the .dx files in the docking directory, DOCKING\TXNPROC on the Siebel Remote server.

3. Transaction Router routes these .dx files to the Mobile user’s outbox on the server according to the Docking rules set on the server.

4. Transaction Processor also purges the records from the master table, once applied in TXNPROC and also it purges the files from the TXNPROC once the router routes the files.

5. When the remote client initiates the synchronization, the Synchronization Manager moves the Client’s Outbox .dx files to server’s Inbox folder.

6. Transaction Merger then applies the .dx files in the Inbox of the docking directory of the user on the server to the server Database.

7. Transaction Merger also deletes the .dx files in the Inbox of the docking directory of the user once they are applied to the server Db.

               Whenever there is change in the Siebel database schema like creating new columns or tables or indexes, a new Database template need to be created for the Siebel remote and this is done by running a job for  component ‘Generate New Database’.

                In order to create a new Remote user or a developer client, a local database need to be created for that user. This is done by running a job for component ‘Database Extract’.

Check out Siebel Remote errors and their solutions for common errors found while using Siebel Remote.

Siebel Architecture

 In this article, we will look into the Siebel technology architecture. Below is the architectural diagram of a typical Siebel implementation containing various blocks.

Let us look into each block and understand their role in entire architecture.  


 1. Siebel Clients 

            The Siebel clients are the ones using which the end user access the Siebel applications. There can be wide variety of Siebel clients but primarily they are as given below.

                                       i.        Siebel Web client.

                                     ii.        Siebel Remote client.

                                    iii.        Siebel Handheld Client

                                    iv.        Siebel Dedicated web client.

 Now, let us look into them one-by-one.

 i. Siebel Web Client: Siebel Web client is based on the user PC’s browser. The Siebel application is accessed like any other website using a URL in the browser. There are two types of Siebel web clients. This is discussed in another article, Types of Siebel Web clients and associated issues.

ii. Siebel Remote Client: Siebel Remote client also uses the browser of the user PC, but has own installation on the PC. It accesses its own local Database instead of Server database.

This topic is discussed in detail in Siebel Remote Architecture article.

iii. Siebel Handheld Client: Siebel Handheld Client is used for accessing the Siebel Application on Handheld device like a PDA. It is similar to Siebel Remote client but a scaled down version. It uses its own URL for accessing the Siebel application. You can check out Differences between Siebel Remote and Handheld for more details.

iv. Siebel Dedicated Web client: This type of Siebel client is directly connects to Siebel database bypassing Siebel web server and Siebel server. It is primarily used for debugging and troubleshooting purposes.

 2. Siebel Web server 

            The Siebel web server is used to serve pages to the Siebel clients. Actually this is normal web server like Microsoft IIS or Apache server but a Siebel plug-in called, Siebel Web Server Extension (SWSE) is installed for Siebel. We can manage multiple Siebel applications using Load balancing strategies. Check out Siebel Load balancing article for more info.

 3. Siebel Gateway Name Server 

            The Siebel Gateway Name server is a single entry point for accessing Siebel application. It controls the Siebel servers and their components. The entire information of the Siebel enterprise is maintained in a single repository file called, Siebns.dat . This stands for ‘Siebel Name Server’ data file.

Siebel servers and their components reads this file while startup and for completing other tasks. A Single Gateway Name server can support multiple Siebel Enterprises (but this kind of implementation become complex to manage) but one enterprise must contain only one Gateway name server.

 4. Siebel Enterprise Server

             Siebel Enterprise server is logical grouping of Siebel servers so as to maintain and manage the Siebel servers easily. It consists of one or more Siebel servers and can be accessed via command-line utility or through GUI. You can check out Using Server Manager utility for accessing the Siebel servers/enterprise through command-line.

 5. Siebel Database server

                The Siebel  Database server includes the RDBMS client software and Siebel tables, indexes, and seed data. Different types of RDBMS software can be used like Oracle, SQL, IBM DB/2, etc.

6. Siebel File System

               It stores the data and physical files used by Siebel clients and Siebel Enterprise Server. Various operations can be performed on this as part of maintainence and increasing the performance of the file system. These will covered in subsequent articles.