Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
- From: "Fred" <me@xxxxxx>
- Date: Tue, 4 Apr 2006 22:59:53 +0100
Hi... (sorry for posting to multiple groups but not really sure where to
post this one)
I'm not a SQL DB by any means and recently played around with some perms in
the DCOMCNFG tool. Basically a push replication job was timing out when
trying to push content from one SQL server to a cluster server. I tested
connectivity with ping and telnet and had no problems. Also this replication
has worked for ages up until recently. I tried increasing the LoginTimeout
parameter in the Run Agent Replication Distributor command line but still
got TimeOut exipred messages when the agent ran - the specific error message
being "Timeout expired (Source: ODBC SQL Server Driver (ODBC); Error number:
S1T00)". I then tried to add some debug logging to the command line for
troubleshooting but this didnt work "-Output
C:\Temp\_sql\OUTPUTFILE.txt -Outputverboselevel 2"
Anyway if i remember correctly i then went into to DCOMCNFG tool and tried
to add/give the local sqlsvc service account the launch right which has now
chnaged the everyone group right to launch when it should be "special
access". My replication agent now fails with:
SQL Server Agent could not access the replication agent. Use the DCOMCNFG
utility to confirm that the SQL Server Agent Windows account has permissions
to launch the replication agent. The step failed.
How do I set the everyone group permission back to "special access" ??? The
only option I have now is Allow or Deny Launch
I have messed up perms on these two agents:
SQL Server Replication Distribution Agent 8.0
SQL Server Replication Merge Agent 8.0
SQL Server Replication Remote Agents don't have the everyone group security
set at all (should these two agents also have "special access set") ?
When i go into set the perms again i get this pop-up window
--------------------------------------------------------------
"The security descriptor contains an access control (ACE) inappropriate to
this context. if you continue it will be rewritten as an allow ACE on the
appropriate access mask. Do you wish to continue?"
I saw these articles on google which relate to my error but cant make the
change as stated in previously
http://groups.google.co.uk/group/microsoft.public.sqlserver.replication/browse_thread/thread/c50821076b7882bd/bc47fe464ecc68f4?lnk=st&q=sql+server+agent+could+not+access+the+replication+agent.+use+the+dcomcnfg+utility+to+confirm+that+the+sql+server+agent+windows+account+has+permissions+to+launch+the+replication+agent.+the+step+failed&rnum=1&hl=en#bc47fe464ecc68f4
Also both SQL servers are members of the same domain yet the cluster uses
the a domain account to run SQL services while the other server uses a local
sqlsvc account to run SQL services. This is the way it was setup before i
got here - should they not use the same account? I thought this was the
recommended setup if using replication between two servers. Anyway, it has
been working with seperate accounts up until now
Thanks for your help
Fred
.
- Prev by Date: endpoint works via localhost/servername not working via IP/external
- Next by Date: create a user who only can execute stores procedures but it can not to view inside of them
- Previous by thread: endpoint works via localhost/servername not working via IP/external
- Next by thread: create a user who only can execute stores procedures but it can not to view inside of them
- Index(es):
Relevant Pages
|
