IBM Informix Ole Db Provider

Hello,

I'm getting the below errors when using sql server's data import wizard. Please Note: My test connection was successful and the error occurs when I click the "Next" button after closing the properties window. For Security reasons I've filled the User Id and DataSource with a bogus account, database, and server i.e. xxxx. Notice the password is blank?... Is that normal? I'm in a jam and appreciate your help.

Thanks,

Matt

===================================

Cannot get the supported data types from the database connection "Provider=Ifxoledbc;Password=;Persist Security Info=True;User ID=xxx;Data Source=xxx@.xxxx". (SQL Server Import and Export Wizard)

===================================

IErrorInfo.GetDescription failed with E_NOINTERFACE(0x80004002).
IErrorInfo.GetDescription failed with E_NOINTERFACE(0x80004002). (System.Data)

Program Location:

at System.Data.OleDb.OleDbConnectionInternal.GetSchemaRowset(Guid schema, Object[] restrictions)
at System.Data.OleDb.OleDbConnection.GetOleDbSchemaTable(Guid schema, Object[] restrictions)
at Microsoft.SqlServer.Dts.DtsWizard.DataSourceInfo.LoadTypeData(OleDbConnection myDestConnection)
at Microsoft.SqlServer.Dts.DtsWizard.DataSourceInfo.CacheDataSourceInfo(IDbConnection myConnection)

Moving to the "SQL Server Integration Services", which deals with data transformation issues.

|||

This means your OLE DB provider does not publish Provider_Types schema. The wizard relies on this schema to map data types between heterogeneous data sources.

You may want to try to build your SSIS package manually using OLE DB Source to access your Informix database.

Thanks.

|||

Hello,

Does your solution apply to the linked server as well? Any chance you know if SQL Server 2005 allows setting up an informix 7.3 db as a Linked Server? I now can connect with ADO.NET 2.0 using the IBM.Data.Informix namespace but have not been able to find any documentation on setting up connection through a linked server. FYI, I now have to correct IBM SDKs installed (2.9).

Thanks,

Matt

|||

I am having the same problem. Is there a way to get SQL server 2005 to talk to the Informix 7.3 engine? I get the following error:

Msg 7399, Level 16, State 1, Line 1

The OLE DB provider "Ifxoledbc" for linked server "MINNYME2" reported an error. The provider did not give any information about the error.

Msg 7303, Level 16, State 1, Line 1

Cannot initialize the data source object of OLE DB provider "Ifxoledbc" for linked server "MINNYME2".

|||

You are in luck. I'm currently still looking into this but have done a significant grind and configured the connection with ODBC. How are you connecting? With the Informix OLEDB? I'm currently waiting for the AIX admin to set something up on the server. He has to run a few scripts to set up the OLEDB properly. I found a page on IBM's site with significant documentation. Please see below. I believe I know what is wrong with my OLEDB connection, it is the set-up. I have a working ODBC now and can help you with that if need be.

http://www-306.ibm.com/software/data/informix/pubs/library/csdk_29.html

Regards,

Matt

|||

Yes, I am connecting using Informix OLE DB. I tried create a linked server with SQL Server 2005 with the IBM Informix OLE DB Provider. Here is my connection info. Did specify something wrong? It seems you abandoned this approach. Should I do the same and try to link the server with ODBC?

/****** Object: LinkedServer [MINNYME5] Script Date: 05/02/2006 11:10:06 ******/

EXEC master.dbo.sp_addlinkedserver @.server = N'MINNYME5', @.srvproduct=N'Informix-CLI 2.9 (32 bit)', @.provider=N'Ifxoledbc', @.datasrc=N'bsco@.becton_tcp', @.provstr=N'server=bsco@.becton_tcp;database=bsco;uid=informix;password=tewwetca'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'collation compatible', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'data access', @.optvalue=N'true'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'dist', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'pub', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'rpc', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'rpc out', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'sub', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'connect timeout', @.optvalue=N'0'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'collation name', @.optvalue=null

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'lazy schema validation', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'query timeout', @.optvalue=N'0'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'use remote collation', @.optvalue=N'true'

|||

Here is the code to set up the ODBC linked server. Please read the comments and notes provided throughout. I can help you further if need be. Just so we are on the same page, I'm using

OS: Windows XP Pro.

DotNet Framework: .NET SDK 1.1

IBM software development kit version: IBM CSDK 2.9

Good Luck!

EXEC sp_addlinkedserver

@.server = 'yourServer', -- defined in SetNet32 on tab 'Server information', -- field 'Informix Server'

@.provider = 'MSDASQL', -- DO NOT CHANGE !

@.datasrc = 'yourOdbcConnectionName', -- name of the ODBC connection defined in your system. (you must configure this.)

@.srvproduct = 'Informix-CLI 3.30 (32 bit)',

@.provstr = 'Host=yourHost;Server=yourServer;Service=yourService;Protocol=olsoctcp;Database=yourDB;UID=yourUIDToConnectToAIX;PWD=yourPWD'

NOTE: I'm not 100% sure if a login is needed but i created one.

EXEC sp_addlinkedsrvlogin 'yourLinkedServer', 'false', 'yourWindowsXPUserID', 'yourUIDToConnectToAIX', 'yourPassword'

READ-You need to set up permission for the UserId connecting to the AIX server in the AIX server. I had a AIX admin set me up considering I know little about IBM products.

Run the following query from SQL SERVER to query an ODBC linked server:

SELECT * FROM OPENQUERY(yourLinkedServer, 'select * from yourTable')

|||i done that , but cant insert into linked server tables and this error happens
OLE DB provider 'MSDASQL' reported an error. The provider reported an unexpected catastrophic failure.
[OLE/DB provider returned message: Query cannot be updated because the FROM clause is not a single simple table name.]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowsetChange::InsertRow returned 0x8000ffff: The provider reported an unexpected catastrophic failure.].
do u know why?

|||

Although I have never tried inserting a row into an Informix Linked Server, I'd assume that it is not possible considering I've seen similar results with other data sources.

|||thank you for replying
also i cant set linked server with oledb informix
when setup linked server with odbc can update, delete and select from linked table but only cant insert into the table

IBM Informix Ole Db Provider

Hello,

I'm getting the below errors when using sql server's data import wizard. Please Note: My test connection was successful and the error occurs when I click the "Next" button after closing the properties window. For Security reasons I've filled the User Id and DataSource with a bogus account, database, and server i.e. xxxx. Notice the password is blank?... Is that normal? I'm in a jam and appreciate your help.

Thanks,

Matt

===================================

Cannot get the supported data types from the database connection "Provider=Ifxoledbc;Password=;Persist Security Info=True;User ID=xxx;Data Source=xxx@.xxxx". (SQL Server Import and Export Wizard)

===================================

IErrorInfo.GetDescription failed with E_NOINTERFACE(0x80004002).
IErrorInfo.GetDescription failed with E_NOINTERFACE(0x80004002). (System.Data)

Program Location:

at System.Data.OleDb.OleDbConnectionInternal.GetSchemaRowset(Guid schema, Object[] restrictions)
at System.Data.OleDb.OleDbConnection.GetOleDbSchemaTable(Guid schema, Object[] restrictions)
at Microsoft.SqlServer.Dts.DtsWizard.DataSourceInfo.LoadTypeData(OleDbConnection myDestConnection)
at Microsoft.SqlServer.Dts.DtsWizard.DataSourceInfo.CacheDataSourceInfo(IDbConnection myConnection)

Moving to the "SQL Server Integration Services", which deals with data transformation issues.

|||

This means your OLE DB provider does not publish Provider_Types schema. The wizard relies on this schema to map data types between heterogeneous data sources.

You may want to try to build your SSIS package manually using OLE DB Source to access your Informix database.

Thanks.

|||

Hello,

Does your solution apply to the linked server as well? Any chance you know if SQL Server 2005 allows setting up an informix 7.3 db as a Linked Server? I now can connect with ADO.NET 2.0 using the IBM.Data.Informix namespace but have not been able to find any documentation on setting up connection through a linked server. FYI, I now have to correct IBM SDKs installed (2.9).

Thanks,

Matt

|||

I am having the same problem. Is there a way to get SQL server 2005 to talk to the Informix 7.3 engine? I get the following error:

Msg 7399, Level 16, State 1, Line 1

The OLE DB provider "Ifxoledbc" for linked server "MINNYME2" reported an error. The provider did not give any information about the error.

Msg 7303, Level 16, State 1, Line 1

Cannot initialize the data source object of OLE DB provider "Ifxoledbc" for linked server "MINNYME2".

|||

You are in luck. I'm currently still looking into this but have done a significant grind and configured the connection with ODBC. How are you connecting? With the Informix OLEDB? I'm currently waiting for the AIX admin to set something up on the server. He has to run a few scripts to set up the OLEDB properly. I found a page on IBM's site with significant documentation. Please see below. I believe I know what is wrong with my OLEDB connection, it is the set-up. I have a working ODBC now and can help you with that if need be.

http://www-306.ibm.com/software/data/informix/pubs/library/csdk_29.html

Regards,

Matt

|||

Yes, I am connecting using Informix OLE DB. I tried create a linked server with SQL Server 2005 with the IBM Informix OLE DB Provider. Here is my connection info. Did specify something wrong? It seems you abandoned this approach. Should I do the same and try to link the server with ODBC?

/****** Object: LinkedServer [MINNYME5] Script Date: 05/02/2006 11:10:06 ******/

EXEC master.dbo.sp_addlinkedserver @.server = N'MINNYME5', @.srvproduct=N'Informix-CLI 2.9 (32 bit)', @.provider=N'Ifxoledbc', @.datasrc=N'bsco@.becton_tcp', @.provstr=N'server=bsco@.becton_tcp;database=bsco;uid=informix;password=tewwetca'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'collation compatible', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'data access', @.optvalue=N'true'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'dist', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'pub', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'rpc', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'rpc out', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'sub', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'connect timeout', @.optvalue=N'0'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'collation name', @.optvalue=null

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'lazy schema validation', @.optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'query timeout', @.optvalue=N'0'

GO

EXEC master.dbo.sp_serveroption @.server=N'MINNYME5', @.optname=N'use remote collation', @.optvalue=N'true'

|||

Here is the code to set up the ODBC linked server. Please read the comments and notes provided throughout. I can help you further if need be. Just so we are on the same page, I'm using

OS: Windows XP Pro.

DotNet Framework: .NET SDK 1.1

IBM software development kit version: IBM CSDK 2.9

Good Luck!

EXEC sp_addlinkedserver

@.server = 'yourServer', -- defined in SetNet32 on tab 'Server information', -- field 'Informix Server'

@.provider = 'MSDASQL', -- DO NOT CHANGE !

@.datasrc = 'yourOdbcConnectionName', -- name of the ODBC connection defined in your system. (you must configure this.)

@.srvproduct = 'Informix-CLI 3.30 (32 bit)',

@.provstr = 'Host=yourHost;Server=yourServer;Service=yourService;Protocol=olsoctcp;Database=yourDB;UID=yourUIDToConnectToAIX;PWD=yourPWD'

NOTE: I'm not 100% sure if a login is needed but i created one.

EXEC sp_addlinkedsrvlogin 'yourLinkedServer', 'false', 'yourWindowsXPUserID', 'yourUIDToConnectToAIX', 'yourPassword'

READ-You need to set up permission for the UserId connecting to the AIX server in the AIX server. I had a AIX admin set me up considering I know little about IBM products.

Run the following query from SQL SERVER to query an ODBC linked server:

SELECT * FROM OPENQUERY(yourLinkedServer, 'select * from yourTable')

|||i done that , but cant insert into linked server tables and this error happens
OLE DB provider 'MSDASQL' reported an error. The provider reported an unexpected catastrophic failure.
[OLE/DB provider returned message: Query cannot be updated because the FROM clause is not a single simple table name.]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowsetChange::InsertRow returned 0x8000ffff: The provider reported an unexpected catastrophic failure.].
do u know why?

|||

Although I have never tried inserting a row into an Informix Linked Server, I'd assume that it is not possible considering I've seen similar results with other data sources.

|||thank you for replying
also i cant set linked server with oledb informix
when setup linked server with odbc can update, delete and select from linked table but only cant insert into the table

IA64 teradata OLE-DB or ODBC

I have a 32 bit development/playbox SQL 2005 SSIS that can see and run 32 bit OLE DB drivers from Teradata. Granted I have the same issues as others where a table or a view would work and not a query or a variable query. The alternative is to use Linked Server and OPENQUERY.

But our real development box is a 64 bit IA 64 using 64 bit SQL 2005. Non of the Teradata.com drivers would work/show up in the dropdown box of the Connection Manager since they are 32 bit. One option is to use the 64 bit Teradata ODBC drivers and then use the .Net ODBC connection instead. Linked server doesn't work either because the SQL 2005 is 64 bit and it is looking for 64 bit drivers.

Has anyone have any experience with 64 bit SQL 2005 and Teradata?

Looked at other 3rd party vendors such as ETI but their documentation excludes IA 64 (Itanium).

Planning to try again using the 64 bit ODBC and .Net Adapter but I'm interested to hear if someone (MSFT & NCR) would have a real solution for 64 bit.

Thanks

Anatole

I'm replying to my own thread as I want to see who else is having the same issue using Teradata Drivers and SSIS (32 or 64 bit).

I think this is a given where the Teradata OLE-DB driver is failing when used as a SQL Stmt rather than Table/View to extract data.

The message is:

An OLE DB error has occurred. Error code: 0x80040E21.An OLE DB record is available. Source: "OLE DB Provider for Teradata" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done."

Has anyone found a work-around and/or contacted MS about this?

I opened a ticket with teradata/ncr but they are pointing back at SSIS and MS.

This error can occur on any box/cpu (32 bit or 64bit).

Since ODBC adaptor in SSIS converts everything into UNICODE, the only option is to use Linkedserver and OPENQUERY cmd.

I would like to hear back from MS (I know thay have teradata servers) or anyone that has either received this error and has a solution OR is also waiting on one.

Thanks

Anatole

|||

Anatole,

Take a look at :

www.openlinksw.com/

They seem to have an IA64 OLE to ODBC driver. I am not sure I even understand the issue well enough, but we had a similar issue and found them, we are still looking to see if they can solve our issue witch is with Sybase and SQL, but I thought I would just throw it out there for you since you had not gotten anyone to reply back, it might at least give you a better lead....

Hope it helps...

Steve

|||

2 other potential resources are:

www.odbcsdk.com

This is another Third Party (Open Access) that advertises a 64bit OLEDB to ODBC Data Provider (Itanium).

http://www.datadirect.com/products/odbc64/overview/index.ssp

This is another Third Party (DataDirect) that advertises a 64bit Sybase ODBC driver (Itanium)

Just trying to be helpful for people running into these types of problems....Hopefully this is helpful...

Steve

|||

Hi!

See also my similar question (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=853174&SiteID=1&mode=1).

I can't work out your suggestion using a ".net ODBC".

B.G.

IA64 teradata OLE-DB or ODBC

I have a 32 bit development/playbox SQL 2005 SSIS that can see and run 32 bit OLE DB drivers from Teradata. Granted I have the same issues as others where a table or a view would work and not a query or a variable query. The alternative is to use Linked Server and OPENQUERY.

But our real development box is a 64 bit IA 64 using 64 bit SQL 2005. Non of the Teradata.com drivers would work/show up in the dropdown box of the Connection Manager since they are 32 bit. One option is to use the 64 bit Teradata ODBC drivers and then use the .Net ODBC connection instead. Linked server doesn't work either because the SQL 2005 is 64 bit and it is looking for 64 bit drivers.

Has anyone have any experience with 64 bit SQL 2005 and Teradata?

Looked at other 3rd party vendors such as ETI but their documentation excludes IA 64 (Itanium).

Planning to try again using the 64 bit ODBC and .Net Adapter but I'm interested to hear if someone (MSFT & NCR) would have a real solution for 64 bit.

Thanks

Anatole

I'm replying to my own thread as I want to see who else is having the same issue using Teradata Drivers and SSIS (32 or 64 bit).

I think this is a given where the Teradata OLE-DB driver is failing when used as a SQL Stmt rather than Table/View to extract data.

The message is:

An OLE DB error has occurred. Error code: 0x80040E21.An OLE DB record is available. Source: "OLE DB Provider for Teradata" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done."

Has anyone found a work-around and/or contacted MS about this?

I opened a ticket with teradata/ncr but they are pointing back at SSIS and MS.

This error can occur on any box/cpu (32 bit or 64bit).

Since ODBC adaptor in SSIS converts everything into UNICODE, the only option is to use Linkedserver and OPENQUERY cmd.

I would like to hear back from MS (I know thay have teradata servers) or anyone that has either received this error and has a solution OR is also waiting on one.

Thanks

Anatole

|||

Anatole,

Take a look at :

www.openlinksw.com/

They seem to have an IA64 OLE to ODBC driver. I am not sure I even understand the issue well enough, but we had a similar issue and found them, we are still looking to see if they can solve our issue witch is with Sybase and SQL, but I thought I would just throw it out there for you since you had not gotten anyone to reply back, it might at least give you a better lead....

Hope it helps...

Steve

|||

2 other potential resources are:

www.odbcsdk.com

This is another Third Party (Open Access) that advertises a 64bit OLEDB to ODBC Data Provider (Itanium).

http://www.datadirect.com/products/odbc64/overview/index.ssp

This is another Third Party (DataDirect) that advertises a 64bit Sybase ODBC driver (Itanium)

Just trying to be helpful for people running into these types of problems....Hopefully this is helpful...

Steve

|||

Hi!

See also my similar question (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=853174&SiteID=1&mode=1).

I can't work out your suggestion using a ".net ODBC".

B.G.

sql

I/O error (bad page ID) detected during read at offset 0x0000000f3e4000

Hi,

Can anyone help me with this error?

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RVHS_database.mdf'.

What should i do to recover my database? Please help me outuse DBCC CHECKDB (use NOINDEX first; id an index is corrrupted it won't be a problem), then try REPAIR_FAST or REPAIR_REBUILD (it's time consuming) - see Books Online for more

Originally posted by Bluetooth
Hi,

Can anyone help me with this error?

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RVHS_database.mdf'.

What should i do to recover my database? Please help me out|||ooops, I don't think the recommended switches will do the trick. It
's REPAIR_ALLOW_DATA_LOSS that will fix page allocation errors (which is what you have here). Do it within a transaction and don't commit untill you see what repairs are done and what errors got fixed.

I want to have a live link to data from SQL Server

This is a bit confusing but here goes: I need to access data in SAP via OLE DB. I can't go direct to the back end database (Oracle), we have to use RFC or BAPI calls to access the SAP data. That's part works, we have a DLL that accesses the SAP data we need.

Next I would like to be able to access the data in that DLL with something like:
Select * from view_SAPData.

We messed around with extended stored procedures and it looked good for a bit because we could call the extended proc from a stored proc and we could create a view from a function so I figured we could make it work, but we couldn't.

So now I'm asking you nice folks if there is a way we can provide a dataset to SQL Server from our DLL? I don't know much about DMO, is there anything there?

Hope this makes sense.
TIA,
Blaise

Hi blaise,

You would to use Microsoft .NET Data Provider for mySAP Business Suite:

http://download.microsoft.com/download/f/7/4/f74cbdb1-87e2-4794-9186-e3ad6bd54b41/DataProviderSAP.exe

You could to see more info about it, here:

Feature Pack for Microsoft SQL Server 2005
http://www.microsoft.com/downloads/details.aspx?familyid=DF0BA5AA-B4BD-4705-AA0A-B477BA72A9CB&displaylang=en

Good Coding!

Javier Luna
http://guydotnetxmlwebservices.blogspot.com/

sql

I want to have a live link to data from SQL Server

This is a bit confusing but here goes: I need to access data in SAP via OLE DB. I can't go direct to the back end database (Oracle), we have to use RFC or BAPI calls to access the SAP data. That's part works, we have a DLL that accesses the SAP data we need.

Next I would like to be able to access the data in that DLL with something like:
Select * from view_SAPData.

We messed around with extended stored procedures and it looked good for a bit because we could call the extended proc from a stored proc and we could create a view from a function so I figured we could make it work, but we couldn't.

So now I'm asking you nice folks if there is a way we can provide a dataset to SQL Server from our DLL? I don't know much about DMO, is there anything there?

Hope this makes sense.
TIA,
Blaise

Hi blaise,

You would to use Microsoft .NET Data Provider for mySAP Business Suite:

http://download.microsoft.com/download/f/7/4/f74cbdb1-87e2-4794-9186-e3ad6bd54b41/DataProviderSAP.exe

You could to see more info about it, here:

Feature Pack for Microsoft SQL Server 2005
http://www.microsoft.com/downloads/details.aspx?familyid=DF0BA5AA-B4BD-4705-AA0A-B477BA72A9CB&displaylang=en

Good Coding!

Javier Luna
http://guydotnetxmlwebservices.blogspot.com/

I try to create a maintenance plan I am getting the error

TITLE: Microsoft SQL Server Management Studio
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
And evenlog message
The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor
of the client library. [CLIENT: <local machine>]
I am using Sql Server 2005 Developer Edition 9.0.1399.
I have searched around but cannot find.
Thank you for your help.
ZaferHi Zafer,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: When you create a
Maintenance plan in SQL Server Management Studio, you get the following
error:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued and failed.
If I misunderstood your concern, please feel free to point it out.
Please verify that your server has a valid cert stored in
computer->personal.
On the SQL Server computer, create a Microsoft Management Console (MMC)
snap-in for the Certificates tool. To do this, follow these steps:
a. Click "Start", click "Run", type "mmc" (without the quotation marks)
in the
"Open" box, and then click "OK".
b. On the "File" menu, click "Add/Remove Snap-in".
c. Click "Add", click "Certificates", click "Add", click "Computer
account",
click "Next", click "Finish", click "Close", and then click "OK".
Also, you may check your SQL Server Service Account. If you run SQL Server
as local system, is this issue occur?
Hope this will be helpful!
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

I try to create a maintenance plan I am getting the error

TITLE: Microsoft SQL Server Management Studio
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
And evenlog message
The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor
of the client library. [CLIENT: <local machine>]
I am using Sql Server 2005 Developer Edition 9.0.1399.
I have searched around but cannot find.
Thank you for your help.
Zafer
Hi Zafer,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: When you create a
Maintenance plan in SQL Server Management Studio, you get the following
error:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued and failed.
If I misunderstood your concern, please feel free to point it out.
Please verify that your server has a valid cert stored in
computer->personal.
On the SQL Server computer, create a Microsoft Management Console (MMC)
snap-in for the Certificates tool. To do this, follow these steps:
a. Click "Start", click "Run", type "mmc" (without the quotation marks)
in the
"Open" box, and then click "OK".
b. On the "File" menu, click "Add/Remove Snap-in".
c. Click "Add", click "Certificates", click "Add", click "Computer
account",
click "Next", click "Finish", click "Close", and then click "OK".
Also, you may check your SQL Server Service Account. If you run SQL Server
as local system, is this issue occur?
Hope this will be helpful!
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

I try to create a maintenance plan I am getting the error

TITLE: Microsoft SQL Server Management Studio
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued
and failed.
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued
and failed.
And evenlog message
The prelogin packet used to open the connection is structurally invalid; the
connection has been closed. Please contact the vendor
of the client library. [CLIENT: <local machine>]
I am using Sql Server 2005 Developer Edition 9.0.1399.
I have searched around but cannot find.
Thank you for your help.
ZaferHi Zafer,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: When you create a
Maintenance plan in SQL Server Management Studio, you get the following
error:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued and failed.
If I misunderstood your concern, please feel free to point it out.
Please verify that your server has a valid cert stored in
computer->personal.
On the SQL Server computer, create a Microsoft Management Console (MMC)
snap-in for the Certificates tool. To do this, follow these steps:
a. Click "Start", click "Run", type "mmc" (without the quotation marks)
in the
"Open" box, and then click "OK".
b. On the "File" menu, click "Add/Remove Snap-in".
c. Click "Add", click "Certificates", click "Add", click "Computer
account",
click "Next", click "Finish", click "Close", and then click "OK".
Also, you may check your SQL Server Service Account. If you run SQL Server
as local system, is this issue occur?
Hope this will be helpful!
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
========================================
==============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.