Hmm I have seen this error before but never found any good solutions. What I did to fix it was delete all the files in the folder and upload them again (you need to delete them programmatically).

Hopefully someone has a better solution. I'm curious myself :).

Frederik

Yeah, that's what I thought about doing. Would I really have to delete them programmatically? Won't it be enough to delete to folder? Or will that perhaps also cause an error?

The problem is one of the files in the folder. So deleting the folder and uploading all the files again should also fix it.

There is an error when you upload a file and it gets deleted in the database, but aint created.

Try to run this code

        protected void Button12_Click(object sender, EventArgs e)
        {
            StartIndexOnItemLit.Text = "";
             StringBuilder builder=new StringBuilder();
             VirtualPathHandler instance = VirtualPathHandler.Instance;
                
            foreach (var a in VirtualPathHandler.Instance.VirtualPathProviders.Keys)
            {
                if (a is VirtualPathUnifiedProvider)
                {

                    var dir = instance.GetDirectory((a as VirtualPathUnifiedProvider).VirtualPathRoot, true);

                    foreach (var element in dir.Children)
                    {
                        CheckItem(builder, element);
                    }
                }

            }
            StartIndexOnItemLit.Text="<ul>"+builder.ToString()+"</ul>";
            // Itera.Cms5Provider.AddToIndexer.Current.AddToIndex(StartIndexOnItem.Text, true, false);
        }

        private void CheckItem(StringBuilder builder, object element)
        {
            if (element is UnifiedDirectory)
            {
                CheckDir((element as UnifiedDirectory), builder);
            }
            if (element is UnifiedFile)
            {
                CheckFil((element as UnifiedFile), builder);
            }
        }
        void CheckDir(UnifiedDirectory dir, StringBuilder builder)
        {
            try
            {
                builder.AppendLine("<ul>");
                foreach (var a in dir.Children)
                {
                    CheckItem(builder, a);
                }
                builder.AppendLine("</ul>");
            }
            catch (System.Exception error)
            {
                builder.AppendLine(dir.Name+" "+dir.VirtualPath+" "+error.Message+" "+error.StackTrace);
            }
        }
        void CheckFil(UnifiedFile fil,StringBuilder builder)
        {
            try
            {
                var a = fil.Summary;
            }
            catch (Exception error)
            {
                
                builder.AppendLine("<li>deleting file since source don't exists " + fil.VirtualPath + "</li>");
                fil.Delete();
            }
        }

Anders, that code worked like a charm! Thank you!!

I got this error when I had made custom event handlings on fileCreate...So if it presists you need to debug some more :)

Good luck, and glad to be of help

I don't really know why this happened to this site, it remains a mystery. I've added this piece of code to the action window just to be sure in the future. ;)

Hi,

We have seen this problem before and also have a hotfix ready for it (bug#23743). But it only fixes the root cause (file version is 0), so you will have to delete the file yourself before you can access the folder again. 

I have experienced exactly the same symptoms in CMS 7. Did you apply the hotfix yourself because it seems to still exists? ;)

Sorry for the late reply. No other solution found so I've got the script saved in the Action Window for every time it occurs.

My mistake, I intended the last comment for Episerver crew (Toni), but didn't indicate it at all :) This bug should be fixed in CMS 6 R2, but I have experienced it at least twice in CMS 7. 

Jouni: It should actually have been fixed in CMS 6. If you can reproduce the problem in CMS 7 please contact support.

We got this error in CMS 6 R2. I made a plugin from Anders code, and that fixed the problem. Reason was probably that the WebEditor had replaced a picture with a new one with the same name. (This of course works most of the time).