(not sure the best news group to post this)

I'm trying to create a new OLEDB connection in the RTM version of SQL 2005

I get back the following error

The connection manager 'OLEDB' is not properly installed on this computer.
(Microsoft.DataTransformationServices.Design)

This is a clean install of SQL (the only previous version was SQL 200)

Any ideas please ?

--

Michael Tissington
http://www.oaklodge.com
http://www.tabtag.com

Have you tried the SQL newsgroup?

news://msnews.microsoft.com/microsof...qlserver.setup
news://msnews.microsoft.com/microsof...lserver.server
news://msnews.microsoft.com/microsof...qlserver.tools
news://msnews.microsoft.com/microsof...erver.newusers

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Michael Tissington" <mtissington (AT) newsgroups (DOT) nospam> wrote

Hello MIchael,

To understand the issue better, I'd like to know the detailed steps you
reproduce the issue. Does it occur for any OLEDB provider?

Based on my experience, you may want to see if you could workaround this
problem by running:

regsvr32 %ProgramFiles%\"Microsoft SQL Server\90\DTS\Binn\dtsconn.dll"

Please let us know if you have any update. Thanks!

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
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.


--------------------

Hello Peter,

I go into SSIS create a new project, right click in the bottom panel to
create a new connection and choose any of the options (with the exception of
'New Connection')

running regsvr32 for dtsconn.dll did not resolve the problem

The only thing that works is New Connection - trying to create any other
type of connection fails
with the error about Connection Manager and
Microsoft.DataTransformationServices.Design.

--

Michael Tissington
http://www.oaklodge.com
http://www.tabtag.com


"Peter Yang [MSFT]" <petery (AT) online (DOT) microsoft.com> wrote

Hello Michael,

It seems that a BI developement tool issue. Please check if there is any
issue when you creating connection directly in SQL server managememt
studio. You could right click a database->tasks->Import data and check if
you could create olddb datasouces there.

If there is not any issues, you may want to reinstall SQL tools via
Add/Remove programs to test the situation.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
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.


--------------------

In SS Management Studio everything seems to work correctly.

I have removed and reinstalled the software several times now

--

Michael Tissington
http://www.oaklodge.com
http://www.tabtag.com


"Peter Yang [MSFT]" <petery (AT) online (DOT) microsoft.com> wrote

Hello Michael,

Did you try to repair/reinstall VS 2005 to test the situation? Since it
works fine in SS Management Studio, it shall be a integration issue between
VS 2005 and its data connection components.

Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
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.

--------------------
<e3gB6Xe3FHA.3244 (AT) tk2msftngp13 (DOT) phx.gbl>
<rvBqizg3FHA.2904 (AT) TK2MSFTNGXA01 (DOT) phx.gbl>

Yes, I have done repair, I have uninstalled/installed many times now and it
still will not work.

--
Michael Tissington
http://www.oaklodge.com
http://www.tabtag.com


"Peter Yang [MSFT]" <petery (AT) online (DOT) microsoft.com> wrote

Hello Michael,

Based on my further research, you may want to check if the following files
exist:

%programfiles%\Microsoft SQL
server\90\SDK\Assemblies\en\Microsoft.SQLserver.DT SRuntimeWrap.xml

%programfiles%\Microsoft SQL
server\90\SDK\Assemblies\Microsoft.SQLserver.DTSRu ntimeWrap.dll

If they does not exist, you may want to complete remove/reinstall SQL 2005
instance and related registry keys to see if it helps.

If the issue is not resolved, to find out the root cause of this issue we
may need to analyze memory dumps or live debug, this work has to be done by
contacting Microsoft Product Support Services. Therefore, we probably will
not be able to resolve the issue through the newsgroups. I recommend that
you open a Support incident with Microsoft Product Support Services so that
a dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.

For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
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.

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

Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:

BCPS:
https://partner.microsoft.com/US/tec...rview/40010469

Others: https://partner.microsoft.com/US/tec...pportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default...rnational.aspx.

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

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
<e3gB6Xe3FHA.3244 (AT) tk2msftngp13 (DOT) phx.gbl>
<rvBqizg3FHA.2904 (AT) TK2MSFTNGXA01 (DOT) phx.gbl>
<#x9sWaj3FHA.2552 (AT) TK2MSFTNGP10 (DOT) phx.gbl>
<C#L5Pir3FHA.1144 (AT) TK2MSFTNGXA01 (DOT) phx.gbl>

Hi all,

Just to let Michael know he isn't alone here - I'm having exactly the
same problem.

Cheers,

Kevin.

Peter Yang [MSFT] wrote: