Sharepoint Server 2013 Search doesn't work
Hello community,
I have SHarepoint Server 2013, but the search service has never functioned. I removed the default search service application and created a new one, but it still dosen't function correctly.
In the windows event log I receive a lot of errors, but I cannot figure what's the real problem with this. The major errors are the following:
EventID: 2548
Content Plugin can not be initialized - list of CSS addresses is not set.
EventID: 1000
Faulting application name: NodeRunner.exe, version: 15.0.4481.1002, time stamp: 0x51075d0e
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b8479b
Exception code: 0xe0434352
Fault offset: 0x0000000000009e5d
Faulting process id: 0x3960
Faulting application start time: 0x01cef065b7b369e1
Faulting application path: C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\NodeRunner.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: f8e620d9-5c58-11e3-a5b8-005056b87a7e
EventID: 1026
Application: NodeRunner.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
Stack:
at Microsoft.Ceres.Common.Utils.Concurrent.AbstractWorker.Run()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
EventID: 101
UsageAnalyticsTimerJob-179fffd7-4eb8-4022-94dd-d9995ddf6cbf: No se pudo recuperar el Servicio del motor de análisis.
EventID: 68
Error en el trabajo del temporizador de implementación del diccionario personalizado. SearchComponent: OWSTIMER.EXE, SearchServiceApplication: {179fffd7-4eb8-4022-94dd-d9995ddf6cbf}, FlowName: Microsoft.CustomDictionaryDeployment, CorrelationId: {bac45c9c-3c2d-b056-9a2b-ff0a2b57654e},
Error: System.InvalidOperationException: No system manager locations set, search application might not be ready yet.
at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.GetSystemClient(IList`1 systemManagerLocations)
at Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition.ExecuteTimerJob().
EventID: 177
Error en el componente de búsqueda de tiempo de ejecución Remoting de SearchComponent de búsqueda de tiempo de ejecución Admin1-179fffd7-4eb8-4022-94dd-d9995ddf6cbf
What can I do to solve this?
Melvintt
MCTS, Windows Server 2008 R2: Network Infrastructure
MCTS, Windows Server 2008 R2: Active Directory, Configuring
what kind of error in browser you are seeing?
is search service application never starterd or its started but cannot crawl?
did you see the timer jobs related to search services and what's their status?
so what about the search results from site collection?
also make sure this service "SharePoint Search Host Controller Service" started on all servers in the farm.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog
In the browser I receive the following error:
The search service app is running, doesn't crawl:
Yes, I can see the timer jobs related to search services, some of them are Succeded, others are Scheduled.
The service SharePoint Search Host Controller Service is started in the first server of the farm, but not in the second
one. When I try to start it, I receive the following error:
Windows could not start the Sharepoint Search Host Controller Service on Local Computer. Error 1067: The process terminated unexpectedly.
Melvintt
MCTS, Windows Server 2008 R2: Network Infrastructure
MCTS, Windows Server 2008 R2: Active Directory, Configuring
Similar Messages
-
SharePoint server 2013 Search Service App on Windows server 2012 R2 not working
Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM
was set up to access the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate
to search service app admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is
in a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem
with Search Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.
Thanks a lot.Hi,
According to your post, my understanding is that SharePoint server 2013 Search Service App did not work on Windows server 2012 R2.
Please make sure you configure Search Service Application correctly. You can refer to:Create and configure a Search service application in SharePoint Server 2013
I recommend to created new Search Service Application, and made a full crawl. Then assigned the new SSA as the default SSA for webapplications. Finnlay checked the issue doesnt occur now,
If all search related components now are online, to keep the enviroonment clean, you can delete the old SSA.
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support -
SharePoint Server 2013 Search Box has disappeared
Hi guys,
SharePoint Server 2013 Search Box has disappeared and not showing on any sites. Even when I try to go to Search centre site I get an error "sorry something went wrong...
Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator. "
My search SA is working fine and crawl running with no error. It seems like there was same issue on SP foundation 2013 where there is fixed released for that:
https://support.microsoft.com/kb/2760625?wa=wsignin1.0
But I have SP Server and i can confirm that I have installed SP1 (KB288055) in my farm.
I wonder if I need to install any CU to fix this.... I haven't installed any CUs in my farm yet.
Shall I go for Feb 2015 CU update or Sept 2014 CU? or is there any fixes for that with no CU or I need to install my farm from the scratch....
Please help.
Any advice greatly appreciated.
BalaiPYou have deactivated SharePoint Search from center Admin.
Please activate it
Regards, Sachin -
Sharepoint Server 2013 Search Issue
Hi,
running Sharepoint server 2013. search service application is not working properly. getting the below error message.
"Unable to retrieve topology component health states. This may be because the admin component is not up and running"
we have 2 tier sharepoint 2013 farm architecture. please find the below server details.
1. WFE & APP server (OS: Windows Server 2008 R2 SP1 and RAM: 8 GB)
2. database server (OS: Windows Server 2008 R2 SP1 and RAM: 8 GB)
I tried the following:
- installed the latest sharepoint server 2013 CU.
- OS is up to date.
- deleted and recreated Search Service Application
- The service account does have access to the search databases
- one account is used, domain\sp2013search, has all necessary permissions
Please help to fix the search issue.Hi Raj0639,
According to your description, my understanding is that you got an error when you run SharePoint 2013 Search.
Firstly, please make sure that all servers are online, and connecting to others.
Please stop all search services on Manage services on server, then restart them. Please try to do as Amit said, compare the result.
If this issue still exists, please repair SharePoint 2013 under Control Panel, then compare the result.
Here is a similar post for you to take a look at:
http://social.technet.microsoft.com/Forums/en-US/a67b0d0f-4f5a-4412-8f83-a57eaff4be45/sharepoint-search-host-controller-does-not-start?forum=sharepoin
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support -
Team Foundation Server 2013 trace doesn't work
I'm trying to turn on tracing on my TFS 2013 instance. To do this I'm modifying C:\Program Files\Microsoft Team Foundation
Server 12.0\Application Tier\Web Services\web.config file like this:
<appSettings>
<add key="traceWriter" value="true" />
<add key="traceDirectoryName" value="%TEMP%\\TFLogFiles" />
</appSettings>
<system.diagnostics>
<assert assertuienabled="false" />
<trace autoflush="false" indentsize="4" />
<switches>
<add name="API" value="4" />
<add name="Authentication" value="4" />
<add name="Authorization" value="4" />
<add name="Database" value="4" />
<add name="General" value="4" />
<!-- WorkItem trace switches -->
<add name="traceLevel" value="4" />
</switches>
</system.diagnostics>
After these manipulations log files appear but they are not verbose at all. I tried the same step with 2 different TFS
2013 deployments and got no results. I also tried this technique with TFS 2010 and it works.
Has anybody tried this feature with TFS 2013 or has precise instructions how to turn off detailed tracing on TFS 2013 (I found the only good article for
outdated TFS 2010: http://blogs.msdn.com/b/bryang/archive/2011/11/14/tracing-in-team-foundation-server-2010.aspx)Hi Shkleinik & Kevin,
TFS 2013 includes low-level tracing for diagnosing complex server problems. You can refer to the page below for tracing configuration for TFS 2013, chekc if it works.
http://larzjoakimnilzzon.blogspot.in/2012/04/tracelogging-configuration-in-team.html
If it doesn't work and you want to report to MS, then you can submit it to Microsoft Connect Feedback portal at:
https://connect.microsoft.com/VisualStudio. Microsoft engineers will evaluate it seriously.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
SharePoint foundation 2013 Search is not working
Hi, Search was working 3 days back, but today its not working. So
1. I Recreated Search Service Application
2. Created Content Source and set full crawl.
3. And service application is associated to the web application also.
4. All Application pool id are running.
5. Created Search Site collection, even though search is not working.
The error message i got was shown below. How to resolve this issue. An help/thoughts.Try to use word Home in search
Do we see site getting crawl in crawl logs
Navigate to the site for which you want to control the Web Parts in search results.
Click Site Actions, and then click Site Settings.
Under Site Administration, click Search and offline availability.
In the Indexing ASPX Page Content section, under
This site does not contain fine-grained permissions. Specify the site’s ASPX page indexing behavior ,
Always index all Web Parts on this site
http://office.microsoft.com/en-in/sharepoint-server-help/enable-content-to-be-searchable-HA010379092.aspx -
Set up Search Service App For SharePoint server 2013 on Windows server 2012 R2 not working
Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM was set up to access
the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate to search service app
admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is in
a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean
isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message:
Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2 at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem with Search
Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue. This seems also to be a SP set up issue.
Thanks a lot.Using new Search Service App wizard to create SSA is always a success. I could delete existing SSA and recreate it and no problem. It says successful but when I open Search Admin page from CA, it gives me errors as mentioned.
Now I used the following PS script for creating SSA from Max Mercher, but it stays at the last setps in following script:
Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
$IndexLocation = "C:\Search" #Location must be empty, will be deleted during the process!
$SearchAppPoolName = "SSAPool"
$SearchAppPoolAccountName = "mydomain\admin"
$SearchServiceName = "SSA"
$SearchServiceProxyName = "SSA Proxy"
$DatabaseServer = "W12R2DC1"
$DatabaseName = "SSA"
$spAppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
if (!$spAppPool)
$spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
$ServiceApplication = Get-SPEnterpriseSearchServiceApplication -Identity $SearchServiceName -ErrorAction SilentlyContinue
if (!$ServiceApplication)
# process stays at the following step forever, already one hour now.
$ServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseServer $DatabaseServer -DatabaseName $DatabaseName
Account mydomain\admin is an farm managed account, domain admin account, in WG_ADMIN role, It is in all SQL server roles and is DBO. I see search DBs are already on SQL server. From Event viewer, I got following errors in sequence:
(1) Crawler:Content Plugin under source Crawler:Content Plugin
Content Plugin can not be initialized - list of CSS addresses is not set.
(2) Warning for SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(3) Error for SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application 'cbc5a055-996b-44a7-9cbc-404322f9cfdf'
(4) Error for SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
(5) Error Shared Services for SharePoint Server Search
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob
Above errors keep being generated. Last step for SSA creation stay there forever. Any clue what is really going on? Thanks. -
Search not working in site collections migrated from MOSS 2007 to SharePoint Server 2013
I have few site collections migrated from MOSS 2007 to SharePoint Server 2013 using database attach (first to 2010 and then to 2013).
When I search for anything in these migrated sites, I get "Nothing here matches your search".
Checked the crawl log for these sites and see this error for all items.
The content processing component failed to process the security descriptor of the item. ( The input ACL is invalid (1210 / 2072).; ; SearchID =
Some-Random-GUID )
Search works fine in newly created sites in 2013 environment.
Please help.Hello
Did you migrate your users to claims when you migrated the databases?
$wa = Get-SPWebApplication http://yourdom.com
$wa.MigrateUsers($true)
$wa.ProvisionGlobally()
I assume the sites that work and the migrated content are in the same database?
MCITP-EA | "Never test how deep the water is with both feet" -
SharePoint Server 2013 - Document file search
HELP! HELP! HELP! HELP!
I am using SP Server 2013. My environment consist of SP server and SQL 2012 database server. I have 3 site collections under one web application http://sharepoint1/
I am having problems with results not being returned on recent uploaded documents when I attempt to search for a file inside the document webpart. Here are my steps:
1) Started a continuous full crawl on my local sharepoint sites...content seems to be crawling just fine
2) After I upload new files to document library, I go to advance settings to reindex the files.
3) I attempt to do a search on the docs that were recently uploaded, but I get a "your search returned no results".
4) I am able to get results back from documents that I uploaded two weeks ago.
I have documents inside their respective folders. Whichever site collection I am in, I want to be able to do a search on files.
My boss has specifically advise me to stay away from enterprise features. I can not enable or activate features that will swing us over to the enterprise license.
The search seems to be partially working since I am getting returns on older uploaded docs. What am I doing wrong or missing. Please provide 'How-to" links or resources on setting up search application the correct way.
Help is greatly appreciated!!!
artisticwebThe default continuous crawl interval is 15 minutes. Do the files appear in search results after 15 minutes from uploading?
If so, you can increase the frequency to a maximum (minimum?) of 1 minute. To set the interval, check out Manage continuous crawls in SharePoint Server 2013
From an elevated SharePoint Management Shell, run:
$ssa = Get-SPEnterpriseSearchServiceApplication
$ssa.SetProperty("ContinuousCrawlInterval",1)
(If you have more than one Search Service Application you'll need to filter accordingly)
Update: Another thing worth looking into -- which patches have you applied to the farm, what is the farm's build version? Earlier releases had search issues that have been fixed in later updates.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights -
Error while opening file from search result in SharePoint Server 2013
Hi All,
I have configured a file system search in SharePoint serve 2013, it is crawling the data and displaying in search result.
But while click on file to open, it gives error "Cannot find 'file://filesystemPath/filename'. Make sure the path or internet address is correct.".
I have given 'Everyone' to read and execute rights on shared folder (used in file system).
Please guide me.
Thanks in advance
Dharmender SharmaHi,
Please check whether this issue occurred on all files or a specific file from the shared folder.
1. If this issue occurred on a specific file, please check if the file exists in the shared folder, whether someone deleted it.
2. If this issue occurred on all files , please check the network and make sure the shared folder is online
Feel free to reply if the issue still exists.
Best regards
Wendy Li
TechNet Community Support -
Mac Mail Version 6.0 (1486) has stopped recieving mesages regularly and the search doesn't work.
Since installing Mountain Lion, Mail seems to be very unresponsive. I have mac mail running on an iMac (which works fine) and a 2012 MacbookPro which is the one having the issues with the Mail app. Both computers are running on Mountian Lion.
When I scroll up in Mail for instance, the frame rate drops to about 5 a second.
When I click on a message it doesn't display it in the preview pane. Which is very annoying!
But I can get around the issue by double clicking on a message and it opens up the message in a new window.
When I search for a message, nothing appears in the results. Even if Im searching for something that is defiently there, eg if I type in my name, you'd think some results would come up. But when I click on something else, the results dispaly for about half a second. Bizarre. Is anyone else having this problem?what kind of error in browser you are seeing?
is search service application never starterd or its started but cannot crawl?
did you see the timer jobs related to search services and what's their status?
so what about the search results from site collection?
also make sure this service "SharePoint Search Host Controller Service" started on all servers in the farm.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog
In the browser I receive the following error:
The search service app is running, doesn't crawl:
Yes, I can see the timer jobs related to search services, some of them are Succeded, others are Scheduled.
The service SharePoint Search Host Controller Service is started in the first server of the farm, but not in the second
one. When I try to start it, I receive the following error:
Windows could not start the Sharepoint Search Host Controller Service on Local Computer. Error 1067: The process terminated unexpectedly.
Melvintt
MCTS, Windows Server 2008 R2: Network Infrastructure
MCTS, Windows Server 2008 R2: Active Directory, Configuring -
Disappearing disk space Windows Server 2012 R2 with SharePoint Server 2013 Enterprise
I've got an interesting problem with a virtual machine in our VMWare environment. It is Windows Server 2012 R2 with SharePoint Server 2013 Enterprise installed. I started out with a 60GB disk and it started running out of space, so I increased
it in VMWare and extended the partition to 100GB. Well, that lasted for a bit and so I extended it again. I've done this 3 or 4 times and now I've got a 160GB disk with about 2-3GB of space remaining (and it started with 10GB remaining).
WinDirStat shows 105GB of <Unknown> space being used, which is probably my issue. However, I can't determine what this is and it keeps growing like a tapeworm. The context menu on the <Unknown> files has all the options disabled,
so WinDirStat doesn't appear to have access to whatever the file(s) is/are. I've performed several chkdsk /f on the C: drive and nothing bad is reported. I don't have any restore points and am not running VSS (that I'm aware of). The pagefile
reports as being about 4.9GB, so that's not the issue. No large files are shown anywhere and my explorer settings are set to show me all files, including system files.
When I try to run WinDirStat with elevated permissions, it hangs and becomes unresponsive.
I've even resorted to running CCleaner to see if it found anything, but it simply found the standard temp files and such...about 1GB.
I'm pulling my hair out...and I don't have much to start with. Anyone have any ideas?
Thanks
RussIt appears that somehow, Microsoft Fusion Assembly binding logging was turned on and many of the temp folders located at c:\users\username\AppData\Local\Microsoft\Windows\InetCache\IE were filling up with hundreds of thousands of Fusion HTM log files.
This is controlled by an entry in the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\ForceLog which was set to 1. Hopefully, setting it back to zero will fix the issue. As a result of figuring this out, I have recovered almost 80GB of disk
space occupied by the log files.
I thought WinDirStat would show me what I needed to know, but it turns out TreeSize (which I've used in the past) works much better.
Russ -
SharePoint Server 2013 - very slow in loading pages (frontend)
Hello, I have a problem.
I have install a SharePoint Server 2013 Enterprise. The enviroment:
1. Web-Front-End Server with 4 Core, 12 GB RAM, SSD (WS2012, SharePoint 2013 RTM + CU March 2013)
2. Backend SQL Server 2012 with 3 Core, 10 GB RAM, SSD (WS2012 + last Update)
The central administration page works fine, how sharepoint 2010.
The problem, when I access a web application, every site (main site, sub site, document library, ...), every action need 2 - 3 seconds. On the right side is the popup information "is in work ...". No CPU or SSD/HDD usage.
I have found the problem in the internet, but no solutions work.
http://social.technet.microsoft.com/Forums/en-US/sharepointitpropreview/thread/16cebde9-da9e-43a2-9d6a-656693ab65c5
http://social.technet.microsoft.com/wiki/contents/articles/14287.sharepoint-2013-how-to-improve-speed-on-sharepoint-2013-en-us.aspx
1. I have set the maximum of the noderunner from 0 to 128 (no solution)
2. I have disable the two search services (no solution)
3. I have export and import the trusted root certificate for the 3 certificates for sharepoint, no solution.
I need help. Does anyone know the problem?Hello, I have check with the dashboard. You can see, with "Wiki Edit Render" the start time is after 6000 ms. The job befor by 107 ms. And this is the wait time from 6 seconds, what I have by every page and site action.
ComputerBereichsnameStartzeit (ms)Dauer (ms)CPU (ms)
servername VBeginRequestHandler 000
servername VSPFederationAuthenticationModule.OnAuthenticateRequest::WifCodeCall 100
servername VSPClaimsCounterScope 132
servername VSPSam.OnAuthenticateRequest::WifCodeCall 132
servername VSPChunkedCookieHandler.ReadCore::WifCodeCall 100
servername VSPChunkedCookieHandler.ReadCore 110
servername VGetWindowsUserKey: Translate NTAccount to SecurityIdentifier 210
servername VSPSam.OnSessionSecurityTokenReceived::WifCodeCall 400
servername VSPSam.AuthenticateSessionSecurityToken::WifCodeCall 400
servername VSPSam.SetPrincipalFromSessionToken::WifCodeCall 400
servername VSPClaimsCounterScope 410
servername VMatching per user conditions for ULS boosting 500
servername VPostAuthenticateRequestHandler 500
servername VSPFederationAuthenticationModule.OnPostAuthenticateRequest::WifCodeCall 510
servername VSPSam.OnPostAuthenticateRequest::WifCodeCall 600
servername VPictureHttpModule: ProcessPictureRequest 600
servername VPublishingHttpModule: PostAuthorizeRequestHandler 600
servername VPostResolveRequestCacheHandler 64020
servername VGetWebPartPageContent 103517
servername VGetFileAndMetaInfo 103516
servername VSPSqlClient 10340
servername VSPFileStreamManager_From_Native 41319
servername VCreateStreamFromRowset 4110
servername VPublishingMobile: Resolve the default or non-default channel custom master url token. 4700
servername VSearchBoxScriptWebPart::OnInit 5311
servername VScriptApplicationManager 5310
servername VSearchCommon::GetCurrentSiteProperty 5300
servername VSearchCommon.GetSearchCenterUrl 5310
servername VSearchCommon::GetCurrentSiteProperty 5310
servername VEnsureListItemsData 553218
servername VSPSqlClient 61239
servername VWiki Edit OnInit 9110
servername VWiki Edit OnInitComplete 9200
servername VWebparts hinzufügen 9200
servername VWiki Edit OnLoad 9200
servername VToolBarMenuButton.CreateChildControls for PersonalActions 9400
servername VToolBarMenuButton.CreateChildControls for SiteActions 9700
servername VIsCheckedOutToSystem 9910
servername VSPPageStateControl:OnLoad 10000
servername VActivate web part connections 10000
servername VWiki Edit OnPreRender 10010
servername VSPPinnedSiteTile Control CreateChildControls 10100
servername VSPSqlClient 10300
servername VSearchBoxScriptWebPart::OnPreRender 10421
servername VSearchBoxScriptWebPart.OnPreRender 10421
servername VSearchCommon.GetSharedSearchBoxSettings 10410
servername VSearchCommon::GetCurrentSiteProperty 10400
servername VSearchCommon::GetCurrentSiteCollectionProperty 10500
servername VSearchCommon.GetSharedSearchBoxSettings: service level 10500
servername VSearchCommon.GetSearchCenterUrl 10500
servername VSearchCommon::GetCurrentSiteProperty 10500
servername VScriptWebPart.OnBeforeSerializeToClient 10510
servername VSPPageStateControl:OnPreRender 10610
servername VWiki Edit OnPreRenderComplete 107 1 1
servername VWiki Edit Render 6146 26 25
servername VPublishingMobile: Resolve the default or non-default channel custom master url token. 614600
servername VRobotsMetaTag Control Render 615100
servername VProjectProperty Control Render 615110
servername VListItemProperty Control Render 615200
servername VSPShortcutIcon Control Render 615200
servername VCSSLink Control Render 615200
servername VScriptLink Control Render 615232
servername VScriptLink Control Render 615510
servername VScriptLink Control Render 615600
servername VScriptLink Control Render 615600
servername VScriptLink Control Render 615600
servername VCustomJSUrl Control Render 615600
servername VSoapDiscoverLink Control Render 615600
servername VRssLink Control Render 615610
servername VCSSRegistration Control Render 615700
servername VImageLink Control Render 615700
servername VSPNoScript Control Render 615700
servername VSPClientIDGenerator Control Render 615700
servername VSharePointForm Control Render 61571110
servername VMenüband rendern 615954
servername VSPTitleBreadcrumb Control Render 616500
servername VSearchBoxScriptWebPart::RenderWebPart 616511
servername VScriptWebPart.OnAfterSerializeToClient 616600
servername VListItemProperty Control Render 616610
servername VSPRibbonButton Control Render 616700
servername VSPRibbonButton Control Render 616700
servername VSPRibbonButton Control Render 616700
servername VFormDigest Control Render 616800
servername VPreSendRequestHeaders 617210
servername VEndRequestHandler SharePointEndRequest 617300
servername VLogRequestUsage 617300
servername VEndRequestHandler SPRequest Disposal 617311 -
Schedule SharePoint Server 2013 discoveries along with SharePoint Foundation 2013 discoveries
Hi
So I'm trying to add the SharePoint Server discoveries in SCOM 2012 - pasted the code straight of the MS guide into the config file:
<Workflow Id="MOSSInstallation.Discovery;WACInstallation.Discovery;SearchExpressInstallation.Discovery;SearchStandardInstallation.Discovery" MP="Microsoft.SharePoint.Server.2013.Discovery" Type="Discovery"
Times="1" />
<Workflow Id="SPService.Discovery" MP="Microsoft.SharePoint.Server.2013.Discovery" Type="Discovery" Times="4" />
<Workflow Id="SPSharedService.Discovery" MP="Microsoft.SharePoint.Server.2013.Discovery" Type="Discovery" Times="4" />
<Workflow Id="SPSharedService.Discovery.WAC" MP="Microsoft.SharePoint.Server.2013.Discovery" Type="Discovery" Times="4" />
However when I run the "Configure" Task I get the following error: (NOTE - I discovered that the Dir "Monitoring Host Temporary Files 28803\2522979" does not even exist - )
The Event Policy for
the process started at 8:13:26 AM has detected errors in the output. The
'StdErr' policy expression:
.+
matched the
following output:
Exception calling
"GetDiscovery" with "1" argument(s): "An object of
class ManagementPackDiscovery with ID fedca251-56d5-be00-d6af-9cae645d6f36 was
not found."
Failed to find
workflows WSSInstallation.Discovery in Microsoft.SharePoint.Foundation.Library
Command executed:
"C:\Windows\system32\cmd.exe" /c powershell.exe -NoLogo -NoProfile
-Noninteractive "$ep = get-executionpolicy; if ($ep -gt 'RemoteSigned')
{set-executionpolicy remotesigned} & '"E:\Program Files\System Center
2012\Operations Manager\Server\Health Service State\Monitoring Host Temporary
Files 28803\2522979\AdminTask.ps1"'
'Microsoft.SharePoint.Foundation.Library.mp.config'"
Working Directory:
C:\Program Files\System Center Management Packs\
One or more
workflows were affected by this.
Workflow name:
Microsoft.SharePoint.ConfigSharePoint
Instance name:
Microsoft SharePoint Farm Group
Instance ID:
{6CB0A80D-D833-26EA-13C1-0CA48A57F5E2}
Management group:
Error Code:
-2130771918 (Unknown error (0x80ff0032)).
If anyone has any ideas that would be great -
JHello Jon,
Thank you for your question.
We are currently looking into this issue and will give you an update as soon as possible.
Thank you for your understanding and support.
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support -
Sharepoint foundation 2013 Search Service Application.
Hi all,
I want to configure search application for sharepoint foundation 2013. I have followed some of the web links.
But did not get success. Can you please provide me the working example of how to configure search application and run the crawl. And make sure the search is working correctly.
Thanks in advance for help.Hi Vishwajeet,
According to your description, my understanding is that you want to configure SharePoint Foundation 2013 Search service application.
In SharePoint Foundation 2013, we cannot add the Search Service to SharePoint Foundation 2013 from the Central Administration GUI after selecting a manual configuration method. It seems that the ONLY way you can add the Search Service to SharePoint Foundation
2013 is by using the SharePoint Configuration Wizard.
More information, please refer to the link:
http://blog.ciaops.com/2012/12/search-service-on-foundation-2013.html
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support
Maybe you are looking for
-
Clearing Vendor and Customer through F.13
Hi. I was wondering if you can configure the vendor and customer masters so that they can be cleared automatically through transaction F.13. Currently this process is done through either F-32 or F-44 but this takes a lot of time. I would like to know
-
Does anyone know how to set up the desktop so that if (for example), two separate windows for Safari are opened, they are always set to be side by side of equal widths? It would be great not to have to manually move windows around. Any ideas? With th
-
IPhone Pre-Order Arriving a Day Early
I woke up to this message: Dear Apple Store Customer, You recently received a Shipment Notification email from Apple advising you that your iPhone has shipped. This email is to confirm that your delivery will occur on June 23rd. Although Apple and Fe
-
TOC disappears after allow blocked content
I have a Robohelp 9 project (single sourced through FrameMaker) I can compile the help and run. When I view it, I see the full help along with the "Allow blocked content" message. When I click Allow Blocked Content, my help appears but now the TOC is
-
SIRI won't call "the mother of my girlfriend"
SIRI won't call "the mother of my girlfriend" and says that an error occured or calls my own "mother"! Please, help me out. I work my self by an Apple Reseller and no one of my collegas can help me out! *the problem is not coming from my Contacts Boo