Hello
I am getting a stupid error. I have two Web Applications, one of them is the MySites and one is my corporate Web App.
So, I setup my Search Service, and crawling on the corporate Web App is working fine. But MySites throwing and error, and does not get crawled.
The errors are:
- sps3://my.corp.domain.com –> the object was not found
- http://my.corp.domain.com –> the object was not found
My apps are all with a host-name header, and all three, the http://corp.domain.com, http://my.corp.domain.com and sps3://my.server.domain.com are in the “Start adresses area”.
I checked that all my used accounts have the “retrieve people data for search crawlers” permission.
One of these accounts is my Default content access account.
So what could the issue be?
/emo
Could not reply anymore to your post, so had to do it this way.
Yes, BackConnectionHostNames was one of the first thing i did, because I could not enter mysites from the server without entering adresses in the BackConnectionHostNames entry.
So now I just hope that I can search for persons, phone-numbers, departments, etc.. 🙂
That is interesting and very SharePoint like. I would say that the most significant thing out of all of which you have done is the DisableStrictNameChecking=1. I will have to have a read up on that to see why that may have helped.
Have you done the BackConnectionHostNames too in the registry. Search for this and do this also as this will only help.
Hi Henry
I checked my environment today, and I no longer get any “top-level” errors in the crawl log, so my my.corp.domain.com and sts3://my.corp.domain.com start adresses are getting crawled (i think).
I dont know what fixed the error, i changed the content access account to my dedicated crawl-account, and I put an entryÂ
One of the perks of SharePoint is that it should handle most of, if not all of what you are after.
So you can browse to my.corp.domain.com without issue and hit the my site host?
To me you just needed to create one web app in CA with a host name of corp on port 80 and another web app with a host name of my on port 80.
Then add two A records within DNS, one for the corp web app and another for the my web app and point to the Web Server.
After that you should have been good to go. So, which server is doing the crawling? The app server?
If you can, I would re-create your mysite web app on port 80 and a host name of my, create my site host site collection and all of that good stuff. Then you should just be able to get to it at my.domain.com and I am sure Search would work fine.
You have created a my site host site collection I presume and all that side of things is working, it is just the search.
As a shot you could add a host file entry on the crawl server to make sure that my.corp.domain.com resolves and see if that works any better. As it will use the host file for name resolution if it can before it looks to DNS. I could of course be barking up completely the wrong tree.
I got a DNS record for my WFE, so now all browsing is going trough my WFE, which is nice.
The bindings on my AppServer IIS are
- for main web app –> http  corp.domain.com  80  *
- for mysites web app –> http my.corp.domain.com  80
And on the WFEServer IIS are
- for main app –> http     80
- http  corp.domain.com  80 *
- for mysites –>  my.corp.domain.com  80
Im a rookie at IIS stuff, so I just tried alot different and tried to look at an old system and there it was set up this way.
/emo
