I have just installed Build 20 of Elevate 2.03 and now when I try to run the EDBMGR, after log on as Administrator I get the error "506 Cannot lock the session manager (ID: 1)"? Going back to Build 19 cures the problem but any idea why Build 20 wont let me connect to my database anymore?


Regards

Edward Jones

Same here. Getting it on Windows 2003 Server as well as a Windows XP
SP3 server

--
Jan


Edward Jones wrote:

> I have just installed Build 20 of Elevate 2.03 and now when I try to
> run the EDBMGR, after log on as Administrator I get the error "506
> Cannot lock the session manager (ID: 1)"? Going back to Build 19
> cures the problem but any idea why Build 20 wont let me connect to my
> database anymore?
>
>
> Regards
>
> Edward Jones

Edward Jones wrote:

<<I have just installed Build 20 of Elevate 2.03 and now when I try to run the EDBMGR, after log on as Administrator I get the error "506 Cannot lock the session manager (ID: 1)"? Going back to Build 19 cures the problem but any idea why Build 20 wont let me connect to my database anymore?>>

That is quite peculiar because I was having problems with that very same error message in EDBMGR build 19, at the end of every script I ran and Tim put a correction into build 20 that has cured the problem.

regards,
Ian Turner

Edward,

<< I have just installed Build 20 of Elevate 2.03 and now when I try to run
the EDBMGR, after log on as Administrator I get the error "506 Cannot lock
the session manager (ID: 1)"? Going back to Build 19 cures the problem but
any idea why Build 20 wont let me connect to my database anymore? >>

Is this with a remote or local session ?  If it is a remote session, can you
replicate this with a 127.0.0.1 connection to the ElevateDB Server running
on the same machine ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Edward,

We've found the problem - it's with the TEDBSession.OnLogin event.  If it is
trigger because the user name and password aren't specified, or aren't
correct, then you'll see this issue.

I'll have a fix for this in a day or so.  Thanks to Uli Becker for finding
this one.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<I'll have a fix for this in a day or so.  Thanks to Uli Becker for finding
this one.>>

This mean a 2.03 B21 or fix is in 2.04 B1?

Thanks.

Tiago,

> This mean a 2.03 B21 or fix is in 2.04 B1?

Since 2.04 B1 was out before the bug was found, I am sure that the fix
will be in 2.04 B2.

Uli

Uli,

<<Since 2.04 B1 was out before the bug was found, I am sure that the fix
will be in 2.04 B2.>>

This is a problem. 2.04 has breaking changes (and some pretty new features). I can't deploy to my customers a very just born version as 2.04. I just need an stable one, just 2.03.21 should be or at least a way to download build 20, which is more stable than build 19 I use currently.

Tiago,

> This is a problem. 2.04 has breaking changes (and some pretty new features). I can't deploy to my customers a very just born version as 2.04. I just need an stable one, just 2.03.21 should be or at least a way to download build 20, which is more stable than build 19 I use currently.

I understand; we have to wait for Tim's answer.

Uli

Tiago,

<< This mean a 2.03 B21 or fix is in 2.04 B1? >>

Both 2.03 B21 (today) and 2.04 B2 (tomorrow).

--
Tim Young
Elevate Software
www.elevatesoft.com