I have a DTS that access an .XLS file and imports the content to a SQL
Server table. I am executing the DTS via a Windows .Net application which in
turns calls a store procedure which actually initiates the DTS Package.
Folder/File permissions are set correctly. In fact, I do the below as the
Administrator.

If I run this application on the server with the source file on a local
drive the DTS works fine.

However, if I run this application on the server with the source file on a
mapped drive on another server, the DTS silently fails.

If I run this application from a client workstation on the LAN with the
source file on a mapped drive the DTS silently fails -- eventhough the path
passed to the stored procedure is a valid path on the server.

Can anyone help on this?

wr

See if you can stop using mapped drives.

What happens when you use UNC paths.

The reason this is probably happening is because of who is executing the
package (if the ownership chain is not broken then the SP is the owner of
the SP)

Mapped drives are user specific.

--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"WhiskyRomeo" <WhiskyRomeo (AT) discussions (DOT) microsoft.com> wrote

I have not used UNC before so here goes . . .

In this application, the user clicks on a button which presents a
folderdialog which he uses to specify the full path to the file. Obviously
this will not be in UNC format.

But, if he maps his O drive to the E drive (share name E$) on a machine
named Server2, now a machine named Server1 need to access that file. So I
would have to translate the path to UNC format in code and . . .

O:\DMSPICS\LHS\1197088.xls becomes \\Server2\E$\DMSPICS\LHS\1197088.xls ??

If he were to use a local drive on his machine called Workstation1 instead
and he shares out C:\MyDocs as MyDocs, does the below also work?

C:\MyDocs\LHS\1197088.xls becomes \\Workstation1\MyDocs\LHS\1197088.xls ??

wr



"Allan Mitchell" wrote:

$ shares AFAIK are only available to Admins

--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"WhiskyRomeo" <WhiskyRomeo (AT) discussions (DOT) microsoft.com> wrote

Not always. The admin shares created by the system are
available to admins only. But you can create hidden shares -
you hide a share by appending the dollar sign.

-Sue

On Thu, 13 Jan 2005 21:06:44 -0000, "Allan Mitchell"
<allan (AT) no-spam (DOT) sqldts.com> wrote:

Now you know whay I do not do the OS stuff <grin>

Thanks Sue

--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"Sue Hoegemeier" <Sue_H (AT) nomail (DOT) please> wrote

There is a .net framework security issue against the assembly. A application
on a mapping drive (even if on its own mapping drive) is not fully trusted
by .net framework by default. You have to let framework trust your assembly
in certain zone. Please check the like
http://blogs.msdn.com/shawnfa/archiv...30/344554.aspx


Mark
"WhiskyRomeo" <WhiskyRomeo (AT) discussions (DOT) microsoft.com> wrote