Error after update to 9.1SR1

Thilo_Menges

Hi,

the webinterface starts after update from 9.1 to 9.1SR1 with the following error message (after login):

Method not found: 'Void Metastorm.ECL.IECLSession.set_ClientType(System.String)'.

Stack:

Error Message: Method not found: 'Void Metastorm.ECL.IECLSession.set_ClientType(System.String)'.

Stack Trace: at Metastorm.Web.BpmContext.get_EngineSession()

at Metastorm.Web.Default.Page_Load(Object sender, EventArgs e)

at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)

at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)

at System.Web.UI.Control.OnLoad(EventArgs e)

at Metastorm.Web.BpmPage.OnLoad(EventArgs e)

at System.Web.UI.Control.LoadRecursive()

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Environment:

Win2003 R2 SP2

SQL 2008

Thilo

Find more posts tagged with

BPM

Comments

Brian Mellert

After we upgraded to 9.1.1 from 9.1.0.1 nobody can log into anything.

I'm working with Helpdesk trying to get it resolved now.

Thilo_Menges

Hi,

it looks like that the setup routine does not register some new dll's into the GAC (global assembly cache)

This Metastorm.ECL.dll version is in the GAC after installing BPM 9.1SR1

[assembly: AssemblyFileVersion("9.0.3.1611")]

The latest available Metastorm.ECL.dll i have found was:

[assembly: AssemblyFileVersion("9.1.1.1692")]

Maybe some other DLL's have the same problem!?

Thilo

Thilo_Menges

Workaround to solve the Problem:

Uninstall BPM v9.1.1 completly
Remove all Metastorm assembly from c:\windows\assembly (rigth mouse click --> uninstall)
fresh install v9.1
update to 9.1SR1

This way works for me, tested on W2K3R2 and W2K8R2.

I think the there was a problem during the update from 9.0.3 to 9.1 to remove the old v9.0.3.x assemblies from GAC

Thilo

Brian Mellert

Our issue ended up being, or appear to be, that the autoproc.xml attachment got corrupted/out-of-sync or something. Once we removed that and euser.js and added euser.js back, things started to work again. We haven't identified any other issues in upgrading to 9.1.1 ourselves.

(Now to try to check out the "mobile device" features ... there appears to be little documentation on it.)