Cannot get proxy account to work.

For some reason I cannot get a job to run under a different account other
than the SQL Agent. What I have done is the following.
1)Created a credential called operations that has the domain\user format
with its password. The user used is the SA of the sql server.
2)I created a proxy that is linked to this credential. In this Proxy I have
set it up to run all subsystems. I have also linked two users to this proxy.
3)I changed the job owner to be a user that will use the proxy
4)I changed each job step to run as the proxy created.
When I run the job, the job instantly fails. I keep getting the following
error.
Executed as user: DOMAIN\user. The process could not be created for step 1
of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
not held by the client). The step failed.
At one time this worked great. I believe this broke because of an update
that was applied.
I have recreated the credential and the proxy several times and I cannot see
what I am doing wrong.
Can anyone help me.
Hi Chris, please take a look at this tip on what to take care of when running
a SQL Server Agent job using a proxy account:
http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"Chris Lumnah" wrote:

> For some reason I cannot get a job to run under a different account other
> than the SQL Agent. What I have done is the following.
> 1)Created a credential called operations that has the domain\user format
> with its password. The user used is the SA of the sql server.
> 2)I created a proxy that is linked to this credential. In this Proxy I have
> set it up to run all subsystems. I have also linked two users to this proxy.
> 3)I changed the job owner to be a user that will use the proxy
> 4)I changed each job step to run as the proxy created.
> When I run the job, the job instantly fails. I keep getting the following
> error.
> Executed as user: DOMAIN\user. The process could not be created for step 1
> of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
> not held by the client). The step failed.
> At one time this worked great. I believe this broke because of an update
> that was applied.
> I have recreated the credential and the proxy several times and I cannot see
> what I am doing wrong.
> Can anyone help me.
|||Thank you for the reply. I will try this out. Is this aimed at the SQL
Agent Service account or the proxy account? Should I apply it to both?
Thanks again.
"Saleem Hakani" wrote:
[vbcol=seagreen]
> Hi Chris, please take a look at this tip on what to take care of when running
> a SQL Server Agent job using a proxy account:
> http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "Chris Lumnah" wrote:
|||That's correct Chris. It's for SQL Server Agent service but you can applyit
for both as well.
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"Chris Lumnah" wrote:
[vbcol=seagreen]
> Thank you for the reply. I will try this out. Is this aimed at the SQL
> Agent Service account or the proxy account? Should I apply it to both?
> Thanks again.
> "Saleem Hakani" wrote:
|||Saleem,
I have done what you suggested. However I still have the same problem. I
did all the items on that list, short of rebooting the server. Any other
ideas?
"Saleem Hakani" wrote:
[vbcol=seagreen]
> That's correct Chris. It's for SQL Server Agent service but you can applyit
> for both as well.
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "Chris Lumnah" wrote:

Cannot get proxy account to work.

For some reason I cannot get a job to run under a different account other
than the SQL Agent. What I have done is the following.
1)Created a credential called operations that has the domain\user format
with its password. The user used is the SA of the sql server.
2)I created a proxy that is linked to this credential. In this Proxy I have
set it up to run all subsystems. I have also linked two users to this proxy
.
3)I changed the job owner to be a user that will use the proxy
4)I changed each job step to run as the proxy created.
When I run the job, the job instantly fails. I keep getting the following
error.
Executed as user: DOMAIN\user. The process could not be created for step 1
of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
not held by the client). The step failed.
At one time this worked great. I believe this broke because of an update
that was applied.
I have recreated the credential and the proxy several times and I cannot see
what I am doing wrong.
Can anyone help me.Hi Chris, please take a look at this tip on what to take care of when runnin
g
a SQL Server Agent job using a proxy account:
http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"Chris Lumnah" wrote:

> For some reason I cannot get a job to run under a different account other
> than the SQL Agent. What I have done is the following.
> 1)Created a credential called operations that has the domain\user format
> with its password. The user used is the SA of the sql server.
> 2)I created a proxy that is linked to this credential. In this Proxy I ha
ve
> set it up to run all subsystems. I have also linked two users to this pro
xy.
> 3)I changed the job owner to be a user that will use the proxy
> 4)I changed each job step to run as the proxy created.
> When I run the job, the job instantly fails. I keep getting the following
> error.
> Executed as user: DOMAIN\user. The process could not be created for step 1
> of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
> not held by the client). The step failed.
> At one time this worked great. I believe this broke because of an update
> that was applied.
> I have recreated the credential and the proxy several times and I cannot s
ee
> what I am doing wrong.
> Can anyone help me.|||Thank you for the reply. I will try this out. Is this aimed at the SQL
Agent Service account or the proxy account? Should I apply it to both?
Thanks again.
"Saleem Hakani" wrote:
[vbcol=seagreen]
> Hi Chris, please take a look at this tip on what to take care of when runn
ing
> a SQL Server Agent job using a proxy account:
> http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "Chris Lumnah" wrote:
>|||That's correct Chris. It's for SQL Server Agent service but you can applyit
for both as well.
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"Chris Lumnah" wrote:
[vbcol=seagreen]
> Thank you for the reply. I will try this out. Is this aimed at the SQL
> Agent Service account or the proxy account? Should I apply it to both?
> Thanks again.
> "Saleem Hakani" wrote:
>|||Saleem,
I have done what you suggested. However I still have the same problem. I
did all the items on that list, short of rebooting the server. Any other
ideas?
"Saleem Hakani" wrote:
[vbcol=seagreen]
> That's correct Chris. It's for SQL Server Agent service but you can applyi
t
> for both as well.
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "Chris Lumnah" wrote:
>

Cannot find module in web data administrator

I just downloaded the web data administrator from MSDN and after entering my credential, I get this error:

Specified module cannot be found
at SqlAdmin.SqlServer.Connect()
at SqlWebAdmin.databases.Page_Load(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain()

The only page I can see is the Import page, the database and the export get the same error.
It's a fresh install, anyone know something I need to do to get a correct install ?Since I had not yet downloaded and installed the Web Data Administrator, I went just now and installed it from Microsoftlink

I just clicked on Download, chose "Open" and just left whatever defaults there might have been. I went into SQL Server and changed the authentication mode to mixed. Then I went to http://localhost/sqlwebadmin/default.aspx and logged in with my sa login and password. It all worked like a charm.

Not sure what help any of that is...

Terri|||I tried doing another clean install, but I get the same problem.

I can login just fine, but after leaving default.aspx, I get the error in the 2 other pages.

Without better error description I fear I won't be able to find the bug in all this code, more so if it work on other machines.

Here is the code of the Connect Method from where the error seem to be coming:

 dmoServer = (NativeMethods.ISqlServer)new NativeMethods.SqlServer();
 dmoServer.Connect(Name, Username, Password);

I have no idea what's this NativeMethods thing is coming from. I'm using MSDE, could that be the problem ?