When usung XP (extended procedures), the login you use to access the SQL
server instance will require permissions within to run extended procedures.
Look for setting permissiones in SQL. To test this out, try running the
command by connecting to SQL instance with Admin rights (sa, blan) or provide
the login that will execute the command admin rights. From there, you can
play with the Security settings for setting up a DB user and providing the
necessary rights you want that user to have. Normally, it is best to setup a
DB System User and use that user to running extended procedures through a job
or DTS once you get things setup the way you need.
"Douglas M" wrote:
Quote:
I have a DTS package that I have had to manually run because it got blocked
by XP Security.
Now XP is even blocking the copyfile command step when I manually run it.
How do I turn off the XP Security or how do I change the scripts to run.
thanks. |