Macola issue
Tim Trinka
We had a server reboot over the weekend and one of our users was not out of Macola software when this occurred. When they go back into the module to work today she gets the message:
APIDFIL Locked Record in Way…Waiting
Any input on how to clear this?
Thank you in advance for the info.
Thank you,
Partners. Expertise. Teamwork. Solutions.
Andy Roth
from a google search
https://www.tek-tips.com/threads/locked-record-in-way.538778/
Hope it helps
Andy
--
You received this message because you are subscribed to the Google Groups "PSIUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to psiusers+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/psiusers/DM4PR19MB5811C4DB950CCB3A8A3AABECC9AA2%40DM4PR19MB5811.namprd19.prod.outlook.com.
Tim Trinka
Andy,
Thanks for the reply. I did the first step in deleting users from the root directory and this did not work. I am not running Novell so I am unsure if the second solution is valid or if this is something I can try.
To view this discussion visit https://groups.google.com/d/msgid/psiusers/f41082f4-e01b-428b-ab38-91548ebae668%40andyroth.com.
Randall Blinn
Hi Tim;
I’ve retired, so I’m not doing much PSI/Macola support anymore, but I saw your post and thought I could help.
I run this script at a client’s site every night to clear some “locking” issues that they have in Macola:
exec sp_who2
USE master;
DECLARE @kill_1 varchar(8000); SET @kill_1 = '';
SELECT @kill_1 = @kill_1 + 'kill ' + CONVERT(varchar(5), spid) + ';'
FROM master..sysprocesses
WHERE dbid = db_id('data')
PRINT @kill_1
EXEC(@kill_1);
The “exec sp_who2” will give you a list of users connected in SQL (and the db they’re using, I believe)
In the next group of commands, you’ll need to change the db_id to the name of your Macola db – here it is “data”. I have highlighted the four characters in red/bold.
When you “Print @kill_1” it will give you a list of the SPID’s that it is about to Kill
The EXEC(@kill_1) will remove any LOCKS on the list of SPID’s in the @kill_1 varable.
OTHER OPTIONS:
Get EVERYONE out and reboot SQL.
I’m not sure what version of SQL you have, so I would hope that the commands outlined above will work.
FYI – I’ve had TWO PSI Users with PSI issues they couldn’t resolve and NO PSI SUPPORT, so be careful or you’ll be doing everything manually.
GOOD LUCK!!
Randall G Blinn
GRAPHIC COMPUTER CONSULTANTS, INC.
To view this discussion visit https://groups.google.com/d/msgid/psiusers/DM4PR19MB58116E76D9A95196C9317425C9AA2%40DM4PR19MB5811.namprd19.prod.outlook.com.