GeeKs Blogging @ dotCOM » Login

Login Failed in Dedicated Web Client : MVF Issue

Himanshu Bajpai — Tue, 30 Aug 2011 21:18:49 +0000

Recently I have met with the Problem in form of defect. The Problem was related to Record Visibility in Activity.

There were activities created for SR as a result of Email Response and properly visible in Activity List Applet under SR. We have Pick Applet in SR Applet for fetching all Email related activities. But strangely same activities were not visible in the Pick Applet.

On investigation, we found that the Applet was based on a different BC i.e. Action Special.
Seeing Different BC It is understood there is a problem of Record Visibility.
And since BC Record visibility is controlled by BusComp View Mode, there were bound to be some issues.
We compared Action and Action Special BCs BusComp View Mode.

Following was the screenshot of BC -Action Special (click to enlarge)

Siebel BC Action-special screenshot

Following was the screenshot of BC-Action (click to enlarge)

Siebel BC-Action screenshot

Above Snapshot shows the difference clearly !!

As a Solution –
1) We made Action Special similar to Action BC and added Visibilty MVF as Organization and Visibility MVL as Organization.
2) Compiled SRF.
3) Login in dedicated Client.
Shock!!!!!!!!!!!!!!
It was throwing error of Wrong User Id and Password while few minutes back it was working fine.
Login again- Shock again-error again.

3rd Time Login (3 is my lucky number ), but error again but this time my luck was better. So error changed to something different and is indicated below (click to enlarge) -

Siebel Error - BC MVF Configuration issue

Since Organization MVL was not present in Action Special, I was not able login into the dedicated client.
Actually I did the View Mode Change by Compare Object utility on Action and Action Special BC. This smartness and laziness created the whole issue because compare object put the MVL and MVF even though MVL/MVF was not present in BC.

If you change the Visibility MVL/MVF Manually then you would not allowed by Siebel to pick MVL/MVF that is not present in BC.

But it is really good for me. Since I have learnt a lesson and that is generic.

Conclusion-If the Reference of MVL or MVF is not present in BC then you would not able to login Siebel Dedicated Client and you can expect to get the below error.
—————————
User ID or password that you entered is incorrect.
Please check the spelling and try again.
—————————

Thanks for reading. Stay tuned for more articles !!

Related posts:

Siebel – Unable to login to mobile client After long time I am writing a blog… This time...

Siebel Admin Mode Flag – II – Issue Log In the last post I described about Admin Mode Flag....

Siebel – Unable to launch Local Client Hi all, I was making a fresh install of Siebel...

Siebel Assets List view – Performance issue / Cannot display records Assets Screen Load is a major problem in Siebel, and...

BI – Actuate Reports in PDF format in Siebel Hi all, Siebel is well integrated with Actuate Reports, used...

Siebel – Forcing User Logoff

Nitin Jain — Mon, 15 Jun 2009 11:26:18 +0000

Hi all,

Somebody recently asked me if there is a way that we can force the user to Logoff from the current session, under some specific conditions. My simple research in Siebel Tools and around it brought up the following alternatives.

Vanilla Business Service Methods:
1) BS Name = LS Medical Product Issue Service
Method = Logoff

2) BS Name = Mktg Saw Service
Method = Logoff
Input = ServerId (This is the Analytics Web Server Id from which to Log off)

3) BS Name = FINS IBC Login Adapter
Method = Logout

I saw this as a very poweful Business Service with methods like, GetLoginId, GetLoginProperties, GetLoginState, GetNewMessageId, Login and of course, Logout. I could not find too much documentation around this BS in both the Bookshelf and Metalink. I will research more and try to post my findings here.

4) BS Name = Communications Client
Method = PreferenceLogout

With the numerous methods to this BS, it seems more related to the Call Center application and CTI.

5) BS Name = SAWSessionServiceSoap
Method = Logoff

All the BS and the methods above can be directly used in Workflows or scripts. One immediate utility that I can think of is to forcibly logoff user sessions whenever we notice a user trying to access data or views that he should not be allowed to access.

We noticed in our implementation that the Logout method sends the SWECmd = Logoff to the Siebel Web Engine. This seems to be the recommended solution by Oracle above all the others. We can easily call the following code in Browser Script, when trying to do this through scripting for our purposes:
top.location = “start.swe?SWECmd=Logoff”;

We also noticed the Command, “Logout” in the Tools Object Explorer which can terminate the user session.

Please add to this in case you feel it is inadequate, or missing some details. I will update this post with the findings as we progress around this.

Related posts:
Siebel – Automatic User Logout Logging out a user automatically, when the user does not...

Siebel – DefaultFocus – User Property In Siebel Application, whenever you navigate to a screen, the...

Siebel – FINS Teller UI Navigation Siebel is POWERFUL! Now, need I even say that? And,...

Siebel – Fetch Active view properties Hi, Working on a typical requirement recently, I came across...

Siebel – Fetch Active view properties – II We discussed about fetching the values from the active view...

Siebel- Close Browser window when logging off

Madhvi Arora — Fri, 22 May 2009 04:43:16 +0000

In case of standard interactivity applications like eSales , eService, when user logs off, he is directed to the page through which he logged in the application. But there is a requirement to close the IE when user logs off. Here we are doing this for eSales Application. This can be done in following manner:

•         Create a new .swt file say “LogOffDestination “ which contains following HTML script:

•         Now place this .swt file in \WEBTEMPL\, \WEBTEMPL\ and \WEBTEMPL.
•         In Siebel tools, navigate to “Web Template” object in Object Explorer. Create a new web template say “LogOff Destination” and give this new “LogOffDestination.swt” in the “File Name” property of the “Web Template File” object.
•         Now Navigate to “Web Page” object in Object Explorer. Create a new Web Page say “Log Off Destination” and set “LogOff Destination” Web Template you just created in “Web Template” object.
•         Now navigate to “Application” object in Object Explorer. Query for “Siebel eSales”. Now change web page in “Logoff Acknowledgement Web Page” from the given value to “LogOff Destination”.
•         Now compile “Web Template”,”Web Page” and “Application” objects in the srf.
Now when you log out from the application, it will close the IE.

Related posts:
Siebel – Remove About SRF Window In my previous post, I had discussed as to how...

Siebel – About SRF Window – Remove data Okay. This is something those who like to toy with...

Siebel – Enable Detailed Logging – Local Very often we come across scenarios wherein the process is...

Siebel – EnableServiceArgTracing – Logging Messages Hi, We have already discussed at quite a length the...

Siebel – Forcing User Logoff Hi all, Somebody recently asked me if there is a...

Siebel – Unable to launch Local Client

Nitin Jain — Sun, 26 Apr 2009 07:09:20 +0000

Hi all,

I was making a fresh install of Siebel yesterday, when something very strange happened. I could not launch my Local Client. This was even more strange because:
1) I could successfully launch my Sample Client
2) I could successfully launch my Local Client when invoking it in Debug mode from within Siebel Tools!

I was installing an instance of Siebel 7.8.2 for the concerned. My operating system in use is Windows XP.

My Sample client was opening successfully. This meant my Internet Explorer settings are fine, and the executables to execute one after the other are installed fine.

I could launch my local client from within Tools using the same CFG file and the login parameters indicated that my configuration of the CFG file was fine, and I was using the correct login credentials. This also concluded that it was not an issue of license keys. I was left in the blue unable to think of as to what the possible reason could be.

I tried increasing the Logging level to maximum, trying to find out what is really hampering the launch of local client. I noticed that there were no errors being indicated in the log files being created. Just that the log files would be created successfully for some time, and then, the entire process would halt. The log files stopped being updated after a certain point, without indicating any error.

On comparing the log files of client launch in debug mode and without debug mode, the only difference was that the log file size in Debug mode was much larger, the log files were being updated properly right till the end and that the debug mode Local client was working fine.

Now, the million dollar question: then how was the problem resolved?

On top of the base install of 7.8.2, I installed the patch 7.8.2.8.
When I tried launching the Local client now, it worked beautifully without hanging.

I am still hunting for the possible difference that the patch installation made, which enabled the successful launch of my Local Client. Any pointers from anybody?

Related posts:
Siebel – Unable to login to mobile client After long time I am writing a blog… This time...

Login Failed in Dedicated Web Client : MVF Issue Recently I have met with the Problem in form of...

Siebel – Enable Detailed Logging – Local Very often we come across scenarios wherein the process is...

Siebel – Unable to check out objects I will discuss the following most prominent ways to enable...

Siebel – Run Case Insensitive queries This is a nice tip I ran across. All the...

Siebel – License keys don’t work / are invalid

Nitin Jain — Tue, 21 Apr 2009 17:12:06 +0000

So, here I am again. After the fabulous solution to enter license key in Siebel by Prachi, I guess I would also just put an icing on the cake!

Okay, Prachi’s post, is valid in case you HAVE the license keys available. What do you do in case you DON’T HAVE the license keys in the first place!!

This is what this post is all about, entering Siebel without a valid license key.

I had this problem once when I was working on Siebel v 7.8. At that time, Siebel 7.8 had been newly launched in the market, and we were having some issues getting all the license keys being made available. It was all tied up in some project politics (not literally, I mean just that the process in the organization was cumbersome) and delays, hampering our project success.

I had the installation of Siebel 7.8 Tools and Client in front of me, and everything was working fine. The problem was, we could only access a few screens for which we had the license. I was however, interested in looking at some of the areas which were unfortunately unavailable since we did not have the appropriate license keys.

Never to be tied down in chains, I tried something which nobody sane would recommend to anybody sane lest they risk to destroy their installations! I did something which I doubt you would get on any other forum or blog, and definitely not on Oracle sponsored websites or links.

I had been working on Siebel 7.7 for a long time then. With an increased focus on Siebel v7.8 and v8.0, I noticed that ORACLE CORP. (R) had reduced its focus on the older versions. So much so, that all inclusive lifelong license keys were now easily available for Siebel v7.7. I was surprised initially, and smiling the next moment!

I entered the very same license (all inclusive) keys of Siebel 7.7 into Siebel 7.8. Guess what, it seemed I had just entered the forbidden world of dwarfs and fairies, with innumerable Siebel screens in front of me in the sitemap, with the entire Siebel functionality exposed even for Siebel 7.8! Now these were lifelong keys of Siebel 7.7 which will never expire, AND are all-inclusive. The same behaviour was carried forward in Siebel 7.8 as well. However, I doubt if it would expose the Siebel 7.8 specific functionality with the 7.7 license keys. Only functionality common to both versions would be exposed, I would guess.

In case you need help on as to how to enter license keys in Siebel, please refer Prachi’s post here. I believe it’s a beautifully written post. We already have 2 more workarounds suggested in the comments there.

Please note that this is my personal solution, and in case you are serious about implementing this, you would be doing so at your own risk. I must say that please read the Disclaimer on this website carefully before implementing this highly insane solution.

I am just waiting to see as to how long it is before ORACLE CORP. (R) finds out about this post! Entering Siebel without having a valid License key, now this is new!!

Cheers

Related posts:
Siebel – Adding License Keys to Sample I am glad to be associated with Geeks Blogging @...

Siebel – Scrolling between records – UP and DOWN Generally in Siebel Client, we very often have the need...

Siebel – EAI Queue – a Critique’ I had introduced the Siebel EAI Queue and its usage...

Siebel – Unable to launch Local Client Hi all, I was making a fresh install of Siebel...

Siebel – Why Upgrade? – Part I Hi all, I am back to Siebel Technical Stuff after...

Siebel – Adding License Keys to Sample

Prachi Sharma — Mon, 20 Apr 2009 02:46:30 +0000

I am glad to be associated with Geeks Blogging @ dotCOM. This is my first post here.

This is a very generic problem that we all come across. Adding License Keys in Siebel Sample Database. This is at times a little difficult and workarounds have to be used.

There are a number of ways that you can enter License Keys in Siebel:
1) When you are installing Siebel, and try to log in for the first time, it asks for valid License Keys. You can enter multiple license keys at this step.
2) Log into Siebel Web Application. Navigate to Sitemap -> Administration – Application -> License Keys.
3) Log into Siebel Tools. Navigate to Help -> Technical Support -> License Keys

However, you will notice that only the first option works in case of Sample Database. The route through Siebel Client and Siebel tools are greyed out. The first option has the drawbacks in case, the license keys entered are not lifelong, and we may need to enter new license keys after some time. Also, we may need to add additional functionality in Siebel using new license keys.

The solution is to login into Siebel Tools. Once logged in, press ‘Shift’. Keep it presses while navigating to Help -> Technical Support. Now, if you notice the ‘License Keys’ button is active. Press License Keys, a new dialogue box will open. Here, you can add new, delete or edit existing license keys. This will solve the problem.

Related posts:
Siebel – License keys don’t work / are invalid So, here I am again. After the fabulous solution to...

Siebel – Autosave Opportunity data – Sample Code This is a follow up post on my previous post,...

Siebel – Scrolling between records – UP and DOWN Generally in Siebel Client, we very often have the need...

Siebel – Unable to launch Local Client Hi all, I was making a fresh install of Siebel...

Siebel – Remove About SRF Window In my previous post, I had discussed as to how...