Error 0x800700C1 about filemeta

[Dijji]

[Dijji@09/12/2015]
This most commonly occurs when an extension has just been set up to use the File Meta property handler, and is sorted out by killing and restarting Windows Explorer, or in extreme cases rebooting the machine. The File Meta Association Manager in Version 1.3 proposes and will perform the required restart when such changes are made.

Does this help in your case?

Dijji

[Dijji]

[UnknownUser@09/12/2015]

[Dijji]

[kelba@09/12/2015]
Thanks for your quick response. However, my problem persists.

I've read

1. the documentation more carefully
2. the three reviews [FAQ: What are users of the software saying?]

I add metadata for extension by:

1. select one extension
2. leave [Simple] unchanged
3. click [Add File Meta Handler]
4. click [To restart Explorer]

I've made sure that the folder I'm experimenting with is

1. indexed
2. not shared

I've restarted Windows Explorer and Windows itself a number of times. Everything behaves as expexted until I click [Save] to save my new value of Tags. I've attached a few screen clips to document what I've done.

Per

[Dijji]

[Dijji@10/12/2015]
Clearly, there is something else going on. The error code 0x800700C1 appears to indicate that Windows is being asked to run something is not a valid executable. Logically, this ought to be either code installed by File Meta, or part of the installed system.

When it comes to saving a property value, there are not many files involved. Specifically, there is the property handler itself, which is written in C++, and the C++ runtime on which it depends. We can rule out .Net, which comes into play only when running the File Association Manager. Then, of course, there is the system itself.

The property handler should be installed at \Program Files\File Metadata\FileMetaPropertyHandler.dll. The main problem that you can have here is installing the 32-bit version of File Meta on a 64-bit system, or vice versa. Either of these might cause the problem that you are seeing.

The C++ runtime should appear in installed programs as “Microsoft Visual C++ 2010 x64 Runtime - 10.0.40219”, or “Microsoft Visual C++ 2010 x86 Runtime - 10.0.40219” for 32-bit systems.

Going more deeply into whether these are in a loadable state is a little more complicated. Checking the system is the easiest thing to do thoroughly. From a command prompt, run

sfc /scannow

This is a capability built into Windows to check that all system files are in a good state, and if not, repair them. It takes a while to run, but is very useful.

Please, let me know what you find.

Dijji

[Dijji]

[kelba@10/12/2015]
Thank you for looking into my problem.

I've made all the checks, which you propose, without finding anything obvious. I attach a zip-file, which contains a Wordpad-document with a somewhat more detailed reports on my checks.

Maybe, I should have tried to update the C++ 2010 Runtime. That's the only thing I can think of. Haven't done it yet though.

Per

PS. Codeplex is so sluggish. I send the attachment separately.

[Dijji]

[UnknownUser@10/12/2015]

[Dijji]

[kelba@10/12/2015]
Attachment / Per

[Dijji]

[UnknownUser@11/12/2015]

[Dijji]

[Dijji@11/12/2015]
Thank you for your detailed report on the state of your system. I agree with you, there’s no sign of the problem yet.

Thinking about the C++ runtime, I installed File Meta on a more or less empty 64-bit Windows 7 machine, and found that it does not show up under installed programs at all. Since it is embedded in the File Meta installer, it is probably just regarded as a subcomponent. Anyway, the acid test is the presence of msvcr100.dll In System32. The version on my test machine is 10.00.40219.325. I strongly suspect that this is present and correct on your system.

So I went on to look at further possible diagnostics. I tried out a few of the tools from my development environment, but they didn’t transplant well. So in the end, I wrote a quick custom diagnostic program. You can find it attached as PropertyTest.zip. This contains an executable, along with the source for it, should you be interested. To run the test, open a command prompt, change to a directory containing a text file on which we can set metadata and run the test like this:

“Full path\PropertyTest.exe" empty.txt

Let me know what it produces. On my machine, for a successful run, I get:

File: empty.txt
Property Handler: {D06391EE-2FEB-419B-9667-AD160D0849F3}

Instantiated Property Handler
Found IID_IInitializeWithFile
Initialized for empty.txt

System.Keywords : Property is in the property store.

System.Keywords : Value = atag

System.Keywords : SetValue succeeded
System.Keywords : Commit succeeded

Dijji

[Dijji]

[kelba@26/12/2015]
a

[Dijji]

[UnknownUser@26/12/2015]

[Dijji]

[kelba@26/12/2015]
Thank you for your effort. Now I'm back at this computer.

• Yes, the file, msvcr100.dll, is present in System32 on my system.
• I failed to run PropertyTest empty.txt. (I'm don't know C++ or have the IDE to try to understand why I fail.)

I attach FileMetadata_part_3.rtf, which contains a few screen clips.

/Per

[Dijji]

[Dijji@27/12/2015]
Okay, this helps a lot. 0xc000007b means ‘could not complete application initialisation’, i.e. either the executable or one of the DLLs on which it immediately depends could not be loaded. In our case, since the executable is fresh minted, then the problem probably lies with the only DLLs involved, the C++ runtime.
So, the problem might be a disk error, or a problem with the C++ runtime installation.

To check the disk errors, I’ve copied these standard instructions from a forum:

Many times hard disk problems can be repaired using the chkdsk command. Press the start button in bottom left corner of your screen.Search for "cmd" and Right click it and select "Run as administrator". A CMD window should appear. In that window you can just type it as you see "chkdsk c: /f /r". If it is the primary windows disk c: it will ask you to schedule it for next boot. When you restart, it will do a chkdsk for you before even getting to the login screen.

To check the C++ runtime installation, the simplest approach is to reinstall it. Uninstall File Meta, then uninstall the 2010 x64 redistributable that you have installed (10.0.30319). Now check in System32 to see if msvcr100.dll is still present. If not, we are good. If it is, more thought will be required to figure out where it came from. However, if we are clear, you can reinstall the runtime from here and then try PropertyTest again.

Let me know what you find.

Dijji

[Dijji]

[UnknownUser@27/12/2015]

[Dijji]

[kelba@27/12/2015]
Now, I think it works!

• chkdsk didn't find any problems
• uninstall of the 2010 x64 redistributable removed msvcr100.dll
• installation of the 2010 x64 redistributable and File MetaData worked fine
• adding a new value to tags of empty.txt caused no problems, see attachment

Thank you so much for the effective help!

Per

[Dijji]

[Dijji@27/12/2015]
Excellent! You now appear to be in great shape. Thank you for all the excellent, clear reports of what you found, they really helped me help you.

I will close this issue as resolved, but I will look to promote some of the material to the documentation so that anybody else with the same error can find it.

[Dijji]

[UnknownUser@28/12/2015]

[Dijji]

[kelba@28/12/2015]
That's a good idea!

I noticed that the [Control Panel, Uninstall or change a program] displays a different size of the reinstalled C++ runtime 13.6MB, whereas it was 13.7MB for the old one. Nevertheless, the version number is the same for the two. See new attachment and #3 of FileMetadata_part_2.rtf.

Per

[Dijji]

[Dijji@30/12/2015]
Yes, it seems that there was something amiss with the old version of the C++ runtime. It is often very difficult to tell where it would have come from, as a redistributable can be installed by any program which depends upon it. The only clue is usually to see what else was installed with the same installation date, which unfortunately does not appear in your recorded image.

I have now added an ‘Errors and their causes’ page to the documentation.

Dijji

[Dijji]

[UnknownUser@30/12/2015]

[Dijji]

Issue closed by Dijji with comment
The underlying cause was a corrupt installation of the Visual C++ runtime.

Reason closed
Fixed