WSS3 does not search subsites from root on AAM

[meastaugh1]

http://i4.forums.community.microsoft.com/WebResource.axd?d=dxLBPOIcPku7kynRK8-ey16j2i8cp3Y29W07r4lsecSmY8J-1eEJtDBlOobHLlJhhw-KQ85SrJNkazWjOrHEvR6Yrv_a6Neggr5uwVVTnab6jwVvDw-VukMDINEKVJ9L0&t=633517143014382172http://i4.forums.community.microsoft.com/WebResource.axd?d=dxLBPOIcPku7kynRK8-ey16j2i8cp3Y29W07r4lsecSmY8J-1eEJtDBlOobHLlJhhw-KQ85SrJNkazWjOrHEvR6Yrv_a6Neggr5uwVVTnab6jwVvDw-VukMDINEKVJ9L0&t=633517143014382172http://i4.forums.community.microsoft.com/WebResource.axd?d=dxLBPOIcPku7kynRK8-ey16j2i8cp3Y29W07r4lsecSmY8J-1eEJtDBlOobHLlJhhw-KQ85SrJNkazWjOrHEvR6Yrv_a6Neggr5uwVVTnab6jwVvDw-VukMDINEKVJ9L0&t=633517143014382172http://i4.forums.community.microsoft.com/WebResource.axd?d=dxLBPOIcPku7kynRK8-ey16j2i8cp3Y29W07r4lsecSmY8J-1eEJtDBlOobHLlJhhw-KQ85SrJNkazWjOrHEvR6Yrv_a6Neggr5uwVVTnab6jwVvDw-VukMDINEKVJ9L0&t=633517143014382172http://i4.forums.community.microsoft.com/WebResource.axd?d=dxLBPOIcPku7kynRK8-ey16j2i8cp3Y29W07r4lsecSmY8J-1eEJtDBlOobHLlJhhw-KQ85SrJNkazWjOrHEvR6Yrv_a6Neggr5uwVVTnab6jwVvDw-VukMDINEKVJ9L0&t=633517143014382172

 

I've recently noticed that searching on the root site is a little bit broken. This has worked in the past, but I've recently had SLG2 installed, as well as install all available Windows Updates and KB913384 and KB949399 to address an issue I had with the timer service crashing.

 

I have WSS3 SP1 with SQL Internal/embedded database. One of the updates I installed, managed to lock out the database by changing the permissions on the database files. From what I've read, this occured because one of the updates made a security change to SQL. As I had moved the database files from their original location of (%systemroot%\sysmsi) to another drive, the correct permissions weren't set by the update.

 

If I search from the default mapping, all searches return as expected.

 

If I search the root site on the extranet AAM, no results are returned.

If I search a list in the root site on the extranet AAM, results are returned.

If I search a subsite of the root site on the extranet AAM, resuts are returned.

 

Any ideas? thanks.

[spc-rocket]

Hiya,

 

sorry i'm not offering a solution to your problem, but how did you move the embedded sql databse to another location. We are having space issues on the C drive and are looking to relocate the sharepoint stuff to another drive.

 

Any instructions, recommended practice when doing this?

 

TIA,

 

Ash.

[meastaugh1]

Hi Ashok,

 

It's easy enough to do it from command line with osql:

WSS/MOSS v3 FAQ - Databases: How do you move the "Windows Internal...

[spc-rocket]

Hi Ashok,

 

It's easy enough to do it from command line with osql:

WSS/MOSS v3 FAQ - Databases: How do you move the "Windows Internal...

 

Thanks for that i'll give it a go. We have on file called SharePoint_Config_303f303d-a54f-4b66-a754-524d8bdd54d8_log.LDF

 

which is taking up 11Gb which is strange as this is the log file. I have tried to do a backup which succeeds but it doesn't appear to shrink the log file.

 

Any ideas?

 

Thanks.

 

Ash.

[apearce]

I'll see if I can solve both problems here

 

1. Database Log file - (reduce size)

Its something you do in SQL 2005 - they is an option you click on to shrink the database when you right click on it.

 

Make sure you have completed a full database which clears all the transactions logs. This does not reduce the size of you ldf file.

 

In SQL Server Management Studio Express, on the left hand side, right click on your database, Tasks->Shrink->File - select the file type (log) and run.

 

2. Search

Moving the search is not easy and hardly ever works - its best to stop the services in central admin (which deletes the current index) and start them again in a new location. You will be prompted about this when you stop the search. Make sure you stop and start the service in windows services as well.

 

A.

[spc-rocket]

Hi Ashok,

 

It's easy enough to do it from command line with osql:

WSS/MOSS v3 FAQ - Databases: How do you move the "Windows Internal...

 

I'll see if I can solve both problems here

 

1. Database Log file - (reduce size)

Its something you do in SQL 2005 - they is an option you click on to shrink the database when you right click on it.

 

Make sure you have completed a full database which clears all the transactions logs. This does not reduce the size of you ldf file.

 

In SQL Server Management Studio Express, on the left hand side, right click on your database, Tasks->Shrink->File - select the file type (log) and run.

 

2. Search

Moving the search is not easy and hardly ever works - its best to stop the services in central admin (which deletes the current index) and start them again in a new location. You will be prompted about this when you stop the search. Make sure you stop and start the service in windows services as well.

 

A.

 

apearce,

 

Does SQL Server Management Studio express also support the windows embedded database?

 

Ash.

[apearce]

I believe it does

 

http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en

[meastaugh1]

I don't think it does, since Embedded is only used by certain MS products (sharepoint, WSUS etc), it doesn't have the same performance limitations as Express, and it doesn't allow the studio interface.

[spc-rocket]

I believe it does

 

http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en

 

I had a go at shrinking the database but it didn't work its still the same size. I think its as mike says something to do with the sql embedded version.

 

I'll see if there is a way to backup of the log to reduce the size.

 

Thanks for your help guys.

 

Ash.

[meastaugh1]

I had a go at shrinking the database but it didn't work its still the same size. I think its as mike says something to do with the sql embedded version.

 

I'll see if there is a way to backup of the log to reduce the size.

 

Thanks for your help guys.

 

Ash.

 

Did the studio refuse connection to the embedded instance (MICROSOFT##SSEE)? That's what I usually get.

 

Edit: My mistake. Can connect with studio if the server is specified as: np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query

Edited September 2, 2008 by meastaugh1

[spc-rocket]

Did the studio refuse connection to the embedded instance (MICROSOFT##SSEE)? That's what I usually get.

 

Edit: My mistake. Can connect with studio if the server is specified as: np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query

 

HI Mike,

 

No the studio actually did connect and i could access the database etc and can nagivate to backup the databases etc.

 

There also a query editor as well so you can do the T-SQL in there against a db.

 

Ash.