Sql Agent Proxy Issue

Sep 26, 2006

I seem to be having issues getting some of our SSIS packages to work with proxy accounts

The package is a simple pull from an access db into a sql table. The package encryption is set to EncryptAllWithPassword. The .dtsx file and the access db are both on local drives and do not have restrictive permisssions.

The package runs fine under the dev studio as well as from the command line on the server while logged in with the domainSqlJobs account. But attempting to execute the job from the Sql Agent using a using a proxy account fails, giving the following error information.

The AcquireConnection method call to the connection manager "test" failed with error code 0xC0202009.

component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.

One or more component failed validation.

There were errors during task validation.

The SSIS service is running under the domainSqlServiceP account.

So here is what I have done....

I have created a login, credential, and proxy for the domainSqlJobs account. The SqlJobs proxy has been assigned principals to the desired login accounts and was assigned as the Run As account in an execute SSIS package step of a Sql Agent Job. With the proxy in place the job fails if started manually from the Managment Studio, or scheudled, no matter what account kicks off the job.

Logging in as an admin and changing the step to execute under the Sql Agent Service Account will allow the job to be run successfully, but I would rather not have to manage all of our developers jobs or elevate their rights. Using the same proxy as before, but changing the step to a cmdexec gives the same error as above. The proxy will execute SSIS packages that do not involve an access db data source

again...Logging in directly to the server with the proxy account and running the package from the command line does work...

Am I missing something?

View 1 Replies


ADVERTISEMENT

FTP Task Failing When Using Agent Proxy

Jan 11, 2008

Hi,

I am having problems with an SSIS package whereby the first step of the package is failing. I am getting the following error message:

Unable to connect to FTP server using "FTPLocation".

This only happens when I use a Agent Proxy as the 'Run as' option. If I change it back to SQL Agent Service Account it works perfectly.

For the credentials of the proxy, I have used my own windows login as the identity. And I have full priveleges on the server, ie if I log on to the server I can successfully ftp to the same site and download the file without any problems. So shouldn't the Agent be able to do so too when it uses my credentials?

Any help would be much appreciated.

DrBrain

View 3 Replies View Related

Do We Need Proxy Setup To Run DTEXEC From Agent ?

Mar 13, 2008

to DTEXEC from a agent job , what will be the permissions that are needed ?
I guess that can be SQL Server login with admin permissions will be fine and we don't need a proxy setup.

View 1 Replies View Related

SSIS Sql Agent Run As Proxy Error

May 29, 2008

I'm attempting to run a ssis package via sql server agent.

The package and the DB are on a cluster.

The package runs fine when 'Sql Server Agent' is the run-as.

When I try and use a proxy to run the package, it fails with this error:

Date 5/28/2008 6:21:54 PM
Log SQL Agent (Current - 5/28/2008 6:21:00 PM)
Message
[136] Job CorpFoo New reported: The process could not be created for step 1 of job 0xDAE2A53F27943D4CA412A0D177CAA546 (reason: A required privilege is not held by the client)


I've:
Create Credential to be used by proxy
Create Proxy
Give Permissions to Proxy in SQL Server
Give Permissions to Proxy at the Server for SQL Agent Batch Run
Give Permissions to Proxy at the Server to Connect to SSIS

EXEC dbo.sp_grant_login_to_proxy
@login_name = N'Myapplication_DBO',
@proxy_name = N'Myapplication_Batch_PROXY' ;


EXEC dbo.sp_grant_proxy_to_subsystem
@proxy_name = 'Myapplication_Batch_PROXY',
@subsystem_id = 11;


I've tried a number of things, including adding the sql user (who has access to the proxy) as sys admin on SQL and the OS. That didn't help either.

Has anyone experienced this error? Is there any way to further diagnose this (completely unhelpful) error message?

Thanks,

Steve.

View 2 Replies View Related

Using Proxy Accounts To Run SSIS Packages By SQL Agent

Feb 13, 2008



Hello!

I have SSIS Package that needs special permissions in network. I want to schedule SSIS running using SQL Agent. I don't want to other Jobs starts with special permissions. So, I decided to use proxy account to impersonate SSIS starting process by account with those permissions. I've perfomed following steps:
1. Create Login for the future proxy account and add it to sysadmins role.
2. Create Credential with account name and password information.
3. Create proxy account and give to it rights to run SSIS, CmdExec and ActiveX create.
4. Set Run as for step that starts my package to this proxy
5. Start my job.
and I receive error "Process couldnot be created for step 1 job xxx. Reason: 1314"
SQL Agent account and proxy accounts has also administrators rights on SQL Server computer and rights to login as service.
When I change step configuration to run as SQL Agent account job completes succesfull.
What do I do wrong?

Thx,
Olga

View 8 Replies View Related

Question About Credential For Proxy For Ssis Package In Agent Job ...

Mar 6, 2008




I had a question about proxy account for ssis.
Is it necessary to set up credential with windows account for proxy account so that ssis package can be setup as a job in agent ?

without proxy account ssis package is unable to run under agent as a job ..but..
does identity in credential for proxy need to be windows account ?

View 4 Replies View Related

Proxy Auto-Configuration Url Not Found Error - But Not Using Proxy

May 15, 2007

I have read all the posts regarding this error, but non-solve my problem as I had already addressed them.

I am setting up Merge Replication via the Web and I get this error when i try to sync. Let me give you some background.

I wrote a small windows test app to test merge replication, in which i am using RMO to accomplish the replication. This works. It syncs every time. I then copied the "sync" code from the winform application and created a Windows Service in which i placed "sync" code. The sync code did not change other than adding the additional following four lines:



_mergeAgent.InternetUrl = _internetURL;

_mergeAgent.InternetLogin = _internetLogin;

_mergeAgent.InternetPassword = _internetPassword;

_mergeAgent.InternetTimeout = _internetTimout;





where the internet url is https://ipaddress/virtualdirectory/replisapi.dll





I have been working with this for a while now trying to figure out why this works (on the same machine) in a winforms app but not through the web (via a windows service).



Any insight would be greatly appreciated.



Thanks...

View 3 Replies View Related

Execute Sql Server Agent Job Task - Job Immediately Returns Success... However Agent Job Is Still Running???

Nov 30, 2006

when I run a package from a command window using dtexec, the job immediately says success.
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 3:37:41 PM
Finished: 3:37:43 PM
Elapsed: 2.719 seconds



However the Job is still in th agent and the status is executing. The implications of this are not good. Is this how the sql server agent job task is supposed to work by design.



Thanks,

Larry

View 1 Replies View Related

Cmd Shell Proxy

Jun 28, 2006

I am attempting to execute xp_cmdshell with a non-sysadmin db login. I have created a Windows account and the associated proxy account in SQL Server. I have verified SQL Server is showing the proxy account credentials. I am still getting the following error. What am I missing? Guidance is very appreciated.



Microsoft OLE DB Provider for SQL Server error '80040e09'

EXECUTE permission denied on object 'xp_cmdshell', database 'mssqlsystemresource', schema 'sys'.

View 1 Replies View Related

Proxy Error

Jun 8, 2006

(Posting this again since my original post has disappeared from the forum sometime during the day.)

I have about a dozen jobs that are being started at the same time (1:30am). Each time they start up, I end up with a random number of those jobs failing to run and logging the follow error:

Unable to start execution of step 1 (reason: Error authenticating proxy LSPJobUser, system error: Logon failure: unknown user name or bad password.). The step failed.

Each night it is a different collection of failed jobs (some work and some do not). If I manually run the job they ALL work EVERY time.

As anybody experienced this before? Is it possible that SQL Agent cannot handle a dozen jobs at once? (Or at a minimum cannot authenticate a dozen jobs at once.) (I do not believe it but cannot think of any other possibility.)

(For a quick fix I am going to stagger the dozen jobs to start over a ten minute period instead of starting at the same time.)

- Jason

View 4 Replies View Related

Problem With A Proxy

Jul 24, 2006

Hi

i have a problem with a proxy and i don't know how to resolve this

So, i want to run a SSIS package so i follow this http://support.microsoft.com/kb/918760

However, the package fails and i have a error message which tell me that i can't get proxy's data for proxy_id = 23!

If someone has the solution please help me!!

View 1 Replies View Related

Proxy Fails To Run The Job

Apr 28, 2008

Hi All,

I need to create a Proxy to run a job. So, I created a Credential, and created a proxy with that credential. The account that I am using has access as under:

1. On the database that I want to fetch data from.
2. Access in msdb - dtsoperator, dtsadmin, dtsltduser, SQLAgentOperatorRole, SQLAgentReaderRole, SQLAgentUserRole
3. The services are running on this account as well.
4. Log on as batch job, Log on as Service.


But, when I run the job, it fails with the below error.


Message
Executed as user: *** . The process could not be created for step 1 of job 0xEC1F800AD7CF2546A2DD58B2365D7D48 (reason: A required privilege is not held by the client). The step failed.


I have searched even in this forum, but could not get a satisfactory answer. Please help.

View 3 Replies View Related

XML Source And Proxy

Oct 8, 2007

Good day
I'm still kinda new at this SSIS thing so pardon my ignorance.
My question has to do with the XML Data Flow source and the XML Connection. The former does not have proxy properties while the latter does.
Thus trying to connect to a RSS feed using the XML Data Flow source does not work as it has no proxy information.
Is there a work around? Or possibly some other way besides downloading the XML source file?
Thanks

View 4 Replies View Related

Proxy Account.

May 8, 2007

Hi Experts,



Is it possible to connect to SQL Server just using the SQL server agent's proxy account and access data ( without SQL management studio or SQL / Window authentication ). The proxy account is active only for SSIS package execution subsystem.



Thanks in advance,



DBLearner.

View 1 Replies View Related

Error On SET Proxy Account

Aug 3, 2005

I'm trying to set a proxy account for the SQL agent. The user is Local
administrator on the SQL Server when I try to set the account I get a message back that says
"The system cannot find the path specified."
I get the same error with TSQL too.

EXEC master..xp_sqlagent_proxy_account
'SET', N'MY_DOMAIN', N'Myadm', N'MyPassword'

My system :
Windows Server 2003 SP1
SQL Server 2000 SP4

I am worried it might be interfering with someing.
Any ideas what paths it could be after?

View 5 Replies View Related

DTS Package - FTP Download Thru Proxy

Jan 9, 2006

Hi,

I'm trying to set up an FTP process in a DTS package to download a file from an external site. There is nowhere to configure an HTTP proxy. It is getting blocked. I do have the internet options set up correctly but I guess it does not use them.

How do I get around this?

Thanks

View 2 Replies View Related

Xp_cmdshell From IIS: Proxy Not Working

Oct 3, 2007

I have a procedure which prepares a csv file on demand using xp_cmdshell to invoke bcp.

It works fine in sql server. In fact, I have setup a proxy account to run as the domain administrator so it should even work for limited sql server accounts.

When IIS 6.0 attempts to run the procedure, however, I get "xp_cmdshell failed to execute because current security context is not sysadmin and proxy acount is not setup correctly."

For some reason, IIS 6.0 is not able to assume proxy privileges.

Recently, the machine hosting IIS was promoted to a domain controller. Is this causing a problem? My suspicion is that the proxy account has to be a LOCAL user, and since DC's do not have local users, the proxy privileges are useless.

Anybody got any thoughts?

Thanks.

View 9 Replies View Related

SQL 2012 :: Proxy Account Not Being Used

Jan 14, 2015

I have a frustrating problem where I am using the Ola Hallengren jobs to backup to a network share. (This isn't something specific to his scripts).

For various reasons the SQL Server account can not be granted access to the share so I thought I would use a proxy account which does have access (this has been fully tested). I am using a CmdExec proxy.

The problem comes now that when I run the job it still thinks access is denied when running the xp_create_subdir command.

When I recreated this problem locally on my machine, as soon as I add the SQL Server account access to the share the backups work, so why isn't the job using the proxy account?

View 1 Replies View Related

Question: Sun-developed SQL 'proxy'

Jul 26, 2005

Hey, all...Some time ago, I used a tool which I believe was available from Sun. Itwas a java applet, as I recall, which sat between a SQL client and aSQL server. It allowed the client to connect to it at any port, andwould in turn connect to the server at the standard TCP port (orwhatever the server was listening on).It logged all SQL traffic between the two nodes to a flat file.Has anyone ever heard of this tool? For the life of me I can't rememberwhat it was called.Thanks!BD

View 2 Replies View Related

Creating A Proxy Account

Oct 30, 2006

I am trying to run SSIS packages under SQL Server Agent 2005 and I keep getting a package failed error in the event viewer.

I've heard that I need to set up a proxy account. I have found the following code and need a little explanation on what all the parts mean since I am very new to this:
Use master
CREATE CREDENTIAL [MyCredential] WITH IDENTITY = 'yourdomainmyWindowAccount', secret = 'WindowLoginPassword'
Use msdb
Sp_add_proxy @proxy_name='MyProxy', @credential_name='MyCredential'
Sp_grant_login_to_proxy @login_name=' devlogin', @proxy_name='MyProxy'
Sp_grant_proxy_to_subsystem @proxy_name='MyProxy', @subsystem_name='SSIS'

Let's say for the sake of argument my domain is called CompanyInc and I log into windows with my name Philip_Jaques and my password is badpassw0rd. Would I modify the above code this way to create my proxy?

Use master
CREATE CREDENTIAL [MyCredential] WITH IDENTITY = 'CompanyIncPhilip_Jaques', secret = 'badpassw0rd'
Use msdb
Sp_add_proxy @proxy_name='MyProxy', @credential_name='MyCredential'
Sp_grant_login_to_proxy @login_name='Philip_Jaques', @proxy_name='MyProxy'
Sp_grant_proxy_to_subsystem @proxy_name='MyProxy', @subsystem_name='SSIS'

Also, when I create this proxy account where in SQL Server 2005 can I go to view it and its properties? And assuming I get the proxy account set up correctly, how do I get my current jobs to start using it so they will successfully run?

Thanks in advance for your help and advice!

View 2 Replies View Related

Proxy Account/Credential

Feb 14, 2008

There is one thing that€™s confusing me in creating a proxy account.

I am trying to get an SSIS package configured as a SQL Server job and execute it from a non-sysadmin login. But when I execute it gives the error message:

Non-SysAdmins have been denied permission to run DTS Execution job steps without a proxy account. The step failed.

I know that we have to create a proxy account for this to happen and creating of proxy account prompts me to choose a credential, and that is where I do not understand the logic. From MS website I can find the following, but it is confusing to me

This proxy account must use a credential that lets SQL Server Agent run the job as the account that created the package or as an account that has the required permissions.


ref: http://support.microsoft.com/default.aspx?scid=kb;EN-US;918760


I tried reading all the related articles, but still the process of creating the credential is confusing to me, can someone throw some light on the logic of proxy/credential here?



Thanks
Satya

View 23 Replies View Related

Proxy Rs 2005 - How To Use The ReportViewerWebControl.axd?

Mar 2, 2006

We have a reverse proxy for rs 2000 -> a client requests a report, it (the proxy) then goes out to the rs box, gets the report, encrypts any return urls and feeds the modified html to the requesting client. I understand this isn't necessary anymore with rs 2005 due to the architecture. Question is, when I use the ReportExecutionService.Render method it is still returning the parameters for the report, and not the ReportSession, ControlID, Controller, etc. parameters which hides the actual return values on the href links of the report.

Documentation is plentiful for rs 2005, but examples are not. Can someone please explain to me if using the new features in rs 2005 to hide the parameter values from the users is possible via web request? Making the parameter values completely and entirely (even via sniffer) is absolutely a must (which is why we are currently encrypting return URL's).

My code:

ReportExecutionService rs = new ReportExecutionService();
rs.Credentials = System.Net.CredentialCache.DefaultCredentials;
ParameterValue[] pvValues = null;
DataSourceCredentials[] credCredentials = null;
ReportParameter[] rptparamRequiredParams = null;
ParameterValue[] pvReportParameters = null;
ExecutionHeader execHeader = null;
ExecutionInfo execInfo = null;
rptparamRequiredParams = null;
string sHistoryID = null;

{fill parameters block}

rs.SetExecutionParameters (pvReportParameters, "en-us");

try
{
string extension;
string encoding;
string mimeType;
Warning[] warnings = null;
string[] streamIDs = null;
byte[] result = rs.Render (sFormat, sDeviceSettings, out extension, out mimeType, out encoding, out warnings, out streamIDs);
string d = System.Text.Encoding.ASCII.GetString(result, 0, result.Length);
HttpContext.Current.Response.Write (d);
}
catch
{
// do stuff
}

My code is returning:
http://henneseyjm1/ReportServer$sql2005?%2fJH.RSReporting%2fBAG&cy_start_date=1%2f1%2f2006&cy_end_date=3%2f1%2f2006&region=RG20&entity_num=nothing&proc_ctr=nothing&office_num=nothing&render_format=htm&view_name=standard&group_id=0&server_name=http%3a%2f%2flocalhost%2fJHnet%2f&user_is_office=False&rs%3aParameterLanguage=&rc%3aParameters=Collapsed&rc%3aToolbar=False

Where I would like it to return:
http://localhost/Reports$sql2005/Reserved.ReportViewerWebControl.axd?ReportSession=iyvsxg45vhzwd2acii3jj4q4&ControlID=de367546-919a-4f67-be4d-cd2747166dca&Culture=1033&UICulture=9&ReportStack=1&OpType=ReportArea&Controller=ClientControllerctl161&PageNumber=1&ZoomMode=Percent&ZoomPct=100&ReloadDocMap=true&EnableFindNext=False&LinkTarget=_top

View 1 Replies View Related

Cannot Use Credentials For Proxy Account

Jul 31, 2006

Hi,

because my package does not run with SQL-Server-Agent, but without problems if started by "hand", I created a new credential which contains the information needed for the package. I did this as described on: http://msdn2.microsoft.com/en-us/library/ms190703.aspx .

After that i tried to create an proxy account, but when I chose the created credential, Management Studio says "Der Proxy "[name_of_credential] ist kein gĂĽltiger Windows-Benutzer(Microsoft SQL Server, Fehler: 14529)". This means something like: "This Proxy is not a valid windows-user. Error: 14529".

Any hints how to use a credential that is not a windows-user?

Regards,

Jan Wagner

View 7 Replies View Related

Principal To Proxy Problem

Aug 8, 2007

I can successfully execute my package via Business Studio but when I schedule it in SQL Agent I get the error message, 'could not get proxy data for proxy id = 2.' I am trying to execute the scheduled job with that proxy (call it abcd_proxy) because I have a logon id (call it abcd) with access to a specific network drive folder, which holds a required source flat file. The abcd logon is defined as a sysadmin account. I am unable to see that the abcd logon id is an added principal within the abcd_proxy, which I think is because the abcd logon principal has a sysadmin role. My proxy id = 2 definition looks to be defined the same way that my first proxy id was.

Does anyone have an idea about what the message means and how I can fix it?

View 1 Replies View Related

Proxy 2005 - A Little Help Needed...

Mar 8, 2006

As posted previously, thank you in advance...
--------------------------------------------

We have a reverse proxy for rs 2000 -> a client requests a report, it (the proxy) then goes out to the rs box, gets the report, encrypts any return urls and feeds the modified html to the requesting client. I understand this isn't necessary anymore with rs 2005 due to the architecture. Question is, when I use the ReportExecutionService.Render method it is still returning the parameters for the report, and not the ReportSession, ControlID, Controller, etc. parameters which hides the actual return values on the href links of the report.

Documentation is plentiful for rs 2005, but examples are not. Can someone please explain to me if using the new features in rs 2005 to hide the parameter values from the users is possible via web request? Making the parameter values completely and entirely (even via sniffer) is absolutely a must (which is why we are currently encrypting return URL's).

My code:

ReportExecutionService rs = new ReportExecutionService();
rs.Credentials = System.Net.CredentialCache.DefaultCredentials;
ParameterValue[] pvValues = null;
DataSourceCredentials[] credCredentials = null;
ReportParameter[] rptparamRequiredParams = null;
ParameterValue[] pvReportParameters = null;
ExecutionHeader execHeader = null;
ExecutionInfo execInfo = null;
rptparamRequiredParams = null;
string sHistoryID = null;

{fill parameters block}

rs.SetExecutionParameters (pvReportParameters, "en-us");

try
{
string extension;
string encoding;
string mimeType;
Warning[] warnings = null;
string[] streamIDs = null;
byte[] result = rs.Render (sFormat, sDeviceSettings, out extension, out mimeType, out encoding, out warnings, out streamIDs);
string d = System.Text.Encoding.ASCII.GetString(result, 0, result.Length);
HttpContext.Current.Response.Write (d);
}
catch
{
// do stuff
}

My code is returning:
http://henneseyjm1/ReportServer$sql2005?%2fJH.RSReporting%2fBAG&cy_start_date=1%2f1%2f2006&cy_end_date=3%2f1%2f2006&region=RG20&entity_num=nothing&proc_ctr=nothing&office_num=nothing&render_format=htm&view_name=standard&group_id=0&server_name=http%3a%2f%2flocalhost%2fJHnet%2f&user_is_office=False&rs%3aParameterLanguage=&rc%3aParameters=Collapsed&rc%3aToolbar=False

Where I would like it to return:
http://localhost/Reports$sql2005/Reserved.ReportViewerWebControl.axd?ReportSession=iyvsxg45vhzwd2acii3jj4q4&ControlID=de367546-919a-4f67-be4d-cd2747166dca&Culture=1033&UICulture=9&ReportStack=1&OpType=ReportArea&Controller=ClientControllerctl161&PageNumber=1&ZoomMode=Percent&ZoomPct=100&ReloadDocMap=true&EnableFindNext=False&LinkTarget=_top

View 1 Replies View Related

Proxy Account Not Responding

Feb 15, 2006

Hi,

I have an SSISS package running in a job step, the job is owned and has to be run by a non-sysdamin SQL login. I have created a new credential (windows autrhentication, sysadmin priviledges) , mapped it to proxies 'SSISS' and 'Operating systems (CmdExec)' and have assigned the job step to run as that credential. Yet I'm getting the following error message:

Unable to start execution of step 1 (reason: Error authenticating proxy DomainUserName, system error: Logon failure: unknown user name or bad password.). The step failed.

Does anyone know why this is?

Thanks

View 4 Replies View Related

Proxy Account - SQL Server

Jan 2, 2008

Hello,
I'm having trouble setting up PROXY account. I follow the documentation, and Under Credentials, I can only select Operator. Is there a way to select any account under Security?

Your help is appreciated!

View 3 Replies View Related

Proxy Account Security.

Apr 26, 2007



Hi experts,



Is there any potential security threat using Proxy accounts in SQL Server 2005 ? If any , Please give URLs for reference.



Thanks,

DBLearner

View 3 Replies View Related

Support Of Proxy Tables

Aug 31, 2007

Does SQL Server 2005 support the creation of proxy tables? I have been working with Sybase ASE 12.5.

Thanks in advance.

View 1 Replies View Related

Proxy Authentication Required

Apr 6, 2007

I have sql server 2005 analysis services insatalled on workstation when I try to deploy a report to the reportserver I get the following error msg.

The workstation and server are on a company network.

I dont have any problem when I create reports on one of the other development servers and deploy to the same reportserver.

I have seen quite a few other threads on this none of which had a solution

===================================

A connection could not be made to the report server http://sqldev2/ReportServer. (Microsoft Report Designer)

===================================

The request failed with HTTP status 407: Proxy Authentication Required. (Microsoft.ReportingServices.Designer)

------------------------------
Program Location:

at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String Item)
at Microsoft.ReportDesigner.Project.ReportServiceClient.GetItemType(String item)
at Microsoft.ReportDesigner.Project.ReportServiceClient.CheckAuthorized()
at Microsoft.ReportDesigner.Project.ReportClientManager.GetCredentials(String url)
at Microsoft.ReportDesigner.Project.ReportProjectDeployer.PrepareDeploy()

View 3 Replies View Related

Snapshot Agent && Log Reader Agent Will Not Start.

Nov 30, 2006

Hi All,

I would appreciate any help here at all. I am pulling my hair out!

I am unable to start the snapshot agent or log reader agent from within SQL management studio. it fails on executing step 2 with unknown username or bad password.

I have checked all account details and they are correctly using my domain admin account. I can connect to SQL using teh same account and it also has sysadmin permissions.

If i copy the step 2 paramters and start from the cmd prompt (again logged in using the same domain account) they both start fine.



Any ideas would be gratefully received.

View 1 Replies View Related

Cannot Start Log Reader Agent And Snapshot Agent

May 18, 2007

I am testing peer to peer replication in our environment. I simulated a three node peer to peer topology and a local distributor.

For some wierd reason I cannot get the Log Reader Agent and snapshot agent to start. The domain account under which SQL Server Agent runs has administrator previlage on the box. I also use a domain account for SQL Server Service. (none of the passwords changed).

This is the error I am getting - "Executed as user: abc. A required privilege is not held by the client. The step failed"

Any ideas???





Also this domain account is a member of



SQLServer2005MSSQLUsers$ServerName$MSSQLSERVER

SQLServer2005MSAgentUser$ServerName$MSSQLSERVER


View 3 Replies View Related

SQL Server Agent Could Not Access Replication Agent

Feb 19, 2007

We just moved source server to newer, bigger box ... Windows 2003 and Active Directory ... Snapshot agent worked but distribution failed ... Same login as on older machine, login is sysadm, used DCOMCNFG to allow ability to launch process ... What are we missing?

View 4 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved