SBL-DAT-00393: An end of file error has occurred.

Applies to:

Siebel Tools - Version: 7.5.3 [16157] and later   [Release: V7 and later ]
Information in this document applies to any platform.
Error Message Area:Data Manager - DAT
Version:Siebel 7.5.3

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00393: An end of file error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.

Scope

This document is informational and intended for any user.

SBL-DAT-00393: An end of file error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.

Possible Causes

1. When using a Siebel adapter which utilizes both Siebel COM and Siebel Java Data Bean for integration, the NextRecord method displays the end of file error. The Siebel JAR files may be a different version than the Siebel Server files.

2. In Siebel Reports version 7.7, when using a non-ENU language character as a parameter value when scheduling a report, the report generates successfully but the character does not appear correctly. Verify in Management Console by navigating to Jobs > Completed and view the Properties. The parameter value appears corrupted. This issue does not occur if the Run Now option is selected in the Web client.

3. When attempting to print more than about 20 records from the Fulfillment screen, only the first few documents are printed and the Document Server task errors out.

4. When you drill down on a child component from Asset > Components and click the Customize button, the end of file error displays.

Corrective Actions

1. Ensure that the Siebel JAR files are of the same version as the Siebel server. (For example, use only the JAR files from a Siebel 7.7 server to connect against a Siebel 7.7 server.) You can get the JAR files of the installed Siebel version from the CLASSES subdirectory of the Siebel server installation.

For more information regarding Java Data Bean, refer to Siebel Bookshelf > Object Interfaces References > Programming > Getting Started with the Siebel Object Interfaces > About Java Data Bean.

2. As a workaround, do not click the Submit button immediately in the Schedule dialog box. Instead, click the Output tab and then click the Submit button. The report will pass the language character correctly.

Bug 12-QDZAE7 has been logged to address this product defect.

3. As a workaround, if this happens with specific requests print them via client side printing. You could also open the documents using MS Word and print them through this program.

Bug 12-KGC3HQ has been logged to address this product defect.

4. As a workaround, retrieve the child component directly in the Asset Mgmt - Assets View / Asset Mgmt - Asset List Applet, not as a sub-component in Asset Mgmt - Asset Sub-Components View / Asset Mgmt - Asset List Applet Sub-Components. Then click the Customize button.

Bug 12-MVCURS has been logged to address this product defect.

Applies to:

Siebel Tools - Version: 8.0 [20405] and later   [Release: V8 and later ]
Information in this document applies to any platform.
""Checked for Relevance on 09-Aug-2010""

Symptoms

The customer received the following error each time they created two consecutive addresses in a custom Address Mvg Applet:
- - -
An end of file error has occurred.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00393)
- - -

This issue occurred only with their customized Siebel application.

Cause

The MVG applet involved was similar to standard 'Address Mvg Applet' based on BC 'Business Address'. By reviewing the customized BC 'Business Address' it was found the following in the BusComp_WriteRecord event:
- - -
function BusComp_WriteRecord ()
{
…
this.ActivateField("xxx");
…
var num = GetFieldValue("xxx");
…
}
- - -

were xxx was the name of a custom field in BC 'Business Address'. This field was not set as Force Active in the BC and not exposed in the MVG applet.

The root cause of the issue is the ActivateField method. This method is used to activate fields prior to executing a query for a BC via scripting. The customer tried to activate a field in a UI context BC. This method shouldn't be used in this context. This matter is discussed in Note 477419.1:

# Accessing UI Context and Non UI Context Object Instances (Doc ID 477419.1)

It is explained in particular the following:
- - -
…
IMPORTANT: Do not use ActivateField method to activate a field in a UI context business component. This may cause some unwanted side effects.
…
- - -

Solution

The solution is to remove the following line:
- - -
this.ActivateField("xxx");
- - -

and either set the field 'xxx' as Force Active in the BC ('Force Active' property set to TRUE) or expose it on the MVG applet.

The ActivateField method is documented in the Bookshelf:

Siebel Object Interfaces Reference
Interfaces Reference
Business Component Methods
ActivateField Method

Bug 12-1SD8OLD has been logged asking to add in the Bookshelf the same warning as the one mentioned in Note 477419.1 (IMPORTANT: Do not use…).

References

BUG:12-1SD8OLD - IMPORTANT: DO NOT USE ACTIVATEFIELD METHOD TO ACTIVATE A FIELD IN A UI CONTEXT BUSINESS COMPONENT.
NOTE:477419.1 - Accessing UI Context and Non UI Context Object Instances

Applies to:

Siebel Tools - Version: 7.7.2 [18325] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Microsoft Windows 2000 Advanced Server SP 4
Checked for Relevance on 30th August 2010. The CR still applies to version 7.7.2

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

Symptoms

SBL-DAT-00393

Hello,

This is also happening in Production, the client went live with 7.7 on Sunday 12/19/04. Sporadically (but much more often than not), users will get the following generic error message when attempting to enter a new appt from the Contact/Calendar view (or Opportunity/Calendar, or Account/Calendar, or My Calendar on the home page):

We detected an Error which may have occurred for one or more of the following reasons:

An end of file error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00393)

*******

If they click the 'Back' button that is provided with the error message, they will see that an activity has been created with 'no description' in the calendar applet. That activity can then be located in the Activities view (description blank when it's not the specialized calendar class applets) and completed, but attempting to drilldown on it will also produce the error.

We have searched support web exhaustively using the following strings:

"SBL-DAT-00393" and "Calendar"
"end of file" and "calendar"
"no description" and "action"
"eCalendar Daily Applet Home Page"
"eCalendar Monthly Applet Without Employee"
"eCalendar Detail View"

We found several postings which seemed somewhat relevant, including 38-1300502611, 38-900185541, and 38-1245063741, but none of the suggested fixes seemed to work in our environment. We have not added any additional BusComp View Mode settings to the Action bc, and have also tested with inactivating the vanilla 'Personal' one as suggested in one posting (but it didn't fix the problem though and anyways we're wary that doing so may mess up expected visibility on Activities). Also, we do not have any FORCE UPPER fields (that was the fix on another SR).

We cannot reproduce the behavior with the vanilla 7.7 srf, nor in the custom 7.5.3 application that was the starting point for the upgrade. I'm wondering if it perh...

Cause

For the benefit of other readers :

Customer was getting following error "SBL-DAT-00393" error When Attempting to Enter New Appt from Contact/Calendar.

Following are steps to reproduce the issue in vanilla Siebel:

Navigate to Siebel application connecting to sample database and attempt to enter a new appointment from the "Contacts" Screen -> "Calendar" view (or Opportunity/Calendar, or Account/Calendar, or My Calendar on the home page):

Following is the error message displayed :
"We detected an Error which may have occurred for one or more of the following reasons:

An end of file error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00393)"

If they click the 'Back' button that is provided with the error message, they will see that an activity has been created with 'no description' in the calendar applet.
That activity can then be located in the Activities view (description blank when it's not the specialized calendar class applets) and completed, but attempting to drilldown on it will also produce the error.

Further investigation revealed that it is caused by PDQ created under Application Administration -> PreDefined Queries.

All the PDQs defined in sample database are deleted and the only PDQ existing is
'Action'.Search = "[Type] LIKE ""Call - Inbound*"""
'Action'.Sort = ""

Solution

The issue is reproducible with the above custom PDQ in sample database with vanilla srf.

A Change Request 12-SHHJ68 was logged to address this issue . Normally , when a Change Request is logged , reviewed , prioritised and a fix is implemented in one of the future releases.

Thank you,
Siebel Technical Support

keywords : SBL-DAT-00393 , new appointment , An end of file error has occurred , custom PDQs , Contact Screen / Calendar View

Applies to:

Siebel Tools - Version: 7.8.2.3 SIA [19221] - Release: V7
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221] Com/Med
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: IBM AIX 5L 5.2

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

Symptoms

The error message "An end of file error has occurred. Please continue or ask your system administrator to check your application configuration if the problem persist.

Error code 'SBL-DAT-00393'" is appearing sporadically to our help desk agents when using the Siebel application. This error is generic enough that our agents are unable to predict when it might occur or what it might mean and thus are forced to requery for customer information, often must retype previous notes or recreate attempted activities, and sometimes must even log out of the application and reboot their PC.

Solution

The above error message only appeared when the customer navigated to the Home Tab and clicked the New button on the Calendar Applet.

A Change Request Bug 12-SHHJ68 was previously logged to address this issue . The following approach was suggested:

1. The problem was found due to the PDQ which the customer had created. It was recommended to make a change to the PDQDisabledView parameter in the uagent.cfg file. In addidtion also add a further PDQDisabledView[*] parameter in the swe section of the cfg file is specific to the view for which is given in the argument.

2. This parameter does not disable running of pdqs in the view. It just does not run the pdq when loading. The issue is just for a single view - and setting of this parameter should solve the issue.

3. The PDQ will look something like this, please replace with the appropriate view name and place it in the swe section of the appropriate cfg file:

PDQDisabledView9        = "eCalendar Detail View"

For version 8.0 and above:

As of release 8.0, the PDQDisabledView is no longer read from the application .cfg file; instead, set it as an application user property in Siebel Tools.

 Value
 Name of the view for which you want to disable the Predefined Query (PDQ) dropdown.

Some of the predefined property values include:
PDQDisabledView0 = Order History View (eSales)
PDQDisabledView1 = Order History View - My Company (eSales)

For further details review: Siebel BookShelf>Version8.1>Siebel Developer's Reference > User Properties > Application User Properties

References

BUG:12-SHHJ68 - SBL-DAT-00393 ERROR WHEN ATTEMPTING TO ENTER NEW APPT FROM CONTACT/CALENDAR

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4

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

Symptoms

SBL-DAT-00393

Hi,

We are getting an error when we create a new contact, which we think is related to Siebel Data Quality. We are using SDQ matching server in real time and batch mode. Possibly after running SDQ matching server in batch mode the follow error was reproducible.

a) Navigate to My Contacts
b) Create a record which does not cause SDQ to fire in the My contacts view but is a duplicate with a Contact in the All Contacts view.(Note: even if the record is not an exact match with the contact in All contacts but is one that would cause the SDQ to fire if it were in the all contacts View then the same behaviour occurs)

Error generated: 'An end of file error has occurred. Please continue or ask your systems administrator to check you application configuration if the problem persists.(SBL-DAT-00393)'

We can also reproduce the same error in the Accounts Screen.

Can you suggest a workaround for this?

Thanks
David

Solution

Message 1

For the benefit of the readers,

Symptoms:
    The creation of a Contact in the My Contact view that is a possible duplicate of a Contact from the All Contact view generates the error message :
'An end of file error has occurred. Please continue or ask your systems administrator to check you application configuration if the problem persists.(SBL-DAT-00393)' when you step off the record.
    Saving with Ctrl + S does not generate the message but neither launch the Deduplication process.
    This also occurs with Account.

Troubleshooting:
    This has been reproduced in house and a Change Request has been opened to address this defect : 12-PX5W9V: "Contact dedup with a contact in the all view and not my contact gives SBL-DAT-00393"

Resolution:
    This Change Request has been fixed as part of the Quick Fix 18325 QF0020.
    This behavior is not reproducible with the Siebel Application 7.8.

Thank you very much for using SupportWeb,
William Dupré
Siebel Technical Support