Discussion Forums/AA Console/Questions
Answered
AA crashes while syncing to AD
Adam Ruth
asked this on November 13, 2009 12:13
As the subject implies, my AA 1.3 keeps crashing on me when it tries to do an AD sync. We recently dumped a lot of old computer accounts out of AD and I wanted to make sure my AA DB reflected it. I did a manual sync to AD, and it started counting up the number of computers, but when it reaches the end of the count, it tells me that AA generated an error and was shut down. It seems to want to do this every time I start AA now. Any thoughts?
Comments
Will you send a screenshot of the error (or an copied entry from the Event Log)? Thanks.
Also, what OS is Admin Arsenal running on?
I'm running on XP Pro.
Here are a few erros frm the event log that are around the same time I remember the crashes happening:
EventType clr20r3, P1 adminarsenal.exe, P2 1.3.1.22, P3 48211f19, P4 brisworks.adminarsenal, P5 1.3.1.22, P6 48211f17, P7 277, P8 0, P9 zn3vdw052s3za2ekd15ififh2igd5s3v, P10 NIL.
Timeout waiting to connect to database.
at Brisworks.AdminArsenal.Database.QueryScalar(String sql, Object[] parameters)
at Brisworks.AdminArsenal.ScanSettings.get_AutoEnabled()
at Brisworks.AdminArsenal.BackgroundWorker.ScanProcess.Read()
Brisworks.AdminArsenal.Exceptions.DatabaseConnectionException
Unexpected error during monitor process: Timeout waiting to connect to database.
Brisworks.AdminArsenal.Exceptions.DatabaseConnectionException
at Brisworks.AdminArsenal.Database.Query(String sql, Object[] parameters)
at Brisworks.AdminArsenal.Monitor.GetAllIDs()
at Brisworks.AdminArsenal.Monitor.OpenAll()
at Brisworks.AdminArsenal.BackgroundWorker.MonitorProcessor.Read()
At the moment I'm able to start AA and run scans with it. I'll try another sync and see what happens.
Now it ran a sync without crashing. I still have errors like the ones I posted in my event log, but the program stayed up and it reduced the number of computers to where it should be.
Thank you for bringing this to our attention. We have found the source of the problem and it will be fixed in version 1.4.