Document summary too long, couldn't unpack
-
Tuesday, January 25, 2011 9:55 AM
Hi All,
Just joined the community and wishing to have a great stay. Hope all are fine :)
We are currently using ESP 5.2 and are seeing a ERROR in our logs often, which is,
" ERROR fdispatch Document summary too long, couldn't unpack"
Any idea or anyone who experienced this before?
Regards,
freddieMaize
Answers
-
Tuesday, January 25, 2011 9:29 PMModerator
Hi and welcome freddieMaize!
The “Document summary too short, couldn't unpack” error generally occurs when an index-profile change has been made, but not all nodes received the update properly. Usually either search is using the wrong docsum or the qrserver is expecting the wrong docsum.
There are a couple of methods one can use to address this situation:
Method 1) Sometimes one can update the index profile again via a cold update, and the update completes.Method 2) One can also perform the below steps without performing a cold update, and this will often resolve the issue:
A - Stop the QRserver: nctrl stop qrserver
delete var/qrserver/webcluster/15100/cache_cs (on the same node),
Restart the QRserver: nctrl start qrserverB - Stop search: nctrl stop search-1,
delete var/searchctrl/ (same node)
Restart search: nctrl start search-1This must be done on each node that runs the QRserver and Search components. Let us know your results.
Thanks!
Rob Vazzana | Microsoft | Enterprise Search Group | Senior Support Engineer | http://www.microsoft.com/enterprisesearch
- Proposed As Answer by Rob Va - MSFTMicrosoft Employee, Moderator Tuesday, January 25, 2011 9:29 PM
- Marked As Answer by Thomas MolbachMicrosoft Employee, Owner Tuesday, March 22, 2011 2:29 PM
All Replies
-
Tuesday, January 25, 2011 9:29 PMModerator
Hi and welcome freddieMaize!
The “Document summary too short, couldn't unpack” error generally occurs when an index-profile change has been made, but not all nodes received the update properly. Usually either search is using the wrong docsum or the qrserver is expecting the wrong docsum.
There are a couple of methods one can use to address this situation:
Method 1) Sometimes one can update the index profile again via a cold update, and the update completes.Method 2) One can also perform the below steps without performing a cold update, and this will often resolve the issue:
A - Stop the QRserver: nctrl stop qrserver
delete var/qrserver/webcluster/15100/cache_cs (on the same node),
Restart the QRserver: nctrl start qrserverB - Stop search: nctrl stop search-1,
delete var/searchctrl/ (same node)
Restart search: nctrl start search-1This must be done on each node that runs the QRserver and Search components. Let us know your results.
Thanks!
Rob Vazzana | Microsoft | Enterprise Search Group | Senior Support Engineer | http://www.microsoft.com/enterprisesearch
- Proposed As Answer by Rob Va - MSFTMicrosoft Employee, Moderator Tuesday, January 25, 2011 9:29 PM
- Marked As Answer by Thomas MolbachMicrosoft Employee, Owner Tuesday, March 22, 2011 2:29 PM
-
Thursday, January 27, 2011 7:27 AM
Hi Rob,
Thanks for the Welcome and reply. I should be trying the 2nd Method. Shall update the thread after I do so.
Regards,
freddieMaize
..A story with Glory is History. Doesn’t matter whether Glory rest in the world of Demon or God. Lets create History..

