Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Cannot initialize the data source object of OLE DB provider

1,121 views
Skip to first unread message

luisalvarado

unread,
Aug 13, 2008, 4:09:26 PM8/13/08
to
Hi. I have problems seting up a linked server in a SQL
Server x64 running on a Windows server 2003 x64 EE. I keep
getting the message "Cannot initialize the data source
object of OLE DB provider ASEOLEDB for linked server". I
did the Allow In Process option under the provider, but
still not working. Any other ideas?. Thanks

Paul

unread,
Aug 14, 2008, 1:55:40 PM8/14/08
to
Hi Luis,

Please disable the "allow in process" - this isn't working yet.

How did you configure the linked server? Using Data Source or using
connection properties directly?

Make sure you have the latest ESD of the SDK for 64 bit (SDK 15.0 ESD#14).

Sometimes the machine has some rights issues. Especially if out of process:

Here are the DCOM configuration steps we took to get the Sybase OleDB
provider working Out of Process.
===========================================================================
=====

4. Open the DCOM Configuration utility by going to Start - Run and type
dcomcnfg

5. Expand Component Services/Computers/My Computer

6. Right click on My Computer and select Properties

7. On the Default Properties tab, check the following:
a. Make sure that "Enable Distributed COM on this computer" is checked
b. Make sure that Default Authentication Level = Connect
c. Make sure that Default Impersonation Level = Identify or Impersonate

8. On the COM Security tab, check the following:
a. In the Access Permissions section, click the Edit Limits and Edit
Default
buttons
b. Under each button, make sure that the local group containing the SQL
Service
account or the SQL Service account itself has Allow on all permissions
c. In the Launch and Activation Permissions section, click the Edit Limits
and Edit
Default buttons
d. Under each button, make sure that the local group containing the SQL
Service
account or the SQL Service account itself has Allow on all permissions

9. On the Default Protocols tab, check the following:
a. Check to verify that Connection-oriented TCP/IP exists in the DCOM
Protocols

10. On the MSDTC tab, click on the Security Configurations button and
check the
following options:
a. Make sure that Network DTC Access is checked
b. Make sure that Allow Remote Clients is checked
c. Make sure that Allow Inbound is checked
d. Make sure that Allow Outbound is checked
e. Make sure that Enable XA transactions is checked
f. Make sure that the No Authentication Required radio button is selected

11. After implementing the changes reboot the server for the changes to
take affect


-Paul
<Luis Alvarado> wrote in message news:48a33f76.594...@sybase.com...

Luis

unread,
Aug 18, 2008, 11:23:47 AM8/18/08
to
Hi Paul.
Unfortunately I had no luck with the instruction you gave
me.
Right now I have no way to download the SDK 15.0 ESD#14. I
have no permissions. I guess I will obtain a copy via my
Sybase provider. Also what you ask me about how I define
the linked server, I answer you that I do it via a data
source, which I tested and work ok. Also I want you to
know, that besides the configuring of the linked server, if
I create a .udl file, I keep getting the message error
“test connection failed because of an error in
initializing provider. Unspecified error.” From here on,
I am sure no linked server will work. Any other ideas, I
will be glad to try. Thanks and bye.

Paul

unread,
Aug 19, 2008, 11:57:28 AM8/19/08
to
Hi Luis,

What version Provider are you using now?

Also - when you setup UDL - you use the Data Source you created?
Please provide exact version information including the EBF #.
If not ESD - or EBF - how did you get this Provider?

Make sure you're using the 64 bit version.

-Paul

<Luis> wrote in message news:48a99403.60b...@sybase.com...

Paul

unread,
Aug 21, 2008, 2:13:08 PM8/21/08
to
Hi Luis,

You blanked out the panel of the Data Link properties
so I don't see how this would work - no Data Source, and not sure what
you entered in other props.

Could you post that portion of your test?

-Paul

<Luis Alvarado> wrote in message news:48ab355c.2ea...@sybase.com...
> Hi Paul.
> I have an original ASE 15.0.2 server x64 disc. From this
> disk, when istalling, I only select the connectivity options
> and the data providers. About the .udl, I dont have no
> server register, no datasource create, and nothing more.
> When I create the udl, I select the driver and then I test
> it out, sadly, I get the error. I attach a document with
> some pictures. Thanks. LDA

Paul

unread,
Aug 21, 2008, 6:42:05 PM8/21/08
to
Hi Luis,

If you can get ESD#14 try it.

One other thing - not sure if discussed - on the Provider settings on teh
linked server (under the Sybase OLEDB Provider
not the linked servers) uncheck the property "allow in process"

If this doesn't work maybe need to call Sybase Tech Support to get this
looked at.

-Paul

<Luis Alvarado> wrote in message news:48adb706.112...@sybase.com...
> Hi again.
> I entered my values. Please check and thanks.
>
> LDA

luisdiegoalvarado

unread,
Aug 29, 2008, 2:37:05 PM8/29/08
to
Hi Paul. Guess what. I created a vbs file and used the
provider ASEOLEDB, and it worked. So, what can I think of
that??? I now think the oledb driver is ok. Somehow, the
udl files cannot use them and neither SQL Server 2005. LDA

luisalvarado

unread,
Aug 29, 2008, 6:20:46 PM8/29/08
to
Hi. Solve my problem using 64-Bit OLEDB Provider for ODBC
(MSDASQL).
0 new messages