It seems to me that only the default objects are indexed in the installation of the Portal I have here (RTM + update 1). For example, if I search on "User" in the MPRs I get all the default MPRs with the word "user" in them - but if I search on "test" I don't get any of the test MPRs I have created - all of which start with that word. Also, for the users, I can search on first name only. Last name and display name retrun nothing. Any ideas? I know I haven't enabled anything special for searching before and its always just worked.http://www.wapshere.com/missmiis

i just created an MPR "test abc" and search for "test". it works for me notice FIM uses full text search, so searching for "est" or "bc" won't workThe FIM Password Reset Blog http://blogs.technet.com/aho/

I don't think this is normal - I think there's something wrong. The question is - how to fix it? It's a pretty newly installed system with not a lot of activity yet, but I don't want to do a complete reinstall because the initial data loading took so long.http://www.wapshere.com/missmiis

HI... Did you try to use %est or tes% ? :) Cheers,***** Paulo H. Campos - So Paulo/Brasil ***** http://identitypedia.blogspot.com (in PT-BR)

do u think u can provide with the exact list (maybe 2-3) of ur MPR? i can try to repro it. if it doesn't repro on my side, the best would be to connect PSS to diagnose your deployment

It's not just the MPR searching - that was just an example. None of the searching is working properly as far as I can tell. Like I mentioned above - I can only search for users by first name, not surname. That's not normal! I won't have access to that particular system for 2 weeks now, so I'd appreciate any troubleshooting tips but I won't be bale to try them out staright away. http://www.wapshere.com/missmiis

sorry, i have absolutely no clue. if i were to guess, there is soemthing wrong with SQL's index

Hi Carol, We've seen a similar problem recently with one of our customers. Try the following in SQL Management Studio: 1. Open up the catalog, ftCatalog, in FIMService => Storage => Full Text Catalogs => ftCatalog 2. Note the Unique Key Count and Item Count. 3. Select Rebuild catalog. This will be a long running process taking upwards of 12 hours if you have a large amount of data. If you can let me know the Unique Key Count and Item Count, I would greatly appreciate it. I'm collecting some data on this issue. Billy

Hi Billy. I am back to the customer again today. The data you asked for is as follows: Unique Key Count = 0 Item Count = 120138 I've kicked off the rebuild. I'll check tomorrow to see if the problem is resolved. Thanks, Carolhttp://www.wapshere.com/missmiis

I can confirm the search is now working. Those numbers have changed substantially. I now have: Unique Key Count = 305941 Item Count = 1950569 http://www.wapshere.com/missmiis