Skip to main content

WAS Listener error

  • April 5, 2021
  • 2 replies
  • 0 views

Forum|alt.badge.img

Hi, 

My team and I started using the WAS utility in some of our projects and I´m getting the error on the listener:

"Unable to create lock. Another instance is probably running alredy"

The thing is that I don´t have another instance. 

I need to know how to solve this, I´m looking at the task manager and theres no waslistener.exe process.

Regards.

2 replies

Michael Taylor

Hi, 

My team and I started using the WAS utility in some of our projects and I´m getting the error on the listener:

"Unable to create lock. Another instance is probably running alredy"

The thing is that I don´t have another instance. 

I need to know how to solve this, I´m looking at the task manager and theres no waslistener.exe process.

Regards.

To protect against multiple listeners running against the same project folder, a file named .WASlistener.lock is created. The file is created as a hidden system file so by default is not seen. As the operating system is meant to delete the temp file when the process exits, I am not sure why it would remain. Was there a system crash?

You should be able to open a command prompt and use the following command in the project folder to make the file visible before deleting it. Once the file is gone, the listener should start normally.

attrib -s -h .WASListener.lock

Mike


Forum|alt.badge.img

To protect against multiple listeners running against the same project folder, a file named .WASlistener.lock is created. The file is created as a hidden system file so by default is not seen. As the operating system is meant to delete the temp file when the process exits, I am not sure why it would remain. Was there a system crash?

You should be able to open a command prompt and use the following command in the project folder to make the file visible before deleting it. Once the file is gone, the listener should start normally.

attrib -s -h .WASListener.lock

Mike

Hi Mike, thanks for the help.

I think I had to restart the pc for an OS update and I forgot to close the listener.