PRB: Import DTS Fails When the Configuration File Is Located on a Mapped Drive (323193)



The information in this article applies to:

  • Microsoft TV Server

This article was previously published under Q323193

SYMPTOMS

When you run the Import DTS utility, and the configuration file is located on a mapped drive or on a protected share, the utility fails.

When the remote directory is shared out (with full access for everyone), and the share is used, the Import DTS utility works correctly.

CAUSE

This behavior occurs because the job runs under the SQL Server Agent context, which is set to localsystem.

WORKAROUND

To use mapped drives or protected shares, set up the SQL Server Agent context with an account that has permissions for both servers.

MORE INFORMATION

Steps to Reproduce the Behavior

  1. Move the file ChatConfig.xls to a remote server.
  2. Map a drive to the remote drive. For example:

    net use g: \\redsand1\d$

  3. Set the Import DTS utility to use the remote share. For example:

    G:\Program Files\Microsoft TV Server\TV Applications\appdata\ChatXML\chatdata\ChatConfig.xls

  4. Run the Import DTS utility.

Modification Type:MinorLast Reviewed:6/18/2003
Keywords:kbprb KB323193