proxy account in SQL 2000 cluster environment

#1

Hi guys,

I have run into issue with proxy account in cluster - after failover from 1
node to 2nd it stops working. Also resetting the password doesn't help -
still jobs fail with an error: a required privilage is not held by the client.
Permissions on server seems to be the same.
Is there any issue with proxy account on cluster (like it was in 7.0
version) or it should work?

#2

Hmm, this is domain account with local admin right.

So my situation looks as follow:
cluster failed over from 1 node to other and after that proxy account
stopped working.
I get following message: a required privilage is not held by the
client.

Now when I try to reset proxy account through TSQL I get the message: Error
executing extended stored procedure: Specified user can not login

Additionally 1 of the jobs is failing with a message (executing with sql
agent account): Error Source= msxml4.dll Error Description: Access is
denied.

SQL Server agent is local administrator and sysadmin. I have also granted it
following permissions explicitly:
- Act as part of the Operating System
- Increase Quotas
- Log on as a Service
- Replace a process level token
- Log on as a batch Job

and SQL proxy account:
- Log on as a batch Job

Still the same issue. Any idea what it might be? Any help appreciated

"Ralf Dietrich" wrote:

Quote:

Hello Karolina,

be aware to use a domain account for proxy - I'm currently not know about
an issue.

HTH
Ralf

Hi guys,

I have run into issue with proxy account in cluster - after failover
from 1
node to 2nd it stops working. Also resetting the password doesn't help
-
still jobs fail with an error: a required privilage is not held by the
client.
Permissions on server seems to be the same.
Is there any issue with proxy account on cluster (like it was in 7.0
version) or it should work?

#3

Hmm, this is domain account with local admin right.

So my situation looks as follow:
cluster failed over from 1 node to other and after that proxy account
stopped working.
I get following message: a required privilage is not held by the
client.

Now when I try to reset proxy account through TSQL I get the message: Error
executing extended stored procedure: Specified user can not login

Additionally 1 of the jobs is failing with a message (executing with sql
agent account): Error Source= msxml4.dll Error Description: Access is
denied.

SQL Server agent is local administrator and sysadmin. I have also granted it
following permissions explicitly:
- Act as part of the Operating System
- Increase Quotas
- Log on as a Service
- Replace a process level token
- Log on as a batch Job

and SQL proxy account:
- Log on as a batch Job

Still the same issue. Any idea what it might be? Any help appreciated

"Ralf Dietrich" wrote:

Quote:

Hello Karolina,

be aware to use a domain account for proxy - I'm currently not know about
an issue.

HTH
Ralf

Hi guys,

I have run into issue with proxy account in cluster - after failover
from 1
node to 2nd it stops working. Also resetting the password doesn't help
-
still jobs fail with an error: a required privilage is not held by the
client.
Permissions on server seems to be the same.
Is there any issue with proxy account on cluster (like it was in 7.0
version) or it should work?

#4

Hmm, this is domain account with local admin right.

So my situation looks as follow:
cluster failed over from 1 node to other and after that proxy account
stopped working.
I get following message: a required privilage is not held by the
client.

Now when I try to reset proxy account through TSQL I get the message: Error
executing extended stored procedure: Specified user can not login

Additionally 1 of the jobs is failing with a message (executing with sql
agent account): Error Source= msxml4.dll Error Description: Access is
denied.

SQL Server agent is local administrator and sysadmin. I have also granted it
following permissions explicitly:
- Act as part of the Operating System
- Increase Quotas
- Log on as a Service
- Replace a process level token
- Log on as a batch Job

and SQL proxy account:
- Log on as a batch Job

Still the same issue. Any idea what it might be? Any help appreciated

"Ralf Dietrich" wrote:

Quote:

Hello Karolina,

be aware to use a domain account for proxy - I'm currently not know about
an issue.

HTH
Ralf

Hi guys,

I have run into issue with proxy account in cluster - after failover
from 1
node to 2nd it stops working. Also resetting the password doesn't help
-
still jobs fail with an error: a required privilage is not held by the
client.
Permissions on server seems to be the same.
Is there any issue with proxy account on cluster (like it was in 7.0
version) or it should work?

#5

Hmm, this is domain account with local admin right.

So my situation looks as follow:
cluster failed over from 1 node to other and after that proxy account
stopped working.
I get following message: a required privilage is not held by the
client.

Now when I try to reset proxy account through TSQL I get the message: Error
executing extended stored procedure: Specified user can not login

Additionally 1 of the jobs is failing with a message (executing with sql
agent account): Error Source= msxml4.dll Error Description: Access is
denied.

SQL Server agent is local administrator and sysadmin. I have also granted it
following permissions explicitly:
- Act as part of the Operating System
- Increase Quotas
- Log on as a Service
- Replace a process level token
- Log on as a batch Job

and SQL proxy account:
- Log on as a batch Job

Still the same issue. Any idea what it might be? Any help appreciated

"Ralf Dietrich" wrote:

Quote:

Hello Karolina,

be aware to use a domain account for proxy - I'm currently not know about
an issue.

HTH
Ralf

Hi guys,

I have run into issue with proxy account in cluster - after failover
from 1
node to 2nd it stops working. Also resetting the password doesn't help
-
still jobs fail with an error: a required privilage is not held by the
client.
Permissions on server seems to be the same.
Is there any issue with proxy account on cluster (like it was in 7.0
version) or it should work?

#6

Hmm, this is domain account with local admin right.

So my situation looks as follow:
cluster failed over from 1 node to other and after that proxy account
stopped working.
I get following message: a required privilage is not held by the
client.

Now when I try to reset proxy account through TSQL I get the message: Error
executing extended stored procedure: Specified user can not login

Additionally 1 of the jobs is failing with a message (executing with sql
agent account): Error Source= msxml4.dll Error Description: Access is
denied.

SQL Server agent is local administrator and sysadmin. I have also granted it
following permissions explicitly:
- Act as part of the Operating System
- Increase Quotas
- Log on as a Service
- Replace a process level token
- Log on as a batch Job

and SQL proxy account:
- Log on as a batch Job

Still the same issue. Any idea what it might be? Any help appreciated

"Ralf Dietrich" wrote:

Quote:

Hello Karolina,

be aware to use a domain account for proxy - I'm currently not know about
an issue.

HTH
Ralf

Hi guys,

I have run into issue with proxy account in cluster - after failover
from 1
node to 2nd it stops working. Also resetting the password doesn't help
-
still jobs fail with an error: a required privilage is not held by the
client.
Permissions on server seems to be the same.
Is there any issue with proxy account on cluster (like it was in 7.0
version) or it should work?

#7

Hmm, this is domain account with local admin right.

So my situation looks as follow:
cluster failed over from 1 node to other and after that proxy account
stopped working.
I get following message: a required privilage is not held by the
client.

Now when I try to reset proxy account through TSQL I get the message: Error
executing extended stored procedure: Specified user can not login

Additionally 1 of the jobs is failing with a message (executing with sql
agent account): Error Source= msxml4.dll Error Description: Access is
denied.

SQL Server agent is local administrator and sysadmin. I have also granted it
following permissions explicitly:
- Act as part of the Operating System
- Increase Quotas
- Log on as a Service
- Replace a process level token
- Log on as a batch Job

and SQL proxy account:
- Log on as a batch Job

Still the same issue. Any idea what it might be? Any help appreciated

"Ralf Dietrich" wrote:

Quote:

Hello Karolina,

be aware to use a domain account for proxy - I'm currently not know about
an issue.

HTH
Ralf

Hi guys,

I have run into issue with proxy account in cluster - after failover
from 1
node to 2nd it stops working. Also resetting the password doesn't help
-
still jobs fail with an error: a required privilage is not held by the
client.
Permissions on server seems to be the same.
Is there any issue with proxy account on cluster (like it was in 7.0
version) or it should work?

#8

Hmm, this is domain account with local admin right.

So my situation looks as follow:
cluster failed over from 1 node to other and after that proxy account
stopped working.
I get following message: a required privilage is not held by the
client.

Now when I try to reset proxy account through TSQL I get the message: Error
executing extended stored procedure: Specified user can not login

Additionally 1 of the jobs is failing with a message (executing with sql
agent account): Error Source= msxml4.dll Error Description: Access is
denied.

SQL Server agent is local administrator and sysadmin. I have also granted it
following permissions explicitly:
- Act as part of the Operating System
- Increase Quotas
- Log on as a Service
- Replace a process level token
- Log on as a batch Job

and SQL proxy account:
- Log on as a batch Job

Still the same issue. Any idea what it might be? Any help appreciated

"Ralf Dietrich" wrote:

Quote:

Hello Karolina,

be aware to use a domain account for proxy - I'm currently not know about
an issue.

HTH
Ralf

Hi guys,

I have run into issue with proxy account in cluster - after failover
from 1
node to 2nd it stops working. Also resetting the password doesn't help
-
still jobs fail with an error: a required privilage is not held by the
client.
Permissions on server seems to be the same.
Is there any issue with proxy account on cluster (like it was in 7.0
version) or it should work?

#9

Hmm, this is domain account with local admin right.

So my situation looks as follow:
cluster failed over from 1 node to other and after that proxy account
stopped working.
I get following message: a required privilage is not held by the
client.

Now when I try to reset proxy account through TSQL I get the message: Error
executing extended stored procedure: Specified user can not login

Additionally 1 of the jobs is failing with a message (executing with sql
agent account): Error Source= msxml4.dll Error Description: Access is
denied.

SQL Server agent is local administrator and sysadmin. I have also granted it
following permissions explicitly:
- Act as part of the Operating System
- Increase Quotas
- Log on as a Service
- Replace a process level token
- Log on as a batch Job

and SQL proxy account:
- Log on as a batch Job

Still the same issue. Any idea what it might be? Any help appreciated

"Ralf Dietrich" wrote:

Quote:

Hello Karolina,

be aware to use a domain account for proxy - I'm currently not know about
an issue.

HTH
Ralf

Hi guys,

I have run into issue with proxy account in cluster - after failover
from 1
node to 2nd it stops working. Also resetting the password doesn't help
-
still jobs fail with an error: a required privilage is not held by the
client.
Permissions on server seems to be the same.
Is there any issue with proxy account on cluster (like it was in 7.0
version) or it should work?

#10

Hmm, this is domain account with local admin right.

So my situation looks as follow:
cluster failed over from 1 node to other and after that proxy account
stopped working.
I get following message: a required privilage is not held by the
client.

Now when I try to reset proxy account through TSQL I get the message: Error
executing extended stored procedure: Specified user can not login

Additionally 1 of the jobs is failing with a message (executing with sql
agent account): Error Source= msxml4.dll Error Description: Access is
denied.

SQL Server agent is local administrator and sysadmin. I have also granted it
following permissions explicitly:
- Act as part of the Operating System
- Increase Quotas
- Log on as a Service
- Replace a process level token
- Log on as a batch Job

and SQL proxy account:
- Log on as a batch Job

Still the same issue. Any idea what it might be? Any help appreciated

"Ralf Dietrich" wrote:

Quote:

Hello Karolina,

be aware to use a domain account for proxy - I'm currently not know about
an issue.

HTH
Ralf

Hi guys,

I have run into issue with proxy account in cluster - after failover
from 1
node to 2nd it stops working. Also resetting the password doesn't help
-
still jobs fail with an error: a required privilage is not held by the
client.
Permissions on server seems to be the same.
Is there any issue with proxy account on cluster (like it was in 7.0
version) or it should work?