Archive for the ‘Administration’ Category


This error popped up when I changed my service account for Search Service & the Search Host Controller Service as these services were using the farm admin account. Below are some of the solutions which provided were,

  • Removing the extra space at the end of ‘PSModulePath’ – This didn’t work for me
  • Adding proper permissions in the database – Which is perfectly fine already
  • Repair SharePoint under Control Panel – This is not going to be a good option

The solution was to provision the WSS usage application proxy. Use the below command to do the same.

$UP = Get-SPServiceApplicationProxy | where {$_.TypeName -like "Usage*"}
$UP.Provision()
Advertisements

For any existing app you have developed & deployed, to update the app, you use the same product ID in the app manifest that you used for the original version. The version number in the app manifest should be greater than the version number of the original app or the most recent update. Within 24 hours after you upload your update to an organization’s app catalog, and within a week of uploading it to the Office Store, a notification that an update is available appears next to the app’s listing on the Site Contents page of every website where it is installed.

When you are developing an update, you don’t want to wait 24 hours every time you upload a new version to your test SharePoint app catalog.

  1. After the latest update is uploaded to the app catalog, open the Site Contents page on the website where the app is installed and choose the button on the app’s tile.
  2. On the call out that opens, choose the About tab. On the About page that opens, there is a notice that a new version is available.
  3. Choose the Get It button. The Site Contents page reopens, and there is a notice on the apps’s tile that the app is being updated.

UpdateApp

Image Source: msdn

Why it takes 24 hours for an app to update is because SharePoint checks every 24 hours for updates to installed apps. A farm administrator can set this to another value by using the following SharePoint Management Shell command, where n is the number of hours between checks.

Set-SPInternalAppStateUpdateInterval -AppStateSyncHours n

If the value is set to 0, then the check is made every time the built-in timer job Internal app State Update executes, which by default is every hour. Farm administrators can use Central Admin to change the frequency of the timer job or run it immediately.


In SharePoint 2010, you may try deploying or upgrading a solution using stsadm and end up with the below error.

A deployment or retraction is already under way for the solution “Solution Name”, and only one deployment or retraction at a time is supported.

This issue occurs if a SharePoint solution deployment fails, yet the timer job is created and not running, you will be unable to redeploy or retract the solution.

To resolve this error and redeploy the solution, follow the below steps.

  1. Go to Central Admin -> System Settings -> Manage Farm Solutions.
  2. Cancel the deployment for your solution. It may have the status failed or deploying, which means deployment is not successful.
  3. Now redeploy your solution.

Hope this helps .


Even with a valid license key, when I tried to open any of my SharePoint site, “The trial period for this product has expired” error popped up.

Digging more in to it, I found my Central Administration site’s application pool was running under Network Service account instead of the farm administrator account. And for some reason Network Service did not have the rights to license the product. I just changed the application pool identity of my site to the Farm administrator account.  You can do this either through the Service Accounts  section of Central Admin or through the IIS. Don’t forget to reset IIS after making the change. Aah!! My site worked like a charm 🙂


In some cases you want to increase the size of the SharePoint DB. So we will be adding extra disk, detach the Db & move it to the newly added  drive. Following are the steps followed.

  1. Take backup of the DB which the site is using from SQL server management studio.
  2. Now go to Central Admin Website -> Application Management ->SharePoint Web Application Management -> Content Databases.
  3. Select the appropriate web application. It will display the content DB(s) used by that application.
  4. Now click on the content DB which opens Manage Content Database Settings page.
  5. Note down all the details in this page, since we require this later. (A screen shot will be a better option).
  6. Select Remove content Database & click OK & again OK.
  7. Now we have to detach our database. To do so go to SQL Management studio & right click on the database and select Take Offline. Once the process is done again right click & select Detach.
  8. Now go to “drivename:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data” and files where the DB is already located.
  9. Copy the mdf & ldf file and place it in a new drive in same location “drivename:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data”
  10. Now go to SQL Management studio right click on the “Databases” in object explorer and click Attach.
  11. Click on Add, browse to the mdf file you copied & click OK.
  12. Now do follow step 2 & 3. In this case we will not see any content DB’s associated with the application.
  13. Click on Attach Content Database & fill in the details which we got in step 5.
  14. Note the DB name should be same as the previous one we detached.
  15. That’s all & your DB is migrated.