DTS from AS 400 to Sql server

Hi DBA's:

I need to transfer data from my source database which is Client Access iSeries AS 400
running DB 400 to my database in SQL Server 2000. Here is what I need to do -

There are files in the Production Enviornment on the DB 400. I need to connect to these files from my SQL Server 2000 database using DTS Wizard and tranfer these files into the tables of my SQL Server 2000 database. Can someone walk me through with the options on the source side of the DTS that I need to choose in order to connect to my AS 400 and get the data.

Thanks in anticipation.I'm assuming you mean DB2, not DB 400...

Look up sp_addlinkedserver in BOL

DTS execution from client machine fails connecting to Oracle

I have created a DTS package that pulls data in from Oracle into SQL
Server. When I run it directly on the server (from Enterprise
Manager), it works fine. When I run it from Enterprise Manager on a
client machine that does not have the Oracle client software, it does
not run, giving me the error: "The Oracle client and networking
components were not found...". I was hoping I wouldn't need to have
the client software installed on a machine other than the server where
Sql Server is running. The problem here is that there are a number of
machines from where I would like to execute this DTS package that I do
not want to install/configure the Oracle client software. I don't
quite understand why the configuration of the client is important
here. In my mind, when I am using enterprise manager from a client
machine, I am using it sort of like a terminal services client to
connect to the server. I guess there is a lot more happening in the
background.

Thanks for any feedback,
MarcusDo you have the proper ODBC driver that you are using in the DTS on the
client machine? same as the one on your server.

"Marcus" <holysmokes99@.hotmail.com> wrote in message
news:1783abaf.0307250838.70a1aaa4@.posting.google.c om...
> I have created a DTS package that pulls data in from Oracle into SQL
> Server. When I run it directly on the server (from Enterprise
> Manager), it works fine. When I run it from Enterprise Manager on a
> client machine that does not have the Oracle client software, it does
> not run, giving me the error: "The Oracle client and networking
> components were not found...". I was hoping I wouldn't need to have
> the client software installed on a machine other than the server where
> Sql Server is running. The problem here is that there are a number of
> machines from where I would like to execute this DTS package that I do
> not want to install/configure the Oracle client software. I don't
> quite understand why the configuration of the client is important
> here. In my mind, when I am using enterprise manager from a client
> machine, I am using it sort of like a terminal services client to
> connect to the server. I guess there is a lot more happening in the
> background.
> Thanks for any feedback,
> Marcus|||Marcus wrote:

> I have created a DTS package that pulls data in from Oracle into SQL
> Server. When I run it directly on the server (from Enterprise
> Manager), it works fine. When I run it from Enterprise Manager on a
> client machine that does not have the Oracle client software, it does
> not run, giving me the error: "The Oracle client and networking
> components were not found...". I was hoping I wouldn't need to have
> the client software installed on a machine other than the server where
> Sql Server is running. The problem here is that there are a number of
> machines from where I would like to execute this DTS package that I do
> not want to install/configure the Oracle client software. I don't
> quite understand why the configuration of the client is important
> here. In my mind, when I am using enterprise manager from a client
> machine, I am using it sort of like a terminal services client to
> connect to the server. I guess there is a lot more happening in the
> background.
> Thanks for any feedback,
> Marcus

The Oracle client is required. So is paying attention to the license
agreement.

--
Daniel Morgan
http://www.outreach.washington.edu/...oad/oad_crs.asp
damorgan@.x.washington.edu
(replace 'x' with a 'u' to reply)sql

DTS execution from client machine fails connecting to Oracle

I have created a DTS package that pulls data in from Oracle into SQL
Server. When I run it directly on the server (from Enterprise
Manager), it works fine. When I run it from Enterprise Manager on a
client machine that does not have the Oracle client software, it does
not run, giving me the error: "The Oracle client and networking
components were not found...". I was hoping I wouldn't need to have
the client software installed on a machine other than the server where
Sql Server is running. The problem here is that there are a number of
machines from where I would like to execute this DTS package that I do
not want to install/configure the Oracle client software. I don't
quite understand why the configuration of the client is important
here. In my mind, when I am using enterprise manager from a client
machine, I am using it sort of like a terminal services client to
connect to the server. I guess there is a lot more happening in the
background.
Thanks for any feedback,
MarcusDo you have the proper ODBC driver that you are using in the DTS on the
client machine? same as the one on your server.
"Marcus" <holysmokes99@.hotmail.com> wrote in message
news:1783abaf.0307250838.70a1aaa4@.posting.google.com...
> I have created a DTS package that pulls data in from Oracle into SQL
> Server. When I run it directly on the server (from Enterprise
> Manager), it works fine. When I run it from Enterprise Manager on a
> client machine that does not have the Oracle client software, it does
> not run, giving me the error: "The Oracle client and networking
> components were not found...". I was hoping I wouldn't need to have
> the client software installed on a machine other than the server where
> Sql Server is running. The problem here is that there are a number of
> machines from where I would like to execute this DTS package that I do
> not want to install/configure the Oracle client software. I don't
> quite understand why the configuration of the client is important
> here. In my mind, when I am using enterprise manager from a client
> machine, I am using it sort of like a terminal services client to
> connect to the server. I guess there is a lot more happening in the
> background.
> Thanks for any feedback,
> Marcus|||Unfortunately you will need the Oracle connectivity on the server/or
anywhere else that tells this package to execute
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org|||Marcus wrote:
> I have created a DTS package that pulls data in from Oracle into SQL
> Server. When I run it directly on the server (from Enterprise
> Manager), it works fine. When I run it from Enterprise Manager on a
> client machine that does not have the Oracle client software, it does
> not run, giving me the error: "The Oracle client and networking
> components were not found...". I was hoping I wouldn't need to have
> the client software installed on a machine other than the server where
> Sql Server is running. The problem here is that there are a number of
> machines from where I would like to execute this DTS package that I do
> not want to install/configure the Oracle client software. I don't
> quite understand why the configuration of the client is important
> here. In my mind, when I am using enterprise manager from a client
> machine, I am using it sort of like a terminal services client to
> connect to the server. I guess there is a lot more happening in the
> background.
> Thanks for any feedback,
> Marcus
The Oracle client is required. So is paying attention to the license
agreement.
--
Daniel Morgan
http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
damorgan@.x.washington.edu
(replace 'x' with a 'u' to reply)

DTS Executable error

We just installed SP3. The problem is that when I'm executing a DTS package
remotely from my client machine, it bombs when on the task that call an exe
cutable (error #128).
I don't get this error when I execute the DTS on the Server.
ThanksDavid,
If you can't install SQL client tools on the client machine, you're going to
have fun now.
Visit: http://www.sqldts.com/default.aspx?6,105,225,0,1
James Hokes
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:6529CE21-68FF-4394-B2F3-0C3AF9F93959@.microsoft.com...

quote:

---

> We just installed SP3. The problem is that when I'm executing a DTS

---

package remotely from my client machine, it bombs when on the task that call
an executable (error #128).

quote:

---

> I don't get this error when I execute the DTS on the Server.
> Thanks

---

sql

DTS Executable error

We just installed SP3. The problem is that when I'm executing a DTS package remotely from my client machine, it bombs when on the task that call an executable (error #128)
I don't get this error when I execute the DTS on the Server
ThanksDavid,
If you can't install SQL client tools on the client machine, you're going to
have fun now.
Visit: http://www.sqldts.com/default.aspx?6,105,225,0,1
James Hokes
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:6529CE21-68FF-4394-B2F3-0C3AF9F93959@.microsoft.com...
> We just installed SP3. The problem is that when I'm executing a DTS
package remotely from my client machine, it bombs when on the task that call
an executable (error #128).
> I don't get this error when I execute the DTS on the Server.
> Thanks

DTS Designer Error: The specified module could not be found

Hi folks
I am connecting to a SQL Server 2000 (SP3) from a client Enterprise
Manager. It connects to it, well.
But if I try to open an existing DTS package (located under Local
packages) it throws an error "DTS Designer Error The specified module
could not be found" and it closes.
Same error occurs if I try to open a .dts file also.
Your help is appreciated.
Thanks in advance
Venkat.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!Hi
Searching google for you error messages turned up these two possible
solutions:
http://tinyurl.com/66tsu
http://tinyurl.com/6e6jm
John
"Venkatesan" wrote:

> Hi folks
> I am connecting to a SQL Server 2000 (SP3) from a client Enterprise
> Manager. It connects to it, well.
> But if I try to open an existing DTS package (located under Local
> packages) it throws an error "DTS Designer Error The specified module
> could not be found" and it closes.
> Same error occurs if I try to open a .dts file also.
> Your help is appreciated.
> Thanks in advance
> Venkat.
>
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!
>

DTS designer error

When I open my DTS package at my PC ( Client ) .There is an error message show like below .
DTR Designer Error.
There was a problem retriving the list of OLE DB providers.
No. Provider is selected .TO continue,you must select a valid provider.
Please helpHowdy

Delete the server registration in EM and re-register the server.

Post back if problems.

Cheers

SG.|||What is the level of service pack of SQL on the client machine?
Ensure to maintain similar service pack on Server and on client as well.|||Originally posted by sqlguy7777
Howdy

Delete the server registration in EM and re-register the server.

Post back if problems.

Cheers

SG.

I have already done as your mention but it still show the same error message

Any idea ??|||Originally posted by Satya
What is the level of service pack of SQL on the client machine?
Ensure to maintain similar service pack on Server and on client as well.

How can I check the service pack verion of both server and client ? Please introduce me

Thanks|||SELECT serverproperty('ProductLevel')

Regards!!|||select @.@.version;

This will give you the details of OS level as well as SQL Server level.|||This causes due to .DLL mismatch or even MDAC version between client and server machines, so ensure you have all the similar levels.

This @.@.Version or Serverproperty will give you version on server for SQL Server and on client machine ensure to run service pack for SQL again which might resolve the issue.

DTS and SOAP Web Service

Hi,

I have a client that needs to issue soap calls to a third-party web
service from within a DTS package. Is this even possible? I've
looked everywhere and found the sqlxml, but that looks like it
provides a soap web service, not consumes one.

Right now, we are consuming the same web service in an ASP.NET
application and would love to use the same code, but am really just
looking for the best solution. Basically, the only firm requirements
are that the client needs to provide a text file of items that need to
be posted to the third-party via their web service. Right now, we use
dts for the client to upload other text files, that's why I was hoping
to use the same procedure, but if we need to go another route, I'm
sure I can convince them.

Any suggestions?

TreyTrey Bean wrote:

Quote:

Originally Posted by

Hi,
>
I have a client that needs to issue soap calls to a third-party web
service from within a DTS package. Is this even possible? I've
looked everywhere and found the sqlxml, but that looks like it
provides a soap web service, not consumes one.
>
Right now, we are consuming the same web service in an ASP.NET
application and would love to use the same code, but am really just
looking for the best solution. Basically, the only firm requirements
are that the client needs to provide a text file of items that need to
be posted to the third-party via their web service. Right now, we use
dts for the client to upload other text files, that's why I was hoping
to use the same procedure, but if we need to go another route, I'm
sure I can convince them.
>
Any suggestions?
>
Trey
>

Trey,

Did you find a solution?

Jonathan

DTS and Fixed Widths

Hi all.

I'm trying to export some tables in fixed width format for a client that needs it this way. The first time I did this, using Import/Export in Enterprise Manager, integer fields were 12 chars long. However, when I saved this as a DTS and ran it again later, it made integers 4 chars in the text file (which matches the lengths of the datatypes you see in enterprise manager.)

Why is this difference there? What do I need to do differently? Also, is there a list of how wide each data type is when exported as fixed delimited text?

thanks,
CraigWell, I just followed the same steps and received consistent results. My integer files were 12 characters with the initial run, and also when I saved it as a DTS package and ran it.

My suggestion is to check the Transform Data Task Properties in the DTS package and check the information in the Size column on the Destination tab for each column.

When you create the package via the Import/Export option in Enterprise Manager, one of the steps includes a "Transform..." button. Click on this so you can explictly set the size of each column you are exporting.

Terri|||yes I found it. There is a "Define Columns" button that specifies the size. Weird that the same DTS package yielded multiple results.

Thanks!

DTS and Fixed Widths

Hi all.

I'm trying to export some tables in fixed width format for a client that needs it this way. The first time I did this, using Import/Export in Enterprise Manager, integer fields were 12 chars long. However, when I saved this as a DTS and ran it again later, it made integers 4 chars in the text file (which matches the lengths of the datatypes you see in enterprise manager.)

Why is this difference there? What do I need to do differently? Also, is there a list of how wide each data type is when exported as fixed delimited text?

thanks,
CraigWhy don't you use bcp in a sproc with format files?

And as far as DTS changing widths...I don't think (damn it, happened again) so...|||I assume you're talking about Bulk Copy? I haven't done that before, but its definitely an option -- I just ASSUMED DTS would be easier.

DTS and Excel 2003

We have a DTS package that imports data from a client's Excel file. Previously our client was using Excel 2000, but recently they upgraded to Office 2003, and now suddenly when I try to view the transformation task properties I get a Jet Database Engine error: "External table is not in the expected format".

Everything else with the file appears the same (layout, formatting, etc.).

Any suggestions?

I have the same problem. Did you ever received suggestions or a solution. I would be happy to have the answer.

Thanks

DTS and Excel 2003

We have a DTS package that imports data from a client's Excel file. Previously our client was using Excel 2000, but recently they upgraded to Office 2003, and now suddenly when I try to view the transformation task properties I get a Jet Database Engine error: "External table is not in the expected format".

Everything else with the file appears the same (layout, formatting, etc.).

Any suggestions?

I have the same problem. Did you ever received suggestions or a solution. I would be happy to have the answer.

Thanks

DTS and Client Routing

Our shop executes "on the fly" DTS packages that copy (with a few
transformations, etc.) from one database to another database all on the same
server. One of the problems we have is that DTS routes the data stream
through the client which gives quite slow response time even for simple DTS
packages. Is there any way around this?
Surely, there's got to be a way to keep the data stream on the server
itself. All help is appreciated.
Run the package as a job on the server. That's the simplest way to achieve
this. Also, you could terminal service onto the server and then invoke the
DTS package from the server itself, instead of running it from a client
machine.
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:F98323F3-1D6A-4819-B160-376A37C024DA@.microsoft.com...
> Our shop executes "on the fly" DTS packages that copy (with a few
> transformations, etc.) from one database to another database all on the
> same
> server. One of the problems we have is that DTS routes the data stream
> through the client which gives quite slow response time even for simple
> DTS
> packages. Is there any way around this?
> Surely, there's got to be a way to keep the data stream on the server
> itself. All help is appreciated.

DTS and Client Routing

Our shop executes "on the fly" DTS packages that copy (with a few
transformations, etc.) from one database to another database all on the same
server. One of the problems we have is that DTS routes the data stream
through the client which gives quite slow response time even for simple DTS
packages. Is there any way around this?
Surely, there's got to be a way to keep the data stream on the server
itself. All help is appreciated.Run the package as a job on the server. That's the simplest way to achieve
this. Also, you could terminal service onto the server and then invoke the
DTS package from the server itself, instead of running it from a client
machine.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:F98323F3-1D6A-4819-B160-376A37C024DA@.microsoft.com...
> Our shop executes "on the fly" DTS packages that copy (with a few
> transformations, etc.) from one database to another database all on the
> same
> server. One of the problems we have is that DTS routes the data stream
> through the client which gives quite slow response time even for simple
> DTS
> packages. Is there any way around this?
> Surely, there's got to be a way to keep the data stream on the server
> itself. All help is appreciated.

DTS and Client Routing

Our shop executes "on the fly" DTS packages that copy (with a few
transformations, etc.) from one database to another database all on the same
server. One of the problems we have is that DTS routes the data stream
through the client which gives quite slow response time even for simple DTS
packages. Is there any way around this?
Surely, there's got to be a way to keep the data stream on the server
itself. All help is appreciated.Run the package as a job on the server. That's the simplest way to achieve
this. Also, you could terminal service onto the server and then invoke the
DTS package from the server itself, instead of running it from a client
machine.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:F98323F3-1D6A-4819-B160-376A37C024DA@.microsoft.com...
> Our shop executes "on the fly" DTS packages that copy (with a few
> transformations, etc.) from one database to another database all on the
> same
> server. One of the problems we have is that DTS routes the data stream
> through the client which gives quite slow response time even for simple
> DTS
> packages. Is there any way around this?
> Surely, there's got to be a way to keep the data stream on the server
> itself. All help is appreciated.

DTExec stops running without error message

For a client i have built an application to give them the possibility to load packages for their data warehouse.

This application starts a database job in SQL Server, which in turn starts a dtsx package. This package loops over the contents of a table and starts the packages that are marked to be executed.

This all work well most of the time. Sometimes though, DTExec, the process running the packages, just stops running. There are no entries in the event viewer or anywhere else.

I run Windows Server 2003 with SQL Server 2005 SE SP1. The packages are run from the filesystem, not the database.

Has anyone encountered the same problem and know a solution? I can't find any info on the internet.

- Matthijs
Do you have package logging turned on? Enable all of the logging events and see if you can catch something that way. Log to a text file or to SQL Server.|||No logging was active. I'll turn it on and see if the problem occurs again. One of the problems is that it stops randomly so it's not easily reproducable.

Thanks for the quick response. I'll post again when it happens again.

- Matthijs
|||The problem occured again. I checked the log and the last thing in there is the OnPostValidate event of one of the script tasks. Again no error in the windows eventlogger and nop apperant reason why it stopped.

There have been some other problems though. It have been brought to my attention that the server on which the process runs has the tendancy to overheat. It gives a message that it will be shut down due to overheating or the loss of cooling and right after that a message that shutdown was cancelled by the administrator.

Because of this it occured to me that the problems might come from damaged memory. I'm going to have the client's IT support department check the systems memory and see where that gets me. Do you think that this is a possiblity? I would say that when memory is damaged it should't effect just one process, but that other processes would suffer from the same damage. This does not seem to be the case however. So it's a longshot but i'll have them check it anyway.

- Matthijs

|||

If the fault is suspected with DTEXEC, package logging may not help, but the console output from DTEEXEC itself may be of use. Ensure you have set the job step log, in teh Advanced tab of the job step. If DTEXEC itself errors I would expect this to capture it.

If a shutdown started and was then cancelled, it could have started to kill off processes? If it is running hot then you could get all sorts of strange corruptions, but they would probably not manifest themselves under normal conditions.

|||The cancelled shutdown scenario has not happened lately. That was mostly last summer. I thought it might be result of the damage done back then. I will enable logging in the job step and wait until it happens again.

- Matthijs

|||There seems to be no logging option in the advanced tab of the job step. In the general tab there is a loggin tab, but i think this just logs the package log entries, just like the package itself does.

DTExec stops running without error message

For a client i have built an application to give them the possibility to load packages for their data warehouse.

This application starts a database job in SQL Server, which in turn starts a dtsx package. This package loops over the contents of a table and starts the packages that are marked to be executed.

This all work well most of the time. Sometimes though, DTExec, the process running the packages, just stops running. There are no entries in the event viewer or anywhere else.

I run Windows Server 2003 with SQL Server 2005 SE SP1. The packages are run from the filesystem, not the database.

Has anyone encountered the same problem and know a solution? I can't find any info on the internet.

- Matthijs
Do you have package logging turned on? Enable all of the logging events and see if you can catch something that way. Log to a text file or to SQL Server.|||No logging was active. I'll turn it on and see if the problem occurs again. One of the problems is that it stops randomly so it's not easily reproducable.

Thanks for the quick response. I'll post again when it happens again.

- Matthijs
|||The problem occured again. I checked the log and the last thing in there is the OnPostValidate event of one of the script tasks. Again no error in the windows eventlogger and nop apperant reason why it stopped.

There have been some other problems though. It have been brought to my attention that the server on which the process runs has the tendancy to overheat. It gives a message that it will be shut down due to overheating or the loss of cooling and right after that a message that shutdown was cancelled by the administrator.

Because of this it occured to me that the problems might come from damaged memory. I'm going to have the client's IT support department check the systems memory and see where that gets me. Do you think that this is a possiblity? I would say that when memory is damaged it should't effect just one process, but that other processes would suffer from the same damage. This does not seem to be the case however. So it's a longshot but i'll have them check it anyway.

- Matthijs

|||

If the fault is suspected with DTEXEC, package logging may not help, but the console output from DTEEXEC itself may be of use. Ensure you have set the job step log, in teh Advanced tab of the job step. If DTEXEC itself errors I would expect this to capture it.

If a shutdown started and was then cancelled, it could have started to kill off processes? If it is running hot then you could get all sorts of strange corruptions, but they would probably not manifest themselves under normal conditions.

|||The cancelled shutdown scenario has not happened lately. That was mostly last summer. I thought it might be result of the damage done back then. I will enable logging in the job step and wait until it happens again.

- Matthijs

|||There seems to be no logging option in the advanced tab of the job step. In the general tab there is a loggin tab, but i think this just logs the package log entries, just like the package itself does.

DTExec stops running without error message

For a client i have built an application to give them the possibility to load packages for their data warehouse.

This application starts a database job in SQL Server, which in turn starts a dtsx package. This package loops over the contents of a table and starts the packages that are marked to be executed.

This all work well most of the time. Sometimes though, DTExec, the process running the packages, just stops running. There are no entries in the event viewer or anywhere else.

I run Windows Server 2003 with SQL Server 2005 SE SP1. The packages are run from the filesystem, not the database.

Has anyone encountered the same problem and know a solution? I can't find any info on the internet.

- Matthijs
Do you have package logging turned on? Enable all of the logging events and see if you can catch something that way. Log to a text file or to SQL Server.|||No logging was active. I'll turn it on and see if the problem occurs again. One of the problems is that it stops randomly so it's not easily reproducable.

Thanks for the quick response. I'll post again when it happens again.

- Matthijs
|||The problem occured again. I checked the log and the last thing in there is the OnPostValidate event of one of the script tasks. Again no error in the windows eventlogger and nop apperant reason why it stopped.

There have been some other problems though. It have been brought to my attention that the server on which the process runs has the tendancy to overheat. It gives a message that it will be shut down due to overheating or the loss of cooling and right after that a message that shutdown was cancelled by the administrator.

Because of this it occured to me that the problems might come from damaged memory. I'm going to have the client's IT support department check the systems memory and see where that gets me. Do you think that this is a possiblity? I would say that when memory is damaged it should't effect just one process, but that other processes would suffer from the same damage. This does not seem to be the case however. So it's a longshot but i'll have them check it anyway.

- Matthijs

|||

If the fault is suspected with DTEXEC, package logging may not help, but the console output from DTEEXEC itself may be of use. Ensure you have set the job step log, in teh Advanced tab of the job step. If DTEXEC itself errors I would expect this to capture it.

If a shutdown started and was then cancelled, it could have started to kill off processes? If it is running hot then you could get all sorts of strange corruptions, but they would probably not manifest themselves under normal conditions.

|||The cancelled shutdown scenario has not happened lately. That was mostly last summer. I thought it might be result of the damage done back then. I will enable logging in the job step and wait until it happens again.

- Matthijs

|||There seems to be no logging option in the advanced tab of the job step. In the general tab there is a loggin tab, but i think this just logs the package log entries, just like the package itself does.

DSN vs login authentication

Hello everybody!
I've created a DSN from a WIN2K Pro client to connect to a SQL Server 7.0
running on a WIN2K Server with domain controller.
The SQL Server authentication mode on the server machine is "Mixed mode"
Inside the client DSN configuration I've specified that the Authentication
Mode is SQL Server Mode, so I've entered the correct values for Access Id
and Password (I've already tested them connecting directly on the server
machine from query analyzer).
If I test this DSN connection everything works fine.
But if I run my VisualFoxPro Application (that use surely the DSN I've set
up) and appears the "sql server connection dialog box" when I click on "Ok"
I obtain the following error:
...
[Microsoft]ODBC-SQL Server Drive][Sql Server][Login failed for u
ser "server
name/user"]
as the Authentication Mode was "Windows" (trusted connection) and not "SQL
Server" as truly is.
Note that on the same network I've others WIN2K box with the same setup
(same MDAC 2.6, same domain user properties, same DSN setup) and for them I
don't have any problems.
Is there a way to force the connection process from the client to the server
to use always "SQL server authentication mode" (if DSN is not enough)?!?!
Can anyone help me? Thanks in advance!
Riccardo Piccini
Supporto Software
EDP SERVICE SRLCheck the version of the SQL Server ODBC driver on the client machine. It
sounds like you are running into a problem with sqlsrv32.dll version
2000.80.194. This version ignores SQL authentication and uses NT
authentication. The only way to resolve the problem is to upgrade teh
version of MDAC. I believe the problem was resolved in MDAC 2.6 SP2.
Rand
This posting is provided "as is" with no warranties and confers no rights.

DSN vs login authentication

Hello everybody!
I've created a DSN from a WIN2K Pro client to connect to a SQL Server 7.0
running on a WIN2K Server with domain controller.
The SQL Server authentication mode on the server machine is "Mixed mode"
Inside the client DSN configuration I've specified that the Authentication
Mode is SQL Server Mode, so I've entered the correct values for Access Id
and Password (I've already tested them connecting directly on the server
machine from query analyzer).
If I test this DSN connection everything works fine.
But if I run my VisualFoxPro Application (that use surely the DSN I've set
up) and appears the "sql server connection dialog box" when I click on "Ok"
I obtain the following error:
...
[Microsoft]ODBC-SQL Server Drive][Sql Server][Login failed for user "server
name/user"]
as the Authentication Mode was "Windows" (trusted connection) and not "SQL
Server" as truly is.
Note that on the same network I've others WIN2K box with the same setup
(same MDAC 2.6, same domain user properties, same DSN setup) and for them I
don't have any problems.
Is there a way to force the connection process from the client to the server
to use always "SQL server authentication mode" (if DSN is not enough)?!?!
Can anyone help me? Thanks in advance!
Riccardo Piccini
Supporto Software
EDP SERVICE SRL
Check the version of the SQL Server ODBC driver on the client machine. It
sounds like you are running into a problem with sqlsrv32.dll version
2000.80.194. This version ignores SQL authentication and uses NT
authentication. The only way to resolve the problem is to upgrade teh
version of MDAC. I believe the problem was resolved in MDAC 2.6 SP2.
Rand
This posting is provided "as is" with no warranties and confers no rights.