Sharepoint 2013 + Windows Server 2012 as reverse proxy

Hello All -
I'd like to ask if anyone has any experience with the new Windows Server 2012 (reverse) proxy, in providing a single sign-on service to Sharepoint 2013.
Scenario:
My client has a Sharepoint 2013 with 3 web applications (portal, teamsites, mysites). All three URLs are available externally via HTTPS only. All clients have AD credentials (no requirement for claims based authentication), although this includes 3 domains
in two different forests (trusts exist). Everything is already configured to allow clients access from domain-joined devices.
My client would like mobile devices (not domain-joined) to be able to access the three web applications without repeated logon prompts. Browser default settings must be used, they do not want to instruct people to perform any configuration on their mobile
device - it all has to work "out of the box" from the client side. Clients will be using iPads and iPhones with Safari, Windows Phones, Androids etc.
I'm considering proposing the use of a reverse-proxy, and rather than using the now depracated Forefront TMG or probably soon-to-be depracated UAG, I would like to jump straight in to the new and very cool looking Windows 2012 proxy server.
It's my understanding that this will provide a single sign-on service in this scenario. I'm unsure whether an ADFS server is also required even for pass-through, the information available is unclear, and also whether any special configuration is required
to a domain controller (DCs in the environment are all 2008R2, with 2008R2 functional level).
I would appreciate it if anyone could give an overview or point me in the direction of some accurate documentation regarding all of the above. Most importantly, if any of my assumptions above seem incorrect, please let me know.
Thank you!
sysadmin

I've heard no supportability statement with SharePoint and the Web Application Proxy (likely because it isn't GA yet). However, it does use ADFS for SSO, so you'll have to SAML-enable your Web Applications. The only downside to this is if you
use anything that is SAML-unfriendly, like PowerPivot [Data Refresh] and at least in 2010, Visio Services and InfoPath Forms Services.
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.

Similar Messages

Getting error 'proc_createNewAppSiteDomainIds' when I try to install SharePoint on Windows Server 2012

I have a Windows Server 2012 setup with SQL 2012 SP1 installed. I have tried to install Sharepoint Foundation 2013 and also full blown Sharepoint version...but during the wizard setup I always get 'Cannot find the object 'proc_createNewAppSiteDomainIds',
because it does not exist or you do not have permission.
The install created my db in sql 'team1p-vm' but that is it.
What am I missing?
During the install I have tried both Complete and Stand-alone as the Server Type.
When it gets to the product configuration wizard I use:
Create a new server farm
I enter my database server name: team1p-vm
Database name: SharePoint_Config
I enter my db access account
I enter a farm security settings passphrase
I use 17012 as my port number, select NTLM
I see my configuration settings...
Click Next and I get the error on task 3 of 10.
here is the dump of the application Log: At least some of it.
An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Cannot find the object 'proc_createNewAppSiteDomainIds', because it does not exist or you do not have permission.
System.Data.SqlClient.SqlException (0x80131904): Cannot find the object 'proc_createNewAppSiteDomainIds', because it does not exist or you do not have permission.

Can you see if there is anything in the SQL ERRORLOG on the SQL Server that may help at the time you see this error?
Does your user account (the user you're installing SharePoint with) have the sysadmin fixed role in SQL Server?
Trevor Seward
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

SharePoint 2013 - SQL Server 2012 PPIV - using a PPIV workbook as a data source - getting PPIV web service error

I created a PowerPivot (SQL Server 2012 SP1) workbook and uploaded it to SharePoint 2010 Portal and started using it as a data source in an excel file. This worked fine and we saw no issues with it until we moved to SharePoint 2013 environment.
I uploaded the same PowerPivot workbook (source workbook) to SharePoint 2013 Portal and now trying to use it as a data source. I tried to change connection properties so that I could use the new portal address for the workbook. When
I try to save my changes, I see that OLAP queries are getting fired "Refreshing OLAP cube" shows up in the status bar, but eventually after running these OLAP queries (I would say after a minute), I get the following error -
Couldn't find anything specific in SharePoint logs or maybe I wasn't looking for the right thing.
Has anyone seen this issue? Why would PPIV service throw an error after running for a while? Is it a timeout issue of some kind? How can we take care of this?
Thanks,
Sonal

ULS log showed the following exception: The maximum number of allowed sessions per user has been exceeded.
Under Excel Services global settings, max limit is set. Default is 25, increasing it resolved this issue.
Thanks,
Sonal

SharePoint 2013, SQL Server 2012 SP1 Enable RBS for Additional Content Databases

We Enabled RBS in our SharePoint 2013 Environment recently. The time when we Configuring we had only one Content Database and we successfully configured. now we created more web applications and we need to enable RBS for newly created Content Databases.
we searched and tried lots of approaches, but we cudn't manage to achieve this. can anyone help us to enable RBS on additional Content Databases. (No offense but direct instructions would be great rather than providing links).
Thank you!

Here is step by step instruction with screenshot
http://thesharepointfarm.com/2011/03/enabling-rbs-on-multiple-content-databases/
Try to run
run this command on the SharePoint server: msiexec /qn /i rbs.msi REMOTEBLOBENABLE=1 FILESTREAMPROVIDERENABLE=1 DBNAME=”WSS_Second” FILESTREAMSTORENAME=FilestreamProvider_1 ADDLOCAL=EnableRBS,FilestreamRunScript DBINSTANCE=”DBServer”
Thank you so much for the reply Indrajeet. we followed the instruction to the letter but when we try the command, it failed. while doing some search, we came across an interesting Article.
http://rudolphoravec.blogspot.com/2012/10/remote-blob-storage-rbs-and-sharepoint.html
And surprisingly it is Working.

Can't install Windows Server 2012 Web Application Proxy

Hello,
I'm using a Server 2012 R2 evaluation copy of windows. Windows is fully patched. I'm having trouble installing the Web Application Proxy using the Ms recommended method - when I use:
https://technet.microsoft.com/en-gb/library/dn383662.aspx#BKMK_PSstep2
The role service is not listed and if I use PowerShell "Install-WindowsFeature Web-Application-Proxy -IncludeManagementTools" I receive an error regarding an invalid role or feature name.
My server has a certificate installed in the personal computer store with private key.
What am I missing?
Thanks
IT Support/Everything

Hi,
Sorry for the delay reply.
For Windows Server 2012R2 standard, we could see the web application proxy.
Please check the image below:
Regards.
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]

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 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

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

Error while uninstalling and then re installing sharepoint 2013 on same server(windows server 2012)

Hi All,
I have installed SharePoint 2013 prerequisites successfully on windows server 2012. While installing SharePoint 2013, system struck on for several minutes. I have restart my system manually. Later I then installed prerequisites which showed a successful
lessage. But When I try to install SharePoint 2013. I am getting the following error:
trial editions and lincensed editions of SharePoint, Project Server, and Office Web apps products may not be installed on the same server.
I am unable to find solution for this issue. what is the solution for this?
Thanks in Advance..
Prem Kumar

To be honest, the quickest thing you could do (and what I would do regardless) is re-build the server (re-install Windows).
Trevor Seward
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.

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

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]

SharePoint 2013 Enterprise with SP1 on Windows Server 2012??????? What am I missing?

Hi there,
As per MS - SharePoint 2013 Enterprise SP1 is compatible with Windows Server 2012 R2.
I have Windows Server 2012 R2 installed - now it does not let me install SharePoint 2013 Enterprise (Standard without SP1).
AND SP1 can ONLY be installed AFTER SharePoint 2013 Enterprise is installed.
So how to install SharePoint 2013 Enterprise with SP1 on Windows Server 2012?
Thanks.

You can download it at the Microsoft Volume Licensing Service Center:
https://www.microsoft.com/Licensing/servicecenter/default.aspx
or at the Microsoft Developer Network:
http://msdn.microsoft.com/
Please note that if you do not have access to either, you will have to work with the vendor who sold you SharePoint 2013 to get you a new ISO with SP1, or you will have to find a way to make a slipstreamed version on your own. I'm really hoping you
have VLSC or MSDN access, as this will make things much easier for you.

Sharepoint 2013 + Windows Server 2012 as reverse proxy

Similar Messages

Maybe you are looking for