SQL DB upgrade to 2012 and DOC IDS not working

%3CLINGO-SUB%20id%3D%22lingo-sub-681712%22%20slang%3D%22en-US%22%3ESQL%20DB%20upgrade%20to%202012%20and%20DOC%20IDS%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-681712%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20in%20the%20Dev%2FQA%20steps%20of%20migrating%20our%20SQL%202008%20DBs%20to%20SQL%202012%20DBs%20for%20SharePoint%202010.%20We've%20have%20success%20on%20most%20site%20collections%2C%20but%20one%20site%20is%20using%20DocIDs..%20on%20their%20site%20any%20link%20that%20uses%20the%20DOC%20ID%20does%20not%20resolve%20to%20the%20full%20URL%20(%20xxx.aspx%20page).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3ECould%20not%20look%20up%20Document%20ID%20%22KQZAP7SFH7E3-777257284-94%22%20due%20to%20an%20error%20encountered%20in%20Microsoft%20Search%20Server.%3CBR%20%2F%3ESystem%20error.%20%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20in%20the%20process%20of%20running%20a%20full%20crawl%20after%20resetting%20the%20Index%2C%20but%20would%20rather%20not%20have%20to%20do%20this%20on%20our%20Production%20site.%20Any%20suggestions%20on%20how%20to%20prevent%20this%20from%20happening%3F%20What%20are%20we%20missing%20with%20this%20move%20of%20the%20database%20to%20a%20new%20server%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3CP%3EJilltre800%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-681712%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

We are in the Dev/QA steps of migrating our SQL 2008 DBs to SQL 2012 DBs for SharePoint 2010. We've have success on most site collections, but one site is using DocIDs.. on their site any link that uses the DOC ID does not resolve to the full URL ( xxx.aspx page).

 

Could not look up Document ID "KQZAP7SFH7E3-777257284-94" due to an error encountered in Microsoft Search Server.
System error.

 

I'm in the process of running a full crawl after resetting the Index, but would rather not have to do this on our Production site. Any suggestions on how to prevent this from happening? What are we missing with this move of the database to a new server?

 

Thanks!

Jilltre800

0 Replies