November 19, 2012 at 6:17 am
How do I add read permission and write permission to the Temp directory of the SQL Server Agent Service startup account.
Many Thanks
Stuart.
November 19, 2012 at 7:25 am
You can give persmion temp folder SQLServerSqlAgentUser$InstanceName
March 12, 2013 at 12:28 pm
ESAT ERKEC (11/19/2012)
You can give persmion temp folder SQLServerSqlAgentUser$InstanceName
I can't find this folder.
What is the entore path?
Thanks!
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 12, 2013 at 12:40 pm
Welsh Corgi (3/12/2013)
ESAT ERKEC (11/19/2012)
You can give persmion temp folder SQLServerSqlAgentUser$InstanceNameI can't find this folder.
What is the entore path?
Thanks!
It appears to mean, grant permissions on the temp directory to the SQLServerSqlAgentUser$InstanceName account.
Just interpreting
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 12, 2013 at 2:29 pm
Thanks.
The folder was hidden granted permissions and I still get the error.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 12, 2013 at 2:31 pm
I get this error when I attempt to run the Package using the Domain Account, SQLServerAgent.
Message
Executed as user: MyDomain\SQLServerAgent. Microsoft (R) SQL Server Execute Package Utility Version 10.50.2500.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 01:29:42 PM Could not load package "\Dev\AS400\CYP_Staging_Load_Truncate_Nightly" because of error 0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80040E4D (Login failed for user 'MuDomain\SQLServerAgent'.). The SQL statement that was issued has failed. Source: Started: 01:29:42 PM Finished: 01:29:42 PM Elapsed: 0.046 seconds. The package could not be loaded. The step failed.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 12, 2013 at 4:40 pm
Is the package stored in msdb or filesystem?
Oh, and it would be a good idea to start a new thread for this. This was an old thread and appears to be slightly different
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 12, 2013 at 4:45 pm
It is stored in MSDB, thanks.
I will open a new thread.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 12, 2013 at 4:52 pm
I opened a new thread:
http://www.sqlservercentral.com/Forums/Forum1550-1.aspx?Update=1">
http://www.sqlservercentral.com/Forums/Forum1550-1.aspx?Update=1
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy