In a development environment,
developers are logged into CorpDomain on workstations joined to CorpDomain,
running Windows XP SP2,
they use Enterprise Manager to connect to SQL 2000 databases using SQL logins,
on various member servers belonging to DevDomain, running Windows Server
2003 SP2 and SQL 2000 Enterprise SP4.
There is no trust between the two domains.
Whenever such a developer has Enterprise Manager open, each connected
registration results in Failure Audit events 529 and 680 in the Security Log
of the server hosting that database, once every second.
Every disconnected registration results in the same errors, once every 10
seconds.
Needless to say, with 50 developers, each working with a large number of
servers, the security logs fill up quickly. The connections work fine, they
just create thousands of event log entries per hour on every server.
Is there a configuration on the servers, clients, network, or some
combination thereof that will prevent these login failures on the servers?
(The failure audit logging is required by corporate policy and cannot be
turned off.)
Thanks,
Tim C
MCSE
Roy Harvey (SQL Server MVP) - 28 Feb 2008 23:01 GMT
The first thing I would try is at the client end, in Enterprise
manager. Right click the server and Edit SQL Server Registration
properties... then be sure to UNcheck "Display SQL Server state in
console" and "Automatically start SQL Server when connecting".
Roy Harvey
Beacon Falls, CT
>In a development environment,
>developers are logged into CorpDomain on workstations joined to CorpDomain,
[quoted text clipped - 22 lines]
>Tim C
>MCSE