Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 4717 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Enterprise Console error..

DilanManjula

Hi,

One of our customer have issue with sophos ent. Console(v 4 with windows 2008 Ent 64 bit and SQL Express 2005).the database size has grown up to 4GB. We have installed around 3,500 PC’’’’s via this console in active directory integrated mode. When while working with console we are getting bellow error. And quit from the console. But can open again and can work for a while.

Further I run “C:\>osql -E -S .\sophos -d sophos4 -Q "select count(id) from groups" to count no: of OU’’’’s of AD and output is “941”

 And the details which we entered under “configure E-mail alerts”  in the console also not getting saved. Pls. advice ASAP.

note : having enough free disk space 

“ Could not allocate space for object 'dbo.Threats'.'IX_Threats_Status_ThreatInstanceID' in database 'SOPHOS4' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

----- [outer exception] -----

   -- error: 0x80004005 (Unspecified error)

   -- facility: Generic (System)

   at void __thiscall ResolveAlertsDlg::acknowledgeAlerts(class std::vector<unsigned long,class std::allocator<unsigned long> > &)

   at __w64 long __thiscall ResolveAlertsDlg::OnAcknowledge(unsigned short,unsigned short,struct HWND__ *,int &)

   at 1

   at __w64 long __thiscall CCompListCtrl::OnActionResolveAlertsAndErrors(unsigned short,unsigned short,struct HWND__ *,int &)

   at int __cdecl Run(int,enum bl::ConsoleType::Type)

   at int __stdcall wWinMain(struct HINSTANCE__ *,struct HINSTANCE__ *,wchar_t *,int) “

:1151


This thread was automatically locked due to age.
Parents
  • 0

    I am not savvy with the administration of a SQL Server Express without the full tools which come with a standard SQL Server edition.

    However, it's possible that the "autoshrink" flag for the database has not been set. In this case, the db will not reclaim the wasted space from deleted entries in a table. You might want to check this. If you have access to the full management tools for SQL Server 2005 or above, this can be seen in the gui. I don't know how to alter the flag from OSQL, though.

    Another approach - if this is your current problem - would be to manually execute a shrink-command with OSQL. Instructions for this command can be found here:

    http://msdn.microsoft.com/de-de/library/ms190488%28SQL.90%29.aspx

    Another approach: Your database might theoretically be blown to 4GB with old alerts. I do not think so because 3500 clients should not create anywhere near this amount of alerts, and the Console is set to remove old alerts after a specific time. You might want to check the configuration of "Reporting" - there is an option to delete old Alerts after x months. You can set this to"don't delete old alerts" which causes the database to grow, but in any case 3500 clients should not generate enough alerts to fill 4GB. Our current database for 7.000 clients with 3 months of alerts is 155MB database and 123MB transaction log.

    Best regards,

    Detlev

    :1206
Reply
  • 0

    I am not savvy with the administration of a SQL Server Express without the full tools which come with a standard SQL Server edition.

    However, it's possible that the "autoshrink" flag for the database has not been set. In this case, the db will not reclaim the wasted space from deleted entries in a table. You might want to check this. If you have access to the full management tools for SQL Server 2005 or above, this can be seen in the gui. I don't know how to alter the flag from OSQL, though.

    Another approach - if this is your current problem - would be to manually execute a shrink-command with OSQL. Instructions for this command can be found here:

    http://msdn.microsoft.com/de-de/library/ms190488%28SQL.90%29.aspx

    Another approach: Your database might theoretically be blown to 4GB with old alerts. I do not think so because 3500 clients should not create anywhere near this amount of alerts, and the Console is set to remove old alerts after a specific time. You might want to check the configuration of "Reporting" - there is an option to delete old Alerts after x months. You can set this to"don't delete old alerts" which causes the database to grow, but in any case 3500 clients should not generate enough alerts to fill 4GB. Our current database for 7.000 clients with 3 months of alerts is 155MB database and 123MB transaction log.

    Best regards,

    Detlev

    :1206
Children
No Data