SBL-DAT-00326: View Map is not initialized.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-DAT-00326

We are in the process of upgrading our Siebel 7.0.4 application to Siebel 7.7.2. After the sucessful upgrade and the repository merge, I ran the Phys. schema upgrade and it finished successfully.

I compiled the SRF (selecting all the objects) and placed it in the Siebsrvr\Objects\ENU directory with the name Premier.srf. Also, placed the scripts under the SWEApp\Public\ENU directory. Then changed the repository file name in the uagent.cfg in the Siebsrvr\Bin\ENU directory with Premier.srf.

Now, after I restarting the services (IIS, App Srvr and Gateway Srvr), am not getting any views at all. I got the following error message.

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

View Map is not initialized.(SBL-DAT-00326)"

I tried to use this SRF with the dedicated client and it works fine.

Solution

Message 1

For the benefit of the reader:

Customer upgraded from Siebel Application Version 7.0.4 to Siebel 7.7.2. After the successful upgrade a new SRF file was compiled. Using this file user log into Dedicated Client and was able to use the application. With the same srf and database when user try to connect login using thin client it failed with following error.


View Map is not initialized.(SBL-DAT-00326)"

Following steps were taken to resolve this issue.

a) Customer was suggested to enable following tracing using Server Manager command :

Change evtloglvl %=5 for comp <AliasNameOfObjectManager>

This will increase required level of tracing for Object manager that user uses to connect.

b) After above tracing was enabled, user logged in and got the same error as above. The object manager log for this user session was provided to Siebel Technical Support.

c)    In the object manager log had following error

            *******

ObjMgrLog    Error    1    0    2005-01-14 12:33:08    (objdef.cpp (14625)) SBL-DAT-00607: Join 'S_PERIOD' in business component 'Opportunity' has the multi-valued field 'Quarter' as the source field.

ObjMgrSessionLog    Error    1    0    2005-01-14 12:33:08    (model.cpp (608)) SBL-DAT-00326: View Map is not initialized.
            ********
After customer corrected the Join property in the Opportunity buscomp, the application works fine.

Thanks
Rajpal Bal
Siebel Technical Support

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] FIN
Database: IBM DB2 8.1 FixPack 3
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.2

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

Symptoms

SBL-DAT-00326

Hi

We have craeted users in Siebel and assigned them Responsibility and Position.

After the insitial login they are getting an error message "View Map is not initialized.(SBL-DAT-00326)".
I spoke with TAM and also did some research on supportweb, but could not find any solution.
This is happening for a very set of users, but this may be significant and can effect the rest of the user base.

If you login as SADMIN from the same machine it works fine and we see the welcome screen and sitemap, but if you login as a specific user it gives me the above mentioned error message.

Thanks
Sai

Solution

Message 1

We have craeted users in Siebel and assigned them Responsibility and Position. After the insitial login they are getting an error message "View Map is not initialized.(SBL-DAT-00326)". This is happening for a very set of users, but this may be significant and can effect the rest of the user base.If you login as SADMIN from the same machine it works fine and we see the welcome screen and sitemap, but if you login as a specific user it gives me the above mentioned error message.
For the benefits of other users:
The non-working user ids were working at some point. When asked what happened around that time, they said they did a database restore. When looking at the database restore, the users that were not working had duplicate user ids - one in upper case and one in lower. Once the lower case ids were deleted from the database the behavior was corrected and users logged in properly.