I managed to resolve this myself. Turns out the derby DB isnt as inpenetrable as I first thought ;)
1. Shut down artifactory 2. Navigate to the file in question, in my case id=88b21d1ef06323beff58664cffa62848c033ecd2 is found like this: cd $ARTIFACTORY_HOME/data/filestore/88/b2/1d 3. Remove the file (should only be 1) 4. Restart Artifactory. Repeat as necessary for any other files that crop up -- View this message in context: http://forums.jfrog.org/server-500-response-w-artifact-in-invalid-state-tp6955471p7578603.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
