Search This Blog

SBL-UIF-00227: Generic Error in Compression Routine

APPLIES TO:

Siebel Tools - Version 8.1 [21039] and later
Information in this document applies to any platform.
*** Checked for relevance on 02-AUG-2013 ***
Error Message Area:UI Framework - UIF
Version:Siebel 8.1


PURPOSE

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00227: Generic Error in Compression Routine.

SCOPE

This document is informational and intended for any user.

DETAILS

Explanation

Error during reading and compressing a chunk of file data into memory.

Corrective Action


"If possible, get the problematic file and report the problem to Siebel Technical Support."




APPLIES TO:

Siebel System Software - Version 7.8.2.10 SIA [19241] and later
Information in this document applies to any platform.

SYMPTOMS

Background
-------------------
An inbound web service is invoked which is intended to create a Service Request, and optionally also attachment data.
Problem
-------------
When just creating a Service Request there is no error.  The application is creating errors when creating a Service Request and an Attachment record.  The reported error is :-

SBL-UIF-00227: Generic Error in Compression Routine


Environment
--------------------
Siebel version : 7.8.2.10
Database version : Oracle 10.2
OS version : Windows 2000

CAUSE

The inbound message includes a file name, which the custom scripted Business Service underlying the web service tries to attach, for example "C:\Documents and Settings\mogalgs\Desktop\ABCD1234.csv".

The error arises in the custom script trying to attach the file using the CreateFile method :-
with (bcSRAtt)
{
  NewRecord(NewAfter);
  sReturn = InvokeMethod('CreateFile', sPath, 'ActivityFileName', 'N');
This code is running on the Siebel Server, and the file was only physically present on the machine from where the inbound web service was invoked.

SOLUTION

As confirmed by customer, the attachment file was missing from the Siebel Server.
To resolve this, the action was :-

1. Copy the file to the Siebel Server.
2. Re-run the web service, and ensure the file name passed into the inbound web service is the location of the file on the Siebel Server.

No comments:

Post a Comment