Forums  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Member List  Search  FAQ  Ticket List  Log Out

 

Database Stopped, But Isn't

 
Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [Networking & Security] >> GFI EventsManager >> Database Stopped, But Isn't Page: [1]
Login
Message << Older Topic   Newer Topic >>
Database Stopped, But Isn't - 9.Sep.2009 9:39:37 AM   
richlich

 

Posts: 7
Score: 0
Joined: 1.Sep.2009
Status: offline
1. New to EventsManager
2. Version 8.0
3. Management console claims database is stopped; however, checking the database server where the EventsManager database is located shows SQL Server is running and the database is available.

So, what are we missing here?

Many thanks in advance for your help!
Post #: 1
RE: Database Stopped, But Isn't - 9.Sep.2009 10:49:44 AM   
DrewE

 

Posts: 1246
Score: 0
Joined: 28.Apr.2008
From: Cary, NC
Status: offline
From the GFI EventsManager configuration, locate the database name - Add a space to the database name, then immediately remove the space and click apply.

_____________________________

Drew Easley
GFI Software
Talk Tech To Me (GFI Blog)Follow Us (Twitter) - Watch Us (YouTube) - Join us (Facebook)

(in reply to richlich)
Post #: 2
RE: Database Stopped, But Isn't - 21.Sep.2009 10:49:59 AM   
richlich

 

Posts: 7
Score: 0
Joined: 1.Sep.2009
Status: offline
Drew,

Sorry for the delayed thank you, but thank you!

(in reply to richlich)
Post #: 3
RE: Database Stopped, But Isn't - 5.Oct.2009 7:19:02 AM   
imatone

 

Posts: 204
Score: 0
Joined: 6.Aug.2007
Status: offline
So, what was the problem? Has this issue been resolved in the current build of ESM?

We are also experiencing similar issue. Our ESM would stop collecting SQL events but after a manual process by going to Configuration -> Event Sources -> Group Type: (Database Servers Groups) select “SQL Server group” and select the custom define group and then click “disable” and “enable” the capture function, the collection resumed.

All other ESM activities are behaving normally. That's is our ESM has no issue collecting events from DC, File, Exchange etc. Only SQL server events and we are using SQL 2005 standard edition w/ Windows authentication. Tks!

(in reply to richlich)
Post #: 4
RE: Database Stopped, But Isn't - 5.Oct.2009 8:17:49 AM   
DrewE

 

Posts: 1246
Score: 0
Joined: 28.Apr.2008
From: Cary, NC
Status: offline
Imatone,

Do you perhaps have anything that is backing up the SQL database nightly or weekly? Sometimes, if you do a restart of the GFI EventsManager Service is necessary after the backup is completed.

_____________________________

Drew Easley
GFI Software
Talk Tech To Me (GFI Blog)Follow Us (Twitter) - Watch Us (YouTube) - Join us (Facebook)

(in reply to imatone)
Post #: 5
RE: Database Stopped, But Isn't - 5.Oct.2009 10:12:23 AM   
richlich

 

Posts: 7
Score: 0
Joined: 1.Sep.2009
Status: offline
Turns out my predecessor had GFI pointing to the wrong SQL Server instance! Once that was corrected, everything has been going fine.

(in reply to DrewE)
Post #: 6
RE: Database Stopped, But Isn't - 15.Oct.2009 1:37:40 AM   
imatone

 

Posts: 204
Score: 0
Joined: 6.Aug.2007
Status: offline
The problem is this issue is happening sporadically. There are 2 SQL 2005 servers involved and they are using different authentication methods (Windoes & Mixed mode) but one of the common factors is both SQL servers are being backup daily/weekly by Symantec BEWS SQL agent. The strange thing is it doesn't happen all the time and this issue is only happening for the SQL event collection but not for other servers such as DC, file, Exchange etc. To complicate the issue, we couldn't reproduce it in our Test Lab & the event logs reveal little or no info. The present workaround is to manually disable & enable the SQL collection inside the EventsMan console. Restarting the EventsMan service is the last resort cuz that could affect other event collections for other business critical servers during the a few seconds.

(in reply to DrewE)
Post #: 7
RE: Database Stopped, But Isn't - 16.Oct.2009 11:20:09 AM   
DrewE

 

Posts: 1246
Score: 0
Joined: 28.Apr.2008
From: Cary, NC
Status: offline
We will need to further investigate this - Can you open a support request online at: http://support.gfi.com/Support/support.aspx?lcode=en

_____________________________

Drew Easley
GFI Software
Talk Tech To Me (GFI Blog)Follow Us (Twitter) - Watch Us (YouTube) - Join us (Facebook)

(in reply to imatone)
Post #: 8
RE: Database Stopped, But Isn't - 16.Nov.2009 2:54:01 PM   
dpattillo@centurymar

 

Posts: 8
Score: 0
Joined: 7.Oct.2009
Status: offline
Did you ever get a fix for this one? We seem to be having the same problem.

Dwain

(in reply to imatone)
Post #: 9
RE: Database Stopped, But Isn't - 24.Nov.2009 5:37:12 PM   
miniman

 

Posts: 4
Score: 0
Joined: 16.Oct.2009
Status: offline
I experienced this issue and found I needed to give the windows logon account read access to the Events database, it appears the Console database status is not checked under the service account credentials.

(in reply to dpattillo@centurymar)
Post #: 10
Page:   [1]
All Forums >> [Networking & Security] >> GFI EventsManager >> Database Stopped, But Isn't Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts