MED-V 1.0: MED-V service is fails to start with the following event in the System Log – Event ID 0
You may encounter problems with a Windows XP host when the MED-V service is trying to start. It will fail to start if any of the critical .NET components are missing or corrupt with the following event in the System Log:
Cannot start service. System.IO.FileNotFoundException: Could not load file or assembly ‘System.Data, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b77a5c561934e089’ or one of its dependencies. The system cannot find the file specified.
File Name : ‘System.Data, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b77a5c561934e089’
at: Kidaro.Foundation.SafeXmlSerializer.Create(Type type)
at: Kidaro.Foundation.Config.XmlConfiguration.get_Item(String path)
at: Kidaro.Foundation.Config.CompositeConfiguration.get_Item(String path)
at: Kidaro.Foundation.Config.Configuration.Get(String path)
at: Kidaro.Features.FeatureManager.Initialize(IFeature feature)
at: Kidaro.Service.KidaroService.OnStart(String args)
Again, this problem is most likely happening because one of the following:
1. The file System.Data.dll has been moved or deleted (or one of its dependent assemblies)
2. The proper version of .NET was never installed (although the MED-V install should check for that)
3. The proper version of .NET was uninstalled after MED-V was installed
To resolve this issue, you should be able to run the .NET Framework 2.0 configuration utility to verify the existence of the System.Data.dll file. It is found in Control Panel under administrative tools.
After that is confirmed check the local directory:
Volume in drive C has no label.
Volume Serial Number is 36E4-4246
Directory of C:\Windows\Microsoft.NET\Framework\v2.0.50727
06/10/2009 03:23 PM 2,933,248 System.Data.dll
1 File(s) 2,933,248 bytes
– You can also use the .NET Verifier to confirm that the .NET 2.0 runtimes are correctly installed and registered.
More information about the .NET Verifier can be found here: