Skip to main content

Unable to Add Attachment in Siebel SBL-UIF-00229

Issue Steps (Siebel UI):
Go to Contact Screen and Contact List.
Drilldown Contact Name and Attachment Detail View.
Click on New Button in Attachment applet, select file.
Step off, or click on save button.
Siebel Return an error.

Error Details:
[1]Error occurred while creating file in filesystem. Please contact your system administrator. (SBL-SVC-00184)
[2]Error occurred while opening file 'S_CONTACT_ATT_ROWID.SAF'.(SBL-UIF-00229)

adding_attachment



Issue Steps (Siebel Workflow):
Invoke workflow which is trying to add attachment using EAI Siebel Adapter.

Error Details:
[1]Error Invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Upsert Attachment'.(SBL-BPR-00162)
[2]Method 'New Record' of business component 'Email Attachments' (integration component 'Email Attachments') for record search specification '[Parent Id] IS NULL' returned the following error: "Error occurred while opening file 'S_CONTACT_ATT_ROWID.SAF'.(SBL-UIF-00229)"(SBL-EAI-04451)


adding_attachment_EAI_WF

Possible Reasons and Solutions:

  • Filesystem drive space is full.

Go to the server where filesystem drive is shared. Check the free space. If there is no space you need to increase the space.

  • Filesystem att folder access control/ permissions.

Navigate to att folder (Path will look like this: E:\Shares\SharedData\Siebel\fs\att) right click and go to properties.
Go to Security tab. Click on Edit button of "Group and user names".
From the new window click on Add button.
In New window type "Everyone" and Click OK button.
Now in previous window "Everyone" will be added in "Group and user names" section.
In Permission section click on "Allow" check box against "Full Control" and click OK button.


adding_attachment_folder_permission

  • Filesystem path issue in Server Configuration.

Check the filesystem in Configuration and compare it with shared filesystem.
Example of filesystem path in Configuration: \\FS\SharedData\Siebel\fs
Example of filesystem path in server: E:\Shares\SharedData\Siebel\fs\

Comments

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...