Let me give you a brief about what Office Web App Server is for those who don’t know what it is used for. Its basically a server which provides the Office Services to edit or view the office documents in the browser itself without the need of office installed on local machine of end users.
Installing OWA Server on Windows Server is not a pain until its Windows Server 2012 R2. Normally one would think like SharePoint it would give the list of pre-requisites which would be installed automatically but it doesn’t do that.
Today, I got this weird error on my SQL script in Visual Studio 2017, where in it was highlighting various SQL statements when I copied the SQL file and added it to the project. Below is the exact error in Visual Studio 2017.
Error SQL70001: This statement is not recognized in this context.
However, the solution is simple. Select the file in the solution explorer, click F4 and change the Build option in properties window to none instead of build.
This seems pretty simple as you can just set the properties of SPContentDatabase and you are good to go. However, this didn’t work atleast in my case.
I was creating a new farm from an existing farm due to project requirements, but I came across a situation wherein I was not able to remove the server from the farm using the SharePoint 2013 UI(server was already removed using the command or you can remove it by using configuration wizard on the server to be removed).
So, the error message which I was getting when I was trying to remove the server from the UI was “cacheHostInfo is null“.
Below is the solution to this problem which I followed and it worked.
Mysites configuration is pretty simple which has the basic pre-requisites:
- User Profile Service must be running
- Mysite host site collection should be created
- Mysite managed path for users’ site should be created
- mysites should be configured
- mysite web application should have self site creation on.
- Also, the end users who want to create mysites should have permission policy level of “Create Subsites – Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites.“
In general, we can delete the columns using UI from SharePoint pretty easily. But some columns are not allowed to be deleted using UI but are allowed to be deleted using PowerShell. But there are some columns which are not deleted from PowerShell as well without some tweaks.
Recently, I ran into trouble in which I couldn’t find a simple way to find the admin database name in MOSS 2007 as its not displayed in Central Admin and there is no PowerShell supported in MOSS 2007 so we have to deal with stsadm tool.
Orphaned Content Database – By orphaned content database I mean that the content database is not associated to any web application and is not visible by using Get-SPContentDatabase command.
So, what is the need of removing the Orphaned Database. Recently, I accidentally removed a database and added it back but somehow it was not adding back and displaying the message that database already exist when I was trying to add the database using the UI or using PowerShell.
So, the way to see is the database present in the farm is to run the following command:
Get-SPDatabase | Select Name, Id
It would display the list of all the databases associated with any service application or web application or any other database present/associated with SharePoint. In this list the orphaned content database would also be listed.
In order to remove just get the database and execute delete method. It would only remove the association with the farm.
$db = Get-SPDatabase -Identity "<GUID>"
Now again, if you run the following command the orphaned content database would not be present anymore.
Get-SPDatabase | Select Name, Id
I couldn’t find any blog/article anywhere related to this, hope it might help someone.