Note that enabling this should not affect performance of either the web services component on the RE web server or the RE client for any of your users at all. But, the most important thing to know is that this logging is local only to the machine where we make the edit below. So we need to make sure and apply the change below on the machine of the user most likely to run into the issue. Here is how to enable logging:
  1. Create a directory/folder on the machine  for the trace file to be placed (example:  C:\trace)
  2. Edit this RE config file located at C:\Program Files (x86)\Blackbaud\The Raisers Edge 7\RE7.exe.config
  3. Anywhere within the <Configuration> node in that file, add the following lines of code (with the location of your directory) and save the file
     <appSettings>
         <add key="TraceDir" value="C:\trace" />
    </appSettings>
    <system.diagnostics>
       <switches>
          <add name="FunctionTraceSwitch" value="4" />
       </switches>
    </system.diagnostics>

EXAMPLE should look like this:
 
<?xml version="1.0"?>
<configuration> 
    <startup>
        <supportedRuntime version="v2.0.50727" />
    </startup>
    <runtime> 
       <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> 
          <probing privatePath="WSE" /> 
       </assemblyBinding> 
    </runtime>
    <appSettings>
         <add key="TraceDir" value="C:\trace" />
    </appSettings>
    <system.diagnostics>
       <switches>
          <add name="FunctionTraceSwitch" value="4" />
       </switches>
    </system.diagnostics>
</configuration> 
 
     4. Launch Raiser's Edge and access the NetCommunity plugin. After this, you should see a file created in the trace directory (EX: ShelbyTrace_1_63_20130516.log)

NOTE: When a crash happens, your Raiser's Edge users will have to *NOT* shut RE down until after you’ve saved a copy of the log file; otherwise we will lose relevant details that won’t get logged. Save that file and send a copy to Blackbaud NetCommunity support analyst