Tag Archives: SharePoint 2010

Road Trippin – Day 17 – Homeward Bound – Canberra to Newcastle NSW

Canberra is the capital of the best country on the planet, Australia. It is where the politicians meet to govern and the city is where you find every government department and museum you can think of. It reminds a lot of America’s ‘Washington Mall’.

On my way out of Canberra I took a couple of photos at the Parliament House which was just around the corner, and having recently visited Canberra in October 2017 I didn’t want to do any site seeing.

The morning of the ride the weather was probably the worst I’ve experienced on this trip with heavy rain and strong winds which made visibility poor so much so that I could barely see through the helmet visor and then through the windshield on the motorcycle.

I made it!! Once I got out of the rain the ride improved and I carried on my way to the Best Western Blackbutt Inn just outside of Newcastle. My stay here was comfortable, but it’s not in the city area so if you’re here for a night then it’s probably best to stay where the action is.

On the way to Newcastle NSW I stopped at the Big Sheep and the Australian Reptile Park which are both great stops if you’re with family. The reptile park has crocodiles aplenty and other reptiles native to Australia. Entry was expensive and so was everything else!!

And just like that I was at the Best Western Blackbutt Hotel where I spent the night after a decent chicken and ham Wellington from their $15 menu.

I got my laundry done at a BP service station laundromat about 3kms away and then returned to the hotel for a good night’s sleep.

Tomorrow I head to Coffs Harbour!! Catch ya then…

InfoPath 2013 Add Colour Coding to the Status of a Form

  • Edit your Form Library page.
  • Add a Content Editor web part to the page and move it below the form library.
  • Open the properties for the Content Editor web part and add the path to the StopLight.txt file. Make sure you upload this file to the Site Assets library in the same site where your form lives.
  • Set the Content Editor Appearance property to hidden and click OK to save the changes.
  • Add a new calculated field column to the Form Library and call it Overall Status (you can call it anything you like).
  • In the formula section add the following: StopLight Formula
  • Save the new column and return to the Form library.
  • Make any additional changes to the form library, for example set the Style to Newsletter to give it a neat professional look.

Download the StopLight.txt file here.

Any questions, let us know in the comments section below.

InfoPath 2013 Moving a Form from an Existing Form Library to a New Form Library

  • Create a document library to store the InfoPath form content type.
  • Publish the form as a content type to the site, save it in the new library created in step 1, then promote any new columns as site columns.
  • Create a new form library and add the new content type as the default.
  • Save a form from the old library by ‘downloading a copy’, then upload it to the new form library.
  • Relink this form in the new library.

It should open and function as normal.

Certified Solutions Australia - SharePoint 2013

Upgrade SharePoint 2010 My Sites to SharePoint 2013 My Sites

Upgrading My Sites from SharePoint 2010 to SharePoint 2013 can be a challenge and some of the information found on the Microsoft site can be a little misleading.

I have put together a few steps that worked for me. The process includes upgrading the Managed Metadata and User Profile Service Applications along with the My Sites content databases.

Disclaimer: This posting is provided “AS IS” with no warranties. Please carry out the tasks below in your Development environment first. I suggest using Hyper V to take a snapshot of your farm first including the SQL Server before carrying out the upgrade.

Microsoft links to refer to

Upgrade My Sites: http://technet.microsoft.com/en-us/library/dn479424.aspx
Upgrade Service Apps: http://technet.microsoft.com/en-us/library/jj839719.aspx

The upgrade process is as follows

Step 1: Copy and restore the following databases from SharePoint 2010 SQL Server to your SharePoint 2013 SQL Server.

– ProfileDB
– SocialDB
– SyncDB
– MetadataDB
– WSS_Content_MySites

The WSS_Content_MySites is the database that holds all the My Sites in my SharePoint 2010 environment. The project I was working on had their My Sites and SharePoint Sites all in the one database so I had to use the Move-SPSite powershell command to move the sites to a dedicated WSS_Content_MySites database for My sites.

Move-SPSite -DestinationDatabase WSS_Content_MySites

Next if you have a setup account you use to run your queries in your farm, make sure this account has DBOwner rights on the database. This account can be the FARM account or a Setup account like the one you used to run the SharePoint installation.

Step 2: Upgrade the Managed Metadata Service Application, but first delete the existing Managed Metadata Service Application and User Profile Service Application in your SharePoint 2013 environment (if it exists), but ensure that both the Managed Metadata Service and the User Profile Service (not synchronization service) are started on the Application Server.

I have a Service Application Pool that I use for most of my Service Applications. If you want to create a separate service application pools for the Managed Metadata Service Application, then please make changes to the commands below to suit your needs.

On your Application Server, log in with your Setup account, open a Powershell command window in Administrator mode and run the following commands:

Get-SPServiceApplicationPool |ft name

$applicationPool = Get-SPServiceApplicationPool -Identity 'Service Application Pool Account'

$mms = New-SPMetadataServiceApplication -Name 'Managed Metadata Service Application' -ApplicationPool $applicationPool -DatabaseName 'MetadataDB'

New-SPMetadataServiceApplicationProxy -Name ‘Managed Metadata Service Application’ -ServiceApplication $mms –DefaultProxyGroup

IISReset /noforce

The above Powershell commands will create a new Managed Metadata Service and upgrade the MetadataDB database.

Now, delete this new Managed Metadata Service Application by selecting it under Service Applicatons in Central Administration and clicking the Delete button at the top of the page. DO NOT check the box to delete the upgraded database. We need this so leave the database as is, only delete the service application.

After you have deleted the service application, re-create it, but this time via Central Administration and in the Database box, give it a database name like MetadataDBRemoveMe for example.

Once the service application is created, we need to change the database and make sure that it uses the upgraded database. So, run the powershell command below to do this:

Set-SPMetadataServiceApplication -Identity "Managed Metadata Service Application" -DatabaseName MetadataDB

Then run IISReset /NoForce

Possible error: “The managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.”

Possible solution: Give the Service Application Pool Account DBOwner rights to the upgraded Metadata database in SQL Server. Also give the service application pool full control permissions to the Service Application in Central Administration.

Make sure there are no errors when you click the Managed Metadata Service Application under Service Applications in Central Administration. It is important that there are no errors, do not proceed to the next step if there are errors.

Step 3: Create a new My Site Web Application in Classic mode.

New-SPWebApplication -Name "MySite WebApp" -ApplicationPool "MySiteAppPool" -AuthenticationMethod "Kerberos" -ApplicationPoolAccount (Get-SPManagedAccount "Contoso\svc-sp2013DevAppPool") -Port 80 -URL "http://mysitesdevsp2013.contoso.com.au" -HostHeader "mysitesdevsp2013.contoso.com.au" -DatabaseName WSS_Content_MySitesRemoveMe

Do not create the My Site Host site collection after creating the Web Application above.

Create a new My Sites User Policy (See Technet documentation regarding creation My Sites for SharePoint 2013 for details)

Don’t try to configure Self-Service site creation as there is no root site collection.

Step 4: Create a new User Profile Service Application.

Run the following Powershell scripts in Administrator mode as you did above:

Get-SPServiceApplicationPool |ft name

$applicationPool = Get-SPServiceApplicationPool -Identity 'Service Application Pool Account'

$upa = New-SPProfileServiceApplication -Name 'User Profile Service Application' -ApplicationPool $applicationPool -ProfileDBName 'ProfileDB' -SocialDBName 'SocialDB' -ProfileSyncDBName 'SyncDB'

New-SPProfileServiceApplicationProxy -Name ‘User Profile Service Application’ -ServiceApplication $upa -DefaultProxyGroup

IISReset /noforce

Next, delete this newly created User Profile Service Application, but do not check the box to delete the database too. We need these upgraded databases so leave them intact.

Create a new User Profile Service Application but for the database names, enter the name for the upgraded databases instead.

Once the new User Profile Service Application is created, select it under Central Administration > Service Applications > click the Administrators tab and add the FARM account and Service Application Pool account.

Also add the FARM account to the local Administrators group on the Application server that will run the User Profile Synchronization Service.

Start the Synchronization service on the Application Server, it will ask you to enter the FARM account password, enter it and wait. This will take some time, it needs to start the ForeFront Identity Manager Service and ForeFront Identity Synchronization Service. So be patient, minimum 10 minutes.

Step 5: Once the Synchronisation Service starts successfully, you need to upgrade the My Sites web application by testing and mounting the restored database from SharePoint 2010. You then need to convert it to Claims authentication.

Make sure you have copied the My Sites Content database across to your new SQL Server and restored it. Ensure that the Setup account has DBOwner rights on the database.

Remove the default database from the My Sites Web Application via Central Administration first.

Then run the following Powershell command to test the restored database with the My Sites Web Application.

Test-SPContentDatabase -name WSS_Content_MySites -webapplication http://mysitesdevsp2013.contoso.com.au

Make sure there are no errors and that they do not block the upgrade of the database.

Then run a Mount-SPContent Database like below:

Mount-SPContentDatabase "WSS_Content_MySites" -WebApplication “http://mysitesdevsp2013.contoso.com.au”

The upgrade should complete successfully.

Next convert the My Sites Web Application to Claims by running the following command:

Convert-SPWebApplication -Identity "http://mysitesdevsp2013.contoso.com.au" -To Claims -RetainPermissions -Force

You now need to create the My Sites host for the My Sites Web Application. So, in Central Administration, create a new Site Collection for the My Sites Web Application and select the My Sites template under Enterprise. Also, make sure that you have selected the root of the web application – ‘/’.

Step 6:

Configure Staff profile photo by editing the Manage User Properties, select Picture and then edit, add a new mapping and select thumbnail photo

Under Central Administration > Service Applications > User Profile Service Application, click ‘Setup My Sites’ and add the My Site Host Location.

Start full profile sync and make sure it completes with no errors.

Once the user synchronization has finished, open the SharePoint 2013 Management Shell as the Farm account svc-SP2013DevFarm and run the following command

$mySitesUrl=”http://mysitesdevsp2013.contoso.com.au” (Enter)
$mySitesHost=Get-SPSite –Identity $mySitesUrl (Enter)
Update-SPProfilePhotoStore –MySiteHostLocation $mySitesHost –CreateThumbnailsForImportedPhotos $true (Enter)

This completes the upgrade of My Sites from SharePoint 2010 to SharePoint 2013. Go to your SharePoint 2013 site and click the Newsfeed link at the top of the page. This will start the process of provisioning a new My Site for your account. Once done, you should receive an email from your SharePoint Farm notifying you of the set up. You will then find all your old files on your SkyDrive page.

If you have any questions or need help with your upgrade, post a message below and I will be happy to assist.



CoolWriteups SharePoint 2010 Post

SharePoint 2010 – An error occurred during the “Generate Key” process. Please try again or contact your administrator


In SharePoint 2010, when you try to set up the Secure Store Service Application, one of the first steps is to generate a key. You open up the page under Central Administration > Application Management > Manage Service Applications > Secure Store Service to add a passphrase but see the error message “An error occurred during the “Generate Key” process. Please try again or contact your administrator”.

Looking at the ULS logs you may see this:

“7557 Critical The Secure Store Service application Secure Store Service is not accessible. The full exception text is: User does not have permission to perform the operation.”


This could be due to the user account that is logged in to the Central Administration page not having enough permissions to generate the key.

Try using the Farm account.

CoolWriteups SharePoint 2010 Post

SharePoint 2010 Services Stuck at Stopping or Starting

You log into Central Administration for SharePoint 2010 > System Settings > Services on Server and notice some of the services are stuck at ‘Starting’ or ‘Stopped’.

This could be due to the fact that SharePoint 2010 Administration Service (spadminv4) is not running on the Server. But when you try to start the service, it does not start in a timely fashion. To learn how to start the SPAdminV4 service follow this article: SharePoint 2010 Administration Service Not Starting

1. To solve the ‘Starting’ and ‘Stopping’, log into the server running Central Admin with the Farm account. Ensure the Farm account is a member of the Administrator’s group on the server you are logging in to;

2. Open a Powershell command window and Run as Administrator;

3. To get all the services running on a particular server, run the following command ‘Get-SPServiceInstance –Server ‘servername’. This will bring up a list of services running on the server like below.

4. To stop the service, enter the following command ‘Stop-SPServiceInstance’ and the GUID of the services from the screen above.

5. The status will now change from ‘Starting’ to ‘Stopping’. This will however not complete if the SharePoint 2010 Administration service is still not running. To stop it, run ‘Start-SPAdminJob’. Refer to this article for more info: http://technet.microsoft.com/en-us/library/ee513051%28v=office.14%29.aspx

6. Give it 10 seconds and the service should now be either ‘Stopped’.

7. The ‘Stop-SPServiceInstance’ command can be used to stop a Provisioned service too. A provisionsed service will have a status of ‘Starting’ or ‘Started’.

8. If the service status is ‘Unprovisionsed’, it means the service is ‘Stopped’ or ‘Stopping’.

9. To start a service, use ‘Start-SPServiceInstance’

That’s it.

CoolWriteups SharePoint 2010 Post

SharePoint 2010 – How To Install A Cummulative Patch

Installing a SharePoint 2010 cummulative patch can be tricky. To ensure everything goes smoothly, the following steps will help. Make sure you test this out in your DEV environment first.


1. Farm username and password;
2. Server names;
3. Downloaded patch/update for SharePoint Server 2010 or Foundation 2010;

Steps to install the patch/update:

1. Run the downloaded patch on all the servers in the farm individually starting first with the Application Server, then the Web Front End. The patch is usually an exe file;
2. Reboot the servers;
3. Log back into the Application server or the server that hosts Central Admin and open a Powershell window as an Administrator;
4. First check if an upgrade of the server is needed by entering this command ‘(get-spserver $env:computername).NeedsUpgrade‘. If one is required, enter the following command and run ‘PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures‘. Do this on all the servers in the farm that have SharePoint installed. This will ensure that all the servers in the SharePoint 2010 farm are upgraded and that they all have the same patch status
5. Once this is done, reboot all the servers one by one.
6. Open Services and check to make sure all the SharePoint services are running including SharePoint 2010 Administration. Also, ensure the Forefront services are running on the Application Server;
7. You may notice the databases are now running in compatibility range. To solve the issue run this Powershell command ‘Get-SPContentDatabase –Identity DatabaseName | Upgrade-SPContentDatabase‘. For a non-content database run this command ‘Get-SPDatabase –Identity DatabaseName | Upgrade-SPDatabase’.

That’s it.

CoolWriteups SharePoint 2010 Post

SharePoint 2010 Administration Service SPAdminv4 Not Starting

The SPAdminv4 service fails to start on a server running Windows Server 2008 after you have installed a SharePoint 2010 cummulative patch or are in the process of building a new server farm. This could be a problem on the Web Front End or the Application Server.

The fix is to add a new registry setting.

1. Click Run and enter ‘Regedit’;
2. In the Registry Window, navigate to ‘HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control’;
3. Right click and create a new DWORD Value option;
4. Replace ‘New Value #1’ with ‘ServicesPipeTimeout’;
5. Right click the new option and click Modify;
6. Enter 60000 as the value and exit the Registry.
7. Restart the server;

The SharePoint 2010 Administration service should now be running.

CoolWriteups SharePoint 2010 Post

SharePoint 2010 – Delete Search Service Application

Ran into a sticky situation where I had to delete a corrupt Search Service Application in SharePoint 2010.

To do this make sure your Farm account is:

1. Used to run the SharePoint Timer Service;
2. Is a member of the local Administrator group on the Web Front End and Application Server;
3. Make sure the Timer service and other SharePoint services are running.

You could try and delete the Search Service Application via Central Administration by selecting the Service Application and clicking the Delete option in the ribbon above.

SharePoint 2010 - Delete Search Service ApplicationIf that doesn’t work, you could try this option:

1. Open Powershell, run as Administrator;
2. Run this command – Get-SPServiceApplication. This will give you a list of the Service Applications on the Farm including the corrupt Search Service Application to delete;
3. Make a note of the GUID connected to the Service Application;
4. Then run Remove-SPServiceApplication -Id “replace with Guid” -removedata

Refer to this article for more info: http://technet.microsoft.com/en-us/library/ee806875%28v=office.14%29.aspx

If the above Powershell command doesn’t do the trick, you could resort to STSADM commands as a last resort.

1. Get the GUID of the Search Service Application above by running the same command above using a Powershell command window (Run as Administrator);
2. The run stsadm -o deleteconfigurationobject -id “replace with GUID”;

Keep checking the log files, you could be missing a PropertyStore database or one of the other SharePoint databases. If this is true then restore the database and continue to the steps above.

That’s it, good luck with it.

Derek Halstead

CoolWriteups SharePoint 2010 Post

SharePoint 2010 Upgrade – Checklist

Welcome to CoolWriteups. Below I have put together a set a activities to check to ensure a smooth upgrade of your MOSS 2007 environment to SharePoint 2010.

Before the upgrade

  • If you have a Nintex database to upgrade, ensure you have first updated the 2007 Nintex database to the latest version ( at the time of writing this) in your existing 2007 environment or move it to a Test 2007 environment and update it there. Then install Nintex Workflow 2010 software on your new 2010 Production Server, update it to the latest version ( at the time of writing this) if you have to. To find out the version of Nintex, check the Licensing page under Nintex Workflow Management. Then restore the updated 2007 Nintex database in the 2010 environment and attach it to Nintex Workflow 2010 by using the Database Setup page found under Nintex Workflow Management;
  • Before starting the actual upgrade, ensure that all the content databases are restored to the new 2010 Production Database Server and all accounts have been recreated ensuring that the FARM account has DBOwner rights on the content databases;
  • Make sure you have enough disk space allocated to the drive where the content databases reside. For example a 350GB content database will grow by approximately 10GB. I know what you’re thinking, so 360GB would be fine? I would recommend the drive be 500GB just to be on the safe side;
  • Also, ensure that the log file is set to autogrow and that no maximum limit is set on it’s size in the Database properties window in SQL Server Management Studio. If your log files are stored on a different drive make sure the drive is more than 150GB in size, your 350GB content database’s log file is likely to grow to approximately 150GB so make sure you have allocated atleast 200GB to the drive. More is better.

During the Upgrade

  • Log into your Production Application Server with the FARM account and open a Powershell command prompt. Type in the following command: Mount-SPContentDatabase -Name -DatabaseServer -WebApplication [-Updateuserexperience], where:

    databasename‘ is the name of the database you want to upgrade.

    servername‘ is server on which the database is stored.

    url‘ is the URL for the Web application that will host the sites.

    Updateuserexperience is the choice to update to the new user experience or stay in the old user experience (part of Visual Upgrade). When you include this parameter, the site is set to preview the new user experience. Omit this parameter if you want the site to remain in the old user experience after upgrade. For more information, see Plan visual upgrade (SharePoint Server 2010). Refer to this link for more details: http://technet.microsoft.com/en-us/library/cc263299.aspx#AddDB

  • Once you run the command, you can keep track of the upgrade by opening the Central Administration page then > Upgrade and Migration > Check Upgrade Status;
  • You can also start Task Manager on the SharePoint 2010 Application server, click the ‘Networking’ tab to see if there is any traffic going through to the Database Server.
  • Most important is the Upgrade log file which can be found in the 14 Hive in the Logs folder or if you have your log files stored in a different drive then check there. The Upgrade log file will give you information about the start time of the upgrade, what it has done, what features are missing, errors, warnings etc;
  • Other options to check the progress of the upgrade include Opening SQL Server Management Studio then right click the Server Instance and select Activity Monitor to make note of the processes running against the content database that is being upgraded to SharePoint 2010. Keep an eye out for any locks;
  • You can also open a new Query Window in SQL Server Management Studio against the content database and enter the following query: SP_HELPDB ‘DBName’ which will give you a list of properties along with information about the log file, the size etc. This is important as most upgrades fail due to a lack of disk space allocated or the log file is set to have a maximum limit that is less that what it needs;
  • During the upgrade the SQL Server will record any errors which can be found by clicking SQL Server Agent in SQL Server Management Studio, then click the Error Logs folder, select SQL Server as the option (not SQL Server Agent) and then double click the ‘Current’ log file. This will tell you if there are any errors and what caused the error.

Questions and Comments always welcome.

Send us a quick enquiry at Certified Solutions Australia to find out how we can help you.

OneNote 2010

OneNote 2010 with SharePoint 2010 Example

In this article I am going to share with you the benefits of OneNote 2010 and how you can leverage it’s features to get rid of all your office documentation stored in different sources and centralise all that information in an electronic notebook.

What is OneNote? OneNote is a digital notebook that let’s you manage your information, orgainise it, quickly find it, and share it with others.

Below is a graphical representation of what OneNote can do for you at home, school and at work.
What is OneNote?

OneNote at Work

OneNote At School

OneNote At Home

OneNote works on the same idea of a notebook. Items in OneNote are stored on pages, these pages can be of any size unlike the pages in a normal notebook and there is no limit to the number of pages you can create. Just like in a normal notebook, you can use sections (represented by Tabs at the top of the page) to organise pages inside a OneNote notebook. You can also rename a section or add more to the OneNote notebook.

There is also a special section called Unfiled Notes which can be used to store random notes. You can move these random notes to anywhere in your OneNote notebook once you have decided where to put them.

To demonstrate the use of OneNote I am going to show you how I have planned my next holiday to America using OneNote. I will then show you how easy it is to share this information with collegues and friends using SharePoint 2010.

To begin, my trip to the US needs the following:

  • A flight ticket, a Visa and Passport which I will store in a section called “Travel Documents”;
  • I will also need a list of contacts in the US who include family and friends. I will store this information in a section called “Contacts”;
  • A list of places I would like to visit which I will store in a section called “Places to Visit”;
  • I’m pretty sure I will keep track of all my receipts along the way, with OneNote it is easy to scan and print a receipt directly to your OneNote notebook instead of printing it to a sheet of paper. I will store these printed receipts in a section called “Receipts”
  • Remember, all the information stored in a OneNote notebook can be shared with friends and collegues. You can do this by syncing your notebook with SharePoint 2010 and then giving only certain people access to the notebook.

Ok, so lets start this exercise by first creating a Document Library in SharePoint 2010 and then creating a OneNote notebook.

  • Log into your SharePoint 2010 Team site and create a new Document Library, call it “My American Holiday”;
  • Then go to Start > All Programs > Microsoft Office > OneNote 2010, to open OneNote. Click File > New, to create a new notebook. In the screen, add a name for the notebook, I have called mine “My American Holiday”;
  • I then selected the Network Location option as I plan on syncing my notebook with SharePoint to share with my collegues and friends;
  • CoolWriteups.com - Create OneNote Notebook

  • Once the notebook is created, you should see a Microsoft OneNote message box saying the notebook has been created and is accessible to anyone. You can choose to email the link to a friend or a collegue using Outlook 2010.
  • CoolWriteups.com - Notebook Created

  • The first section of the notebook created by default is called “New Section 1”. Right click the section and select “Rename” to rename it to “Travel Documents”. In the same way, go ahead and add three more sections and name them “Contacts”, “Places to Visit” and “Receipts”. Your notebook should look like the one below.;
  • CoolWriteups.com OneNote 2010 - Sections

  • Now start adding content to the sections created above as you would normally do using a normal notebook. Click save as you go and the information is automatically saved to the SharePoint Document Library as seen below.
  • Coolwriteups.com - SharePoint OneNote Notebook

As you can see above, the possibilities are endless. Students can use OneNote to keep track of individual projects, real estate agents can use it to keep track of potential buyers, the properties they are interested in and other contact details. Large organisations can use it to keep track of various in-house projects and share all documentation with other staff across the organisation centralling using the Intranet.

I hope you found this post useful, questions and comments always welcome. Cheers.

Send us a quick enquiry at Certified Solutions Australia to find out how we can help you.

CoolWriteups SharePoint 2010 Post

CoolWriteups Solved : Muhimbi The remote Server Returned An Error: (401) Unauthorized


The service account that MDCS is running under does not have the privileges to load the XSN file from SharePoint


07/31/2012 08:52:17.58 w3wp.exe (0x1A28) 0x1E18 SharePoint Foundation Workflow Infrastructure 98d4 Unexpected System.ServiceModel.FaultException`1[SomeCompany.ConvertToPdf.WorkflowActivity.MuhimbiService.WebServiceFaultException]: Muhimbi.DocumentConverter.WebService.Data.WebServiceInternalException: Exception of type ‘Muhimbi.DocumentConverter.WebService.Data.WebServiceInternalException’ was thrown. – Details: “The remote server returned an error: (401) Unauthorized.” at Muhimbi.DocumentConverter.WebService.InfoPathConverterFullFidelity.Convert() at Muhimbi.DocumentConverter.WebService.DocumentConverterService.Convert(Byte[] sourceFile, OpenOptions openOptions, ConversionSettings conversionSettings, Boolean checkLicenseStatus) (Fault Detail is equal to SomeCompany.ConvertToPdf.WorkflowActivity.MuhimbiService.WebServiceFaultException). 3c893397-76f0-40ed-af08-5e4023277759


  • Log into the Server running the Muhimbi Document Converter Service with an account that has sufficient privileges to access the Services running on the server;
  • Go to Start > Administrative Tools > Services and scroll down till you find “Muhimbi Document Converter Service”;
  • Right click the service and open Properties, click the Log On Tab and make a note of the account running the service;
  • Go back to the SharePoint 2010 site, click Site Actions > Site Permissions and add the Service Account to the “Visitors” group.

Helpful Resources:

Questions and comments welcome, leave a message below.

Thank you.

Join the Forum discussion on this post

CoolWriteups SharePoint 2010 Post

CoolWriteups Solved: InfoPath 2010 Form Items Opening In Browser Instead Of Client Application

Problem: The form link in an email notification is meant to open in the InfoPath client application but instead it opens in a Browser.

Solution 1: Go to Form Library > Form Library Settings > Advanced Settings and change the option for “Opening documents in the Browser” to “Open in Client Application”

Solution 2: Log into the Farm, open Central Admin > General Application Settings > InfoPath Forms Services and uncheck the option to Render Forms in the Browser.

Solution 3: Open Site Actions > Site Settings > Modify All Settings. Under Site Collection Administration, click Site Collection Features and Activate the “Open Documents in Client Applications by Default” feature.

Join the Forum discussion on this post

CoolWriteups SharePoint 2010 Post

CoolWriteups Solved: InfoPath 2010 Items Not Showing Up In Form Library

Problem: InfoPath Items not showing up in Form Library.


1. Go to Form Library Settings > Advanced Settings and “Allow Management of Content Types”;
2. Click the “Form” content type and then Advanced Settings. In the next screen, click Edit Template to open the Form in Edit mode in InfoPath;
3. Right click the Submit button and click Properties;
4. Click Submit Options > Manage > Modify and check the Document Library path to ensure that it is pointing to the Library only and nothing more.

For example: http://servername/sites/testingworkflows/Derek%20Travel%20Form%20Library/

Join the Forum discussion on this post

MOSS 2007 Post

MOSS 2007/ SharePoint 2010 – Cannot Generate SSPI Context



While working with MOSS 2007, you may come across the errors below while trying to open up your MOSS 2007 and Central Administration websites.

The error message “Cannot connect to the Configuration database” is displayed in the browser, while “Cannot generate SSPI context” is found in the Event Viewer.

Most of the online blogs and the solutions found on the Microsoft website are helpful, but none of them may be of any help to you.

One way to solve this problem is to:

  • Log into the SQL Server box, open up SQL Management Studio and once connected right click on the Server Name and select “Activity Monitor”. This should tell you if there are any incoming connections to the SQL Server.
  • If you notice there is no activity from the Web Server, then it is pretty obvious the Web Server cannot make contact with the SQL Server.

To test this theory, on the Web Server Desktop create a temporary “Test.UDL” connection file and try to connect to the SQL Server, first using the IP Address of the SQL Server and then using the Name of the SQL Server. Also, use either Windows Authentication of a dedicated SQL Account to connect.

You may be able to connect with the IP Address but not the name of the server or vice versa. This is a DNS issue which is preventing the Web Server from making contact. Immediately get in touch with your Network Administrator to resolve the DNS issue.

The problem may have occurred after installing updates on the Server.

A .UDL file must be able to connect to the SQL Server with the IP Address or the Name of the SQL Server. The .UDL file is created to test connection between the servers only and not for any other purpose.

You can also read How to Create a Three Tier SharePoint 2010 Development Environment Part 1 and then try and reproduce the above error and solution.


CoolWriteups SharePoint 2010 Post

How to Create a Three Tier SharePoint 2010 Development Environment Part 2


Check out How to Create a Three Tier SharePoint 2010 Development Environment Part 1 to read about the requirements for this task.

Part 2 begins here…

Three Tier SharePoint 2010 Development Environment

Three Tier SharePoint 2010 Development Environment

Step 6

Starting with the Domain Controller, change the IP configuration details to the following sample configuration. Uncheck the Get Automatic IP Address and enter a manual one.

Domain Controller – “DomainController”

Subnet Mask:
Default Gateway:
Preferred DNS Server:

For the Application Server – “AppServer”

Subnet Mask:
Default Gateway:
Preferred DNS Server: (notice the IP address here is the IP address of the Domain Controller)

For the SQL Server – “SQLServer”

Subnet Mask:
Default Gateway:
Preferred DNS Server: (notice the IP address here is the IP address of the Domain Controller)

For the Web Server – “WebServer”

Subnet Mask:
Default Gateway:
Preferred DNS Server: (notice the IP address here is the IP address of the Domain Controller)

Now reboot all the servers and login with the domain\Administrator account on each of the servers.

Step 7

To configure SharePoint 2010 is easy! Create 2 accounts (spAdminAcct and spFarmAcct) with least priviledges – meaning don’t add them to the Admins group on the Domain Controller. Add the spAdminAcct to the Administrator group on the Application Server, Web Server and in the SQL Server, create a new Login for spAdminAcct and check the DBCreator and SecurityAdmin checkboxes. Do not add the spFarmAcct to the Adminstrators group on the servers.

Run the SP 2010 installation with the SPAdminAcct and use the SPFarmAcct as the Farm Account when prompted.

Kerberos Configuration

I used Kerberos Authentication which involved a couple of extra steps wherein I had to allow the two accounts and the AppServer to be trusted for delegation in Active Directory, and then I ran the following command: setspn -a http/appserver.domain.local domain\spAdminAcct. Download the SetSpn.exe from the Microsoft website (see suggested reading below).

Join Web Server to Farm

Next, run the SP 2010 configuration on the Web Server and during configuration make sure you select the “Add to existing farm” setting and follow the steps from there.

And there you have it, 4 virtual machines comprising of a Domain Controller, a Web Server, an Application Server and a SQL Server with SharePoint 2010.

This article was more about getting 4 virtual machines talking to each other with the basics of installing and configuring SharePoint 2010.

If you have any questions please feel free to ask, any suggestions please let me know.

CoolWriteups SharePoint 2010 Post

How to Create a Three Tier SharePoint 2010 Development Environment Part 1

SharePoint 2010 Post

SharePoint 2010 Post

Ok, so today we are going to look at setting up a three tier SharePoint 2010 Development environment real quick. I spent alot of time trying to figure out how to get this done and in the end it turned out to be real simple.

What you will need:

  • VMWare Workstation 7.1
  • 500GB External USB drive
  • Laptop with 8GB memory
  • Windows Server 2008 R2 64 Bit
  • Windows Server 2003 (optional)
  • SQL Server 2008 R2 64 Bit
  • SharePoint Server 2010


Three Tier SharePoint 2010 Development Environment.

Three Tier SharePoint 2010 Development Environment with optional Index Server.


How to build your SharePoint 2010 development environment:

The diagram above also includes an optional Index Server. In this example we won’t be looking at configuring an Index server. However, in future articles this will be discussed.

First thing you need to do is create 4 virtual machines
Server Name Memory Disc Space Processor
Domain Controller 512 MB 20 GB 1
Web Server 2048 GB 50 GB 1
Application Server 2048 GB 50 GB 1
SQL Server 2048 GB 50 GB 1

The Web, Application and SQL servers will form the three tier. For the Domain controller I chose to install Windows Server 2003. Microsoft have some great articles on how to configure a Domain Controller here http://technet.microsoft.com/en-us/library/cc759011%28WS.10%29.aspx

Step 1

For the other servers I installed Windows Server 2008 R2. You can create one windows server 2008 and then run SysPrep to ensure each copy you make of the original thereoff will be unique. This will be our template. Make 3 copies of the template.

Great, so at this stage you should have 3 Windows Server 2008 R2 servers and 1 Windows Server 2003 Domain Controller called “DomainController”.

Step 2

Go ahead and install SQL Server 2008 on one of the servers and make sure you give the server a reasonable name, I have named mine “SQLServer”…literally, no confusion here! Also, ensure TCP/IP connections are set to allow for network configuration.

Step 3

Grab another copy of the Windows Server 2008 template and use this as the Application Server. We will call this “AppServer”. On this server you will install SharePoint Server 2010 but will not configure SharePoint 2010 just yet.

Step 4

Grab another copy of the template and use it as the Web Server, call it “WebServer”, and on this we will install SharePoint Server 2010 but will leave the configuration for later.

To give these servers a proper name go to Computer Properties and change the name accordingly but make sure you document everything.

Step 5

Now for the all important bit….to get 4 virtual machines talking to each other you will need to ensure that the “Network Adapter” setting in VMWare Workstation 7.1 for each VM is set to “Host Only”.

Next, power on each of the Servers and log in with the default Administrator password (not the domain account but the local account).

In Part 2 we shall focus on configuring the servers and connecting them up to the domain controller.

Check out How to Create a Three Tier SharePoint 2010 Development Environment Part 2 here

Display a List item ID at the top of the List Item Window in SharePoint 2010.

This is useful when you need to display the List Item ID at the top of the List Item window in SharePoint 2010.

Thank you to Christophe@PathToSharePoint.com for the javascript code only to display the List Item ID.

  • Open the List
  • Hit the List tab
  • Click the Form Web Parts dropdownlist
  • Choose “Default Display Form”
  • At the top of the Page – Insert Tab, Click the Web Part button to add a new Content Editor web part.
  • From Categories choose “Media and Content” > “Content Editor” and add it to the main section of the page
  • Click the “Click here to add content” and then click the HTML button in the Ribbon to bring up the Edit source code window.
  • In the window add the following code to display the Item ID at the top of the list item window.<script type=”text/javascript”>
    // Item ID in DispForm.aspx and EditForm.aspx
    // Feedback and questions: Christophe@PathToSharePoint.com
    function DisplayItemID()
    var regex = new RegExp(“[\\?&]”+”ID”+”=([^&#]*)”);
    var qs = regex.exec(window.location.href);
    var TD1 = document.createElement(“TD”);
    TD1.className = “ms-formlabel”;
    TD1.innerHTML = “<h3 class=’ms-standardheader’>Issue ID</h3>”;
    var TD2 = document.createElement(“TD”);
    TD2.className = “ms-formbody”;
    TD2.innerHTML = qs[1];
    var IdRow = document.createElement(“TR”);
    var ItemBody =   GetSelectedElement(document.getElementById(“idAttachmentsRow”),”TABLE”).getElementsByTagName(“TBODY”)[0];
  • Ignore any Warnings! Next hit the Page tab at the top of the page and view the list item. Done!


Any questions please just ask.

Certified Solutions Australia - SharePoint 2013

Print a List Item in SharePoint 2010 and SharePoint 2013

You may need to print a single list item in SharePoint 2010 or SharePoint 2013. However, this functionality does not exist unless you print with Excel, which isn’t what you are looking for anyway.

So, how do we go about accomplishing this?

  • Open a List;
  • Hit the List tab;
  • Click the Form Web Parts dropdownlist;
  • Choose “Default Display Form”;
  • At the top of the Page – Insert Tab, Click the Web Part button to add a new Content Editor web part (CEWP);
  • From Categories choose “Media and Content” > “Content Editor” and add it to the main section of the page;
  • Click the “Click here to add content” and then click the HTML button in the Ribbon to bring up the Edit source code window;
  • In the window add the following code to display a Print Button at the top of the list item window.
    <input type=”button” value=” Print this page ” onclick=”window.print();return false;” />
  • Ignore any warnings;
  • Next, hit the Page tab at the top of the page to view the List item. You should see the Print button;
  • Hit the Print button to print just the list item.

So there you go, with just a little tweaking you can print a single List item in SharePoint 2010 or SharePoint 2013.

Let us know if this worked for you….


Join the Forum discussion on this post