We had the same issue.   I checked the existing .pid file and it was owned by the LSF Admin user, not the LASR Admin user, so I think last time LASR was started it was done with the LSF Admin user by mistake.  Because of this, the .pid file was owned by the LSF Admin user, and so the LASR Admin user couldn't over-write the file when it tried to create the new .pid file.   Now I think there is a second issue here.  If the LASR server isn't stopped manually/explicitly in the VA Administrator, the .pid file gets left behind (when it would have been deleted if it was manually/explicity stopped in VA Administrator).  This is why you can now stop and start with any user, because every time you stop the .pid file is deleted.  I think you'll find if you leave the LASR server running but then stop the SAS services (e.g. in the Windows Services.msc) then you will fine the .pid file is not deleted, and you will then only be able to start LASR with the same user that started it last time until you start and stop LASR for the .pid file to be deleted again.   Sorry, that's a very squiggly explanation.  I hope it can be followed.   I need to validate this theory next time I can actually stop and start the Services without stopping LASR first.   Anyway, thanks for all of your info.  It helped me to find the issue. ... View more