SSO Login issue

Hi ,

After completing the setup of SSO authentication when i trying login to Metastorm . Getting the following error.

Unable

toexecute specifiedscript expression. Reason 'Error(-2146823281) : 'undefined' is null or not an object, at line 284, character 4. Source: Unavailable.' Error occurred while executing SAP.

Could any one help in resolving the issue.

Regds

Find more posts tagged with

BPM

Comments

Paul Lawrence

Hi Harry,

What SAP script(s) are you using and if you have multiple scripts in which order are they?

Harikrishnan Janardhanan

I was able to resolve the issue.

Scott_Altham

Hi Harry,

Could you pls let us know how you sorted this?

Thanks

Richard Galt

I'm getting the exact same error message after upgrading to 9.1 SR2 and setting up SSO.

I get 2 messages :-

An exception occured while executing eSSO_Web. Error 424 : Object required.

Unable to execute specified script expression. Reason 'Error(-2146823281) : 'undefined' is null or not an object, at line 284, character 4. Source: Unavailable.' Error occurred while executing SAP.

Please can someone shed some light on this as the error messages don't help at all.

Rajeshwar Potu

Hi Harry ,

Could you please provide us the with solution for above issue? we are facing same issue in our applciation after SSO set up.

Thanks,

Rajeshwar.

Chris_Pickford

I am experiencing the same issues and would appreciate to know how this was resolved.

Error messages appearing in eLog table:

Unable to execute specified script expression. Reason 'Error(-2146823281) : 'undefined' is null or not an object, at line 284, character 4. Source: Unavailable.' Error occurred while executing SAP.

An exception occured while executing eSSO_Web. Error 424 : Object required.

Hardik Bhatt

I believe possible reason could be:

- Configuring Trusted Account in SAP script

- Fail to reattach the Script file from Admin tool.

- No entry in eUser table.

- Fail to restart engine

John Hartley

We've had some issues with this the last few weeks when we upgraded from 9.1 to 9.1. SR2 so I can empathise. It seems implementing SSO particularly after an upgrade is not as straightforward as it sounds - and seeing as I personally hadn't experienced implementing sso on my machine first off (a colleague did it for me) it made it all the more harder for me.

Anyway, basically after an upgrade on your dev environment Metastorm does some weird things so you need to a) reset the identity for all the Metastorm Application pools and BPM Service Engine in IIS back to your service accounts, as if you were implementing SSO from scratch and restart IIS b) it also overwrites certain but not all lines in the config files so you need to check all of these. Be warned there is more than one...

I checked a colleagues machine who had not upgraded and used a text comparer to check the following files post and pre (which can be found in root C:\Program Files\Metastorm\BPM). In future we will copy these files to a fileshare pre-deployment in the event of any upgrade

ECL.NET\web.config

ECL.WS\web.config

Engine\application.config

IIS Extensions\DeploymentServiceConfig.xml

IIS Extensions\EngineServiceConfig.xml

IIS Extensions\Web.config

Web\Web.config

For us we needed to alter the ones in bold post deployment which had overwritten the original sso setup.

For web\Web.config we followed the steps on pages 42-43 on the 9.1 SR1 Administration Guide

1.Open the web client’s web.config file in a text editor such as Notepad. This file is located

C:\Program Files\Metastorm\BPM\Web

locate the following section of code:

<forms name="MetastormBPMAuth"

loginUrl="Login.aspx"

protection="All"

timeout="525600"

path="/">

Uncomment tag and comment out <authentication

mode="Forms"> tag, you should be left with a section of code similar to the one shown below:

Locate the following section of code:

Uncomment the tag, you should be left with a section of code similar to

the one shown below:

Save the edited file and restart IIS.

For ECL.WS\Web.config we changed the following line (around 149):

To:

For \IIS Extensions\EngineService.config we changed the following line (around13-14)

<Transport Type="

Remoting">

tcp://WORKFLOWSBLD:4001/ECL

To:

<Transport Type="

Remoting">

http://localhost/BPMEngine.Net/ECL.rem

If troubleshooting also compare all files listed above for any changes but mostly check \Engine\Application.config still contains the following line:

Check your amended Authentication js script in Administrative tools website contains the correct service account (around line 15) and is in lower case.

var trustedAccount = "adslocal\\MStorm_svc_dev";

Also that it is above eUser.js file so it renders this one first. Also check your amended sql statement is correct.

For further troubleshooting check all the settings set out in steps in Chapter 4 of 9.1 SR1 Administration Guide for setting up sso from scratch are correct. On some environments we needed to redo the steps on page 43 entitled Update Metastorm virtual directory.

Be warned also if doing an upgrade from 9.1.0 to 9.1.2 its quadruply harder, if trying to upgrade on your production servers and you have a split deployment environment. You proably need to consult all steps in Chapter 4 of the Administration Guide.to check sso is fine on all servers. And you may get an error when trying to upgrade on your process engine machine after upgrading on your web server.

Hope this helps everyone else a litte to not go quite through the same pain as myself.