Below options are available under "Manage Farm-Level Search Settings" in Central Administration
Connection time (in seconds): 60
Request acknowledgement time (in seconds): 60
I would like to know that how it affects the SharePoint Performance ?
Let's say, what will be the consequences if we set 90 instead of the default value 60.
Help me with your thoughts ?
Changing this value might make your crawl take longer time; it will wait another 30 seconds for requests. And if your crawls take long time and you are crawling from your WFE's it might slightly affect the performance if your crawl takes longer time than the anticipated window in time for crawling.
When I go to manage service applications in Central Administration and try to create a new service application like: New > Create a new service application, the link isn't active. My issue is I would like to create a Search Service Application after installing Search Server Express 2010. Do I need to run the Farm Configuration Wizard and install the below if I can create a Search Service... migrated WSS v3 to SharePoint Foundation 2010 and then installed Search Express 2010 on top of it. I am logged in with an account that has full farm administration access. Update 2: I migrated WSS
Directory domain. If I try to set up synchronization (Application Management > Manage service applications > User Profile Service Application > Configure Synchronization Connections > Create New... jobs running at the time, plus I tried a reboot and got the same error message. I also try to start Forefront Identity Manager Service and it stops straight away (domain account or local system...). Edit 2: Using stsadm -o sync -listolddatabases 0 I get: User Profile Application 'User Profile Service Application' - Partition '0c37852 b-34d0-418e-91c6-2ac25af4be5b' ID
After deploying a SharePoint application, what maintenance actions can be done to ensure optimal performance and avoid degradation of performance over time? I can think of the following: Schedule disk defragmentation Set Scheduled virus scans for the system (need to eliminate some paths to not affect SP performance: more about it here ) Clean up old unused log files. What else can be done?
Question : User has changed his name in the active directory and wants see his mysite with the new URL. Can we follow the steps given below: ○ Take the backup of the existing site collection (Stsadm -o export) ○ Goto SSP -> User profile -> remove Personal site URL -> Save ○ Ask her to click on the "Mysite" Link ○ New site collection will be created for her ○ Import the old collection content (Stsadm -o import) ○ you may need to change the site title of the new site collection after the import.
While accessing My Site -> My Interests and Newsfeed Settings, I am getting this error: Error An unexpected error has occurred. Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: ee7ff5fe-feed-472e-add8-639424410447 Date and Time: 4/8/2010 2:23:31 PM However the My Site -> My Colleagues option work well. Anybody faced this problem before? Environment: SP2010 Server on Windows 2008. I am using Administrator ID to login to the site. Digged the LOGs and found this: 04/08/2010 14:33:14.55 w3wp.exe (0x0828) 0x1AFC SharePoint
. For instance… If I add a user into the Designer site permission group I can create pages – excellent, just as I would expect. If I create a new site permissions level - let’s call it ‘customer-designer’ - by copying the Designer site permission level and then assign this ‘customer-designer’ level to a new site permission group. I then add my user into the new group and… I cannot create pages, even... The issue seems to lie somewhere when the new group is created. For example if I create a new group called ‘customer-designers’ and assign it the Design permission level I still cannot create a page
SharePoint 2010 appears to continue SharePoint 2007's tradition of automatically creating horribly named SQL Databases. Like many companies we have multiple farms and developer workstations connecting to a central database server. To make sure things don't become messy and difficult to manage, we prefer to use database names such as: DEV_WS004_SharePoint_AdminContent DEV_WS004_User Profile Service Application_ProfileDB rather than: SharePoint_AdminContent_9fc4ac7c-6895-4a74-bf10-df6ac4c2c1d6 User Profile Service Application_ProfileDB_a17efbf6942341f785c69829ce7f2d97 I am creating
I have run into a problem several times now where I have developed a custom timer job, and I want my site collection administrators to manage the schedule of this job with a custom application page but I keep running into security related obstacles. Since timerjobs are child objects of SPWebApplication, they are stored in the config database. If you have set up your farm properly in such a way... the Central Admin app pool account can write to the config database But then we lose the whole point - I want my site collection administrators to be able to manage the schedule! The only alternative solution
When attempting to enable search query logging from the Shared Services Provider of my SharePoint 2007 farm, IIS returns the HTTP 403 error page. My account has full-control rights at the farm and site-collection levels.