Date
1 - 7 of 7
Action locks up
|
Rob Westland
Hi,
I'm here at a customer. Server is Windows 2019 Actian is 15.11 Magic 9.4 SP7 They moved a week ago from an old server to this one. And now they have problem with locking up Pervasive This mostly happens when about 30-40 users are logged in. Suddenly all connections to the database are lost from the clients. A session started at the server locally keeps runnning. When you try to restart Magic, the application freezes at startup. The mff is load, main program is started and all files in the main programs are opened. But then Magic tries to read from that files and there it stops. Magic is waiting to read the records. The dbms setting in magic.ini for to the database was wrong. It said: locking: both. I'm not sure (yet), but it looked that when the mglock.dat was deleted for the users, Magic continued But what is the best place to put the mglock.dat? And where to put the mgres.loc? And I never thought about it, but where is this file needed for? At the previous server these settings where the same, but nothing ever happened. Rob |
|
|
|
Rob,
toggle quoted message
Show quoted text
I recommend setting Magic Locking to None and to direct each user's Magic Lock File (named MGLOCK.DAT, by default) to the user's local TEMP folder via Logical Name. Regarding the Resource Lock File (named MGRES.LOC, by default), this file MUST be located in a shared location, Read|Write accessible to all users, else the Lock() and Unlock() functions will not. Steven G. Blank
Ξ SGBlank Consulting On 3/1/2023 8:55 AM, Rob Westland
wrote:
Hi, |
|
|
|
Rob Westland
ok, thanks.
I changed the settings and today and everyone has a local mglock.dat. But the problem occurred again, suddenly all client connection are lost. The Pervasive connection. I looked at the Zen monitor, and within a second all where lost accept the local connections. The old Pervasive database server is still running, so we want to use that server to test everything. But on the client is version 12.11.026 running and the Pervasive server is 1211.026. Are those compatible? And is Client 12.11.026 compatible with Zen15? Rob |
|
|
|
Rob Westland
Forget my previous question. That was not correct.
What is compatible? Client V12 -- Server V15 Client V15 - Server V12 Rob |
|
|
|
Rob
toggle quoted message
Show quoted text
Client needs to be a less than or equal version to the server, otherwise the client could issue requests the sever doesn't understand. However, Magic's gateway (until recently) was using very old base level commands.
Keith
From: main@magicu-l.groups.io <main@magicu-l.groups.io> on behalf of Rob Westland <magicrob@...>
Sent: Thursday, March 2, 2023 8:10:50 AM To: main@magicu-l.groups.io <main@magicu-l.groups.io> Subject: Re: [magicu-l] Action locks up Forget my previous question. That was not correct.
What is compatible? Client V12 -- Server V15 Client V15 - Server V12 Rob |
|
|
|
Rob Westland
We are using Magic 9.4.
Do think that a client V12 will work with Server V15? This should be for about a month. At the and of the month all clients get a new image. Rob |
|
|
|
Rob,
toggle quoted message
Show quoted text
According to the v15 Release Notes, v15 Servers are supported with v14 clients. Full Stop. This reflects the historical MO of servers first and clients last. I would strongly recommend NOT running a v12-v15 difference for either clients or servers. Steven G. Blank
Ξ SGBlank Consulting On 3/2/2023 5:26 AM, Rob Westland
wrote:
We are using Magic 9.4. |
|
|