Managed Application Throws System.Runtime.InteropServices.COMException (0x80040154) Problem: A managed synchronization application throws System.Runtime.InteropServices.COMException with the following error message: "Retrieving the COM class factory for component with CLSID {565AEDBF-3108-4405-AF1F-9C2C25925DAE} failed due to the following error: 80040154." Solution: This occurs when the processor type for which an application is built does not match the processor type for which Sync Framework is installed. For example, your application targets the x86 processor and you have the x64 version of Sync Framework installed. In Visual Studio, change the Platform Target in the Build pane of your project properties to match the Sync Framework processor type. Solution: This also occurs when an unmanaged synchronization component, such as Synchronization.dll, is missing from the installation. This can occur when Sync Framework has been uninstalled or when installation was not completed successfully. Reinstall Sync Framework to fix this.
When Sync Framework tracing runs for a long time, the tracing output file gets very large, and there isn't any integrated support for rolling over to a new tracing file or for clearing out old traces to keep the file size manageable. This blog post about Rolling over TextWriterTraceListener logs does a nice job of showing you how to override the System.Diagnostics.TextWriterTraceListener class to start logging to a new file on a pre-specified interval. For more information on tracing Sync Framework, see How to: Trace the Synchronization Process.
Side-by-side installation of 32-bit and 64-bit versions of Sync Framework 2.1 SDK is not supported. For example, if you try to install 32-bit version of Sync Framework 2.1 SDK on a computer that already has 64-bit version on it, you will receive an error message: "Unable to install because a newer version of this product is already installed". It is not possible have full 32-bit Sync Framework 2.1 SDK installed side-by-side with the 64-bit SDK; therefore you will have to install one version of SDK (64-bit) completely and only selected components of other version (32-bit) of SDK. You can install the selected components of the SDK from Sync Framework 2.1 Redistributable Packages page and full SDK package from Sync Framework SDK download page .
ALTER TABLE ExampleTable ALTER COLUMN idCol IDENTITY(10,1)
A large metadata file can take a long time to send to each client during synchronization. The solution to this is to store the metadata file on each client, rather than just on the server. To do this, specify a local client path for the metadata file when the FileSyncProvider object is created on the client, such as in the following code example:
FileSyncProvider myClientProvider =
new
FileSyncProvider(
"c:\\syncfolder"
, myFilter,
myOptions,
"c:\\syncmetadata"
,
null
);
Carsten Siemens edited Revision 7. Comment: Added tag: en-US
Laren Crawford (MSFT) edited Revision 2. Comment: Added tracing tip.