יום חמישי, 4 באוקטובר 2012

SBL-SFR-00117: The local Siebel database was not found.





Applies to:


Siebel Remote - Version: 7.7.2.6 [18372] and later    [Release: V7 and later]
z*OBSOLETE: Microsoft Windows Server 2003

Product Release: V7 (Enterprise)

Version: 7.7.2.6 [18372]

Database: Oracle 9.2.0.6

Application Server OS: Microsoft Windows 2003 Server SP1

Database Server OS: Sun Solaris 8



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



Symptoms


SBL-SFR-00117, SBL-SEC-10001Hi,

We're about to introduce Danish mobile web clients but we ran into some problems.
From a fresh client installation, I open up the danish login window, enter username and password
and choose to connect to "Local". (I have not yet downloaded a local dbf file). I get the error
message "Wrong user name and password. Please check the spelling and try again." The log file
displays the following:
2021 2006-09-04 13:30:06 2006-09-04 13:30:20 +0200 00000004 001 003f
0001 09 siebel 3984 1324 C:\Sea770\client\log\siebel.log 7.7.2.6 [18372]
DAN

ObjMgrLog    Error    1    0    2006-09-04
13:30:06    (wccon.cpp (2025)) SBL-SFR-00117: Den lokale Siebel-database blev
ikke fundet. Vil du tilslutte til Siebel Remote-serveren for at initialisere den lokale
database?

GenericLog    GenericError    1    0    2006-09-04
13:30:06    (secmgr.cpp (2288) err=7010018 sys=126) SBL-SEC-10018:
1%

GenericLog    GenericError    1    0    2006-09-04
13:30:06    (secmgr.cpp (2360) err=7010001 sys=0) SBL-SEC-10001: Der opstod
en intern fejl i godkendelsesundersystemet i Siebel-programmet. Kontakt systemadministratoren for
at få hjælp.

I'm expecting the message "Local database was not found, do you wish to
connect and download? YES/NO". It works fine for our ENU, SVE and ITA clients, but not the
Danish. We have tested on several different computers, but the error is the same.
Please
advise.






Cause


Change Request #12-1FZ5FBC


Solution



Message 1


For the benefit of other readers



The customer was using the Danish 7.7.2.6 Mobile Web Client. When
connecting to the Local Database for the first time, it failed to
perform the synchronize steps to download the local database.



Change Request #12-1FZ5FBC has been opened to address this as a Product Defect.



The workaround is to initialise the Local Database by running the Remote Icon that executes the ‘siebelsync.exe’ executable.



Regards,








Applies to:


Siebel Tools - Version: 7.7.1 [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000

Product Release: V7 (Enterprise)

Version: 7.7.1 [18306]

Database: Oracle 9.2.0.4

Application Server OS: Microsoft Windows 2000 Advanced Server

Database Server OS: Microsoft Windows 2000 Advanced Server



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



Symptoms


SBL-SFR-00117, SBL-DCK-00182, SBL-SEC-10001Hi,

We are facing issues with the tools after initializing the local extract. We were
able to connect Tools to sample database and once we initialized the local extract , we were not
able to connect Tools to the Sample Database or Local Database.
Afetr starting the tool, it
will ask for username/ password and then it opens for a moment and disappears immediately.



Other info:

Oracle Version : 9.2.0.4 (Server & Cleint)
Siebel Version -
7.7.1 with Hotfix

Thanks,







Solution


For the benefit of other readers



The following workaround has been found for the Tools crash.



1) Edit the "SSD Local Db default instance" DSN

2) Put some junk characters in the "Database name" under Database Tab. Please find the Screen Shot attached.

3) Once Connected with the tools remove the junk characters for the Check-in/check-out.



Investigations have shown that Tools 7.7 makes a ODBC connection during startup. This was not the case for previous versions.



In a working env the ODBC connection will connect to the server db. In
the customer case with the error Tools tries to connect with the ODBC to
the local db and crashes then.





As this issue was not reproducible inhouse, no change request has been
logged. If you are affected by this error, please log a service request
in Oracle Support



Thank you

אין תגובות:

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