With the recent release of SharePoint 2016, I decided it was time to perform an install in a Lab environment to check out all the new bells and whistles. So, I went over to codeplex and downloaded the latest version of everybody’s favorite SharePoint installation script, AutoSPInstaller*.
*At the time of this writing the version of AutoSPInstaller was v3.99.51.
The lab environment consists of four servers:
(2) Front End Servers
(1) Application Server
(1) Search Server
(1) Database Server
Each server is running Windows Server 2012 R2 Standard Edition and SharePoint 2016 was to be installed on the Front End, Application and Search servers.
Over the past few years, the healthcare industry has undergone a complete overhaul of how it processes information. This was brought about by a growing list of new and complicated regulations handed down by federal and state governments that stem from the Healthcare Insurance Portability and Accountability Act (HIPAA) and the Patient Protection and Affordable Care Act (ACA), designed to improve the efficiency and effectiveness of the industry. These regulations include standardization of the electronic transmission of Electronic Data Interchange (EDI), which also protect the security and privacy of electronically transmitted information provided by their patients.
These mandates created an immediate challenge to healthcare organizations, because it required the industry to take increased ownership and control of Electronic Health Records (EHR). In order to meet this demand quickly, healthcare providers scramble to leverage a variety of methods to manage their EDI…
I was tasked last week with learning how to install SharePoint 2010 as part of our SharePoint IT Training Module. It’ll be easy they told me, or maybe they didn’t tell me that and I told myself that. It’s only an installation, how hard can it be? Famous Last words. Well after a long time setting up every little thing I get hit with this error and spend a day trying to get past it trying a number of different strategies :
We’ve been hearing Q1 2014 as a release date for SharePoint 2013 SP1 for some time now, and most of us have been thinking we’d get that date at SharePoint Conference 2014. The conference Yammer feed was just updated with the news that SharePoint 2013 SP1 has been released.
SP2013 SP1 Download Info
Ensure you follow all the guidance listed here when installing:
Windows Server 2012 R2 Support
One major change we’ve been waiting for is support for Server 2012 R2. You *must* use the slipstreamed version available for download via MSDN, VSLC, or MPN.
The issues fixed are listed in the download at the following URL:
Stephan Gossner has provided an FAQ at the following url:
I was trying to get the new workflow engine installed and configured with SharePoint 2013 but was encountering an error in the Service Bus configuration step.
Installation Instruction for Workflow Manager and SharePoint 2013 Workflow Configuration:
The full installation steps are provided here (in a video series): http://technet.microsoft.com/en-us/library/dn201724.aspx and here: http://technet.microsoft.com/en-us/library/jj193478
The instructions provided above are pretty detailed and helpful except that I kept getting this error while configuring workflow manager and there was not much to go with online.
Program C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricDeployer.exe exited with error: Windows Fabric deployment failed.DeploymentValidator:
warning: The Fabric Data Collection Agent is disabled for this deployment.
None of the declared nodes is for the current machine.
Finally i looked at the hosts file on the Developer VM and noticed that I had an entry for 127.0.0.1. Since I was using FQDNs for my workflow configuration, I commented this line and…
I recently installed and configured a small SharePoint farm containing two virtual servers using Oracle Virtual Box and decided to share my experience of the process. For the most part the configuration is simple, but there are a number of common small discrepancies that can be the difference between your servers communicating correctly, or you throwing your laptop out of the window after a week of errors. I will not be going through a click by click summary of setting up the SharePoint farm, and will instead be giving a high level overview of the process and spend more time on these issues I ran into.
I recently came across a frustrating issue when looking at ULS logs for a client with a SharePoint 2010 installation. We were seeing huge numbers of repeated errors stating :
Performance Counter OS (pdh) call failed with error code
PDH failure on counter \<servername>\Sandboxed Code Process
Pool\\Processes Stopping with error Unknown error (0xc0000bc0)
Unable to create system performance counter <server name>\Sandboxed
Code Process Pool\<counter name>\. The following exception was
thrown: System.ComponentModel.Win32Exception: Unknown error
They were so prevalent they were clogging up the logs and making it impossible to diagnose the other issues we were looking at. (See screenshow below)
To try to resolve the issue, I opened performance monitor on the SharePoint server and look at the counters myself.
I launched the tool (Admin Tools –> Performance Monitor), selected Performance Monitor under the Monitoring Tools folder, then clicked the [+] icon on the toolbar to add counters.
Under the Available…
I recently installed SharePoint 2010 on my client machine to investigate some of the BCS and Search features for a client project. SharePoint 2010 now allows a standalone installation on Vista x64 SP1 or higher and Windows 7 x64, which is a major improvement over the remote development nightmare that existed with MOSS 2007.
For instructions on the proper method for installation, read the following MSDN article : Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008
Description of Issue
After installation, I was repeatedly unable to log onto SharePoint using Firefox, repeatedly getting “Access Denied” errors after typing in my domain account and password. (Note: This was the same account I used for installation).
Switching to IE allowed me access to the central administration site, however there were many functions and features that were unavailable…