Archive for December, 2011
Microsoft Sync Framework Unhandled Exception “Retrieving the COM class factory for component with CLSID…”
From the Microsoft Sync Framework 2.1 SDK download page http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23217
in the last part where it says instructions:
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. See Sync Framework Tips and Troubleshooting topic for details.
But that statement isn’t totally clear: The way to install for 64bit development machine is to download the x64 for the SDK and the fill the x86 parts with the redistributables from http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=19502
It works for me at least. Hope it helps.
Unrelated tidbit: I broke the Microsoft Forums layout when I posted this as a reply to http://social.microsoft.com/Forums/en/syncdevdiscussions/thread/34a04f62-014a-48a0-9397-256b6ad1387b
Check this out:
PTR, rDNS, SPF, DKIM, DomainKeys and SMTP set up for sending emails
The DNS records related to sending emails has to be set correctly according to prevailing standards otherwise you will get into various non-delivery issues.
PTR and rDNS
When the sender server (S) email arrives at the recipient server (R), R will do a rDNS check and this sequence of events will happen:
- R will check the IP that S is connected on
- R will check the IP for a valid hostname by doing a DNS lookup for the PTR record for the IP. This PTR record is recorded in the ISP zone for S.
- S’s ISP will return a hostname to R.
- R will check the hostname for an IP by doing a DNS lookup for the A record for the hostname. This A record is recorded in the zone of the hostname’s domain.
- R will compare the IP in step 1 and 4 to make sure it is the same.
Additionally, R may require that the hostname in step 2 be the same as the sender email domain’s MX and be the same as the hostname in the HELO/EHLO command sent by S. Although this will be over doing it.
SPF
R may also check whether S implements the Sender Policy Framework (SPF) in the DNS by looking up the TXT record in the email domain zone. Typically, an SPF TXT looks like:
- “v=spf1 mx a ~all”
This will tell R that emails originating from the MX server and the Web Server (specified at the A record for the domain) are allowed to send emails for the email domain.
DomainKeys, DKIM
S can also implement a “signature” protocol where every email sent out will be signed by the it. Then when R recieves the email, it will look up TXT record in the DNS zone of the email domain for the DomainKey and DKIM rules to parse and determine if the signature on the email is valid.