Earlier, I posted a solution for the Scribe error – defined maximum memory usage (300 MB) exceeded. The solution involves increasing the maximum memory usage setting for Scribe by adding a couple of registry keys.
Later, we received the same error on our Scribe Production server running on Windows Server 2008 R2 64-bit version. Since, we were running the 32-bit version of Scribe, we could not use the default 64-bit Registry editor (that runs when you fire the command regedit.exe) to add the required keys. The 64-bit Registry editor displays the 32-bit entries under the
Wow6432Node sub-key. The
HKEY_LOCAL_MACHINE\SOFTWARE 32-bit sub-key can be found under
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node on the 64-bit registry editor. There was a process of Registry Reflection in use till Windows Server 2008, but it has been deprecated in Windows 7 and Windows Server 2008 R2. Reflection involved copying registry keys between the two (32-bit and 64-bit) views, creating two separate physical copies. Windows 7 and Windows Server 2008 R2 share the same copy, instead of using reflection.
The 32-bit registry editor can also be used to manage 32-bit registry keys. It can be run by going to Start -> Run and entering
%systemroot%\syswow64\regedit and clicking OK. For more details, visit this link.
A better solution, in our case, was to use the 64-bit version of Scribe Insight.