Hi David,
I enabled CR logger also and ran a report. What I see in my log at the end is this
2015-11-23-11-29-33 13200 .\QERowset.cpp 3137 Beginning CQERowset::fetchColumnValue 20
2015-11-23-11-29-33 13200 .\QERowset.cpp 3249 Finishing CQERowset::fetchColumnValue 20
2015-11-23-11-29-33 13200 .\QERowset.cpp 1441 Beginning CQERowset::readNextRecord 20
2015-11-23-11-29-33 13200 .\QERowset.cpp 1576 Beginning CQERowset::_readNextRecord 20
2015-11-23-11-29-33 13200 .\QERowset.cpp 1840 Finishing CQERowset::_readNextRecord <no more records> 20
2015-11-23-11-29-33 13200 .\QERowset.cpp 1565 Finishing CQERowset::readNextRecord 20
2015-11-23-11-29-45 13200 .\qecommon.cpp 117 File Name: ".\QEQueryInfo.cpp". Line: 826 1
2015-11-23-11-29-45 13200 .\qecommon.cpp 117 File Name: ".\QEQueryInfo.cpp". Line: 854 1
2015-11-23-11-29-45 13200 .\qecommon.cpp 117 File Name: ".\QEQueryInfo.cpp". Line: 826 1
2015-11-23-11-29-45 13200 .\qecommon.cpp 117 File Name: ".\QEQueryInfo.cpp". Line: 826 1
2015-11-23-11-29-45 13200 .\qecommon.cpp 117 File Name: ".\QEQueryInfo.cpp". Line: 854 1
2015-11-23-11-29-47 13200 ..\..\src\print\format\imageretriever.cpp 905 Destroy API called. Image Retriever was not used. No cleanup necessary. 20
As you can see the logs show the connection being cleaned up... You log just stopped while reading data. So I think there is something Server Side blocking accessing more rows or the registry key.
ProcessMonitor should show you the key not being read or access denied...
Don