Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 323193 - Last Review: June 18, 2003 - Revision: 1.1
PRB: Import DTS Fails When the Configuration File Is Located on a Mapped Drive
This article was previously published under Q323193
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.
This behavior occurs because the job runs under the SQL Server Agent context, which is set to
localsystem.
To use mapped drives or protected shares, set up the SQL Server Agent context with an account that has permissions for both servers.
Steps to Reproduce the Behavior
- Move the file ChatConfig.xls to a remote server.
- Map a drive to the remote drive. For example:
net use g: \\redsand1\d$
- 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
- Run the Import DTS utility.
APPLIES TO
- Microsoft TV Server 2.0 Service Pack 1
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate