portal.lck still exists after shutdown of LMS processes

Unanswered Question
Jul 31st, 2008

usually a .lck file indicates that a process has unique access to a certain file/process/db etc.

when stopping the lms processes there is the following file left :


is it just forgotten to be removed or does this has a certain reason?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Joe Clarke Thu, 07/31/2008 - 08:36

This file typically exists after the portal is first initialized. I haven't seen any problems with it being left behind.

Martin Ermel Thu, 07/31/2008 - 15:34

no, it is not a real problem. I stumbled accross this file, because a customer reported the following error generated by the backup software (acronis) while taking a backup of the LMS server:

ERR - failure reading file: D:\Program


(WIN32 33: The process cannot access the file because another process has locked a portion of the file. )

Interesting thing is that the processes were stopped before taking the backup and I was wondering if that could point to a deeper not obvious problem with the system.

I told the customer just to exclude that file from the backup process. I think that's all what needs to be done.

Joe Clarke Thu, 07/31/2008 - 16:12

It would be interesting to run Process Explorer to find out what process still had that file open when the daemons were shutdown. Under normal operation, it should be Tomcat that owns that lock.

Martin Ermel Fri, 08/01/2008 - 09:16

the customer reported that this problem wasn't seen from begining but suddenly started and now appears on a regular basis when a full server backup is taken. A test with a manual shutdown of dmgtd and investigation with Process Explorer does not show an abnormal behaviour. 'portal.lck' was not in use by any process. All LMS processes are stopping in less then 5 mins (around 300 devices Win2k3 AS 2CPU with 8 GB RAM :-) ). And they are stopped by a script around 30 mins before the backup takes place.

Because the real backup happens on sunday night at 02:00 am, I told the customer he should try to recreate the problem on a regular business dayto find the cause of this message;

- I will report if there are any news -but I cannot follow-up this thread the next 3 weeks :-))


This Discussion