Solved! Go to Solution.
I was referring to anyone else directly connected to your file geodatabase, not through the web services. If these file geodatabases are only accessed by the web service, then stopping the web service should let you delete the file geodatabase.
I believe Zach was suggesting to delete the contents of the file geodatabase, then delete the empty geodatabase container.
Jamal, as Nidhin suggested, you need to ensure no ArcGIS Server process is still using your file geodatabase. Your second screenshot in your last post here, clearly shows the ArcSOC.exe process, which is part of ArcGIS Server (see this Help page and specifically the topic "Processes started by the GIS server"), still keeping hold of your file geodatabase files.
So whatever you did to stop the relevant ArcGIS Server processes, something / some process (the ArcSOC.exe) is clearly still running and needs to be stopped before you can delete the remaining file geodatabase files.
Jamal,
Try to delete the contents of File Geodatabase after stopping the services associated with ArcGIS Server in "Windows Services"
The other option is to use Task Manager, and select the ArcSoc.exe under processes and End Process.
Regards,
I made this suggestion in a different-but-related post from earlier this month, but it may help if there happens to be a process lock on one or more of the files within your file geodatabase.
If you are still having issues with deleting a geodatabase on the file system despite the fact that the .lock files no longer exist, it's possible there is still a process lock on one or more of the files within it. That being said, if you're using Windows Server 2008 / Windows 7 or later you can try one of the following methods:
1. From the Start menu, type FSMGMT.MSC, then multi-select the files you want from the GUI, then right click them and chose "Close". That method should force close the files that are technically still open due to a process lock.
or
2. From a batch file, run the following (example is for a file geodatabase) to close a file named a00000225.gdbtable:
cd C:\this_server\directory\subdirectory
for /f "skip=4 tokens=1,2*" %%a in ('net files') do if %%b == C:\this_server\...\a00000225.gdbtable net file %%a /close
You can modify the command above to loop through all of the files in the file geodatabase to close them all rather than specify them individually, which would be tedious since there are so many.
From the command prompt, type NET FILES to see what the underlined text above should contain.
Remember that double percent characters are required for batch files (in other words, %% rather than %) but single percent characters are used when running the command outside of a batch script.
I made this suggestion in a different-but-related post from earlier this month, but it may help if there happens to be a process lock on one or more of the files within your file geodatabase.
If you are still having issues with deleting a geodatabase on the file system despite the fact that the .lock files no longer exist, it's possible there is still a process lock on one or more of the files within it. That being said, if you're using Windows Server 2008 / Windows 7 or later you can try one of the following methods:
1. From the Start menu, type FSMGMT.MSC, then multi-select the files you want from the GUI, then right click them and chose "Close". That method should force close the files that are technically still open due to a process lock.
or
2. From a batch file, run the following (example is for a file geodatabase) to close a file named a00000225.gdbtable:
cd C:\this_server\directory\subdirectory
for /f "skip=4 tokens=1,2*" %%a in ('net files') do if %%b == C:\this_server\...\a00000225.gdbtable net file %%a /close
You can modify the command above to loop through all of the files in the file geodatabase to close them all rather than specify them individually, which would be tedious since there are so many.
From the command prompt, type NET FILES to see what the underlined text above should contain.
Remember that double percent characters are required for batch files (in other words, %% rather than %) but single percent characters are used when running the command outside of a batch script.