DTS Fails

Good Morning,

I've been running into a small problem. There are two people that usually create local packages to be executed by the DTS. Either my boss or I. The problem that I have been running into is, there are some local packages that will not execute when I try to run them. These packages are that my boss has created. When she runs them they work fine. But when I run them they just don't run. The only way I can run the local package is if I log in into the server and run it from there.

The error that I keep getting is:

Unspecified Error
[Microsoft][ODBC Driver Manager] Data Source Name not found and no default driver specified.

What would I be able to do so that I can execute this local package from my computer?Could try changing the owner of the DTS package.

Have a look at the following link and tell me if it helps your situation.

http://www.sqldts.com/?212|||What is the package doing exactly. Is it accessing an odbc datasource and if so do you have this set up locally?|||It is accessing a datasource, and it has been set up on my machine. We use the same data source to import information. I am able to run other DTS that have been created by her, but I am not successful at executing all of them.

I did go to the link listed by aldo_2003 and there was some helpful information. So if I am not apart of the sysadmin group, then that can be a reason for me not being able to execute the local package? Cause like i said, when I log on the our server, I am able to execute the package just fine. Just not from my machine.|||You need to be either ower or part of sysadmin to execute the package to run.|||Otherwise what you can do is open the query analyzer, connect to the remote server and EXECUTE master.dbo.xp_cmdshell 'dtsrun /S (local) /U {uid} /P {password} /N {name dts package}'

With this you can see whether the package executes well or not.

If you wish to schedule this package on the remote server you need to modify the DTSrun on each step from the schedule as well.
Modify the dts to read the same: dtsrun /S (local) /U etc... via the Tab Steps and the button Edit|||Thank you very much for all your help. I was listed as a sysadmin, but there were a few drivers that I had to add to my user dsn. That was the whole reason why I was getting the error. Everything works fine now.|||This is how I did this.

control panel -> administrative tools -> Data Sources -> User DSN -> Add -> Select Driver -> Finish

Then you will be prompted to type in the Data Source, Host, and Port.

Then you should be able to run the local package.

DTS error message

I am trying to DTS data from one db on server A to the same db on server B. Server B is my own local sql server registration. I get this error when trying to move data into a new db:

error description:[DBNETLIB][ConnectionOpen(Connect()).]SQLServer does not exist or access denied
Context: Error during initialization of the provider

any ideas?? Thanks a ton, in advance!! :rolleyes:I am trying to DTS data from one db on server A to the same db on server B. Server B is my own local sql server registration. I get this error when trying to move data into a new db:

error description:[DBNETLIB][ConnectionOpen(Connect()).]SQLServer does not exist or access denied
Context: Error during initialization of the provider

any ideas?? Thanks a ton, in advance!! :rolleyes:

hi,
this error may be is the server name, you use the (local) o the name of the server, in sql 2000 with instance name, is better write the name\instance.
test this and tell me.

DTS disaster recovery

Can anyone recommend any best practices for restoring local packages? In a
disaster recovery situation I will have 1 SQL Server box rather than 4 so I
won't be able to restore all of my local packages by restoring MSDB. Any
thoughts?
In the same situation, I would restore the MSDB databases from each server
as MSDB1, MSDB2, etc, then move the data into the main MSDB database...
Also, save out each DTS package as a Structured Storage file and dump that
into a version control application such as Source Safe.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Terri" <terri@.cybernets.com> wrote in message
news:dml9p8$vqu$1@.reader2.nmix.net...
> Can anyone recommend any best practices for restoring local packages? In a
> disaster recovery situation I will have 1 SQL Server box rather than 4 so
> I
> won't be able to restore all of my local packages by restoring MSDB. Any
> thoughts?
>
|||"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:evifdFg9FHA.2792@.TK2MSFTNGP11.phx.gbl...
> In the same situation, I would restore the MSDB databases from each server
> as MSDB1, MSDB2, etc, then move the data into the main MSDB database...
Would anyone have any code that would select and insert this data.

> Also, save out each DTS package as a Structured Storage file and dump that
> into a version control application such as Source Safe.
Does this need to be done with the GUI?
More generally would named instances help here?

DTS disaster recovery

Can anyone recommend any best practices for restoring local packages? In a
disaster recovery situation I will have 1 SQL Server box rather than 4 so I
won't be able to restore all of my local packages by restoring MSDB. Any
thoughts?In the same situation, I would restore the MSDB databases from each server
as MSDB1, MSDB2, etc, then move the data into the main MSDB database...
Also, save out each DTS package as a Structured Storage file and dump that
into a version control application such as Source Safe.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Terri" <terri@.cybernets.com> wrote in message
news:dml9p8$vqu$1@.reader2.nmix.net...
> Can anyone recommend any best practices for restoring local packages? In a
> disaster recovery situation I will have 1 SQL Server box rather than 4 so
> I
> won't be able to restore all of my local packages by restoring MSDB. Any
> thoughts?
>|||"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:evifdFg9FHA.2792@.TK2MSFTNGP11.phx.gbl...
> In the same situation, I would restore the MSDB databases from each server
> as MSDB1, MSDB2, etc, then move the data into the main MSDB database...
Would anyone have any code that would select and insert this data.

> Also, save out each DTS package as a Structured Storage file and dump that
> into a version control application such as Source Safe.
Does this need to be done with the GUI?
More generally would named instances help here?

DTS disaster recovery

Can anyone recommend any best practices for restoring local packages? In a
disaster recovery situation I will have 1 SQL Server box rather than 4 so I
won't be able to restore all of my local packages by restoring MSDB. Any
thoughts?In the same situation, I would restore the MSDB databases from each server
as MSDB1, MSDB2, etc, then move the data into the main MSDB database...
Also, save out each DTS package as a Structured Storage file and dump that
into a version control application such as Source Safe.
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Terri" <terri@.cybernets.com> wrote in message
news:dml9p8$vqu$1@.reader2.nmix.net...
> Can anyone recommend any best practices for restoring local packages? In a
> disaster recovery situation I will have 1 SQL Server box rather than 4 so
> I
> won't be able to restore all of my local packages by restoring MSDB. Any
> thoughts?
>|||"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:evifdFg9FHA.2792@.TK2MSFTNGP11.phx.gbl...
> In the same situation, I would restore the MSDB databases from each server
> as MSDB1, MSDB2, etc, then move the data into the main MSDB database...
Would anyone have any code that would select and insert this data.
> Also, save out each DTS package as a Structured Storage file and dump that
> into a version control application such as Source Safe.
Does this need to be done with the GUI?
More generally would named instances help here?

DTS deployment issues

Hello!

I'm trying to deploy an application that runs DTS packages from the local machine.

I've read some articles that it would be enough to install the SQL Client Tools on the local machine to make the DTS work . I did this, the package executes a few steps (it shows message boxes and writes data into the database), then (before executing some validation tasks on the data) it throws an exception 'Execution was canceled by user'. I've set the pbCancel flag and the package runs fine on some computers, but on an empty system that only contains my application and the Sql Client Tools I get this exception.

Do I have to install anything else or do I have to make some changes to DTS package to make it work?

Thank you in advance!

this is the wrong forum; Unless your are using SSIS (SQL SERVER 2005).|||sorry, my mistake

DTS Copy SQL Server Task

I want to copy a database on a remote server to a local instance of SQL Server. I created a package that has the Copy SQL Server Task in it, but it seems to fail half way through every time i execute it.

I can view the local machine error log which simply reports that the table transfer was attempted.. but no explanation of why it fails. I don't have access to the host error log files either, so I have no idea why it fails.

I once almost got the 'Copy SQL Server Task' to work, but it would create duplicate records in the destination database, which I didn't want. It seems choosing the intuitive options like 'replace existing data' and choosing the table I want copied over.. does not work. I am not 100% sure the 2 databases are referentially identical either.. so it would be nice to know how to do a copy by first deleting the entire database on the destination machine, then recreating it all.

Can anyone give me some advice on which options I need to choose to achieve a proper database copy? Or, if you could show me a tutorial online that could explain how all the options work, and how I can debug what's causing my current method to fail, would be nice.

BrentWell I got it to work. It turns out that you can double click the error message to get some more details as it occurs. Strangely every account I had tried to use on my local server did not have permission to do the copying.. but only for certain attributes. So, basically by trial and error, I selected the right configuration to only copy the tables to the destination database (the accounts seemed to have permission to do certain activities).

It sure would be nice to find some info on the meaning of all the options in help or online somewhere.. if anyone knows of such a resource, they should post it.|||Thanks me!

I forgot how to view DTS backup log errors, and found my own old post to show me... double click the error in Ent. Manager!

This is what i needed to fix the problem!

DTS 2000 package designer and SQL Server 2005

I am not sure where to ask this question. So I figured here may be ok

I have several DTS 2000 packages and I have SQL 2005 installed on my local machine. However the rest of the company is still using SQL 2000 (for now). So I do not want to convert them to ssis yet. One of the things we just did to the packages is make all flat files use \\localhost and any servers point to (local). Now in ssis this works fine but using the DTS 2000 package designer it does not like either of these at all. The reason we wanted to do this is so when we switch out servers there is no changes to our DTS packages.

I have found some problems using \\localhost as a UNC path in SSIS packages (for whatever reason it occassionally returned a duplicate name exception). Instead, try using \\127.0.0.1\ssis , which is essentially a loopback share onto the package execution host machines. Naturally, you would need to create the share on each machine. I haven't used or looked at DTS in eons so I couldn't tell you whether that works with DTS let alone migration issues.|||

yes the 127.0.0.1 worked for paths, however the (local) for servername does not. I Think it is a bug because the DBA that has SQL Enterprise manager can put (local) for servers and localhost for paths. But when I use SQL Server management studio (2005) and the DTS 2000 package designer neither works (except like I said 127.0.0.1).

Now if I build a new ssis then I can use (local) but you are right I think you still have to use 127.0.0.1 for paths.

Thanks for your reply.

DTS "Execute Process Task" fails...

I have a DTS package which utilizes an "Execute Process
Task". This task calls an EXE local to my machine. When I
initially setup the DTS routine it worked. A few days
later I tried to run it again and the executable failed
on one of its steps.

I tested the executable thoroughly and decided that the
problem was with the DTS routine. I found that when I
perform the following steps the task runs properly:

1. Edit the DTS routine
2. Edit the properties of the Execute Process Task
3. Click on the "..." button to navigate to my EXE (even
though the path supplied is already correct)
4. Run it

However, after saving the package and then closing and re-
opening SEM, the same DTS routine fails when I execute it
manually without performing the steps above.

Any ideas?
Thanks.All I can think is that the pathing for the EXE is not the same for the server as it is on your local machine. Try running the job directly from the server in the same manner. If you get the same error it is to do with the pathing to the EXE file. I have something similar here and I have to run some DTS packages via terminal services to ensure correct pathing.|||I know what you are saying (I've run into that before). I don't think that's the case here though because I am running everything on my local machine. So, if I understand you right, I am running the job on the "server" (my machine).

Thanks for the input though. Any other ideas?|||Ok, cools, so the local machine is the server. What error message are you recieving?|||I'v been tinkering with DTS packages and found myself getting caught out with the server path vs client path. Some times it looks on the server i.e Browse folder will actually present a view of C:\Win... of the machine on which your instance resides and sometimes you're looking at your local machine. Confusing but makes sense sometimes.|||The error message:
Step Error Source: Microsoft Data Transformation Services (DTS)Package
Step Error Description:CreateProcessTask 'DTSTask_DTSCreateProcessTask_1': Process returned code -1, which does not match the specified SuccessReturnCode of 1.
Step Error code: 80040496
Step Error Help File:sqldts80.hlp
Step Error Help Context ID:4900

I thought it was some kind of permissions issue, but I've tried several things relating to DTS package permissions to no avail.|||if you set the package as a job on the server then it is a problem with the path name. The automatied job will run on the server thinking that the server is "god" not the local machine. I would say to share the local drive, map it to the server and set the path that way. It will work if you are running a job.
Jim|||1. The server machine is my local machine so there is no issue with executable paths.

2. The DTS package is not running as a job. This issue occurs when I run it manually.

More information:
When I run the DTS package and it gets to the "Execute Process Task" step it does run the EXE every time. However, the EXE fails if I don't perform the steps listed in my initial post.

Thanks for the input.|||So it does not error out in the dts step it actualy dies when the exe is run? what is the EXE?
Jim|||The EXE is a C++ Console application which serves as a wrapper around a 3rd party DLL.

The DLL basically performs an import into SQL server while encapsulating necessary business rules.

It is a very simple application.

Step 1: Connect
Step 2: Import (it fails here)
Step 3: Disconnect|||The only thing that I can think of is that a paramiter is lost or not saved in the dts package. But why that would need a path for an exe im not sure. Does the exe have varialbles in it? Jim|||JDionne! You da man!! You got me thinking about the parameters and...
I just figured it out!!

I've been so busy looking at possible security resolutions that I missed an obvious one.

The problem was with the parameters to the EXE. One of the parameters is a filepath to an import file. Since the EXE is in the same directory with this file I had just been supplying the file name (with out specifying a path) to the parameter. This works when the current working directory is the path to my EXE. So that's why it would always work after performing the steps in my initial post. These steps changed the current working directory to be that of my EXE.

The solution was to add the path to my filepath parameter.

Thanks JDionne and everyone for the help!|||Im glad that I could help. A fresh mind is always a good thing.
If you ever have any other problems dont hesitate to ask. you can private msg me too if youd like.
Regards Jim

DTS - Strange Behavior

Hi,
I've created quite a few DTS packages that open up VPN connections to remote
SQL Servers, transfer data to local SQL Servers, writes audit records, then
close the VPN connections. Everything has been working well. Saturday all
of the packages (scheduled as jobs) began to fail. Friday we did do some
physical server migrations but the SQL Servers were not touched. Nothing
else has changed. When I examined the DTS packages I noticed that if I
execute the package manually none of the tasks ever execute; they stay in a
"Waiting" state with a yellow icon. This occurs for both Meta Data and SQL
Server stored packages. If I open the package in design mode, I get the
same "Waiting" behavior. Eventually an error is returned in either case
which states:
Error Source: Microsoft OLE DB Provider for SQL Server
Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Server does
not exist or access is denied.
After the error for each step it lists "Not Run" with a white X in a black
circle. In the past successful execution of the package would list success
(green icon) for each step moving down through the package as each step
succeeded (as expected).
The funny thing is if I open the package up in design mode and execute any
individual step, the the step executes successfully. I.e., individual steps
work but not the whole DTS package whether opened in design mode or not.
If I create a new test DTS package, the package works as expected. If I
save one of the existing DTS packages out to a DTS file and import it back
into DTS and save it under a different name, same failure behavior as listed
above. If I create a new DTS package and copy/paste the steps individually
(from a failing package) into a new package and then save it, the package
works as expected.
Any ideas? I need to get this working again because were talking about
millions of records. And preferably, I would rather not spend two days
recreating the same packages over again.
Thanks
Jerry
PS - The double post is in leu of time constraints.
Also,
This is Windows 2000 SP4 SQL Server 2000 SP4. No errors are reported in the
DTS error log.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23A1ebigFGHA.3700@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I've created quite a few DTS packages that open up VPN connections to
> remote SQL Servers, transfer data to local SQL Servers, writes audit
> records, then close the VPN connections. Everything has been working
> well. Saturday all of the packages (scheduled as jobs) began to fail.
> Friday we did do some physical server migrations but the SQL Servers were
> not touched. Nothing else has changed. When I examined the DTS packages
> I noticed that if I execute the package manually none of the tasks ever
> execute; they stay in a "Waiting" state with a yellow icon. This occurs
> for both Meta Data and SQL Server stored packages. If I open the package
> in design mode, I get the same "Waiting" behavior. Eventually an error is
> returned in either case which states:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Server does
> not exist or access is denied.
> After the error for each step it lists "Not Run" with a white X in a black
> circle. In the past successful execution of the package would list
> success (green icon) for each step moving down through the package as each
> step succeeded (as expected).
> The funny thing is if I open the package up in design mode and execute any
> individual step, the the step executes successfully. I.e., individual
> steps work but not the whole DTS package whether opened in design mode or
> not.
> If I create a new test DTS package, the package works as expected. If I
> save one of the existing DTS packages out to a DTS file and import it back
> into DTS and save it under a different name, same failure behavior as
> listed above. If I create a new DTS package and copy/paste the steps
> individually (from a failing package) into a new package and then save it,
> the package works as expected.
> Any ideas? I need to get this working again because were talking about
> millions of records. And preferably, I would rather not spend two days
> recreating the same packages over again.
> Thanks
> Jerry
> PS - The double post is in leu of time constraints.
>
|||Also,
This is Windows 2000 SP4 SQL Server 2000 SP4. No errors are reported in the
DTS error log.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23A1ebigFGHA.3700@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I've created quite a few DTS packages that open up VPN connections to
> remote SQL Servers, transfer data to local SQL Servers, writes audit
> records, then close the VPN connections. Everything has been working
> well. Saturday all of the packages (scheduled as jobs) began to fail.
> Friday we did do some physical server migrations but the SQL Servers were
> not touched. Nothing else has changed. When I examined the DTS packages
> I noticed that if I execute the package manually none of the tasks ever
> execute; they stay in a "Waiting" state with a yellow icon. This occurs
> for both Meta Data and SQL Server stored packages. If I open the package
> in design mode, I get the same "Waiting" behavior. Eventually an error is
> returned in either case which states:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Server does
> not exist or access is denied.
> After the error for each step it lists "Not Run" with a white X in a black
> circle. In the past successful execution of the package would list
> success (green icon) for each step moving down through the package as each
> step succeeded (as expected).
> The funny thing is if I open the package up in design mode and execute any
> individual step, the the step executes successfully. I.e., individual
> steps work but not the whole DTS package whether opened in design mode or
> not.
> If I create a new test DTS package, the package works as expected. If I
> save one of the existing DTS packages out to a DTS file and import it back
> into DTS and save it under a different name, same failure behavior as
> listed above. If I create a new DTS package and copy/paste the steps
> individually (from a failing package) into a new package and then save it,
> the package works as expected.
> Any ideas? I need to get this working again because were talking about
> millions of records. And preferably, I would rather not spend two days
> recreating the same packages over again.
> Thanks
> Jerry
> PS - The double post is in leu of time constraints.
>
|||Got it. For future views of this post:
The issue lied in the fact that logging for the package execution was going
to another SQL Server that was taken down (testing box). Updating the
logging to the prod box (which should have occurred at the begining) fixed
the issue.
Jerry
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23A1ebigFGHA.3700@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I've created quite a few DTS packages that open up VPN connections to
> remote SQL Servers, transfer data to local SQL Servers, writes audit
> records, then close the VPN connections. Everything has been working
> well. Saturday all of the packages (scheduled as jobs) began to fail.
> Friday we did do some physical server migrations but the SQL Servers were
> not touched. Nothing else has changed. When I examined the DTS packages
> I noticed that if I execute the package manually none of the tasks ever
> execute; they stay in a "Waiting" state with a yellow icon. This occurs
> for both Meta Data and SQL Server stored packages. If I open the package
> in design mode, I get the same "Waiting" behavior. Eventually an error is
> returned in either case which states:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Server does
> not exist or access is denied.
> After the error for each step it lists "Not Run" with a white X in a black
> circle. In the past successful execution of the package would list
> success (green icon) for each step moving down through the package as each
> step succeeded (as expected).
> The funny thing is if I open the package up in design mode and execute any
> individual step, the the step executes successfully. I.e., individual
> steps work but not the whole DTS package whether opened in design mode or
> not.
> If I create a new test DTS package, the package works as expected. If I
> save one of the existing DTS packages out to a DTS file and import it back
> into DTS and save it under a different name, same failure behavior as
> listed above. If I create a new DTS package and copy/paste the steps
> individually (from a failing package) into a new package and then save it,
> the package works as expected.
> Any ideas? I need to get this working again because were talking about
> millions of records. And preferably, I would rather not spend two days
> recreating the same packages over again.
> Thanks
> Jerry
> PS - The double post is in leu of time constraints.
>

DTS - Strange Behavior

Hi,
I've created quite a few DTS packages that open up VPN connections to remote
SQL Servers, transfer data to local SQL Servers, writes audit records, then
close the VPN connections. Everything has been working well. Saturday all
of the packages (scheduled as jobs) began to fail. Friday we did do some
physical server migrations but the SQL Servers were not touched. Nothing
else has changed. When I examined the DTS packages I noticed that if I
execute the package manually none of the tasks ever execute; they stay in a
"Waiting" state with a yellow icon. This occurs for both Meta Data and SQL
Server stored packages. If I open the package in design mode, I get the
same "Waiting" behavior. Eventually an error is returned in either case
which states:
Error Source: Microsoft OLE DB Provider for SQL Server
Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Server
does
not exist or access is denied.
After the error for each step it lists "Not Run" with a white X in a black
circle. In the past successful execution of the package would list success
(green icon) for each step moving down through the package as each step
succeeded (as expected).
The funny thing is if I open the package up in design mode and execute any
individual step, the the step executes successfully. I.e., individual steps
work but not the whole DTS package whether opened in design mode or not.
If I create a new test DTS package, the package works as expected. If I
save one of the existing DTS packages out to a DTS file and import it back
into DTS and save it under a different name, same failure behavior as listed
above. If I create a new DTS package and copy/paste the steps individually
(from a failing package) into a new package and then save it, the package
works as expected.
Any ideas? I need to get this working again because were talking about
millions of records. And preferably, I would rather not spend two days
recreating the same packages over again.
Thanks
Jerry
PS - The double post is in leu of time constraints.Also,
This is Windows 2000 SP4 SQL Server 2000 SP4. No errors are reported in the
DTS error log.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23A1ebigFGHA.3700@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I've created quite a few DTS packages that open up VPN connections to
> remote SQL Servers, transfer data to local SQL Servers, writes audit
> records, then close the VPN connections. Everything has been working
> well. Saturday all of the packages (scheduled as jobs) began to fail.
> Friday we did do some physical server migrations but the SQL Servers were
> not touched. Nothing else has changed. When I examined the DTS packages
> I noticed that if I execute the package manually none of the tasks ever
> execute; they stay in a "Waiting" state with a yellow icon. This occurs
> for both Meta Data and SQL Server stored packages. If I open the package
> in design mode, I get the same "Waiting" behavior. Eventually an error is
> returned in either case which states:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Serv
er does
> not exist or access is denied.
> After the error for each step it lists "Not Run" with a white X in a black
> circle. In the past successful execution of the package would list
> success (green icon) for each step moving down through the package as each
> step succeeded (as expected).
> The funny thing is if I open the package up in design mode and execute any
> individual step, the the step executes successfully. I.e., individual
> steps work but not the whole DTS package whether opened in design mode or
> not.
> If I create a new test DTS package, the package works as expected. If I
> save one of the existing DTS packages out to a DTS file and import it back
> into DTS and save it under a different name, same failure behavior as
> listed above. If I create a new DTS package and copy/paste the steps
> individually (from a failing package) into a new package and then save it,
> the package works as expected.
> Any ideas? I need to get this working again because were talking about
> millions of records. And preferably, I would rather not spend two days
> recreating the same packages over again.
> Thanks
> Jerry
> PS - The double post is in leu of time constraints.
>|||Also,
This is Windows 2000 SP4 SQL Server 2000 SP4. No errors are reported in the
DTS error log.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23A1ebigFGHA.3700@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I've created quite a few DTS packages that open up VPN connections to
> remote SQL Servers, transfer data to local SQL Servers, writes audit
> records, then close the VPN connections. Everything has been working
> well. Saturday all of the packages (scheduled as jobs) began to fail.
> Friday we did do some physical server migrations but the SQL Servers were
> not touched. Nothing else has changed. When I examined the DTS packages
> I noticed that if I execute the package manually none of the tasks ever
> execute; they stay in a "Waiting" state with a yellow icon. This occurs
> for both Meta Data and SQL Server stored packages. If I open the package
> in design mode, I get the same "Waiting" behavior. Eventually an error is
> returned in either case which states:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Serv
er does
> not exist or access is denied.
> After the error for each step it lists "Not Run" with a white X in a black
> circle. In the past successful execution of the package would list
> success (green icon) for each step moving down through the package as each
> step succeeded (as expected).
> The funny thing is if I open the package up in design mode and execute any
> individual step, the the step executes successfully. I.e., individual
> steps work but not the whole DTS package whether opened in design mode or
> not.
> If I create a new test DTS package, the package works as expected. If I
> save one of the existing DTS packages out to a DTS file and import it back
> into DTS and save it under a different name, same failure behavior as
> listed above. If I create a new DTS package and copy/paste the steps
> individually (from a failing package) into a new package and then save it,
> the package works as expected.
> Any ideas? I need to get this working again because were talking about
> millions of records. And preferably, I would rather not spend two days
> recreating the same packages over again.
> Thanks
> Jerry
> PS - The double post is in leu of time constraints.
>|||Got it. For future views of this post:
The issue lied in the fact that logging for the package execution was going
to another SQL Server that was taken down (testing box). Updating the
logging to the prod box (which should have occurred at the begining) fixed
the issue.
Jerry
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23A1ebigFGHA.3700@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I've created quite a few DTS packages that open up VPN connections to
> remote SQL Servers, transfer data to local SQL Servers, writes audit
> records, then close the VPN connections. Everything has been working
> well. Saturday all of the packages (scheduled as jobs) began to fail.
> Friday we did do some physical server migrations but the SQL Servers were
> not touched. Nothing else has changed. When I examined the DTS packages
> I noticed that if I execute the package manually none of the tasks ever
> execute; they stay in a "Waiting" state with a yellow icon. This occurs
> for both Meta Data and SQL Server stored packages. If I open the package
> in design mode, I get the same "Waiting" behavior. Eventually an error is
> returned in either case which states:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Serv
er does
> not exist or access is denied.
> After the error for each step it lists "Not Run" with a white X in a black
> circle. In the past successful execution of the package would list
> success (green icon) for each step moving down through the package as each
> step succeeded (as expected).
> The funny thing is if I open the package up in design mode and execute any
> individual step, the the step executes successfully. I.e., individual
> steps work but not the whole DTS package whether opened in design mode or
> not.
> If I create a new test DTS package, the package works as expected. If I
> save one of the existing DTS packages out to a DTS file and import it back
> into DTS and save it under a different name, same failure behavior as
> listed above. If I create a new DTS package and copy/paste the steps
> individually (from a failing package) into a new package and then save it,
> the package works as expected.
> Any ideas? I need to get this working again because were talking about
> millions of records. And preferably, I would rather not spend two days
> recreating the same packages over again.
> Thanks
> Jerry
> PS - The double post is in leu of time constraints.
>

DTS - Strange Behavior

Hi,
I've created quite a few DTS packages that open up VPN connections to remote
SQL Servers, transfer data to local SQL Servers, writes audit records, then
close the VPN connections. Everything has been working well. Saturday all
of the packages (scheduled as jobs) began to fail. Friday we did do some
physical server migrations but the SQL Servers were not touched. Nothing
else has changed. When I examined the DTS packages I noticed that if I
execute the package manually none of the tasks ever execute; they stay in a
"Waiting" state with a yellow icon. This occurs for both Meta Data and SQL
Server stored packages. If I open the package in design mode, I get the
same "Waiting" behavior. Eventually an error is returned in either case
which states:
Error Source: Microsoft OLE DB Provider for SQL Server
Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Server does
not exist or access is denied.
After the error for each step it lists "Not Run" with a white X in a black
circle. In the past successful execution of the package would list success
(green icon) for each step moving down through the package as each step
succeeded (as expected).
The funny thing is if I open the package up in design mode and execute any
individual step, the the step executes successfully. I.e., individual steps
work but not the whole DTS package whether opened in design mode or not.
If I create a new test DTS package, the package works as expected. If I
save one of the existing DTS packages out to a DTS file and import it back
into DTS and save it under a different name, same failure behavior as listed
above. If I create a new DTS package and copy/paste the steps individually
(from a failing package) into a new package and then save it, the package
works as expected.
Any ideas? I need to get this working again because were talking about
millions of records. And preferably, I would rather not spend two days
recreating the same packages over again.
Thanks
Jerry
PS - The double post is in leu of time constraints.Also,
This is Windows 2000 SP4 SQL Server 2000 SP4. No errors are reported in the
DTS error log.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23A1ebigFGHA.3700@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I've created quite a few DTS packages that open up VPN connections to
> remote SQL Servers, transfer data to local SQL Servers, writes audit
> records, then close the VPN connections. Everything has been working
> well. Saturday all of the packages (scheduled as jobs) began to fail.
> Friday we did do some physical server migrations but the SQL Servers were
> not touched. Nothing else has changed. When I examined the DTS packages
> I noticed that if I execute the package manually none of the tasks ever
> execute; they stay in a "Waiting" state with a yellow icon. This occurs
> for both Meta Data and SQL Server stored packages. If I open the package
> in design mode, I get the same "Waiting" behavior. Eventually an error is
> returned in either case which states:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Server does
> not exist or access is denied.
> After the error for each step it lists "Not Run" with a white X in a black
> circle. In the past successful execution of the package would list
> success (green icon) for each step moving down through the package as each
> step succeeded (as expected).
> The funny thing is if I open the package up in design mode and execute any
> individual step, the the step executes successfully. I.e., individual
> steps work but not the whole DTS package whether opened in design mode or
> not.
> If I create a new test DTS package, the package works as expected. If I
> save one of the existing DTS packages out to a DTS file and import it back
> into DTS and save it under a different name, same failure behavior as
> listed above. If I create a new DTS package and copy/paste the steps
> individually (from a failing package) into a new package and then save it,
> the package works as expected.
> Any ideas? I need to get this working again because were talking about
> millions of records. And preferably, I would rather not spend two days
> recreating the same packages over again.
> Thanks
> Jerry
> PS - The double post is in leu of time constraints.
>|||Also,
This is Windows 2000 SP4 SQL Server 2000 SP4. No errors are reported in the
DTS error log.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23A1ebigFGHA.3700@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I've created quite a few DTS packages that open up VPN connections to
> remote SQL Servers, transfer data to local SQL Servers, writes audit
> records, then close the VPN connections. Everything has been working
> well. Saturday all of the packages (scheduled as jobs) began to fail.
> Friday we did do some physical server migrations but the SQL Servers were
> not touched. Nothing else has changed. When I examined the DTS packages
> I noticed that if I execute the package manually none of the tasks ever
> execute; they stay in a "Waiting" state with a yellow icon. This occurs
> for both Meta Data and SQL Server stored packages. If I open the package
> in design mode, I get the same "Waiting" behavior. Eventually an error is
> returned in either case which states:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Server does
> not exist or access is denied.
> After the error for each step it lists "Not Run" with a white X in a black
> circle. In the past successful execution of the package would list
> success (green icon) for each step moving down through the package as each
> step succeeded (as expected).
> The funny thing is if I open the package up in design mode and execute any
> individual step, the the step executes successfully. I.e., individual
> steps work but not the whole DTS package whether opened in design mode or
> not.
> If I create a new test DTS package, the package works as expected. If I
> save one of the existing DTS packages out to a DTS file and import it back
> into DTS and save it under a different name, same failure behavior as
> listed above. If I create a new DTS package and copy/paste the steps
> individually (from a failing package) into a new package and then save it,
> the package works as expected.
> Any ideas? I need to get this working again because were talking about
> millions of records. And preferably, I would rather not spend two days
> recreating the same packages over again.
> Thanks
> Jerry
> PS - The double post is in leu of time constraints.
>|||Got it. For future views of this post:
The issue lied in the fact that logging for the package execution was going
to another SQL Server that was taken down (testing box). Updating the
logging to the prod box (which should have occurred at the begining) fixed
the issue.
Jerry
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23A1ebigFGHA.3700@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I've created quite a few DTS packages that open up VPN connections to
> remote SQL Servers, transfer data to local SQL Servers, writes audit
> records, then close the VPN connections. Everything has been working
> well. Saturday all of the packages (scheduled as jobs) began to fail.
> Friday we did do some physical server migrations but the SQL Servers were
> not touched. Nothing else has changed. When I examined the DTS packages
> I noticed that if I execute the package manually none of the tasks ever
> execute; they stay in a "Waiting" state with a yellow icon. This occurs
> for both Meta Data and SQL Server stored packages. If I open the package
> in design mode, I get the same "Waiting" behavior. Eventually an error is
> returned in either case which states:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen(Connect)).] SQL Server does
> not exist or access is denied.
> After the error for each step it lists "Not Run" with a white X in a black
> circle. In the past successful execution of the package would list
> success (green icon) for each step moving down through the package as each
> step succeeded (as expected).
> The funny thing is if I open the package up in design mode and execute any
> individual step, the the step executes successfully. I.e., individual
> steps work but not the whole DTS package whether opened in design mode or
> not.
> If I create a new test DTS package, the package works as expected. If I
> save one of the existing DTS packages out to a DTS file and import it back
> into DTS and save it under a different name, same failure behavior as
> listed above. If I create a new DTS package and copy/paste the steps
> individually (from a failing package) into a new package and then save it,
> the package works as expected.
> Any ideas? I need to get this working again because were talking about
> millions of records. And preferably, I would rather not spend two days
> recreating the same packages over again.
> Thanks
> Jerry
> PS - The double post is in leu of time constraints.
>

DTC error

Hi,
I have two MS SQL2000 servers in local network . Let's
say A and B. Server B is linked server for A.
When I'm starting following select on server A :
========================================= BEGIN TRAN
SELECT *
FROM OPENQUERY(DW_SERVER, 'SELECT p.AP_ID,
p.AP_NAME, p.PT_NAME,
p.AP_DEBIT_SOURCE, dbo.UF_GET_FULL_SOURCE
(p.AP_DEBIT_SOURCE, p.PT_NAME) AS AP_FULL_SOURCE,
p.AP_VOL_FACE, p.AP_TIME_FACE,
p.AP_EXPIRED_PERIOD
FROM dbo.AAA_DW_PROFILE_DIM p ')
ROLLBACK TRAN
============================================
I'm getting following error:
========================================= Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB
provider 'SQLOLEDB' was unable to begin a distributed
transaction.
[OLE/DB provider returned message: New transaction cannot
enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
==========================================
DTC is started on both servers.
During investigation of this issue I've started
DTCPing utilite. After this, in DTCPing's log file
I have found only following problem string:
================================================= 07-14, 19:55:100-->WARNING:the CID values for both test
machines are the same
while this problem won't stop DTCping test, MSDTC
will fail for this
====================================================
Am I right? The error was connected with this issue?
What should I do next?What is dbo.UF_GET_FULL_SOURCE in your SQL? and has no comma after
"andy" <akorotaev@.estylesoft.com> wrote in message
news:07dd01c34ab1$8b611c90$a601280a@.phx.gbl...
> Hi,
> I have two MS SQL2000 servers in local network . Let's
> say A and B. Server B is linked server for A.
> When I'm starting following select on server A :
> =========================================> BEGIN TRAN
> SELECT *
> FROM OPENQUERY(DW_SERVER, 'SELECT p.AP_ID,
> p.AP_NAME, p.PT_NAME,
> p.AP_DEBIT_SOURCE, dbo.UF_GET_FULL_SOURCE
> (p.AP_DEBIT_SOURCE, p.PT_NAME) AS AP_FULL_SOURCE,
> p.AP_VOL_FACE, p.AP_TIME_FACE,
> p.AP_EXPIRED_PERIOD
> FROM dbo.AAA_DW_PROFILE_DIM p ')
> ROLLBACK TRAN
> ============================================> I'm getting following error:
> =========================================> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB
> provider 'SQLOLEDB' was unable to begin a distributed
> transaction.
> [OLE/DB provider returned message: New transaction cannot
> enlist in the specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> ==========================================> DTC is started on both servers.
> During investigation of this issue I've started
> DTCPing utilite. After this, in DTCPing's log file
> I have found only following problem string:
> =================================================> 07-14, 19:55:100-->WARNING:the CID values for both test
> machines are the same
> while this problem won't stop DTCping test, MSDTC
> will fail for this
> ====================================================> Am I right? The error was connected with this issue?
> What should I do next?
>
>
>
>
>|||dbo.UF_GET_FULL_SOURCE is function.
No any comma needed here.
>--Original Message--
>What is dbo.UF_GET_FULL_SOURCE in your SQL? and has no
comma after
>"andy" <akorotaev@.estylesoft.com> wrote in message
>news:07dd01c34ab1$8b611c90$a601280a@.phx.gbl...
>> Hi,
>> I have two MS SQL2000 servers in local network . Let's
>> say A and B. Server B is linked server for A.
>> When I'm starting following select on server A :
>> =========================================>> BEGIN TRAN
>> SELECT *
>> FROM OPENQUERY(DW_SERVER, 'SELECT p.AP_ID,
>> p.AP_NAME, p.PT_NAME,
>> p.AP_DEBIT_SOURCE, dbo.UF_GET_FULL_SOURCE
>> (p.AP_DEBIT_SOURCE, p.PT_NAME) AS AP_FULL_SOURCE,
>> p.AP_VOL_FACE, p.AP_TIME_FACE,
>> p.AP_EXPIRED_PERIOD
>> FROM dbo.AAA_DW_PROFILE_DIM p ')
>> ROLLBACK TRAN
>> ============================================>> I'm getting following error:
>> =========================================>> Server: Msg 7391, Level 16, State 1, Line 2
>> The operation could not be performed because the OLE DB
>> provider 'SQLOLEDB' was unable to begin a distributed
>> transaction.
>> [OLE/DB provider returned message: New transaction
cannot
>> enlist in the specified transaction coordinator. ]
>> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
>> ITransactionJoin::JoinTransaction returned 0x8004d00a].
>> ==========================================>> DTC is started on both servers.
>> During investigation of this issue I've started
>> DTCPing utilite. After this, in DTCPing's log file
>> I have found only following problem string:
>> =================================================>> 07-14, 19:55:100-->WARNING:the CID values for both test
>> machines are the same
>> while this problem won't stop DTCping test, MSDTC
>> will fail for this
>> ====================================================>> Am I right? The error was connected with this issue?
>> What should I do next?
>>
>>
>>
>>
>
>.
>|||Andy,
take a look at technet article Q306843.
Section 11 refers to duplicate CIDs and using GUIDGEN to
fix this...
You might also want to look at the following article :
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;162001
I am guessing this is on a ghosted or cloned server ?
Hope this helps.
Steve.
>--Original Message--
>
>dbo.UF_GET_FULL_SOURCE is function.
>No any comma needed here.
>
>>--Original Message--
>>What is dbo.UF_GET_FULL_SOURCE in your SQL? and has no
>comma after
>>"andy" <akorotaev@.estylesoft.com> wrote in message
>>news:07dd01c34ab1$8b611c90$a601280a@.phx.gbl...
>> Hi,
>> I have two MS SQL2000 servers in local network . Let's
>> say A and B. Server B is linked server for A.
>> When I'm starting following select on server A :
>> =========================================>> BEGIN TRAN
>> SELECT *
>> FROM OPENQUERY(DW_SERVER, 'SELECT p.AP_ID,
>> p.AP_NAME, p.PT_NAME,
>> p.AP_DEBIT_SOURCE, dbo.UF_GET_FULL_SOURCE
>> (p.AP_DEBIT_SOURCE, p.PT_NAME) AS AP_FULL_SOURCE,
>> p.AP_VOL_FACE, p.AP_TIME_FACE,
>> p.AP_EXPIRED_PERIOD
>> FROM dbo.AAA_DW_PROFILE_DIM p ')
>> ROLLBACK TRAN
>> ============================================>> I'm getting following error:
>> =========================================>> Server: Msg 7391, Level 16, State 1, Line 2
>> The operation could not be performed because the OLE DB
>> provider 'SQLOLEDB' was unable to begin a distributed
>> transaction.
>> [OLE/DB provider returned message: New transaction
>cannot
>> enlist in the specified transaction coordinator. ]
>> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
>> ITransactionJoin::JoinTransaction returned 0x8004d00a].
>> ==========================================>> DTC is started on both servers.
>> During investigation of this issue I've started
>> DTCPing utilite. After this, in DTCPing's log file
>> I have found only following problem string:
>> =================================================>> 07-14, 19:55:100-->WARNING:the CID values for both test
>> machines are the same
>> while this problem won't stop DTCping test, MSDTC
>> will fail for this
>> ====================================================>> Am I right? The error was connected with this issue?
>> What should I do next?
>>
>>
>>
>>
>>
>>.
>.
>

dt_ stored procedures

I am trying to use microsoft access project file to access msde databases on local workstations. I have to set the users security to db_owner due to the application requirements.
The problem users are having is since they are owners they see the dt_?? stored procedures in the queries list which are created when access addes a table to the database.
I need to keep these "Version Control" stored procedures from being created. I have tried triggers on the sysobject table but this is not allowed. The users can not delete the triggers due to sql security.
I did find out that in access if the view system objects is not check the dt_ stored procedures will not show up. But I still want to stop these from being created.
Any ideas on how to stop them from being created.
dt_ procedures are created by default (I thought only when diagrams are
created). I don't believe you can prevent them from being created, however
you could have the app use a custom query from INFORMATION_SCHEMA views that
leaves out any objects that start with dt_
http://www.aspfaq.com/
(Reverse address to reply.)
"Eric Brasher" <Eric Brasher@.discussions.microsoft.com> wrote in message
news:FAB9C710-45A0-47D2-9914-CB94D55138F4@.microsoft.com...
> I am trying to use microsoft access project file to access msde databases
on local workstations. I have to set the users security to db_owner due to
the application requirements.
> The problem users are having is since they are owners they see the
dt_?? stored procedures in the queries list which are created when access
addes a table to the database.
> I need to keep these "Version Control" stored procedures from being
created. I have tried triggers on the sysobject table but this is not
allowed. The users can not delete the triggers due to sql security.
> I did find out that in access if the view system objects is not check the
dt_ stored procedures will not show up. But I still want to stop these from
being created.
> Any ideas on how to stop them from being created.

DSN-less connection to SQL Server with sql 7 and sql 2k

Hi,
I have commercial asp webspace hosting an application that connects to
an SQL machine on my local network. THe machine has both SQL 7 and SQL
2k running on it. Webspace and SQL are both running on Win2k.
The connection string I am using is as follows:
Application("Application_ConnectionString") = "Provider=sqloledb;" & _
"Network Library=DBMSSOCN;" & _
"Data Source=aaa.bbb.ccc.ddd,1433;" & _
"Initial Catalog=DBName;" & _
"User ID=xxx;" & _
"Password=yyy;"
It works fine when pointing to a database in the sql 7 instance. But
what I want to achieve is to connect to a database in the sql 2k
instance. Running locally, I can achieve this by substituting
aaa.bbb.ccc.ddd\servername_sql2k. But I cannot get it to connect to
the sql 2k instance from the commercial webspace. I get the following
message in this case:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBMSSOCN]General network error. Check your network documentation.
SO, my question is, how do you address a database in the sql 2k
instance via a dsn-less connection? Do you have to set SQL 7 and SQL
2k to listen on different ports? I have tried this but have not met
with success.
Any help gratefully received...
Thanks in advanceCan you make a connection from a DSN from the commercial webspace using
aaa.bbb.ccc.ddd\servername_sql2k as the server name?
Also can you connect via Query Analyzer form the commercial webspace using
that servername?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hi Rand
Thanks for your reply. Restricted access to the commercial web space
means that I DSN cannot be established, hence the DSN less connection.
For that reason I cannot try your suggestion of connecting Query
Analyser from that server. However, I have ascertained that both
instances of SQL Server can be reached from an external server by
connecting from a server where where I do have SQL and OS level
access.
rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<A1F7CV6gEHA.480@.cpms
ftngxa06.phx.gbl>...
> Can you make a connection from a DSN from the commercial webspace using
> aaa.bbb.ccc.ddd\servername_sql2k as the server name?
> Also can you connect via Query Analyzer form the commercial webspace using
> that servername?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.

DSN-less connection to SQL Server with sql 7 and sql 2k

Hi,
I have commercial asp webspace hosting an application that connects to
an SQL machine on my local network. THe machine has both SQL 7 and SQL
2k running on it. Webspace and SQL are both running on Win2k.
The connection string I am using is as follows:
Application("Application_ConnectionString") = "Provider=sqloledb;" & _
"Network Library=DBMSSOCN;" & _
"Data Source=aaa.bbb.ccc.ddd,1433;" & _
"Initial Catalog=DBName;" & _
"User ID=xxx;" & _
"Password=yyy;"
It works fine when pointing to a database in the sql 7 instance. But
what I want to achieve is to connect to a database in the sql 2k
instance. Running locally, I can achieve this by substituting
aaa.bbb.ccc.ddd\servername_sql2k. But I cannot get it to connect to
the sql 2k instance from the commercial webspace. I get the following
message in this case:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBMSSOCN]General network error. Check your network documentation.
SO, my question is, how do you address a database in the sql 2k
instance via a dsn-less connection? Do you have to set SQL 7 and SQL
2k to listen on different ports? I have tried this but have not met
with success.
Any help gratefully received...
Thanks in advance
Can you make a connection from a DSN from the commercial webspace using
aaa.bbb.ccc.ddd\servername_sql2k as the server name?
Also can you connect via Query Analyzer form the commercial webspace using
that servername?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Rand
Thanks for your reply. Restricted access to the commercial web space
means that I DSN cannot be established, hence the DSN less connection.
For that reason I cannot try your suggestion of connecting Query
Analyser from that server. However, I have ascertained that both
instances of SQL Server can be reached from an external server by
connecting from a server where where I do have SQL and OS level
access.
rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<A1F7CV6gEHA.480@.cpmsftngxa06.phx.gbl>...
> Can you make a connection from a DSN from the commercial webspace using
> aaa.bbb.ccc.ddd\servername_sql2k as the server name?
> Also can you connect via Query Analyzer form the commercial webspace using
> that servername?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.