OLEDB error while trying to import MDB data into SQL 2005

Hello,

I am getting an error while trying to import data into SQL 2005 from an existing Access MDB database. When I try this on another workstation there are no problems and the data is imported successfully.

Could someone tell me what to look for or what setting I have incorrect. On the workstation with the problem I had removed SQL 2000 Personal Edition and installed SQL 2005 Standard Edition. Also, I have both Visual 2003 and 2005 installed on this workstation as well.

Thanks

TITLE: SQL Server Import and Export Wizard

Could not set up data flow connections.

The connection type "OLEDB" specified for connection manager "{DAE0A984-862B-4E4A-890E-8DB4860C9F6B}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.

ADDITIONAL INFORMATION:

The connection type "OLEDB" specified for connection manager "{DAE0A984-862B-4E4A-890E-8DB4860C9F6B}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
({55FFB2C2-E461-4FDB-B3C4-EE4677B80C77})

BUTTONS:

OK

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Error)

Messages

The connection "SourceConnectionOLEDB" is not found. This error is thrown by Connections collection when the specific connection element is not found.
({3DDD68E3-30A4-4513-B0AB-45F340BAB4C0})

- Setting Destination Connection (Stopped)

- Validating (Stopped)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Stopped)

- Copying to [EJTest].[dbo].[Journal] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Did you ever figure out how to fix this. I had the same problem on my laptop, and I had to rebuild my laptop from scratch to fix it. I have another person with the same problem. I would like to fix this with out rebuilding.

Thanks

Michael Robey
mrobey@.worldinsco.com

|||This is a SSIS issue.|||

Yes it is a SSIS issue. Open SQL Server Configuration Manager. Right click on SQL Server Integration Services. Select properties and in the Log On tab change the built-in account.

It should be the same account you are using to run SQL Server. In my case is a standalone server for test/dev purpuse so I don't use Network account. I changed both to Local System. That should fix the issue.

|||

I had the same problem too.

Thanks Carlos, fixed it perfectly.

|||

I had the problem in general. Couldnt import tables from sql2000 / 2005 same and different databases.

Trough Your remark (Thank You) i fiddeld a little with the properties of SSIS and MSSQL Services. if both log on as the built in local system user,it works too. or local system and a Windows user of the machine, thats ok too.

I had posted this problem in

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=344363&SiteID=1

but never got a reaction from ms

With some combinations you can optionally save the package, with some the wizard throws an error.

A definite clarification from ms about the conditions would be very helpful.

Michael

|||It really solved the problem.
Thank you very much!!!
|||

Better late than never!

Your solution solved my issue as well.

Thank you very much!

|||

It worked for me as well,

I wanted to import a visual foxpro Database to SQL2005, I installed Visual Foxpro oledb (9.0) . but I got the Error message. I tried importing a MSAccess db and it gave me the same error. following up Carlos Instruction, It worked both for msAccess db and Foxpro OleDB

Thanks

|||

Please read the KB article http://support.microsoft.com/kb/913817

The SSIS service does not have to run as the same account as SQL Server instance. What helped you is that you've changed it to run as account with Administrator rights. While this does fixes the problem, it exposes you to unnecessary risks as you are granting the service more priviledges than it really needs.

It is better to fix the real cause as described in the article.

|||

It is working now!!!

THanks

|||Bingo! That did it. Thanks!

OLEDB error while trying to import MDB data into SQL 2005

Hello,

I am getting an error while trying to import data into SQL 2005 from an existing Access MDB database. When I try this on another workstation there are no problems and the data is imported successfully.

Could someone tell me what to look for or what setting I have incorrect. On the workstation with the problem I had removed SQL 2000 Personal Edition and installed SQL 2005 Standard Edition. Also, I have both Visual 2003 and 2005 installed on this workstation as well.

Thanks

TITLE: SQL Server Import and Export Wizard

Could not set up data flow connections.

The connection type "OLEDB" specified for connection manager "{DAE0A984-862B-4E4A-890E-8DB4860C9F6B}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.

ADDITIONAL INFORMATION:

The connection type "OLEDB" specified for connection manager "{DAE0A984-862B-4E4A-890E-8DB4860C9F6B}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
({55FFB2C2-E461-4FDB-B3C4-EE4677B80C77})

BUTTONS:

OK

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Error)

Messages

The connection "SourceConnectionOLEDB" is not found. This error is thrown by Connections collection when the specific connection element is not found.
({3DDD68E3-30A4-4513-B0AB-45F340BAB4C0})

- Setting Destination Connection (Stopped)

- Validating (Stopped)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Stopped)

- Copying to [EJTest].[dbo].[Journal] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Did you ever figure out how to fix this. I had the same problem on my laptop, and I had to rebuild my laptop from scratch to fix it. I have another person with the same problem. I would like to fix this with out rebuilding.

Thanks

Michael Robey
mrobey@.worldinsco.com

|||This is a SSIS issue.|||

Yes it is a SSIS issue. Open SQL Server Configuration Manager. Right click on SQL Server Integration Services. Select properties and in the Log On tab change the built-in account.

It should be the same account you are using to run SQL Server. In my case is a standalone server for test/dev purpuse so I don't use Network account. I changed both to Local System. That should fix the issue.

|||

I had the same problem too.

Thanks Carlos, fixed it perfectly.

|||

I had the problem in general. Couldnt import tables from sql2000 / 2005 same and different databases.

Trough Your remark (Thank You) i fiddeld a little with the properties of SSIS and MSSQL Services. if both log on as the built in local system user,it works too. or local system and a Windows user of the machine, thats ok too.

I had posted this problem in

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=344363&SiteID=1

but never got a reaction from ms

With some combinations you can optionally save the package, with some the wizard throws an error.

A definite clarification from ms about the conditions would be very helpful.

Michael

|||It really solved the problem.
Thank you very much!!!
|||

Better late than never!

Your solution solved my issue as well.

Thank you very much!

|||

It worked for me as well,

I wanted to import a visual foxpro Database to SQL2005, I installed Visual Foxpro oledb (9.0) . but I got the Error message. I tried importing a MSAccess db and it gave me the same error. following up Carlos Instruction, It worked both for msAccess db and Foxpro OleDB

Thanks

|||

Please read the KB article http://support.microsoft.com/kb/913817

The SSIS service does not have to run as the same account as SQL Server instance. What helped you is that you've changed it to run as account with Administrator rights. While this does fixes the problem, it exposes you to unnecessary risks as you are granting the service more priviledges than it really needs.

It is better to fix the real cause as described in the article.

|||

It is working now!!!

THanks

|||Bingo! That did it. Thanks!

OLEDB error while trying to import MDB data into SQL 2005

Hello,

I am getting an error while trying to import data into SQL 2005 from an existing Access MDB database. When I try this on another workstation there are no problems and the data is imported successfully.

Could someone tell me what to look for or what setting I have incorrect. On the workstation with the problem I had removed SQL 2000 Personal Edition and installed SQL 2005 Standard Edition. Also, I have both Visual 2003 and 2005 installed on this workstation as well.

Thanks

TITLE: SQL Server Import and Export Wizard

Could not set up data flow connections.

The connection type "OLEDB" specified for connection manager "{DAE0A984-862B-4E4A-890E-8DB4860C9F6B}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.

ADDITIONAL INFORMATION:

The connection type "OLEDB" specified for connection manager "{DAE0A984-862B-4E4A-890E-8DB4860C9F6B}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
({55FFB2C2-E461-4FDB-B3C4-EE4677B80C77})

BUTTONS:

OK

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Error)

Messages

The connection "SourceConnectionOLEDB" is not found. This error is thrown by Connections collection when the specific connection element is not found.
({3DDD68E3-30A4-4513-B0AB-45F340BAB4C0})

- Setting Destination Connection (Stopped)

- Validating (Stopped)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Stopped)

- Copying to [EJTest].[dbo].[Journal] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Did you ever figure out how to fix this. I had the same problem on my laptop, and I had to rebuild my laptop from scratch to fix it. I have another person with the same problem. I would like to fix this with out rebuilding.

Thanks

Michael Robey
mrobey@.worldinsco.com

|||This is a SSIS issue.|||

Yes it is a SSIS issue. Open SQL Server Configuration Manager. Right click on SQL Server Integration Services. Select properties and in the Log On tab change the built-in account.

It should be the same account you are using to run SQL Server. In my case is a standalone server for test/dev purpuse so I don't use Network account. I changed both to Local System. That should fix the issue.

|||

I had the same problem too.

Thanks Carlos, fixed it perfectly.

|||

I had the problem in general. Couldnt import tables from sql2000 / 2005 same and different databases.

Trough Your remark (Thank You) i fiddeld a little with the properties of SSIS and MSSQL Services. if both log on as the built in local system user,it works too. or local system and a Windows user of the machine, thats ok too.

I had posted this problem in

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=344363&SiteID=1

but never got a reaction from ms

With some combinations you can optionally save the package, with some the wizard throws an error.

A definite clarification from ms about the conditions would be very helpful.

Michael

|||It really solved the problem.
Thank you very much!!!|||

Better late than never!

Your solution solved my issue as well.

Thank you very much!

|||

It worked for me as well,

I wanted to import a visual foxpro Database to SQL2005, I installed Visual Foxpro oledb (9.0) . but I got the Error message. I tried importing a MSAccess db and it gave me the same error. following up Carlos Instruction, It worked both for msAccess db and Foxpro OleDB

Thanks

|||

Please read the KB article http://support.microsoft.com/kb/913817

The SSIS service does not have to run as the same account as SQL Server instance. What helped you is that you've changed it to run as account with Administrator rights. While this does fixes the problem, it exposes you to unnecessary risks as you are granting the service more priviledges than it really needs.

It is better to fix the real cause as described in the article.

|||

It is working now!!!

THanks

|||Bingo! That did it. Thanks!

OLEDB error while trying to import MDB data into SQL 2005

Hello,

I am getting an error while trying to import data into SQL 2005 from an existing Access MDB database. When I try this on another workstation there are no problems and the data is imported successfully.

Could someone tell me what to look for or what setting I have incorrect. On the workstation with the problem I had removed SQL 2000 Personal Edition and installed SQL 2005 Standard Edition. Also, I have both Visual 2003 and 2005 installed on this workstation as well.

Thanks

TITLE: SQL Server Import and Export Wizard

Could not set up data flow connections.

The connection type "OLEDB" specified for connection manager "{DAE0A984-862B-4E4A-890E-8DB4860C9F6B}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.

ADDITIONAL INFORMATION:

The connection type "OLEDB" specified for connection manager "{DAE0A984-862B-4E4A-890E-8DB4860C9F6B}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
({55FFB2C2-E461-4FDB-B3C4-EE4677B80C77})

BUTTONS:

OK

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Error)

Messages

The connection "SourceConnectionOLEDB" is not found. This error is thrown by Connections collection when the specific connection element is not found.
({3DDD68E3-30A4-4513-B0AB-45F340BAB4C0})

- Setting Destination Connection (Stopped)

- Validating (Stopped)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Stopped)

- Copying to [EJTest].[dbo].[Journal] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Did you ever figure out how to fix this. I had the same problem on my laptop, and I had to rebuild my laptop from scratch to fix it. I have another person with the same problem. I would like to fix this with out rebuilding.

Thanks

Michael Robey
mrobey@.worldinsco.com

|||This is a SSIS issue.|||

Yes it is a SSIS issue. Open SQL Server Configuration Manager. Right click on SQL Server Integration Services. Select properties and in the Log On tab change the built-in account.

It should be the same account you are using to run SQL Server. In my case is a standalone server for test/dev purpuse so I don't use Network account. I changed both to Local System. That should fix the issue.

|||

I had the same problem too.

Thanks Carlos, fixed it perfectly.

|||

I had the problem in general. Couldnt import tables from sql2000 / 2005 same and different databases.

Trough Your remark (Thank You) i fiddeld a little with the properties of SSIS and MSSQL Services. if both log on as the built in local system user,it works too. or local system and a Windows user of the machine, thats ok too.

I had posted this problem in

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=344363&SiteID=1

but never got a reaction from ms

With some combinations you can optionally save the package, with some the wizard throws an error.

A definite clarification from ms about the conditions would be very helpful.

Michael

|||It really solved the problem.
Thank you very much!!!
|||

Better late than never!

Your solution solved my issue as well.

Thank you very much!

|||

It worked for me as well,

I wanted to import a visual foxpro Database to SQL2005, I installed Visual Foxpro oledb (9.0) . but I got the Error message. I tried importing a MSAccess db and it gave me the same error. following up Carlos Instruction, It worked both for msAccess db and Foxpro OleDB

Thanks

|||

Please read the KB article http://support.microsoft.com/kb/913817

The SSIS service does not have to run as the same account as SQL Server instance. What helped you is that you've changed it to run as account with Administrator rights. While this does fixes the problem, it exposes you to unnecessary risks as you are granting the service more priviledges than it really needs.

It is better to fix the real cause as described in the article.

|||

It is working now!!!

THanks

|||Bingo! That did it. Thanks!

OLE DB Provider Oracle

english:

Hello,

I have got a problem with the a linked server in SQL server 2005 (64 bit) to Oracle 8.0.5. (32 bit).

Further details:

The old existing SQL server 2000 (32 bit) has a linked server to Oracle 8.0.5. The works with the OLE DB provider from Microsoft. The new SQL server 2005 (64 bit) should also have a linked server to this Oralce database. I have installed the Oracle 8.0 clients on the new server. The connection to oracle works with the client tools from Oracle.

But the SQL server 2005 couldn't connect to the oracle database.

The error message from the SQL server sounds (translated form a german error message):

A instance of the OLE DB provider "OraOLEDB.Oracle" for the linked server "xxxxxx" can't create.

Is the Oracle client software / OLE DB provider the problem?

Exist an other OLE DB provider for Oracle, may be from Microsoft, which works?

Thanks for your help

german:

Hallo Zusammen,

ích habe ein Problem bei der Migration von SQL Server 2005 auf ein x64 Windows System.

Problem ist folgendes:
Auf dem alten Server Windows x32 lief SQL Server 2000 mit einem Verbindungsserver zum Oracle Server 8.05. Das funktionierte mit dem OLE DB treiber von Microsoft hervoragend. Nun haben wir aber eine neue Windows x64 Maschine und ich m?chte die Verbindung zum Oracle Server wieder nutzen. Hatte die Oracle Client Software installiert und bekomme eine Fehlermeldung:

Eine Instanz des OLE DB Anbieters "ORAOLEDB.ORACLE" für den Verbindungsserver "xxxxx" kann nicht erstellt werden.

Ist das ein Problem mit der Oracle Client Software bzw. dem zugrunde liegenden OLE DB Treiber?
Gibt es einen anderen OLE DB Treiber für Oracle, z.B. von Microsoft, der funktionieren k?nnte?

Bin schon l?nger damit besch?ftigt, das zum Laufen zu bekommen. Die Oracle Version ist nicht die neueste, ich wei?.
Was kann ich tun, damit das endlich l?uft.

Für Hilfen w?re ich sehr dankbar.

If you are running 64-bit SQL, you need to use a 64-bit OLEDB provider with linked servers.

So you need to get Oracle's 64-bit OLEDB Provider for Oracle, Microsoft does not provide a 64-bit OLEDB Provider for Oracle.

|||

I got it mostly working with the latest oracle client (10.2.0.3) which you can download from Oracle if you have support with them. If you don't have the .3 version, you'll encounter a bug with their client if you make connections in DTS / intergration services packages to the Oracle DB server. I'm still running into an issue with a remote link server (see my other post).

Here are the steps I did to make the client work. Hope this helps you.

1) To get it working you need to do a custom installation and select at minimum:

Oracle Windows Interfaces (all)

Oracle Database Utilities

SQL*Plus

Oracle Net

2) You then need to copy the files: tnsnames.ora AND sqlnet.ora from another DB server to where ever the Oracle client is installed. In my case it's located at: D:\oracle\product\10.2.0\client\NETWORK\ADMIN

3) You then need to modify the registry to change the dll's that MDAC uses to connect to Oracle:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI

OracleXaLib=oraclient10.dll

OracleSqlLib=orasql10.dll

OracleOciLib=oci.dll

4) You then need to reboot to have the changes take effect.

5a) Browse to: /Server Objects/Linked Servers/Providers and right click on OraOLEDB.Oracle and select properties. Then check the following boxes: Dynamic parameter, Allow inprocess

5b) Then you need to create the link server in the Microsoft SQL Server Management Studio by doing the following:

Browse to: Server Objects/Linked Servers, right click and select "New Linked Server"

Enter the linked server name

Under provider select "Oracle Provider for OLE DB"

Enter a product name IE Oracle...

Enter the data source name (the same name in the tnsnames.ora file)

Select "Security" on the left side and select the last radio button "Be made using this security context" and enter the user name and password to connect to the remote db.

6) Then click OK :)

|||

Hello Arron,

thanks for the information.

I have installed the oracle version 10.2.0.1.0. That was the latest that I found on http://www.oracle.com/technology/software/products/database/oracle10g/index.html for Windows with 64-bit.

We haven't got a support contract with oracle, because it is an old version.

We wouldn't use DTS or integration services (would be nice if it's working also).
We need this only in stored procedures with SQL statements (SELECT, INSERT and UPDATE).

Stefan and MediaK

OLE DB Provider Oracle

english:

Hello,

I have got a problem with the a linked server in SQL server 2005 (64 bit) to Oracle 8.0.5. (32 bit).

Further details:

The old existing SQL server 2000 (32 bit) has a linked server to Oracle 8.0.5. The works with the OLE DB provider from Microsoft. The new SQL server 2005 (64 bit) should also have a linked server to this Oralce database. I have installed the Oracle 8.0 clients on the new server. The connection to oracle works with the client tools from Oracle.

But the SQL server 2005 couldn't connect to the oracle database.

The error message from the SQL server sounds (translated form a german error message):

A instance of the OLE DB provider "OraOLEDB.Oracle" for the linked server "xxxxxx" can't create.

Is the Oracle client software / OLE DB provider the problem?

Exist an other OLE DB provider for Oracle, may be from Microsoft, which works?

Thanks for your help

german:

Hallo Zusammen,

ích habe ein Problem bei der Migration von SQL Server 2005 auf ein x64 Windows System.

Problem ist folgendes:
Auf dem alten Server Windows x32 lief SQL Server 2000 mit einem Verbindungsserver zum Oracle Server 8.05. Das funktionierte mit dem OLE DB treiber von Microsoft hervoragend. Nun haben wir aber eine neue Windows x64 Maschine und ich m?chte die Verbindung zum Oracle Server wieder nutzen. Hatte die Oracle Client Software installiert und bekomme eine Fehlermeldung:

Eine Instanz des OLE DB Anbieters "ORAOLEDB.ORACLE" für den Verbindungsserver "xxxxx" kann nicht erstellt werden.

Ist das ein Problem mit der Oracle Client Software bzw. dem zugrunde liegenden OLE DB Treiber?
Gibt es einen anderen OLE DB Treiber für Oracle, z.B. von Microsoft, der funktionieren k?nnte?

Bin schon l?nger damit besch?ftigt, das zum Laufen zu bekommen. Die Oracle Version ist nicht die neueste, ich wei?.
Was kann ich tun, damit das endlich l?uft.

Für Hilfen w?re ich sehr dankbar.

If you are running 64-bit SQL, you need to use a 64-bit OLEDB provider with linked servers.

So you need to get Oracle's 64-bit OLEDB Provider for Oracle, Microsoft does not provide a 64-bit OLEDB Provider for Oracle.

|||

I got it mostly working with the latest oracle client (10.2.0.3) which you can download from Oracle if you have support with them. If you don't have the .3 version, you'll encounter a bug with their client if you make connections in DTS / intergration services packages to the Oracle DB server. I'm still running into an issue with a remote link server (see my other post).

Here are the steps I did to make the client work. Hope this helps you.

1) To get it working you need to do a custom installation and select at minimum:

Oracle Windows Interfaces (all)

Oracle Database Utilities

SQL*Plus

Oracle Net

2) You then need to copy the files: tnsnames.ora AND sqlnet.ora from another DB server to where ever the Oracle client is installed. In my case it's located at: D:\oracle\product\10.2.0\client\NETWORK\ADMIN

3) You then need to modify the registry to change the dll's that MDAC uses to connect to Oracle:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI

OracleXaLib=oraclient10.dll

OracleSqlLib=orasql10.dll

OracleOciLib=oci.dll

4) You then need to reboot to have the changes take effect.

5a) Browse to: /Server Objects/Linked Servers/Providers and right click on OraOLEDB.Oracle and select properties. Then check the following boxes: Dynamic parameter, Allow inprocess

5b) Then you need to create the link server in the Microsoft SQL Server Management Studio by doing the following:

Browse to: Server Objects/Linked Servers, right click and select "New Linked Server"

Enter the linked server name

Under provider select "Oracle Provider for OLE DB"

Enter a product name IE Oracle...

Enter the data source name (the same name in the tnsnames.ora file)

Select "Security" on the left side and select the last radio button "Be made using this security context" and enter the user name and password to connect to the remote db.

6) Then click OK :)

|||

Hello Arron,

thanks for the information.

I have installed the oracle version 10.2.0.1.0. That was the latest that I found on http://www.oracle.com/technology/software/products/database/oracle10g/index.html for Windows with 64-bit.

We haven't got a support contract with oracle, because it is an old version.

We wouldn't use DTS or integration services (would be nice if it's working also).
We need this only in stored procedures with SQL statements (SELECT, INSERT and UPDATE).

Stefan and MediaK

old sql2k5 folder

I have remove the existing sql 2k5server db by "remove/add program" and the
install a new sql2k5 in another folder. Now I tried to remove the old MS SQL
server folder and within. But it gives me an error saying it is in used ...
and therefore I cannot remove it. Can anyone please advise me how to remove
this folder? I thought the old folder is not used by any program after I
re-install a new ms sql server. Please help. Thanks.Hi,
have a look in the registry and search for the absolute path of the old
installation. There might be some logs which be flushed to the old
location.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--|||Can anyone please help? Thanks
"00MichaelJordan" <MJ@.yahoo.com> wrote in message
news:ObrvrOfOHHA.4940@.TK2MSFTNGP03.phx.gbl...
>I have remove the existing sql 2k5server db by "remove/add program" and the
>install a new sql2k5 in another folder. Now I tried to remove the old MS
>SQL server folder and within. But it gives me an error saying it is in used
>... and therefore I cannot remove it. Can anyone please advise me how to
>remove this folder? I thought the old folder is not used by any program
>after I re-install a new ms sql server. Please help. Thanks.
>|||You need to see what process still has this folder open. When I'm
*desperate* I use this program:
http://ccollomb.free.fr/unlocker/
It will tell you what's using the file and will let you "force" it
closed, allowing you to delete it. Hopefully SQL Server will not be
using it. Try not to force-delete these things. See what program is
using the file first, shut it down, then delete the file. Just be
careful not to hose your SQL Server installation ;-)
-Dave Markle
http://www.markleconsulting.com/blog
00MichaelJordan wrote:
> I have remove the existing sql 2k5server db by "remove/add program" and th
e
> install a new sql2k5 in another folder. Now I tried to remove the old MS S
QL
> server folder and within. But it gives me an error saying it is in used ..
.
> and therefore I cannot remove it. Can anyone please advise me how to remo
ve
> this folder? I thought the old folder is not used by any program after I
> re-install a new ms sql server. Please help. Thanks.
>

old sql2k5 folder

I have remove the existing sql 2k5server db by "remove/add program" and the
install a new sql2k5 in another folder. Now I tried to remove the old MS SQL
server folder and within. But it gives me an error saying it is in used ...
and therefore I cannot remove it. Can anyone please advise me how to remove
this folder? I thought the old folder is not used by any program after I
re-install a new ms sql server. Please help. Thanks.
Hi,
have a look in the registry and search for the absolute path of the old
installation. There might be some logs which be flushed to the old
location.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Can anyone please help? Thanks
"00MichaelJordan" <MJ@.yahoo.com> wrote in message
news:ObrvrOfOHHA.4940@.TK2MSFTNGP03.phx.gbl...
>I have remove the existing sql 2k5server db by "remove/add program" and the
>install a new sql2k5 in another folder. Now I tried to remove the old MS
>SQL server folder and within. But it gives me an error saying it is in used
>... and therefore I cannot remove it. Can anyone please advise me how to
>remove this folder? I thought the old folder is not used by any program
>after I re-install a new ms sql server. Please help. Thanks.
>
|||You need to see what process still has this folder open. When I'm
*desperate* I use this program:
http://ccollomb.free.fr/unlocker/
It will tell you what's using the file and will let you "force" it
closed, allowing you to delete it. Hopefully SQL Server will not be
using it. Try not to force-delete these things. See what program is
using the file first, shut it down, then delete the file. Just be
careful not to hose your SQL Server installation ;-)
-Dave Markle
http://www.markleconsulting.com/blog
00MichaelJordan wrote:
> I have remove the existing sql 2k5server db by "remove/add program" and the
> install a new sql2k5 in another folder. Now I tried to remove the old MS SQL
> server folder and within. But it gives me an error saying it is in used ...
> and therefore I cannot remove it. Can anyone please advise me how to remove
> this folder? I thought the old folder is not used by any program after I
> re-install a new ms sql server. Please help. Thanks.
>

old sql2k5 folder

I have remove the existing sql 2k5server db by "remove/add program" and the
install a new sql2k5 in another folder. Now I tried to remove the old MS SQL
server folder and within. But it gives me an error saying it is in used ...
and therefore I cannot remove it. Can anyone please advise me how to remove
this folder? I thought the old folder is not used by any program after I
re-install a new ms sql server. Please help. Thanks.Hi,
have a look in the registry and search for the absolute path of the old
installation. There might be some logs which be flushed to the old
location.
HTH, Jens K. Suessmeyer.
--
http://www.sqlserver2005.de
--|||Can anyone please help? Thanks
"00MichaelJordan" <MJ@.yahoo.com> wrote in message
news:ObrvrOfOHHA.4940@.TK2MSFTNGP03.phx.gbl...
>I have remove the existing sql 2k5server db by "remove/add program" and the
>install a new sql2k5 in another folder. Now I tried to remove the old MS
>SQL server folder and within. But it gives me an error saying it is in used
>... and therefore I cannot remove it. Can anyone please advise me how to
>remove this folder? I thought the old folder is not used by any program
>after I re-install a new ms sql server. Please help. Thanks.
>|||You need to see what process still has this folder open. When I'm
*desperate* I use this program:
http://ccollomb.free.fr/unlocker/
It will tell you what's using the file and will let you "force" it
closed, allowing you to delete it. Hopefully SQL Server will not be
using it. Try not to force-delete these things. See what program is
using the file first, shut it down, then delete the file. Just be
careful not to hose your SQL Server installation ;-)
--
-Dave Markle
http://www.markleconsulting.com/blog
00MichaelJordan wrote:
> I have remove the existing sql 2k5server db by "remove/add program" and the
> install a new sql2k5 in another folder. Now I tried to remove the old MS SQL
> server folder and within. But it gives me an error saying it is in used ...
> and therefore I cannot remove it. Can anyone please advise me how to remove
> this folder? I thought the old folder is not used by any program after I
> re-install a new ms sql server. Please help. Thanks.
>

old question about login, but no help from the existing threads

osql -d adventureworks2000 -U admin -P admin
Login failed for user 'admin'. Reason: Not associated with a trusted SQL
Server connection.
My system and configurations:
- Winxp + sp2
- mssql developer edition + sp3a
- Windows Authentication only
- Local System Account is used to start the sql instance
- admin/admin is the administrator account to login to the xp box
- admin/admin was added to "SQL Server Group/[Machine Name]/Security/Log
ins"
with the database access and all database role assigned to the database in
question.
- admin/admin was added to "Databases/[database in question]/Users, with
Permit in Database Role all checked.
Am I missing anything?
Thanks> - Windows Authentication only
osql -d adventureworks2000 -E
AMB
"man-in-nature" wrote:

> osql -d adventureworks2000 -U admin -P admin
> Login failed for user 'admin'. Reason: Not associated with a trusted SQL
> Server connection.
> My system and configurations:
> - Winxp + sp2
> - mssql developer edition + sp3a
> - Windows Authentication only
> - Local System Account is used to start the sql instance
> - admin/admin is the administrator account to login to the xp box
> - admin/admin was added to "SQL Server Group/[Machine Name]/Security/L
ogins"
> with the database access and all database role assigned to the database in
> question.
> - admin/admin was added to "Databases/[database in question]/Users, wi
th
> Permit in Database Role all checked.
> Am I missing anything?
> Thanks
>