SBL-SFR-00118: A newer version of software is required



Applies to:


Siebel Wireless - Version: 7.5.3 [16157] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000

Product Release: V7 (Enterprise)

Version: 7.5.3 [16157]

Database: Oracle 9.2.0.2

Application Server OS: Microsoft Windows 2000 Server SP 4

Database Server OS: Compaq Tru64 UNIX



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



Symptoms


SBL-SFR-00118We tried to synchronize handheld device with mobile client for the first time and got error
message as follow:

10:52:03     INFO: 2003 m. spalio 21 d.
10:51
10:52:03     INFO: Attempting to login using Companion
Sync.
10:52:03     INFO: User =
gvilius
10:52:04     INFO: TXN Error Level =
1
10:52:05     INFO: Connected to device. : Message ID =
304
10:52:05     INFO: Checking for Local
Database
10:52:05     INFO:
C:\sea752\client\bin\ENU\salesce.cfg
10:52:05     INFO:
ENU
10:52:06     INFO: Cfg file is loaded. : Message ID =
291
10:52:06     INFO:     Data Source =
Local
10:52:06     INFO:     Connect String =
C:\sea752\client\local\sse_data.dbf -q -m -x NONE -gp 4096 -c40m
-ch60m
10:52:07     ERR: A newer version of software is required. Press
Yes to upgrade now or press No to continue.

Component Version Information:
Component:
Siebel Sales CFG__ENU, Current Version: 0.0, Minimum Version: 100, Maximum Version: Any
Version
(SBL-SFR-00118)






Cause


Configuration/ Setup


Solution



Message 1


For the benefit of other readers:



The customer tried to synchronize handheld device with mobile client’s
local database for the first time and received the following messages:



10:52:06     INFO: Cfg file is loaded. : Message ID = 291

10:52:06     INFO:     Data Source = Local

10:52:06     INFO:     Connect String = C:\sea752\client\local\sse_data.dbf -q -m -x NONE -gp 4096 -c40m -ch60m

10:52:07     ERR: A newer version of software is required. Press Yes to upgrade now or press No to continue.



Component Version Information:

Component: Siebel Sales CFG__ENU, Current Version: 0.0, Minimum Version: 100, Maximum Version: Any Version

(SBL-SFR-00118)



Per the error messages, a new upgrade kit had been distributed and the
version checking avoided the synchronization. As this was a Development
environment, the customer commented the “ComponentName” parameter in the
[Siebel] section of the *.CFG file to avoid the version checking
functionality.



After this, the customer received the following messages in the Syncmanager_Log.txt file:

...

15:41:50     WARN: Could not read AppBinDir from device registry. Proceding with install using default install directory.

...

15:42:43     INFO: Processing transactions. : Message ID = 26

15:42:44     ERR: Rapi retured S_FALSE.

15:42:44     ERR: CreateProcessFailed

15:42:44     ERR: Error detected while communicating with the device. Sync cannot continue.

Please close sync, disconnect from the device and reconnect.

Perform sync again.



<Continued 1/2>


Message 2


<Continued 2/2>



15:42:45     ERR: One or more of your handheld transactions have failed.
Please make the necessary changes and synchronize again. : Message ID =
13



The first warning message indicated that the Siebel Handheld Application
was not installed successfully in the handheld device. And the
remaining error message indicated that the communication between the
synchronization program in the client machine and the handheld device
could not be established successfully.



The customer re-installed the Siebel Handheld Application in the handheld device and the synchronization worked fine.



Thank you.










Applies to:


Siebel Remote - Version: 8.0.0.5 SIA [20420] to 8.1 [21039] - Release: V8 to V8
Information in this document applies to any platform.



Symptoms




The requirement was to use Siebel anywhere to distribute new srf to local users.

To accomplish that we followed following steps:

Created an upgrade kit, Siebel Client Repository File__ENU 1, having
Upgrade Kit Components Siebel Client Repository File__ENU and having
Upgrade Kit Items Titled: 1. Install Siebel SRF file(ENU) and 2.
Generate browser script and having Upgrade Kit Item Parameters 1. File
Name and 2. Destination





After that I created Upgrade configuration Siebel Client Repository
File__ENU 1 and added Upgrade Component : Siebel Client Repository
File__ENU, added an employee USER1 and distributed it.



Now when I login as USER1 to dedicated client I do get a message A
newer version of software is required. Press Yes to upgrade now or press
No to continue.

When I press Yes nothing comes up and when I press no I get read only client


Cause







Based on the log file attached we and see that it properly detects the upgrade kit:



Upgrade Component: Siebel Client Repository File__ENU, Min Version: 1, Max Version: 1, Current Version: 0

UpgradeLog UpgradeInfo 3 000000024b700668:0
2010-02-08 16:43:14 An upgrade to the component (Siebel Client
Repository File__ENU) is requires upgrade. Its current version is 0. The
required new version should be 1.

ObjMgrSessionLog Error 1 000000024b700668:0
2010-02-08 16:43:15 (upgchkvr.cpp (184)) SBL-SFR-00118: A
newer version of software is required. Press Yes to upgrade now or
press No to continue.



Component Version Information:

Component: Siebel Client Repository File__ENU, Current Version: 0, Minimum Version: 1, Maximum Version: 1

And it properly locates the kit:



The above error message indicates there was an issue with the filesystem.


Solution


The problem was due to incorrect filesystem.
They were able to to resolve the issue by changing the File System
FileSystem = C:\PROGRA~1\Siebel\8.0\WEBCLI~1\bin\att

To

FileSystem = \\ps001\FS\att

After making the above changes they were able to download the upgrade kit.


References


NOTE:475727.1
- My client is getting unable to download the upgrade kit... why do I
get these error messages when attempting to download an upgrade kit?

useful document

תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

FINS Data Transfer Utilities

תמונה
The best thing while working on siebel is you are never short of options. Recently we had requirement of updating a Service request from contact. Finally we did that using "EAI Siebel Adapter" business service. However during that time i came across another business service "FINS Data Transfer Utilities" popularly known as DTU business service. As i was not having prior knowledge of it going by the rule of not learning swimming lessons while drowning i decided not to go for it. Lately i have tried to explore this service and trust me it can do wonders. Here is a sample example update of Service Request from contact. We need to follow below steps in order to understand strength of this business service. 1 - Navigate to Site Map. Go to Administration - Application -> Data Map Administration tab. Create a new Record with following options: Name: Service Request Test Source Business Object: Contact Destination Business Object: Service Request Here the source business
המשך לקרוא

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima
המשך לקרוא

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of
המשך לקרוא