On Moss 2007, there are two search services WSS and MOSS. As Moss search provides all functions from WSS, can I shut down WSS search services?
View Complete Post
We want move our search database to a different drive on the same database server. In order to do this, we need all the SharePoint things that would connect to that database to be off. I see there is an stsadm command for stopping search but
it looks like this would have the same effect as using the Central Admin site--it would basically be the equivalent of uninstalling it. While I realize it is easy to uninstall and reinstall, the index of crawled content is pretty big and it would take
some time to rebuild the index completely.
Short of shutting down the SharePoint farm while we make the database move, how can you stop the SharePoint services that connect to the search database?
If we stop all of the app pools and all of the windows services related to SharePoint, will this accomplish the objective? So far at this point, it seems to me that the safest way to handle this would be to simply shut down the farm servers while we
do the db maintenance and restart them when it is done.
Search server gatherer calls CloseAccessor() and shutdown() on ISearchProtocol after GetChunk() even if the FILTER_E_END_OF_CHUNKS is not returned. After calling shutdown() it stops calling the createaccessor() with new URL. I want to create a hierarchical
indexing but I am not gatherer is not suporting this. The same piece of code is working fine in MOSS 2007, I am facing this issue in MOSS 2010 only. Is there anything changed in MOSS 2010 which is creating this issue?
The Search Results page in MOSS seems to list the results as links by default. My customer asked me if I could customize the search results so that they show in a data view web part. Is this possible?
I am tasked with writing reports for existing MOSS 2007, for that i am doing a test installation and test connection to a test moss server (copy of the main one)
So, i have a already set and running MOSS 2007. I am following theese tutorials
But in my case, i have only two machines - one with main site moss and one with reporting services and sql for reporting services.
So far, i have installed SQL server, installed moss and reporting services on the reporting services machine.
I joined my moss into the existing farm successfully.
I've set up reporting services according to the tutorial (Except i use an account provided by test server administrator, which has all rights granted, since we dont bother with least privellege here, not a very big company...)
But when i check the /reportingservices page i see an error (its in russian) that teh server is wrongly configured. rsServerConfigurationError is the kind of error.
The tutorial said that i should see a blank page at this point. I will continue tutorial futher tomorrow (work day ends now
This error started on 29 April and I cannot get rid of it...ÃÂ My search works fine, both site and people.ÃÂ AD profile import works fine.ÃÂ Full and incremantal crawls work as scheduled.ÃÂ Just that this error keeps showing up every five minutes in one of two WFE's.ÃÂ The other WFE does notÃÂ receive this error
I have verified all Security Configuration/Service Accounts, verified all Services on Server/Search accounts, Stopped/Restarted all search, and verified SSP accounts.ÃÂ The last thing I did was verify there was an indexer attached to the SSP...
I set the diagnostic logging to verbose and the only thing that stood out around the time of the error was
System.Data.SqlClient.SqlException: Invalid object name 'AR_CacheCounters'.
SqlError: 'Invalid object name 'AR_CacheCounters'.'ÃÂ ÃÂ ÃÂ Source: '.Net SqlClient Data Provider' Number: 208 State: 1 Class: 16 Procedure: 'proc_ar_GetCacheInvalidationCountersWithCount' LineNumber: 3 Server: 'SERVER'
MOSS farm: 1 index, 1 WFE,ÃÂ SQL cluster
When we try to start the wss search service from the web UI we gat a 'system policies must have full control' message. I can start it manually but the app log is full of event ID's 6482:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (da839862-de1b-4d3e-9015-3f23999ad32a).
Reason: System policies must have Full Control.
Techinal Support Details:Microsoft.SharePoint.SPException: System policies must have Full Control.ÃÂ ÃÂ at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.SynchronizeDefaultContentSource(IDictionary applications)ÃÂ ÃÂ at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()ÃÂ ÃÂ at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
There is an additional similar event (event ID 6483) that we also see regularly in the event log concerning Excel services:
Application synchronization failed for Microsoft.Office.Excel.Server.ExcelServe
Hello there, I have recently started using SQL Server Reporting services. I currently have a problem.
I am trying to achieve a search by dates in a report.
I have a table with the fields RequestDate in e.g. 22-Jan-2010 or 23-Sep-2010
I have created a report in Query Designer with two parameters in it RequestDate & RequestDate2. The Operators are for RequestDate is: Is more than or equal toThe value is: 1-Jan-2010
And the Operator for RequestDate2 is: Is less than or equal to.The value is 30-Dec-2010
When i go to the SQL Statement this is produced:
SELECT MHRA.ImportRequestID ,MHRA.UniqueID ,MHRA.CreatedBy ,MHRA.RequestDateFROM MHRAWHERE MHRA.RequestDate >= @RequestDate AND MHRA.RequestDate <= @RequestDate2
When i go to view report i want to be able to search for dates between the dates 1 Jan 2010 and 30-Aug-2010
My query seems to pick up all or most of the results between these dates.
How can i build this query so i can get specific results. For example...in the Request Date Parameter box i would put 2-feb-2010 and in Request Date 2 i would put in 5-Jun-2010 and this would return all the results between these dates.