It is hard to diagnose some of the search issues on the new Ektron/Microsoft search. If you have ever worked with SharePoint, you know of the rogue SharePoint errors that mean almost nothing. The error “Failed to connect to the specified Search Server. Please verify that the Search Server URL and port number are valid and try again.” is one of those. Here is the steps I recently used to fix the error.
Open the Windows Services control panel.
Right-click on the entry for the Ektron Search Server Service.
Choose the ‘Properties’ option from the context menu.
Select the ‘Log On’ tab from the properties dialog window.
Select the radio button labeled ‘This account’
Enter the credentials to match those of the SharePoint Server Search 14 (OSearch14) service.
Commit your changes.
Sometimes it is hard to know exactly what version of Ektron you are on. Lately they have been better at the version numbers, but in the last some version from SP1 to SP2 had the same version number. So the easiest trick to do is to look in SQL. Run this script on the Ektron database.
select convert (varchar, version) from settings
This will tell you exactly what version of Ektron you are on.
http://alipka.wordpress.com/2008/12/17/how-to-change-cluster-ip-address-or-move-the-default-cluster-group-in-windows-server-2008/
http://www.cryer.co.uk/brian/sqlserver/howto_list_table_sizes.htm
use [WSS_Content]
select * FROM sys.database_files
ALTER DATABASE [WSS_Content] SET RECOVERY SIMPLE WITH NO_WAIT
DBCC SHRINKFILE(WSS_Content_log, 1)
ALTER DATABASE [WSS_Content] SET RECOVERY FULL WITH NO_WAIT
When you are in anonymous mode, published, you dont want any of the SharePoint scripts to be running like named.dll. The way to hide it is to wrapped the SharePoint scripts in a security tab. Thus security trimming the scripts and SharePoint overriding CSS classes.
<Sharepoint:SPSecurityTrimmedControl PermissionsString=”BrowseDirectories” runat=”server”>
<!–showing sharepoint scripts –>
<SharePoint:ScriptLink name=”init.js” runat=”server”/>
<Sharepoint:CssLink runat=”server”/>
</Sharepoint:SPSecurityTrimmedControl>
I think there might be an issue with .NET 2.0 SP2 that causes my normal fix of “click the reinstall button on .NET 2.0″ to fix this issue. i recently ran into this issue again and it didnt work. What did work is the commands below. Bascially it is uninstalling and reinstalling via regiis.
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -u (uninstall)
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -i (reinstall)
Why did this happen? No idea. How did I fix it, read below.
- Open central admin
- Goto Operations
- Goto Services on server and located your index server
- On “Office SharePoint Server Search” click “Stop”. This deconfigures it.
- Now click “start”
- Then click “Shared Services Administration”, hover over the failing SSP and select edit.
- You will notice now the indexer is not selected. Select it from the drop down.
- HERE IS THE IMPORTANT PART. The server you have selected is probably the same server as you used before. If it is, go to that server and locate the indexer files. It is in the textbox right below the drop down you just used. For me it was “F:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications”. In there you will find a folder with Guid name. At the end of that folder add “_old”. Now go back to your SSP and click OK. Wait 1 minute and the index will recreate the guid folder.
- Tada, all fixed.
For what ever reason server 2008 creates a file on the OS drive for hybrinating the same size as the RAM that is in the server. Not sure how many servers hybrinate, but not mine.
To turn it off just run this from command line
powercfg -h off
Enjoy.
