I'm having trouble trying to do a simple backup of our 2-server SharePoint 2010 farm. I'm running the backup process with a Powershell command, backing up to a UNC shared folder on the SharePoint server.
I have SP2010 on one server and SQL 2012 on another. SQLserver.exe is being run by a new Managed Service Account.
We have a Microsoft Online Services Tenant and we're looking at the following services:
Office 365 E3
Sharepoint Online Plan 2
Office 365 E3 includes Sharepoint Online Plan 2 and also a bunch of other stuff like Lync and Exchange Online.
Is it possible to mix both these services on one Tenant, and also switch between them, etc?
For example:
Can you have 100 people on Office 365 E3 and 100
I have an SQL 2012 AlwaysOn Cluster and need to setup SharePoint reporting services.
Within SharePoint farm configuration it reports that the SQL server agent is not running.
Since I have multiple SQL nodes to which the connection can fail over to any, how do I handle the SQL server agent or is this clustered also?
Does the downloadable SharePoint reporting SQL script need to be ran on each nod
I have SharePoint 2007. When the database backups run using SQLCMD SharePoint sites go into read-only. Users can't add anything to the sites the buttons are grayed out. On the backend the databases do not get set to read-only. My question is this, is this normal with SharePoint? I have read some forums that say SharePoint does this by default but the information is a little murky.
Thanks
Bryan
Simple two-server farm:
One SharePoint Foundation 2010 WFE on Windows Server 2008 R2 Std SP1
One SQL Server 2008 Std SP1 backend on Windows Server 2008 SP2
I've just installed Service Pack 1 (14.0.6029.1000) on the SharePoint server and rebooted.
I am accessing the built in SharePoint 2010 on SBS2011 via Microsoft Office Excel and Word.
When saving a file, I get prompted from within Microsoft Office 2010 Word/Excel for credentials - entering the correct credentials just prompts the window again.
I'm trying to attach a WSS 3.0 content database to a new (new after I uninstalled and started over) SharePoint Server 2010 farm. I followed the Attach Database procedure and saw no issues with the preupgradecheck. Installation and general setup of the farm was flawless, but I've been stuck for hours trying to attach this content database.
We run SharePoint 2007 in our environment and currently have a non-transitive, external trust setup between the two domains because we're planning on migrating to SharePoint 2010. Our SQL Server is in the domain 2, while domain 1 has the front end web servers.
We run SharePoint 2007 in our envirnoment and currently have a non-transitive, external trust setup between the two domains because were planning on migrating to SharePoint 2010. Our SQL Server is in the domain 2, while domain 1 has the front end web servers.