.svn/lock file access denied - windows

I have got a SVN Server. Which worker perfect untill this morning (Last commit 10:35:39). There was a file created at the hidden .svn folder which is named "lock" at that commit time.
After the file was created I cannot COMMIT, UPDATE, CLEAN-UP and tried to login as Server admin. When I right click the file and select properties, the Security tab shows I do not have access to see the information. It is not possible to set myself as file admin. I can not delete the file.
Other checkout directories which also use the same SVN server still work.
Anyone knows how to delete this file or fix this issue?

I had a similar access denied issue when trying to move a repo from another server. I was able to load the repo by making sure I was the Owner of the target files

Related

Windows: XAMPP install folder ini file permission error, Access denied upon configuration save

After installing XAMPP to Windows 10 (all default/recommended installation attributes), I now have an issue changing its configuration after opening it.
Error: Cannot create file "C:\xampp\xampp-control.ini".
Access is denied
Clicking Save to a change in Configuration of Control Panel:
This "Configuration of Control Panel" box opens after clicking the "Config" button at the top right of the running XAMPP app:
I've tried a suggestion to run the XAMPP app with Administrator (elevated) access… but that seems like a major security issue, considering I don't know exactly what XAMPP would or could do with my files that require that permission, whether intended by the people who run XAMPP or not.
I've tried re-installing to another folder, like to C:\Users\Me, or a sub-folder like Documents or a custom one, but I just got different permissions issues that I struggled to figure out.
If you know a solution that worked for you, that avoided running XAMPP with Admin privileges, please let me know. I've gone through a handful of seemingly-related questions here but they seem to be related to MySQL/PHP questions and not Windows file system permissions.
I found a solution after noticing that the file already existed from apparently a past workaround I tried with running XAMPP as Admin... based on the permissions of the file being different than its parent folder. I discovered this by right-clicking the xampp folder or the xampp-control.ini file then selecting Properties and clicking the Security tab, then clicking into each attached user account's permissions.
So, my C:\xampp folder has these permissions: for Admin, basically full access; for my user account, Read, Execute, and Write.
The xampp-control.ini file has only Admin permissions; my user account is not attached to it.
Adding my user account to the xampp-control.ini file's Security, and adding Write permission then allowed XAMPP's config panel to save my changes.
Note that I typed my username into the "Enter the object names to select" box, then clicked Check Names; this auto-populated my username reference (?), though I'm not sure how it would work if it finds multiple results. Then I could click OK to get back to the Permissions box to add "Modify" and "Write" for it. I'm completely OK giving my user account permission to modify and write to this file through the XAMPP app.
Now, that fixes that file for that scenario; now I'm wondering if there will be other permissions issues with other files, because I noticed some other files (that I checked randomly) don't all share the same permissions for my user account!
Maybe I should have instead modified the xampp folder's permissions recursively to give my user account Write and/or Modify access (I'm not sure of the difference, Windows permissions seem far more complicated to understand and use than Linux's and Mac's do).
I think the file permissions were all set by XAMPP during install; I don't know yet that expanding permissions on certain files will not create new problems...
I found a solution after noticing that error, here is my solution
go to xampp installation folder on the c drive
Xampp Destination
then find xammp control panel.exe
Xampp Control Panel
then right click and go to properties(or press ALT+ENTER)
Click Properties
then go to compatibility and enable Run this program as an administrator
Compatibility tab
Your Problem is now fixed

Windows 10 - Permission Difference Between CommonAppDataFolder and User's Application Data Folder

My application keeps failing with an access denied error when writing to a file in Windows 10. When the file is in C:\ProgramData\, it fails. As a test, I moved it to C:\Users\username\AppData\Roaming\ and the access denied error went away. I've also noticed that when right clicking on the file when its in ProgramData, I need administrative access to delete or rename the file. In AppData\Roaming, I do not. However, there doesn't appear to be any security differences between the two folders. I can't figure out why one works and the other doesn't, any help is appreciated.
Thank you.

Laravel and Dropbox file permissions conflict

I'm running apache on my Mac and have a website folder in Dropbox so I can work from a few different machines. Laravel works if /app/storage is 775. If 750, Laravel doesn't work. However, with the permission at 775, Dropbox tries to sync and fails with an "access denied" error.
I tried enabling Dropbox selective sync and unchecked the app/storage folder but it removed it completely from my computer which obviously breaks Laravel.
How can I make Dropbox and Laravel friends again?
I was able to get Dropbox to ignore the folder by following these steps.
I ignored the sessions and views folders but I may have only needed to ignore the sessions folder. I am not sure.
The steps were:
Copy the /apps/storage/views and /apps/storage/sessions folders
to your desktop
Delete the originals in /apps/storage/views and
/apps/storage/sessions
Create empty view and session folders in /apps/storage/
Turn on selective sync via Dropbox and uncheck the
/apps/storage/views and /apps/storage/sessions
Both folders will be deleted by dropbox, re-add the copies you made
on your desktop.
Dropbox sync should not have any more conflicts and will now ignore files in views and sessions folders.

Eclipse workspace as htdocs in XAMPP not working in Mac?

I've bought a MacBook Air(I've been converted from a PC guy to a Mac) today and I have recently installed XAMPP and Eclipse for Mac and I try to set the workspace for Eclipse as the htdocs folder in XAMPP. I always get the warning:
Workspace in use or cannot be created, choose a different one!
The directory i try to set is /Applications/XAMPP/htdocs
I've been trying to set an another directory it works fine as long as it is not the one above. What have I done wrong? I want the directory above. Pls. help
The solution is this:
Go into the htdocs folder and hit CMD+I to bring up the "Get Info" window
In this window, go to the bottom right and click on the padlock icon, enter your password to unlock the permissions settings in the window
You'll see a list of users and their respective permissions. Change the "admin"'s permission to "Read & Write"
Click the padlock once more to save your changes and lock the permissions for the htdocs folder
Start up Eclipse and then select htdocs as your workspace, and
Voila! You're done.
Hope that helps.
It's likely a permissions issue. The application may not be requesting admin rights to write to (or in some way control) that directory, it may just be silently failing. Generally, you need to supply admin rights to modify anything under /Applications/.
I wouldn't recommend using /Applications/XAMPP/htdocs/ as your workspace anyway. Your workspace should either be in your home directory (Documents or perhaps even Library though the former would be more intuitive), or in some other shared location if multiple users need to access it. Bundling it with the application itself would risk losing the data during an application upgrade, or in some other way confusing the issue.
Why do you want your data in the /Applications/ directory?
The problem here is that this workspace is locked. The quick solution is to delete /Applications/XAMPP/htdocs/.metadata/.lock
The slightly longer solution is to try the following command whenever such a situation occurs:
find /Applications/XAMPP/htdocs -name "lock" -exec echo {} \;
This will show you any file in that directory that has lock in the name. Remember that hidden files start with a . (such as .lock or .metadata).
The even longer answer is that /Applications is outside of the userspace and should not be used for user documents (like code files). These should ideally be moved to somewhere in /Users or into a directory specifically created for this purpose (such as /home or /shared). I'm particularly fond of having a /Users/Shared directory for sharing files between accounts.

Delete queue in NTFS?

In my apps (VB6 and C# 2008) on Windows 2003 twice now I have seen similar behavior regarding deletion of folders containing files. My code will build some temporary folders and generates files in that folder for subsequent processing. Upon processing completion, my code will try to delete the generated temp folder. The delete operation completes without error.
However, upon further inspection, you can see that the folder still exists in windows explorer. Attempting to browse this folder results in a permission denied error. Later on the app will process another round of files and try to create the temp folder again. Unfortunately, the previous Pending Delete has not finished so trying to create the folder again results in permission denied error. The folder is not truly deleted until i close my app. As soon as the app is closed the folder gets deleted. Why are my folder delete operations not committed until the app is closed?
I wonder - is it possible you have accidentally retained a lock on that directory? that would explain why the directory cannot be removed until your app has departed.
There are some tools - try SysInternals - which will list file/directory locks. Try your app and then see if it retains a lock. I think you can then forcefully remove that lock - see then if the directory immediately disappears.

Resources