25 September 2012

Alfresco on Windows Server 2008 R2 causing error 'no buffer space available'

On a Windows Server 2008 R2 x64 SP1 with Alfresco installed we were getting the following errors in a loop :
"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"
"no buffer space available"
"No buffer space available (maximum connections reached?)"
 Simply installing this hotfix should do the trick

#1

14 September 2012

Error in Analysis Services : The system is out of memory (Event ID 2)

If Analysis Services is repeatedly crashing with the following error on a Windows Server 2008 R2 x64 running SQL Server R2 x64 SP1 :
1
Log Name:      Application
2
Source:        MSSQLServerOLAPService
3
Date:          6/09/2012 08:58:13
4
Event ID:      2
5
Task Category: (289)
6
Level:         Information
7
Keywords:      Classic
8
User:          N/A
9
Computer:      rto-dwu.effigy.be
10
Description:
11
The system is out of memory.
12
Event Xml:
13
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
14
  <System>
15
    <Provider Name="MSSQLServerOLAPService" />
16
    <EventID Qualifiers="16673">2</EventID>
17
    <Level>4</Level>
18
    <Task>289</Task>
19
    <Keywords>0x80000000000000</Keywords>
20
    <TimeCreated SystemTime="2012-09-06T06:58:13.000000000Z" />
21
    <EventRecordID>332713</EventRecordID>
22
    <Channel>Application</Channel>
23
    <Computer>rto-dwu.effigy.be</Computer>
24
    <Security />
25
  </System>
26
  <EventData>
27
  </EventData>
28
</Event>
You should simply consider to install the SP2 for SQL Server 2008 R2 ;)

This solves an incomprehensible error seeing that the server has 18GB of RAM installed and the data volume is not so huge.

10 September 2012

BSOD : Stop 0x0000006B PROCESS1_INITIALIZATION_FAILED (caused by bootcat.cache)

If you get a BSOD on your Windows 7 system with the following error code : 0x0000006B, the problem could be caused by a corrupted bootcat.cache file (normal file's size is ~6MB and on a corrupted system the file is around ~14kb).
A workaround is to boot on a live system (linux, Windows repair, ...), delete the corrupted bootcat.cache file (in %SystemRoot%\system32\codeintegrity), copy it from a working copy (downloaded from internet, taken from a healthy system, ...) and reboot your computer on Windows session.
Once logged in as an administrator, edit asap the bootcat.cache's properties (if the file size is already around 14kb, you have to restart the procedure) and set the file as readonly.

This should do the trick...

#1 #2

03 September 2012

Fix Resource Monitor not working after installing DSM 4.1

Seems to be a problem linked to the ipkg's package net-snmp.
Simply remove it, reboot and the problem should be fixed.
(You may have to remove some dependencies if asked for)
> ipkg remove ntop
> ipkg remove net-snmp

#1