Re: Search Issues persist event id 2424 remains
- From: "Jaap Wesselius" <jaapwess@[remove-this].xs4all.nl>
- Date: Sun, 2 Dec 2007 15:57:41 +0100
Hi,
I'm facing the same issues, but my two WFEs and SQL are on the same network
segment. Also the installation is completely fresh and I got the errors from
the first minute.
We will call Microsoft PSS tomorrow I'm afraid. The only thing that bothers
me right now is that the server is an X64 with Windows 2003 SP2. It won't be
the first time when it turns out to be SP2 issues with SP2 :-(
Thanks,
Jaap
"LRM" <Fskspam@xxxxxxxxxxxxx> wrote in message
news:OuhI7piMIHA.4228@xxxxxxxxxxxxxxxxxxxxxxx
Just wanted to check back in with this. Our issue was not anything in the
config. We had problem with a corrupt web app. Our DB had crashed and we
restored from backup, but we didn't restore the web app, or attempt to
discover the real cause of the crash. This is still unknown. At any rate
we finally caved and called MS for help. It took my top tech and the MS
tech several hours and a rebuild to get the thing put back together.
Thanks again for the quick support Mike, even if it didn't solve my issue.
Your efforts are appreciated.
"Mike Walsh" <englantilainen@xxxxxxxxxxx> wrote in message
news:uAIawRALIHA.4272@xxxxxxxxxxxxxxxxxxxxxxx
I think I'd better quit while I'm ummm "ahead".
I was thinking that possibly because of missing (or incorrect) AAM
settings there was a partial lack of communication between the server in
the DNZ and the SQL Server in your Intranet.
I always look at my definitions based on the page you first get when you
access Alternate Access Mappings in Central Admin which in my case looks
like (Zone column)
Default
Intranet
Internet
Custom
Extranet
Default
Intranet
Internet
Custom
Extranet
with the first set being for http://wss and the second for
http://wss:port
I've generally had the feeling that it doesn't really matter whether
Intranet/Internet/Custom or Extranet is used for alternative settings but
there's a small niggle which tells me that Intranet might be different.
But that's all - no answer to your follow-up I'm afraid. What we now need
is someone who has like you a server in the DMZ and a SQL Server that
isn't.
Mike Walsh
LRM wrote:
Mike,
Thanks for the fast reply,
So that I don't get more confused, our setup as it appears on the config
page of our SharePoint administration page is:
Internal URL http://wss Default Zone Public
http://wss
Internal URL https://my.SPS.com Internet Zone Public
https://my.sps.com
Internal URL https://wss.SPS.com Internet Zone Public
https://my.sps.com
Internal URL http://wss:40895 Default Zone Public
http://wss:40895
You are saying to take the https://wss.sps.com and create a custom zone
and map it to a public URL of https://wss.sps.com then?
Will this resolve our search problem?
The SPS server's name for this discussion is wss.myco.com and the web
site is my.sps.com and I have it mapped via external ip to internal ip
and DNS at my isp resolves to my.sps.com
internally the server is in the DMZ the internal web http://wss is not
resolvable on the server itself or from inside the LAN.
Meanwhile the wss:40895 is resolvable internally.
Thanks again Mike
"Mike Walsh" <englantilainen@xxxxxxxxxxx> wrote in message
news:uZukW1$KIHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
The Alternate Access Mappings setup is:
http://wss Default http://wss
https://my.SPS.com Internet https://my.sps.com
https://wss.SPS.com Internet https://my.sps.com
http://wss:40895 Default http://wss:40895
It looks like your settings are incomplete
So
http://wss Default http://wsswhere is the equivalent Internet setting ?
https://my.SPS.com Internet https://my.sps.comWhere is the equivalent Default setting ?
https://wss.SPS.com Internet https://my.sps.comWhere is the equivalent Default setting ?
http://wss:40895 Default http://wss:40895where is the equivalent Internet setting ?
--------------------------
In fact a more usual (and I can't tell in your case) setup would be
something more like two sets as follows.
Default http://wss
Internet https://my.sps.com
Custom https://wss.SPS.com
Default http://wss:40895
Internet https://my.sps.com:40895
Custom https://wss.SPS.com:40895
Mike Walsh
WSS FAQ www.wssfaq.com / wss.collutions.com
no private e-mail questions please
LRM wrote:
Greetings:
We are running WSS 3.0 web server in DMZ with separate SQL 2005
database server on internal LAN.
We continue to have a search problem and continue to get even errors
2424.
We have reset the service accounts and no matter what we set them to
they continue. Admin accounts on SQL server and service accounts do
not fix this issue.
Changing both content and search Databases has not solved the issue.
We also continue to get searches that ALL return:
No results matching your search were found.
1. Check your spelling. Are the words in your query spelled correctly?
2. Try using synonyms. Maybe what you're looking for uses slightly
different words.
3. Make your search more general. Try more general terms in place of
specific ones.
4. Try your search in a different scope. Different scopes can have
different results.
The search issue has been happening ever since AAM was configured.
The Alternate Access Mappings setup is:
http://wss Default http://wss
https://my.SPS.com Internet https://my.sps.com
https://wss.SPS.com Internet https://my.sps.com
http://wss:40895 Default http://wss:40895
Can someone help us with this? I am stuck.
Thanks
.
- Prev by Date: Re: WSS 3.0 personal regional settings
- Next by Date: Re: Sharepoint Installation MSDE Location Question
- Previous by thread: Re: WSS 3.0 personal regional settings
- Next by thread: WSS 3.0 minimum CPU requirement
- Index(es):
Relevant Pages
|
