Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / February 2008

Tip: Looking for answers? Try searching our database.

Security Failure Audit events with Enterprise Manager

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tim C - 28 Feb 2008 20:37 GMT
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
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.