A developer delivered a schema workspace modifying table columns, but the physical database schema was not updated, causing Object Managers to crash when querying non-existent columns.

1. In Web Tools, verify that the active workspace has been successfully delivered to `MAIN`.
2. Run Database Schema Sync via `dbdict` / `ddlctl` utility or perform **Apply/DDL** on target tables from Siebel Tools/Web Tools.

App server processes serve stale repository definitions from local process memory after a deployment, throwing dynamic SQL runtime exceptions.

1. Clear the server-side dictionary cache and bounce affected Object Managers using `srvrmgr`.

One node in an Enterprise cluster runs an older `siebel.srf` binary file while other nodes run a newly deployed version, causing intermittent load-balancer thread crashes.

1. Ensure deployment scripts sync the compiled `siebel.srf` file identically across all server nodes in `$SIEBEL_ROOT/siebsvr/objects/`.

A field marked as `Nullable = FALSE` in Siebel repository allows `NULL` values in the physical database definition, causing runtime C++ integrity check failures.

1. Regenerate physical database schema definitions or update mandatory column attributes in Siebel Tools and execute `Apply DDL`.

Attempting to deliver a child workspace to `MAIN` fails because another developer delivered changes to the same Business Component or Applet properties in the interim.

1. In Web Tools, open the target workspace and click **Rebase**.
2. Review conflicting object properties in the **Merge Conflicts** panel and select target attribute resolution (`Mine` vs `Latest`).
3. Re-test the workspace locally prior to re-initiating delivery to `MAIN`.

An application server process or developer session crashed during a workspace delivery, leaving the repository branch permanently locked in `DELIVERY_IN_PROGRESS`.

1. Run SQL diagnostics to inspect workspace tree locks in `S_WORKSPACE` and reset stuck delivery flags.

A developer workspace created several release cycles ago attempts to rebase against a substantially modified parent branch, causing automated merge engine failure.

1. Export developer workspace object changes to XML via Web Tools.
2. Discard the stale workspace, create a new child workspace from latest `MAIN`, and re-import objects.

Delivering a workspace fails because an applet control or business component field references a join or picklist object defined in a separate un-delivered workspace.

1. Sequence workspace deliveries so underlying data structures and picklists are delivered to `MAIN` prior to dependent UI component workspaces.

The File System Manager (`FSManager`) fails to retrieve or store attachment files (`.SAF`) because the network storage mount point unmounted or timed out.

1. Verify the status of the file system share on the Linux/Windows host running the Application Server.
2. Ensure the `siebel` OS service account possesses full read/write permissions across all subdirectories.

The Enterprise parameter `FileSystem` points to an invalid UNC network path or non-existent local directory structure.

1. Query and update the `FileSystem` parameter across Enterprise components using `srvrmgr`.

Uploading or downloading compressed attachment files (`.SAF`) fails because underlying OS binary compression libraries are unreadable by the `siebel` service account.

1. Check read and execute permissions on `$SIEBEL_ROOT/siebsvr/bin/minizip` or OS compression binaries. Grant execute rights to the server service account.

A record in `S_ACCNT_ATT` or `S_PARTY_ATT` references a file name token that was deleted or renamed directly on the storage file system.

1. Run diagnostic SQL to cross-reference unlinked database attachment tokens against physical storage.

Attachment write requests fail across all application components because the primary NAS/SAN disk volume ran out of free block space.

1. Configure multi-directory storage paths separated by semicolons in the `FileSystem` parameter to distribute attachments across multiple storage pools.

Heavy concurrent attachment read/write operations cause file transfer latency to exceed the default `FSConnectTimeout` threshold, dropping client sessions.

1. Increase the `FSConnectTimeout` parameter in `srvrmgr`.

Deleted business records leave unlinked `.SAF` attachment files behind on the file system, consuming gigabytes of disk space over time.

1. Run orphaned file system purge scripts (`sfsclean`) to cross-reference database attachment tables against physical `.SAF` files and free disk space.

Storing over 65,000 files in a single attachment subdirectory (e.g., `/att`) degrades directory lookup performance and triggers I/O execution errors.

1. Enable nested directory storage parameters in Siebel File System configuration to balance files into subfolders (e.g., `/att/01`, `/att/02`).

Transaction records remain stuck in `Processing` or `Error` state due to unhandled tier evaluation or point calculation logic exceptions inside `LoyEnginePrc`.

1. Run SQL diagnostics to locate stuck or errored Loyalty transaction records in `S_LOY_TXN`.
2. Reset failed transaction status back to `Queued` for re-processing.

Peak transaction import volume overwhelms the single `LoyEnginePrc` task thread, causing engine queue backlogs and processing timeouts.

1. Adjust thread allocations and task scaling parameters for `LoyEnginePrc` via `srvrmgr`.

A loyalty program promotion attempts to assign points to an unconfigured Point Type bucket or active period, halting transaction rule processing.

1. Navigate to **Administration - Loyalty > Program Design**.
2. Ensure all Point Types, Buckets, and Action Sets assigned to active promotions are enabled and valid.

A misconfigured tier assessment rule triggers infinite evaluation loops between tier upgrade and downgrade triggers, crashing `LoyEnginePrc` threads.

1. Inspect loyalty engine log files for recursive rule execution, deactivate target promotion, and fix tier assessment criteria logic.

Issue: The CTI driver definition references an absolute path that does not exist on target Linux/Windows app server nodes.

1. Navigate to **Administration - Communications > Communications Drivers and Profiles**.
2. Select the target CTI driver (e.g., *Avaya TSAPI* or *Genesys T-Server*) and inspect the **Driver Parameter** record named DriverPath.
3. Ensure relative paths use bin or direct server library structures.

Issue: Generic CTI initialization errors hide underlying middleware connection parameters.

1. Raise event logging on the `CommSessionMgr` component to output detailed vendor CTI API traces.

Issue: Primary CTI server failover does not occur automatically, dropping agent CTI toolbar sessions.

1. Navigate to **Administration - Communications > Communications Drivers and Profiles > Driver Profiles**.
2. Configure redial, backup server addresses, and heartbeat interval profile parameters.

Issue: Network firewalls silently drop idle CTI sockets between Siebel App Servers and CTI Middleware servers after 300 seconds.

1. Adjust OS-level TCP Keep-Alive settings on the Siebel Server host to send keep-alive probes every 60 seconds.
2. Ensure the CTI Middleware `HeartbeatInterval` parameter is strictly lower than firewall state-table cleanup intervals.

Issue: Incoming CTI events fail to trigger screen-pops due to missing Event Response parameters.

1. Navigate to **Administration - Communications > All Configurations**.
2. Select the target Agent Configuration and inspect **Event Handlers**.
3. Verify that the event `DeviceEvent` name matches the exact string payload emitted by the vendor CTI driver (e.g., `EventRinging`).

Issue: Changes made to CTI commands or profile event maps do not take effect for connected agents.

1. Navigate to **Administration - Communications > All Configurations**.
2. Click the **Clear Cache** button on the configuration applet.
3. Have affected agents log out and log back into the CTI toolbar to fetch the re-indexed event tree.

Issue: Modern email servers (Microsoft Exchange Online / O365, Gmail) reject legacy SSL ciphers used by CommInboundRcvr.

1. Configure `CommInboundRcvr` component profile parameters to enforce modern TLS standards.
2. Isolate corrupted email messages into the error directory (`$SIEBEL_ROOT/siebsvr/bin/nonparse`).

Issue: A single malformed MIME email with invalid header syntax halts queue processing for all subsequent inbound emails.

1. Check the `$SIEBEL_ROOT/siebsvr/bin/nonparse` directory on the server filesystem for blocked `.eml` files.
2. Move corrupted files out of the active directory queue, then restart the `CommInboundRcvr` task via `srvrmgr`.

Issue: Load balancers close silent TCP socket channels after 300 seconds, breaking agent UI event pushes.

1. Navigate to **Administration - Communications > All Configurations**.
2. Set the configuration parameter PushKeepAlive to a value lower than the load balancer idle timeout (e.g., 60 seconds).

Issue: Open UI clients fail to re-establish WebSocket push connections when `CommSessionMgr` runs on a separate app server node from AOM.

1. Verify that Application Interface `web.xml` enables channel streaming protocols properly.
2. In **Administration - Communications > Agent General Profile**, ensure `CommHost` specifies the cluster virtual IP or sticky load balancer address of the `CommSessionMgr` pool.

Issue: Firewalls block port 25/587 or reject unauthenticated SMTP connection requests from app server IP addresses.

1. Test direct SMTP socket delivery from the Siebel Application Server node using `curl` or `telnet`.
2. Configure SMTP credentials in the `Email Outbound Utility` profile.

Issue: High outbound volume throttles `CommOutboundMgr` threads, causing connection drops on the mail gateway.

1. Adjust thread concurrency and retry settings for `CommOutboundMgr` via `srvrmgr`.
2. Set SSL parameters for secure SMTP connections.

Issue: Stale or uncompiled assignment rules cause the engine to read invalid pointer references in `rulecache.dat`.

1. Navigate to **Administration - Assignment > Rule Groups**.
2. Click the **Clear Cache** button on the Rule Groups applet.
3. Navigate to **Administration - Server Management > Jobs** and submit a job for **Generate Rule Cache** (`GenRuleCache`).
4. Restart the `AsgnSrvr` component via `srvrmgr`.

Issue: Processing thousands of complex skills against large candidate pools exhausts standard process limits.

1. Adjust thread memory thresholds and pool sizes on the server component.

Issue: Misconfigured LDAP base paths or admin credentials prevent initial directory user searches.

1. Inspect and update LDAP Security Adapter subsystem parameters using `srvrmgr`.

Issue: System admin credentials used by Siebel to search the LDAP directory have expired or been locked out.

1. Test connectivity directly from the OS host running the Application Server using `ldapsearch`.

Issue: Rules created in UI are not associated with an active Rule Group before cache generation.

1. Navigate to **Administration - Assignment > Rule Groups**.
2. Ensure all required rules are assigned to active Rule Groups and marked with **Activation Status = Active**.
3. Re-run the **Generate Rule Cache** server task.

Issue: The LDAP directory username does not match the `LOGIN` column in `S_USER` exactly (case-sensitivity or domain prefix mismatch).

1. Query `S_USER` to verify user existence and status.

Issue: Skill comparisons scan millions of rows without leveraging database indexes.

1. Identify the dynamic SQL generated by Assignment Manager by raising component logging (`evtloglvl AssignmentQuery=5`).
2. Add database indexes on custom foreign key columns evaluated in Assignment Attributes.

Issue: Interface rows fail foreign key resolution because parent Business Unit or Parent Account names are missing or misspelled.

1. Query the interface table for failed rows (`IF_ROW_STAT = 'FOREIGN_KEY_FAILED'`).
2. Perform an explicit `LEFT OUTER JOIN` against the parent base table to identify missing natural keys.

Issue: Optional foreign keys fail import when interface columns are left empty.

1. Use the FIXED COLUMN directive inside the `.ifb` configuration file to supply fallback parent key defaults.

Issue: Staging tables populated by external ETL tools contain duplicate natural keys within the same batch ID.

1. Run a SQL deduplication query prior to initiating the EIM task to keep only the latest `IF_ROW_ID`.
2. Ensure the `.ifb` configuration file permits both updates and inserts (`INSERT ROWS = TRUE`, `UPDATE ROWS = TRUE`).

Issue: Non-standard parameter syntax causes task initialization crashes.

1. Validate the structure of the `.ifb` file against the official Siebel Enterprise schema.
2. Place the file inside `$SIEBEL_ROOT/siebsvr/admin` and verify file encoding is ASCII/UTF-8 without BOM.

Issue: Staging rows omit required party classification types or status columns during raw data loads.

1. Run a SQL pre-population script on the interface table to ensure all mandatory columns contain valid non-null values.

Issue: Parallel EIM tasks contend for exclusive locks on the `S_PARTY` base table.

1. Assign distinct, non-overlapping batch number ranges to separate parallel tasks.
2. Execute EIM tasks asynchronously using `srvrmgr`.

Issue: Programmatic Order Creation via eScript bypasses manual UI validation, generating invalid quote line items and crashing the Configurator session.

1. Invoke the eCfg Engine Business Service explicitly in eScript to validate constraints prior to calling SetInstance or SyncInstance.
2. Inspect conflict items returned in the output PropertySet hierarchy to resolve errors programmatically.

Issue: Updated constraints edited in Administration - Product remain in Draft status, causing engine discrepancies against cached production models.

1. Navigate to **Administration - Product > Customizable Products**.
2. Select the target customizable product, click **Validate** to test engine constraints, and click **Release** to create an active version.

Issue: Complex customizable products with deep BOM hierarchies exceed default 32-bit/64-bit eConfigurator process memory structures.

1. Increase the memory allocation limits for the eConfigurator server component in `srvrmgr`.
2. Configure worker process pooling to prevent single-process thread exhaustion.

Issue: Corrupt binary blobs in the `S_PROD_INT_CR` database cache table prevent new engine sessions from starting.

1. Navigate to **Administration - Product > Cache Management**.
2. Click **Clear Cache** to invalidate all active in-memory product definitions across the server enterprise.

Issue: Custom quote line item fields required by the `Basic Pricing Procedure` are missing from the PSP dynamic transform map.

1. Navigate to **Administration - Business Executive > Signals** and inspect the input parameters bound to the `CalculatePrice` signal.
2. Verify that the line item field exists on the **Quote Item** Business Component and is populated prior to pricing invocation.

Issue: Legacy asset migration scripts created orphan records with null `INTEGRATION_ID` values, breaking the ABO Delta engine.

1. Execute SQL to verify that all child asset records under the target account possess valid `INTEGRATION_ID` handles.
2. Re-run the standard **SIS OM Edit Delta Workflow** to regenerate quote action codes (`ADD`, `MODIFY`, `DELETE`).

Issue: Line items inherit a quote currency (e.g., EUR) that does not match the active price list rate currency.

1. Navigate to **Administration - Pricing > Price Lists**.
2. Query for the target Price List name, open the **Price List Items** applet, and verify that the product exists with an active status and valid rate.

Issue: Custom PR files fail to load because the module path inside `define()` does not match the Manifest Files entry.

1. Ensure the file path registered under Administration - Application > Manifest Files uses relative web pathing: siebel/custom/CustomPR.js.
2. In JavaScript, ensure the RequireJS module name matches the exact relative path without extension.

Issue: Manifest mapping updates made in Web Tools or Administration screens do not take effect immediately.

1. Navigate to **Administration - Application > Manifest Administration**.
2. Select the expressions menu and click **Reload Manifest**.
3. Clear browser HTTP cache or append `?SWECmd=AutoOn` in the URL to bypass client caching.

Issue: Web server session timeout settings disconnect users earlier than the Application Object Manager parameter configuration.

1. Set the `SessionTimeout` parameter on the Application Object Manager via `srvrmgr`.
2. Configure matching timeout values in Application Interface `web.xml` / container configurations.

Issue: F5 / NetScaler load balancers route requests round-robin instead of binding `JSESSIONID` to a single app server instance.

1. Configure HTTP Cookie Persistence on the Load Balancer targeting `JSESSIONID` and `SWECOUNT`.
2. Ensure HTTP response headers preserve `SameSite=Lax` or `SameSite=Strict` attribute rules.

Issue: Custom web templates (.swt) created in Web Tools are missing from target server filesystem directories.

1. Verify that custom `.swt` files exist inside `$SIEBEL_ROOT/siebsvr/webtmpl` and `$SIEBEL_ROOT/applicationcontainer/webapps/siebel/webtmpl`.
2. Apply correct read permissions for the OS application account (`siebel`).

Issue: Custom code attempts to query DOM elements using jQuery before the Open UI engine completes rendering.

1. Never perform DOM manipulations inside constructor or `Init()` phases. Place all visual controls inside `ShowUI()` or `BindData()`.
2. Wrap DOM element queries with length validation checks before invoking jQuery plugins.

Issue: Users invoke business service methods directly from browser URLs without explicitly declared applet user properties.

1. Verify user responsibility mapping under **Administration - User > Responsibilities**.
2. To permit web service calls safely, declare the method explicitly in the Applet user property `CanInvokeMethod: = TRUE`.