DTS export problem

Hello

i can 't use DTS export via entreprise manager betwen 2 identic server (same os ,same
sqlserver 7 ,same pack et...)

I have this message

The licensing mode don t let to use DTS export ...

Where i find a parameter ?
Where i find a tool to change the licensing mode ?

RegardsControl Panel/Licensingsql

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 Errors with Access?

Hi,

I have a DTS package that when executed through Enterprise Manager works just fine.
I have an Access app on a different computer that executes the DTS package via VB using the syntax below. This process causes the DTS package to return an error of 'SQL Server Does Not Exist or Access Denied'.
I have tried both authentication types, not making a difference. I have used the SA login from Access and still get the error. All the necessary DTS drivers are installed on the second box and I can connect to the SQL tables succesfully also...
Any ideas? Thanks!

Private Sub cmd_MPSDTS_Click()

Dim oPackage As New DTS.Package
On Error GoTo eh

oPackage.LoadFromSQLServer "SVRName", "sa", "pwd", DTSSQLStgFlag_Default, "", "", "", "Pkg_Name", 0
'Execute the Package

oPackage.Execute
'MsgBox oPackage.Description, vbInformation, _
"Re-import Excel sheet."

'Clean up.
MsgBox ("Ran DTS Package")
Set oPackage = Nothing
Exit Sub
eh:
MsgBox Err.Description, vbCritical, _
"Error Running Package"

End SubI assume you have tried pinging the server from the machine with the access db? or rather from the machine that opens the access db.|||You should also check that the user you are executing as from Access is the same as the user that is executing from Enterprise Manager or at least has the same privileges.|||Not sure why that would make a difference (Not saying it wouldn't, I'm just not sure why it would). The error they are receiving makes it look as though they can't reach the server at all...|||Found the problem,

The DTS package imported information from an Informix database. The necessary drivers weren't installed on the second machine so the job failed even though I could connect to the SQL server just fine. I got around it by changing the code to execute a SQL Job which in turn executed the DTS package. This way it ran on the SQL server.

Thanks!

DTS Design Error - Access is denied

I am pretty new to MS SQL Server ...

I have installed SQL Server Enterprise Manager Version 8.0. I am getting the following error while try to create a new DTS Package.

"DTS designer Error ... Access Denied"

getting the DTS packge design window but there is no TASK icon visible
either in the tool bar or menu....

Enterprise Manager Version 8.0

OS : Windows XP pro with SP1If you go to the msdb database, the user you are using needs to have EXEC permissions on the procs that have dts in the name. This is by default granted to public, so I'm not sure why your user wouldn't have that. ?|||See whether this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;814113 is any help to you.

DTS and Interbase/Firebird

I have written several DTS pakages to copy data from an Interbase/Firebird db to SQL Server. They execute under Enterrpise Manager perfectly but when scheduled return an error.

I am aware that permissions are a normal source of these problems but I have hopefully excluded them from teh equation by using a local admin/domain/sysadmin user throughout for SEM, SQLServerAgent and even the SQLServerAgentProxy.

The problem appears to be related to the interaction between the Microsoft OLE DB Provider for ODBC Drivers and the Interbase/Firebird Driver. I have checked several forums and the MSDN website but few people seem to have experienced this type of problem in this environment.

Error msgs:

Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
Step Error Description:[Easysoft][InterBase]unavailable database
Step Error code: 80004005
Step Error Help File:
Step Error Help Context ID:0

OR

Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
Step Error Description:unavailable database
Step Error code: 80040E4D
Step Error Help File:
Step Error Help Context ID:0

My Setup:

MS SQL Server 2000 with SP3
MDAC 2.8 RTM
Interbase v6 /Firebird 1.03 db Server

Have tried the following driver/connectors:

Firebird ODBC v1.02.00.41
Easysoft ODBC v2.01.00.01
XTG Interbase6 ODBC v1.00.00.15

I have even tried OLE DB providers for Interbase/Firebird but they won't schedule either giving me an SQLCODE=-904

Any insight/help/sympathy appreciated. I have struggled with this single issue for nearly a week.I finally resolved the issue and wanted to post it so that someone else might benefit.

There is a difference between the way Enterprise Manager 'interfaces' with the ODBC connections setup on the machine and the way SQL Server Agent does when a scheduled job is executed. Not entirely sure what the difference is I think that the difference is that SQL Enterprise Manager assumes / defaults to a TCP/IP connection whereas the SQL Server Agent assumes / defaults to a named pipe connection.

So if you are using Interbase make sure you specify a TCP/IP connection in the ODBC setup, e.g. 127.0.0.1:C:\Interbase\db\test.gdb

DTS

What is the easiest way to give a user the abilitiy to run a DTS package
without having the Enterprise Manager on their workstation?I'm no expert my any stretch...I think there's an option to save your DTS
package as a Visual Basic executable file. If I remember correctly, this
option is provided while you go through the import/export wizard.
"Johnny" wrote:

> What is the easiest way to give a user the abilitiy to run a DTS package
> without having the Enterprise Manager on their workstation?|||Hi
Does the user have QA on his/her workstation?
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:5EAD6100-98E2-4378-B38D-D3BB8F059CE0@.microsoft.com...
> What is the easiest way to give a user the abilitiy to run a DTS package
> without having the Enterprise Manager on their workstation?|||> What is the easiest way to give a user the abilitiy to run a DTS package
> without having the Enterprise Manager on their workstation?
They need to have the dts runtime on their computer, then you can call
dtsrun.exe from the command line, for more info look in BOL.
If you wish to call a dts package from a sql script you can use
xp_cmdshell..

DTC Crashing

Has anybody here seen and resolved the following error?

The MS DTC Transaction Manager is in an inconsistent state and cannot proceed. Please contact Microsoft Product Support. (null)

File: .\tmtx.cpp, Line: 2570.

We've had this just crop up on a server over the last week. Not finding a lot.what OS are u using?,windows 2003 or windows xp sp2?.
If you are using COM+/Enterprise Services components that talk to resource managers like Oracle or other XA RM, on Windows Server 2003 you need to make some additional steps to allow this scenario to work. This is due to a security change in MSDTC that requires you to register the XA DLL in registry. See more details at http://support.microsoft.com/?id=817066|||This is on 2000 AS.

It has been workinmg fine for 3 years until last week. No patches were installed last week.|||I think it might have something to do with one of the october microsoft security updates.For more details about this problem,check this link,
http://support.microsoft.com/kb/902400 and http://support.microsoft.com/kb/909444/|||Microsoft has a private fix for this. It is related to a security patch so help is free, call.....

Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.

DSV in SSIS

Hi,
How can we make use of DSV in SSIS?

In the connection manager of a package i tried to add a link to it but couldn't.

I believe it has an importance since it is there. Could anyone tell me what is its benefits and how it could be implemented?

Thanks

Christina

A DSV allows you to create a metadata layer over an existing Data Source. Within a DSV, you can select a subset (or all) of the tables and views available from a Data Source, rename any of the tables/views and/or their columns, add new Named Calculations (which act like computed columns within a table/view), and add new Named Queries (which are complete select statements, which basically act like views).

To use a DSV within SSIS, you still create a Connection Manager that points to the Data Source that the DSV is based on. Then, when you select the Connection Manager, you should have the option to select the DSV that is based on it. For example, if you have a Data Source based on an OLE DB provider connecting to SQL Server, you could create a DSV based on the database that the Data Source is connecting to. Then, within a Data Flow task, if you add an OLE DB Source adapter, when you select the Connection Manager based on your OLE DB data source, you should be able to also select the DSV.

HTH,

Dave Fackler

|||

Thanks Dave.

Actually this is what I read about it in the books online. However when I come to add a data source in the connection manager i don't see the DSV among the possible connections.

Have you tried it? I could have missed something.

Thanks again

Christina