﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / SQL Server 2008 - General  / sql server x64 access x86 COM object / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 22 May 2013 13:29:05 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: sql server x64 access x86 COM object</title><link>http://www.sqlservercentral.com/Forums/Topic1419915-391-1.aspx</link><description>I had the same or very similar problem, a COM object on x64 ported from sql 2000 and helped installing management studio, still don't know why :-)</description><pubDate>Thu, 14 Feb 2013 04:20:28 GMT</pubDate><dc:creator>e4d4</dc:creator></item><item><title>sql server x64 access x86 COM object</title><link>http://www.sqlservercentral.com/Forums/Topic1419915-391-1.aspx</link><description>I want to transfer a database from SQL Server 2000 x86 to SQL Server 2008 R2 x64 but it uses a x86 COM object that I have no inside knowledge of. I know there are some articles out there about the same topic, but my problem is slightly different.After registering the DLL Server for Surrogate Activation, I can connect to COM object with sp_OACreate without errors, but sp_OASetProperty returns -2147352565 and sp_OAGetErrorInfo returns error source "ODSOLE Extended Procedure" and error description "Invalid index".Another thing I don't understand is that although the COM server is executable, and so out of process, I could not connect to it before using dll surrogate.  Out of process servers aren't supposed to work without surrogate?</description><pubDate>Thu, 14 Feb 2013 03:14:38 GMT</pubDate><dc:creator>aoikonom</dc:creator></item></channel></rss>