Windows Server 2012 R2 - SharePoint 2013

After an front end server upgrade from Windows Server 2012 Datacenter to Windows Server 2012 R2 Datacenter of our SharePoint 2013 farm, the following error is being experienced when trying to open a document library with Windows Explorer (this
feature worked prior to the upgrade): Message from webpage "We're having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again."
Our domain is in the trusted sites list (*domain.com), the Webclient services are running, and the User Interfaces and Infrastructure > Desktop Experience feature is installed.
It looks like this error was previously remedied with KB2903928. This update doesn't seem to apply to Windows Server 2012 R2 Datacenter.
UPDATE: We have also discovered that site email boxes are not working.
Thank you for your assistance,
Jeanne

Hi,
Glad that the issue was solved.
Meanwhile, please understand that before the release of Microsoft SharePoint Server 2013 Service Pack 1 (SP1), Microsoft did not support the installation of SharePoint Server 2013 in a Windows Server 2012 R2-based environment.
http://support.microsoft.com/kb/2891274/en-au
Regards.
Vivian Wang

Similar Messages

Install AD / SQL Server 2012 and SharePoint 2013 on a single server as Development Environment

Hi All,
I'm planning to prepare a SharePoint 2013 development environment. The current idea is to install Domain controller, SQL Server 2012 and SharePoint 2013 all on a single server. Even though this is for development purposes,
would there be any limitations specially when it comes to SP 2013 functionalities according to your experience?
Some articles i referred.
http://sharepoint-tutorial.net/post/2012/07/18/install-sharepoint-2013-domain-controller.aspx
http://social.technet.microsoft.com/Forums/en-US/f438c9a6-02e8-43d3-9963-7a0608f0b961/sharepoint2013-on-domain-controller
Thanks,
Dilip

Hi
i understand this is a sandbox environment but you should be able to install everything.
http://sharepoint-tutorial.net/post/2012/07/18/install-sharepoint-2013-domain-controller.aspx
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hyper link of public image(hyperlink or image) can not be saved on windows server 2012 and sharepoint 2010 problem

hyper link of public image(hyperlink or image) can not be saved on windows server 2012 and sharepoint 2010 problem, is this a bug?
thanks for any reply.
Rosone

It is not a bug, you might be using IE in Windows server 2012 and and browser might be restricting your site actions to respond properly.
Check this in a different browser or access site in a differ OS.
Adnan Amin MCT, SharePoint Architect | If you find this post useful kindly please mark it as an answer.

How to join a Domain Controller Server to an two-tier (SQL Server 2012) and Sharepoint 2013 (SP2013) farm

Hi,
I am trying to build a 3-tier SharePoint 2013 farm.
1. SQL Server 2012, Windows 2012 VM
2. DC Server, Windows 2012 VM
3. SharePoint 2013, Windows 2012 VM
I didn't built the DC server. Someone else did. However, I created about 14 service domain user accounts for SQL Server and SharePoint install and operation.
I was able to join the SQL Server into the SharePoint server farm using SharePoint 2013 Product Configuration Wizard. When I start the Central Admin, and click on Servers in the Farm, I only see the SharePoint server and SQL server,
but the DC server is not listed. Any suggestion on what did I miss?
Thanks
Jean

You cannot join the Domain Controller to your SharePoint farm. You must instead join each server from that farm to the domain that is served up by that DC. You will want to uninstall SharePoint and probably SQL before you do this. If it's
an option, I would re-provision your VMs completely and start fresh. Once you login to a new server, join that server to the target domain like this:
http://www.petri.co.il/join-windows-server-2012-to-domain.htm
You'd have to ensure that your DNS resolves to the target domain on the server being joined to the domain. If it doesn't, you can always use HOSTS entries to overcome that in the short term.
Once you've joined both the future SQL and SharePoint servers to the domain, you can install SQL Server and then SharePoint on their prospective servers to create your farm.
I trust that answers your question...
Thanks
C
|
RSS |
http://crayveon.com/blog |
SharePoint Scripts | Twitter |
Google+ | LinkedIn |
Facebook | Quix Utilities for SharePoint

Install sharepoint 2013 on Windows server 2012, Microsoft Identity Extensions issue !!!!!!!!!

Sharepoint 2013 comes with prerequisitesinstaller.exe to install the software required for the actual Sharepoint installation.
I 've installed Windows server 2012 in the R2 edition as well as Standard edition, but installing the prerequisites ends with an issue for the Microsoft Identity Extensions (MIE) on both versions (screenshot).
The 2012 R2 server has been updated with all latest files by executing Windows update.
In case of the Server 2012 R2, MIE is already installed , but somehow the Sharepoint installation is missing something.
I al;so tried removing default install to let prerequisiteinstaller.exe to install it's own version, but that did not help.
When I skip the prerequisites remaining items, the Sharepoint installation stops directly , requesting the missing items.
I've tried several Sharepoint server installation files, including the 180 days free version.
Screenshots will be uploaded after my account has been checked......

Hi Jay,
Installing SharePoint Server 2013 on a computer that is running Windows Server 2012 R2 could lead to unexpected behavior, therefore, Microsoft does not support SharePoint Server 2013 in Windows Server 2012 R2.
SharePoint Server 2013 with Service Pack 1 and SharePoint Foundation 2013 with Service Pack 1 will offer support for Windows Server 2012 R2.
Refer to:
SharePoint 2013 Support for Windows Server 2012 R2
In addition, as Dave suggested, for the sharepoint server issue, please post in the dedicated forum for a better response.
Best Regards,
Anna Wang
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 Support, contact [email protected]

Prepare sharepoint 2010 with sp2 environment on windows server 2012 R2

HOw prepare sharepoint 2010 with sp2 environment how i install sharepoint 2010 with sp2 in a windows server 2012
i mean
from scratch i just prepared a windows server 2012 R2 vm
and i set all required roels (Appserver,webserver etc) according to this link
http://social.technet.microsoft.com/wiki/contents/articles/12502.how-to-install-and-configure-windows-server-2012-for-sharepoint-2010.aspx
and i have sharepoint 2010 set up, and i downloaded sharepoint 2010 sp2
from this link
http://www.microsoft.com/en-us/download/details.aspx?id=39672
now should i install sp2 and install sharepoint 2010 binaries?
adil

SharePoint 2010 has no supportability statement for Server 2012 R2. I would not use it until Microsoft releases a supportability statement.
Even it has no supportability for server 2012, but sharepoint 2010 running fine in my server 2012 test environment
adil
You indicated you were using 2012 R2. SharePoint 2010 supports Server 2012 (non-R2) with SP2 media, but has no supportability statement for Server 2012 R2.
Trevor Seward, MCC
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Exchange 2013 Windows Server 2012 NLB and DAG on the same server

Hi all, I am installing Exchange 2013 infrastructure with two servers.
Both servers have the CAS and Mailbox roles.
For mounting on High Availability, will create a DAG.
Client Access I have no external Network Load Balancer.
I thought about installing the NLB servers in the DAG members, this could not be done before.
I do not know if in Windows Server 2012 and Exchange 2013
Can I install NLB on members of a DAG?
regards
Microsoft Certified IT Professional Server Administrator

Hi,
I’m afraid that WNLB and DAG cannot coexist in the same server. Because WNLB is incompatible with Windows failover clustering. If we're using an Exchange 2010 DAG and we want to use WNLB, we need to have the Client Access server role and the Mailbox server
role running on separate servers.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/ff625247(v=exchg.141).aspx
Thanks,
Angela Shi
TechNet Community Support

Windows Server 2012 VSS error "The system writer is missing"

Hello All,
I have a HP server that I have just installed Server 2012 standard, SQL Server 2012 and Sharepoint 2013.
When I try to take bare metal backup I get the error: "The system writer is missing", I have tried the backup as the local admin and domain admin.
The backup will only work if I decide to back up C:, once I select "Bare Metal" or "System State" the backup fails.
I have tried this solution: http://technet.microsoft.com/en-us/library/cc734021.aspx but have not had any luck yet.
When I run the command "vssadmin list writers" I can not see "System Writer" listed.
How can I add/turn on the System Writer?

Hi,
The system writer fails due to the fact that the trusted installer & system accounts are missing permissions to files in the directory %windir%\winsxs\filemaps\.
To resolve this issue, please run the following commands from an administrative elevated Command Window:
CD c:\windows\system32
Takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\filemaps\*.* /grant "BUILTIN\Users:(RX)"
For more information, please also refer to the following links:
Discussion Forum FAQ: VSS System Writer is missing.
http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/0b1eb10a-d666-4f5e-b657-c93b1d754a7f
Failure during Windows Server 2008 System State Backup & System Writer Missing
http://blogs.technet.com/b/chrad/archive/2009/11/18/failure-during-windows-server-2008-system-state-backup-system-writer-missing.aspx
Regards,
Arthur Li
TechNet Community Support

SQL server requirement for sharepoint 2013

Hello All,
currently i have installed SharePoint2013 in server farm mode, and i have used SQL Server 2008 R2 for DB. Can i use SQL Server 2012 for SharePoint 2013?
Thanks

SharePoint 2013 is compatible with SQL 2008 R2 and SQL 2012 so yes.
What you can do is "move" the SharePoint DBs from SQL 2008 R2 to SQL 2012 without restore or backup.
Link to msdn: https://technet.microsoft.com/en-us/library/cc512725(v=office.15).aspx
Here you have an example for SharePoint 2010 (is the same for SharePoint 2013): http://www.codeproject.com/Articles/664029/Migrate-SharePoint-s-SQL-Server-to-another-SQL-Ser
Here an different example: http://surya20p.blogspot.com.es/2013/09/migrate-sql-2008r2-sp2-to-sql-2012-sp1.html
Best regards.

How to install Windows Server 2012 Macbook Pro?

Need to ascertain if I can install Windows Server 2012 and Sharepoint Server on an Intel i7 Quad Core 4 GB RAM 15" Macbook Pro.
Else will have to buy a PC for this learning experience. Any help is welcome

Welcome to Apple Support Communities
Apple only supports client versions in Macs, but you should be able to install Windows Server. However, note that you may have problems installing Boot Camp drivers in order to make it work correctly.
If you only want a computer for Windows Server, buy a PC. Macs aren't completely ready for Windows Server editions even if they may work

SharePoint Foundation 2013 installed on Windows Server 2012 not sending out email notification

I have a server where i installed SP Foundation 2013 on top of Windows Server 2012. I have configured the SMTP as well as the outgoing SMTP in Central Administration
of SharePoint. When i create an alert on a document library, its did not sent any email notification on the changes made to the document in the document library. So, i created a workflow to send out email using SPD2013. The workflow run, but it cannot sent
out email with error saying that outgoing email is not configured correctly. I have checked with another server which i installed SP foundation 2013 on top of Windows Server 2008 R2 - its sending out email just fine using same configuration and outgoing SMTP.
I need help to resolve this issue or at least the cause of the problem.
Any help is greatly appreciated.

Try below:
http://social.technet.microsoft.com/wiki/contents/articles/13771.troubleshooting-steps-for-sharepoint-alert-email-does-not-go-out.aspx
Go to Central Admin ---->Operations----->outgoing email settings and verify that SMTP server is mentioned correctly
2) Test the connectivity with the SMTP server.
In order to do that follow these steps:
Open cmd
telnet <SMTP server name> 25 ( We connect smtp server to the port 25)
you should see a response like this 220 <servername> Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at date and time
Beware that different servers will come up with different settings but you will get something
If you dont get anything then there could be 2 possible reasons, either port 25 is blocked or
the smtp server is not responding.
For testing response from your server
For testing response say ehlo to it.
Type :
ehlo <servername>
output:
250 <servername> Hello [IP Address]
Now a test mail can be sent from that SharePoint server.
Now we need to enter the From address of the mail.
Type :
mail from: [email protected]
output:
250 2.1.0 [email protected]….Sender OK
It's time to enter the recepient email address.
Type : rcpt to: [email protected]
output:
250 2.1.5 [email protected]
Now we are left with the data of the email. i.e. subject and body.
Type : data
output:
354 Start mail input; end with <CRLF>.<CRLF>
Type:
subject: this is a test mail
Hi
This is test mail body
I am testing SMTP server.
Hit Enter, then . and then Enter.
output:
250 2.6.0 <<servername>C8wSA00000006@<servername>> Queued mail for delivery
Type: quit
output:
221 2.0.0 <servername> Service closing transmission channe
3) Check alerts are enabled for your web application
verify if the windows timer service is running or not.
Run this stsadm command to check that
Stsadm.exe -o getproperty -url http://SharePoint-web-App-URL -pn alerts-enabled
This should return <Property Exist="Yes" Value="yes" />
If you don’t get this, Enable alerts by:
stsadm.exe -o setproperty -pn alerts-enabled -pv "true" -url http://SharePoint-web-App-URL
If its already enabled, try turn off and turn on it back.
4) Check the Timer job and Properties
Go to
MOSS 2007: Central Administration > Operations > Timer Job Definitions (under Global Configuration)
In SharePoint 2010: Central Administration > Monitoring > Review Job Definitions
Check whether the "Immediate Alerts" job is enabled for your web application. check these properties:
job-immediate-alerts
job-daily-alerts
job-weekly-alerts
stsadm.exe -o getproperty -url "http://Your-SharePoint-web-App-URL" -pn job-immediate-alerts
The expected output is:
<Property Exist="Yes" Value="every 5 minutes between 0 and 59"/>.
If you don’t get this, run the following command to set its value.
stsadm.exe -o setproperty -pn job-immediate-alerts -pv “every 5 minutes between 0 and 59" -url http://Your-SharePoint-web-App-URL
5) Check whether the account is subscribed for alerts and it has a valid email account. This should be the first thing to check if the problem persists for some users not for all.
6) Then check if at all those users have at least read permission for the list. Because the first mail should go out for every user without security validation but the next ones won't be delivered unless the user has at least read
permission.
7) If it is happening for one user, can also try to delete and re add the user in the site.
8) Most importantly , you should try this one.
Run this SQL query to the content db < Select * from Timerlock>
This will give you the name of the server which is locking the content database and since when.
In order to get rid of that lock
Go to that server which is locking the content db and then restart the windows timer service.
within some time it should release the lock from content db, if not then at the most stop the timer job for some time
Once the lock will be released then try to send some alerts
You will surely get the email alert.
I found this is the most probable reason for alert not working most of the time. We should start troubleshooting with above steps before coming to this step for any alert email issue but from step 1 to step 7 are best for new environments or new servers.
If the issue is like this ,alert was working before and suddenly stopped working without any environmental change then above conditions in step 1-7 should be ideally fine.
Even after this if it is not working, then you can try these few more steps too
9) Try re-registering the alert template:
stsadm -o updatealerttemplates -url http://Your-SharePoint-Web-App-URL -f "c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\XML\alerttemplates.xml" -LCID 1033
10) Try to clear the configuration cache
If this helped you resolve your issue, please mark it Answered

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.

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

Error while installing Microsoft Identity Extensions Setup during installation of SharePoint Foundation 2013 on Windows Server 2012

Hi All,
When i try to manually (no internet connection on the server) install SharePoint 2013 Prerequisites on Windows Server 2012 I get the below error
I have installed .Net Framework 3.5, 4.0 and Windows Identity Foundation using Add server roles or features from the server manager.
From Software & Hardware requirements for SharePoint 2013 give
Prerequisites for SharePoint 2013 I can see that the identity extensions are available only of Windows Server 2008 R2 and not for windows server 2012. Can you please provide the link for windows server 2012?
I have installed all the prerequisites required except Microsoft Identity Extensions.
Raghavendra Shanbhag | Blog: http://moss-solutions.blogspot.com
Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
Disclaimer: This posting is provided "AS IS" with no warranties.

I fixed it by installing Microsoft Identity extensions from command line, please find command line below.
C:\Windows\System32>msiexec.exe /i "C:\SharePoint2013ServerFiles\prerequisiteinstallerfiles\MicrosoftIdentityExtensions-64.msi" /quiet /norestart
Note: In the above command C:\SharePoint2013ServerFiles\prerequisiteinsTallerfiles is the path where I had downloaded all the prerequisites for SP2013
This will install Microsoft Identity Extensions and creates registry entries, which will help the SharePoint 2013 Prerequisite installer to complete the setup
For more details check out
here
Raghavendra Shanbhag | Blog: http://moss-solutions.blogspot.com
Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
Disclaimer: This posting is provided "AS IS" with no warranties.

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
Russ

It 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

Windows Server 2012 R2 - SharePoint 2013

Similar Messages

Maybe you are looking for