Tags: causes, common, database, distribution, executingexec, initialize, language, level, line, microsoft, mysql, oracle, procedure, quotfailed, runtimequot, saysmsg, server, sp1, sp_browsereplcmds, sp_browsereplcmdssql, sql, standard, state

sp_browsereplcmds causes "Failed to initialize the Common Language Runtime..."

On Database » Microsoft SQL Server

2,046 words with 3 Comments; publish: Sat, 29 Dec 2007 16:42:00 GMT; (25078.13, « »)

When executing

  • exec distribution..sp_browsereplcmds

SQL Server 2005 Standard SP1 says:

  • Msg 6513, Level 16, State 27, Procedure sp_browsereplcmds, Line 110
  • Failed to initialize the Common Language Runtime (CLR) v2.0.50727 due to memory pressure. Please restart SQL server in Address Windowing Extensions (AWE) mode to use CLR integration features.
I have two (nearly) identically machines (test has 2, prod has 4 CPUs), both 3071MB RAM, Win 2k3 Server SP1, both have no AWE running.

On test-machine the procedure works fine, on production in doesn't.

I checked performance. Test machine has about 180MB available memory, production about 160MB (nearly constant). Thread count for process sqlservr is constant and similar at about 65.

Any idea why it runs on test but not on production machine?


All Comments

Leave a comment...

    • Are you running 32bit SQL Server on 64bit Windows by any chance?


      #1; Tue, 04 Sep 2007 18:40:00 GMT
    • Sorry, I forgot to mention this.

      Everything is 32 bit. The machines, the Windows and the SQL Server 2005.

      #2; Tue, 04 Sep 2007 18:41:00 GMT
    • There is the distinct possibility that the virtual address space of the SQL Server process on your production system is simply too fragmented for loading SQLCLR (despite the fact that you have 160MB free). If you haven't done so already, you may want to try specifying /3GB in boot.ini to enable 3GB user-mode address space and see if that resolves the issue. Enabling AWE like the error message suggests may also be a possibility but given that you have less than 4GB of physical memory, I am not sure if that helps (disclaimer: I am no expert in the various tradeoffs of AWE). Given the kind of memory consumption pattern on your servers, you may be better off to simply move to 64bit.


      #3; Tue, 04 Sep 2007 18:42:00 GMT