At one of our customers we had the error message, that the managed metadata service or the connection is not available. I am not sure, but it may be due to an update we installed a few days earlier.
I read a post which says that the application pool account does not have enough rights to read the registry. The suggestion was to run the following powershell script:
psconfig -cmd secureresources
After i did this, it starts a script similiar to the configuration wizard with three steps and after that we did an issreset. It was working fine after doing this. Hope this helps you some day.
Powershell has great functionalities. One of those is the sendmail function. We used it like a timer job for reminding people to do something special. We built a small script which checks certain list items in SharePoint and fetches the title, the create date and the author. If the item is older than 30 days, the author gets a reminder to do a task on the item.
The powershell is stored as scheduled task in windows. But i’d like to share the sendmail function with you.
$to = "email@example.com"
$subject = 'Subject Text'
$body = 'Body Text'
#SMTP server name (which is configured in SharePoint)
$smtpServer = "SMTPServer"
#Creating a Mail object
$msg = new-object Net.Mail.MailMessage
#Creating SMTP server object
$smtp = new-object Net.Mail.SmtpClient($smtpServer)
$msg.From = "firstname.lastname@example.org"
$msg.subject = $subject
$msg.body = $body
$msg.isBodyHTML = $true
That’s it. Now you can put some values from the list into the body or subject or even the receiver address (to). Enjoy it.
In the last weeks we resolved an error, which might be interesting for others as well. We got this Error message, that there was an error for a file from a specific module and that the list was not available.
It came up at several features, if we tried to activate them. It was always a list which were used by the publishing features. The publishing feature were not activated, but could not be activated using the UI.
Therefore we used stsadm, to resolve it.
stsadm -o deactivatefeature -id f6924d36-2fa8-4f0b-b16d-06b7250180fa -url "http://server/sites/sitecollection" -force
stsadm -o activatefeature -id f6924d36-2fa8-4f0b-b16d-06b7250180fa -url "http://server/sites/sitecollection" -force
After that it worked well again. We assume that it had to problems with the publishing features.
I already made a post about the word automation services in SharePoint 2010. I then used Powershell to convert a word document to a pdf, which both were stored in a document library in SharePoint.
That was typically for 2010:
- Solutions have to wait for a timer job to complete the converting process
- Files can only be in SharePoint
- No UI
- No message if it’s done
The reason to create a new post is, that SharePoint 2013 offers a lot more things now which make the word automation services powerful and interesting in every direction. It now can offer
- Conversion process is synchronized, immediate response is possible
- Convert one file at a time per request
- Setting options in Central Administration for simoultaneous requests
- Notify / Updating files in SharePoint items if conversion is ready
- Support of streams
- Convert streams as inputs and outputs for file operations
- Storing streams in the application server and worker manager not in the database
Let’s see how we can use it. I created a small console project to check the functionality. I found some cool functions which I used from this post and expand it to my needs. A second post was about using it as web service which might be really cool if you need a converter service for other applications or applications within sharepoint. Continue reading
If you are responsible for a SharePoint Farm or developing things for a SharePoint farm, I bet you’ve heard things like “it’s not supported by Microsoft to do…” and those things mostly dealing with database operations like updating values or settings. But what is about doing administration stuff like defragmentation of indices or shrinking a database?
In this post I try to make some things more clear. My information is based on this technet article, so I was not creative at all. The things I will point out are valid for SharePoint 2010.
Routine database maintenance is essential for the smooth operation of Microsoft SharePoint 2010 databases
That means that we have to do some work on the SQL Server. Microsoft recommends to check database integrity, defragment indexes by reorganizing or rebuilding them as well as set the fill factor for your server.
In SharePoint 2010 the health analyzer evaluate the health of database indexes and statistics daily and reports them at the central administration. But this happens only for some SharePoint databases like
- Configuration DB
- Content DBs
- User Profile Service Application Profile DB
- User Profile Service Application Social DB
- Web analytics service application reporting DB
- Web analytics service application staging DB
- Word automation services DB
Let’s see what are the details and what you should not do. Continue reading