Re: SQL Agent Non SysAdmin Job Proxy User Account

Tech-Archive recommends: Fix windows errors by optimizing your registry


Andy Haberer <AndyHaberer@xxxxxxxxxxxxxxxxxxxxxxxxx> schrieb ...
Hi Elmar,
meinst Du das Konto, unter dem der SQL Agent läuft muss
Administrationsrechte auf dem lokalen System haben?

Lies:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_xp_aa-sz_8sdm.asp

"The SQL Server service for that instance must be running under a
Windows administrator account to read or set the SQL Server Agent
proxy account."

oder in Deiner aktualisiertenten deutschen SQL Server Dokumenation,
stände da:
"Der SQL Server-Dienst für die betreffende Instanz muss unter einem
Windows-Administratorkonto ausgeführt werden, um das Proxykonto
von SQL Server-Agent zu lesen oder festzulegen"

meines Wissens, muss dann die Datenbank auf
die ich dieses Statement absetze dem 'sa' gehören...

Wiederholt: Nein.

Der Fehler tritt ja schon auf, wenn ich versuche den User zu
speichern...aber eben seltsamerweise nur unter SP4 und W2K3...

hier läuft W2K3 + 2000 SP4 ohne Probleme.


.

Relevant Pages

  • Re: Outlook for MAPI on SBS
    ... I wound up looking at another thread here on installing SQL 2005 which I ... I have noticed something interesting here in SBS ... agent from the SBS Monitoring Agent to the 2005 agent instance. ... Is there an easy way to set up notifications from SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook for MAPI on SBS
    ... I wound up looking at another thread here on installing SQL 2005 which I ... particularly 2005 on SBS. ... agent from the SBS Monitoring Agent to the 2005 agent instance. ... Is there an easy way to set up notifications from SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
    ... trying to push content from one SQL server to a cluster server. ... Also this replication ... got TimeOut exipred messages when the agent ran - the specific error message ... SQL Server Agent could not access the replication agent. ...
    (microsoft.public.sqlserver.replication)
  • Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
    ... trying to push content from one SQL server to a cluster server. ... Also this replication ... got TimeOut exipred messages when the agent ran - the specific error message ... SQL Server Agent could not access the replication agent. ...
    (microsoft.public.sqlserver.connect)