Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 10 of 29 total |
ElevateDB Error #506 Cannot Lock the Session Manager (ID:1). |
Fri, Mar 4 2016 8:25 PM | Permanent Link |
Steve Gill | A customer has reported that they sometimes get this error when the application has been sitting idle for an hour or so.
Any suggestions on what could cause it? SessionType is stRemote. RemotePing is True. RemotePingInterval is 60 seconds. KeepConnections is True on Session and Database components. EDB 2.22 Build 1 RAD Studio XE7 Thanks. = Steve |
Sat, Mar 5 2016 4:32 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Steve
There was a thread way back in 2010 about this issue Path: news.elevatesoft.com Message-ID: <B0B634C6-F95D-4268-BBF9-A7D0929E2809@news.elevatesoft.com> From: "G Patena" <gpatena@achworks.com> Newsgroups: elevatesoft.public.elevatedb.sql Subject: ElevateDB Error #506 Cannot lock the session manager (ID: 1) - Again Date: Fri, 24 Sep 2010 14:19:21 -0700 Lines: 51 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-RFC2646: Format=Flowed; Original It may help Roy Lambert |
Sat, Mar 5 2016 10:18 PM | Permanent Link |
Steve Gill | << There was a thread way back in 2010 about this issue >>
Thanks Roy. I'll give it a try. = Steve |
Mon, Mar 7 2016 8:29 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Steve,
<< A customer has reported that they sometimes get this error when the application has been sitting idle for an hour or so. >> This error indicates that your application tried to execute a call using the remote session, but it was already in the middle of doing something. Are you doing any type of timer-based operations, or any threading in the client application ? Tim Young Elevate Software www.elevatesoft.com |
Mon, Mar 7 2016 12:19 PM | Permanent Link |
Charles Bainbridge | << Roy Lambert wrote:
There was a thread way back in 2010 about this issue >> The solution was:- << Problem solved. Upgraded to Version 2.03 Build 21 >> I'm interested, as I saw this error on Friday, D10S, EDB 2.22b1. Program left doing not a lot, but with open tables in remote session, running in a VM. It does however periodically, on a timer tick, run a query to update certain info displayed in the GUI. The first thing the timer tick event does is disable the timer. |
Mon, Mar 7 2016 9:08 PM | Permanent Link |
Steve Gill | Hi Tim,
<< This error indicates that your application tried to execute a call using the remote session, but it was already in the middle of doing something. Are you doing any type of timer-based operations, or any threading in the client application ? >> Yes, once every couple of minutes it refreshes a grid (although the customer may have changed this setting to do it more frequently). I have put the following code in the timer event to see if that stops it: if TEDBEngineSessionManager(dmMain.DBSession.Handle).TryLock(1, 0) then begin TEDBEngineSessionManager(dmMain.DBSession.Handle).Unlock; RefreshGrid; end; = Steve |
Tue, Mar 8 2016 3:03 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Steve
Did you have to make this post - now I have received one - first ever. Roy Lambert |
Tue, Mar 8 2016 3:10 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
I've just received my first ever 506 error. I was working in my email/news client so ignoring the app I received the error for. The client app does have threads running which will check the status of various tables. The client has three timers but they are operating locally only. One fires after a resize event, one implements a time display and the third handles alarm blinking (which is managed by flags set by posting messages back from the threads) Roy Lambert |
Tue, Mar 8 2016 3:49 AM | Permanent Link |
Matthew Jones | Steve Gill wrote:
> in the timer event Timers can be re-entrant, so you need to check that the timer is not already doing things. I use a simple boolean on the form for such checks. The lock is probably better, but I mention it just in case. -- Matthew Jones |
Tue, Mar 8 2016 7:39 AM | Permanent Link |
Charles Bainbridge | A colleague has experienced 4 of them today. All in a program which has worked without obvious problems before EDB 2.22.
|
Page 1 of 3 | Next Page » | |
Jump to Page: 1 2 3 |
This web page was last updated on Monday, April 29, 2024 at 05:23 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |