The document could not be created. The required application may not be installed properly, or the template for this document library cannot be opened.


Working within my VM this morning, and just testing out basic functionality of SharePoint on my demo site. I went to do a very simple task of creating a new document. I received the following pop up.

It took me a moment, but I realised I didn’t have any Office products installed on my VM, however I did have Office Web Apps. I thought I should still be able to create a new document. It turns out that if you disable an Internet Add-On this message goes away. The Internet Add-On is called SharePoint OpenDocuments Class, (which sounds like it needs to be enabled for it to work!)

As soon as I disabled it, without any browser restart, I was able to create a new document.

Advertisements

VMWare 9 where has Synchronize guest time with host gone?


When at work I’m working with VMWare. Personally I prefer Hyper V, but there you are. Today when I got into work, I noticed my clock on the guest machine was about 3 hours out. This indicated to me that the Synchronization hadn’t been turned on. So I clicked on the VM icon in the tray of the guest machine. All I received was the About VMWare tools.

So where in VMWare 9 is the Synchronization settings?

  • Goto VMWare Workstation and on the menu bar select VM -> Settings.
  • Under the option tab, select VMWare Tools.
  • At the top right you will see VMWare Tools features.
  • Tick the checkbox for Synchronize guest time with host.

Your host and guest machine will now be in synch.

Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 10 – Setting Up Visual Studio


UPDATE: SharePoint 2016 development machine

I am doing a collection of blog posts, you can access the other parts of this post below.

Setting up Visual Studio

The last part of this 10 part series is to set up visual studio so you can start developing on your machine.

  1. From the Start menu, type Visual Studio 2012 and open the application.
  2. As it is the first time Visual studio 2012 has opened, you will be prompted with choose default environment settings dialog. Choose your preference. Mine is Visual C# Development Settings. For the local help documentation, I’m selected None so that I don’t fill up my virtual machine with help files that I can obtain by looking online. Click Start Visual Studio.
  3. As soon as I loaded up my environment, I got a message saying that there are Visual Studio 2012 updates from the system tray of my Server. Either click the icon in the system tray, or select from the Visual Studio menu Tools > Extensions and Updates… Update anything that needs updating.
  4. Close Visual Studio 2012.

Install Office and SharePoint 2013 Developer Tools

  1. From the Start Menu, type Microsoft Web Platform Installer. Open the Application.
  2. Once loaded, in the Search box type SharePoint press Enter.
  3. Select Add for Microsoft Office Developer Tools for Visual Studio 2012 – Preview 2
  4. Then Click Install.
  5. Click I Accept on the Prerequisties page.
  6. Once complete, you will have the Office and SharePoint tools installed for Visual Studio.

Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 9 – Configuring Workflow


UPDATE: SharePoint 2016 development machine

I am doing a collection of blog posts, you can access the other parts of this post below.

Install SharePoint Designer 2013

I have noticed in my blog I haven’t yet told you to install SharePoint Designer 2013. There is a good reason to install it now, because I can use it to prove if you have correctly configured Workflow Manger with SharePoint. SharePoint Designer 2013 is a free tool from Microsoft.

  1. Download SharePoint Designer 2013 32bit from the Microsoft site http://www.microsoft.com/en-GB/download/details.aspx?id=35491
  2. Once downloaded run the file sharepointdesigner_32bit.exe.
  3. Accept the License terms and click Continue
  4. Click Install Now.
  5. Once installed, I’d recommend performing a Windows Update. From the Start Menu type Windows Update, open up the application and run any updates required. Reboot if necessary.

Check to see Workflow settings in SharePoint Designer.

  1. From the start menu, type SharePoint Designer and open the application.
  2. Once SharePoint Designer has opened, click Open Site.
  3. Type the URL http://dev.cannonfodder.local click Open.
  4. If prompted, enter your credentials User: Cannonfodder\Administrator Password:Pa55w0rd.
  5. From the Navigation menu, select Workflows
     
  6. On the ribbon menu, select List Workflow > Documents.

     
  7. In the Create List Workflow dialog, at the bottom you will see a dropdown box for Choose the platform to build your workflow on. Only SharePoint 2010 will be listed.  
  8. Close down SharePoint Designer.

Configuring Workflow Manager

First we need to create a Workflow account.

  1. In the Start Menu, type Active Directory Users and Computers. Select the application.
  2. Expand the tree in the left hand pane to see the Users OU. Select the Users OU.
  3. Right Click on User and select New > User. Create a new user called SP_Workflow. Set the Full Name and Log on name to SP_Worflow. Click Next.
  4. In the password dialog screen, enter the following and click Next.
    1. Password and Confirm Password as: Pa55w0rd
    2. Untick User must change password at next logon.
    3. Leave User cannot change password as unticked.
    4. Tick Password never expires
    5. Leave Account is disabled as unticked.
    6. Click Next. Then click Finish.

Setting up SQL with the correct Security Accounts.

  1. From the start menu, type SQL Server Management Studio and open up the application
  2. In SQL Server click Connect. (This should be to SQL2012 database instance).
  3. In the left hand menu expand Security. Right click Logins. And select New Login…
  4. In the Login – New dialog box, click the Search button.
  5. Type SP_Workflow in the Enter the object name to select, and click Check Names. This will resolve the name. Click OK.
  6. In the left hand panel select Server Roles.
  7. Tick both securityadmin and dbcreator then click OK.
  8. Close down SQL Server Management Studio

Giving SP_Workflow administrative rights.

  1. From the start menu, type Active Directory Users and Computers and open up the application.
  2. In the left hand panel, expand Active Directory users and Computer > cannonfodder.local > Builtin.
  3. In the right hand panel, right click Administrators and select Properties.
  4. In the members tab, click Add.
  5. Type SP_Workflow in the Enter the object names to select box, click Check Names, then click OK.
  6. Click OK to the Administrators Properties dialog box, and close Active Directory Users and Computers.

Installing Workflow Manager

  1. Go to the URL http://www.microsoft.com/web/downloads/platform.aspx and download the latest Microsoft Web Platform Installer.
  2. Once downloaded run the file WebPlatformInstaller_amd64_en-US.msi
  3. Accept the license terms and click Install.
  4. Once installed, you can open from the start menu by typing Web Platform.
  5. Once loaded, type Workflow in the top right search box and press Enter. Find Workflow Manager 1.0 and click Install.
  6. On the Prequisites page, click I Accept.
  7. Once installer has complete, Click Continue and then Finish to start the configuration process.

Configuring Workflow Manager

  1. From the Start menu, type Workflow Manager Configuration and open the application.
  2. On the Welcome Page, click Configure Workflow Manager with Default Settings (Recommended).
  3. On the New Farm Configuration Page set the SQL server Instance to SQL2012
  4. Set the User ID to SP_Workflow@cannonfodder.local and the password to Pa55w0rd
  5. Tick the Allow Workflow management over HTTP on this computer.
  6. Click the Test Connection button to ensure your credentials work.
  7. In the Certificate Generation Key and Confirm Certificate Generation key enter Pa55w0rd into both textboxes.
  8. At the bottom right of the dialog box click the right arrow button to proceed to next screen.
  9. A summary will appear. You can either click the tick icon at the bottom right to continue, or Get PowerShell Commands to obtain the powershell scripts to run later. In this instance, click the tick icon.
    (Please note the screen shot was taken during my first attempted, I used the wrong RunAs Account)
  10. Once the process has completed everything should have been configured.

Connecting Workflow to SharePoint 2013.

  1. From the start menu, type Workflow manager powershell and open the application.
  2. Type
     Get-WFFarm | ft HttpPort 
  3. Take note of this port (12291), as this is the port number that you will connect SharePoint 2013 to the Workflow Manager 1.0 farm.
  4. Close Workflow Manager PowerShell.
  5. From the start menu, type SharePoint 2013 Management Shell and open the application.
  6. Type
     Register-SPWorkflowService –SPSite "http://intranet.cannonfodder.local" –WorkflowHostUri "http://cannonfodderser:12291" –AllowOAuthHttp 
  7. Once you get the command prompt appearing again your SharePoint 2013 farm in now connected to the Workflow Manager 1.0 farm.

Check to see Workflow settings are working in SharePoint Designer.

  1. From the start menu, type SharePoint Designer and open the application.
  2. Once SharePoint Designer has opened, click Open Site.
  3. Type the URL http://dev.cannonfodder.local click Open.
  4. If prompted, enter your credentials User: Cannonfodder\Administrator Password:Pa55w0rd
  5. From the Navigation menu, select Workflows
  6. On the ribbon menu, select List Workflow > Documents.
  7. In the Create List Workflow dialog, at the bottom you will see a dropdown box for Choose the platform to build your workflow on. Both SharePoint 2010 and SharePoint 2013 should be listed if the Workflow is set up correctly.
  8. Close down SharePoint Designer.

Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 8 – Configuring My Sites and User Profiles


UPDATE: SharePoint 2016 development machine

I am doing a collection of blog posts, you can access the other parts of this post below.

MySites

We are now going to create a new Web Application for our My Site site. However we are not going to create a HNSC like we did for dev.cannonfodder.local, here we are going to create path-based site collections. From the Microsoft Technet article (which is for SP2010, so it might be different now, but couldn’t see anything saying something different) that there is a guideline for mysite sites.

  • You must use the self-service site creation feature that is included with SharePoint Server to create path-based site collections. MySite should be created as a path-based site or a custom solution should be provided.

Creating a Web Application for MySites

  1. From the start menu, type Central Administration and open the site.
  2. Select Application Management > Manage Web Applications.
  3. In the ribbon click the New icon.
  4. In the Create New Web Application dialog leave Create a new IIS web site selected and type the name as SharePoint My Site Host, leave the port as 80, and put my.cannonfodder.local in the host header.
  5. For simplicity in finding the Web Applications, I put the path on a different drive. D:\VirtualDirectory\MySite
  6. Under Claims Authentication Types set the Integrated Windows Authentication to Negotiate (Kerberos)
  7. Under Application Pool, select Use existing application pool and select SPContent App Pool
  8. Under Database Name and Authentication set the Database Name to SP_DEV_MySites.
  9. Scroll down to the bottom and click OK.
  10. Once the Web Application of My Site Host has been setup, click the link to Create
    Site Collection

Creating a Site Collection for MySites.

  1. On the Create Site Collection put the Title as My Site Host
  2. Set the URL as /
  3. The Template section as My Site Host, which can be found in the Enterprise tab
  4. Set the Primary Site Collection Administrator as cannonfodder\administrator

  5. Scroll down to the bottom and click OK.

Configure the Web Application to Host My Sites.

  1. After you have created your site collection, you should be returned to the Manage Web Application page. Select SharePoint My Site Host by clicking on it. This will highlight the line and items in the ribbon will become available to you.
  2. In the ribbon click the button Managed Paths

  3. In the Define Managed Paths dialog tick Sites. Then click the link Delete selected paths.
  4. Now add a new path called personal and make it Wildcard inclusion.
  5. Add another new path called my and make it Explicit inclusion. Then click OK.

  6. With SharePoint My Site Host still selected click the icon on the ribbon called Self-Service Site Creation.

  7. On the Self-Service Site Creation page, under Site Collections, select the on radio button. Click OK.

Add my.cannonfodder.local to DNS

  1. From the start menu, type DNS and open the application.
  2. Expand Forward Lookup Zones,
    right click cannonfodder.local and select New Host (A or AAAA)…
  3. For Name put my. Put the IP Address as 192.168.139.99, click Add Host. Click OK to the DNS message box stating the host record wad successfully created. Close DNS Manager.

Create Kerberos SPN for my.cannonfodder.local

  1. From the start menu, type cmd and open Command Prompt.
  2. Type setspn –S HTTP/my.cannonfodder.local cannonfodder\SP_Content
  3. While here also flush dns by typing ipconfig /flushdns
  4. Close Command Prompt window.

Configuring the User Profile Service Application My Site settings.

  1. In Central Administration left hand menu, select Application Management.
  2. Under Service Applications select Manage Service Applications.
  3. Find the User Profile Service Application in the list and click on it.

  4. Under the My Site Settings section click the Setup My Sites link.
  5. On the My Site Settings page, set the My Site Host to http://my.cannonfodder.local
  6. Under the heading Personal Site Location set the value to personal. Now click OK.

Configuring SharePoint User Profile Service Application with Active Directory.

There is a new way to import users into the user profile from Active Directory in SharePoint 2013. It is called Active Directory Import. It is a faster than the SharePoint 2010 way of using the FIM approach. Spencer Harbar has written a good blog about it here.

  1. From the start menu, type Central Administration and open.
  2. Under Application Management click Manage Service Applications.
  3. Find the User Profile Service Application and click the link.
  4. Under Synchronization, click Configure Synchronization Settings.
  5. On the Configure Synchronization Settings page, under Synchronization select Use SharePoint Active Directory Import and click OK.
  6. Back on the User Profile Service Application page, under Synchronization, select Configure Synchronization Connections.
  7. On the Configure Synchronization page, select Create New Connection.
  8. Put the following details in the Add New Synchronization Connection page.
    1. Connection Name: Cannonfodder AD
    2. Type: Active Directory import
    3. Connection Settings:
      1. Fully Qualified Domain Name: cannonfodder.local
      2. Authentication Provider Type: Windows Authentication
      3. Account Name: cannonfodder\administrator
      4. Password: Pa55w0rd
      5. Confirm Password: Pa55w0rd
    4. Under Containers click Populate Containers.
    5. After it loads, expand CANNONFODDER and then tick Users. Click OK.
    6. You will now be returned to the Synchronization Connection Page. You will see your new connection display.
  9. Repeat Steps 2 + 3 to navigate back to User Profile Service Application.
  10. Take note that on the right hand side of the screen under Profiles it states that there are 2 User Profiles.
  11. Under Synchronization, click Start Profile Synchronization.
  12. Select Start Full Synchronization and click OK.
  13. Refresh the Manage Profile Service: User Profile Service Application page, and you should see more User Profiles.

Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 5 – Configuring SQL 2012 Ready for SharePoint 2013


UPDATE: SharePoint 2016 development machine

I am doing a collection of blog posts, you can access the other parts of this post below.

When I started planning the 10 parts of the blog, the one bit I forgot about was Kerberos. So I have squeezed part of it in here. As I am a developer and not really an IT-Pro I had to look up information on the web to help me write this bit on Kerberos and speak to the IT Pro at my work. My references are blksthl blog and my work colleague Adam McEwen, who blogs you can access via these links.

Creating the Accounts required.

First we need to create 4 different accounts.

SP_Farm – SharePoint Farm Account

SP_Content – SharePoint Content account for the Content Databases.

SP_Services – SharePoint account for the Shared Services within SharePoint.

SP_SQL – The account to run SQL with.

  1. In the Start Menu, type Active Directory Users and Computers. Select the application.
  2. Expand the tree in the left hand pane to see the Users OU. Select the Users OU.
  3. Right Click on User and select New > User. Create a new user called SP_Farm. Set the Full Name and Log on name to SP_Farm. Click Next.
  4. In the password dialog screen, enter the following and click Next.
    1. Password and Confirm Password as: Pa55w0rd
    2. Untick User must change password at next logon.
    3. Leave User cannot change password as unticked.
    4. Tick Password never expires
    5. Leave Account is disabled as unticked.
    6. Click Next. Then click Finish.
  5. Repeat the steps 1-4 for the remaining accounts (SP_Content, SP_Services and SP_SQL).

Setting up Kerberos for SP_SQL account.

We will need to set up Kerberos for the other accounts, but this section of blog is getting your SQL ready for SharePoint 2013. Therefore at this point we will just set SQL up for Kerberos.

Name Resolution.

  1. In the Start Menu, type DNS. Open the application to the DNS Manager.
  2. Expand the forward lookup zones container in the left panel.

  3. Right click on the zone cannonfodder.local and click on a New Host (A or AAAA).

  4. Type in the name of the record. In this case we are going to name our SQL Server SQL2012. Set the IP address at the IP of the machine. We set this to a static IP in the last blog. (If you have forgotten you can find out by bringing up a command prompt and type ipconfig /all and look at the IP4 IP address.) Click on Add Host.

  5. Click on Done. You will then get a verification dialog, and after click OK to that, you will see the record has been created in the right pane of the DNS manager.
  6. To check that this is all working, open a command prompt, and type
    ipconfig –flusdns

    Then type

    Ping SQL2012

Service Principle Name

  1. Open a command prompt from the Start Menu by typing in cmd. Right click Command Prompt and along the bottom of the screen will be an option to Run as Administrator.
  2. Type the following in the command window. This will create the SPN for the service account paired with the host name.
    setspn –S MSSQLSvc/SQL2012:1433 CANNONFODDER\SP_SQL
  3. Type the following in the command window. This will create the SPN for the service account paired with the FQDN.
    setspn –S MSSQLSvc/SQL2012.cannonfodder.local:1433 CANNONFODDER\SP_SQL
  4. Now by typing in setspn –L CANNONFODDER\SP_SQL it will list all the SPN for that account.


Trust for delegation

As our server is a domain controller we do not need to set it up so that it is Trusted for Delegation. We can prove this by doing the following.

  1. From the Start Menu type Active Directory Users and Computers. Open the application.
  2. In the left hand panel, expand cannonfodder.local and select Domain Controllers.
  3. In the right hand panel you will see the computer CANNONFODDERSER.
  4. Right click this computer and select Properties. From the properties window, select the Delegation tab. As you can see this computer is already set to Trust this computer for delegation to any service (Kerberos only).

Configuring SQL Server 2012

As SQL was installed using a built in account, and also installed on the machine before it was sysprepped, SQL now needs to be configured to work properly on this server in preparation for SharePoint.

  1. From the start screen type SQL Server Configuration Manager and select the application.
  2. Click to expand SQL Server Network Configuration (not the 32 bit), and choose Protocols for MSSSQLServer, and ensure TCP/IP and Named Pipes are enabled. To enable them right click them and select Enable. Click OK at the warning.
  3. Now in the left hand pane, click SQL Server Services.
  4. For SQL Server (MSSQLSERVER) right click the service name and choose Properties.
  5. Select the Log On tab.
  6. Select this account: radio button and enter cannonfodder\SP_SQL and enter the password as Pa55w0rd. Click Apply, and Yes to restart the service, or Start the service if not already.
  7. Click OK and close SQL Server Configuration Manager.

Now we need to give cannonfodder\administrator access and update SQL Server 2012 local instance after the machine name has been changed.

  1. From the start screen type SQL Server Management Studio and select the application.
  2. Change the server name to SQL2012 and logon using SQL Authentication with the sa account using the password Pa55w0rd. If you try to log in at the moment as cannonfodder\administrator using windows authentication, you will fail to access SQL.
  3. Now give cannonfodder\administrator the correct security access.
    1. Expand Security and right click Logins to select New Login…
    2. Next to the Login Name click Search
    3. Type cannonfodder\administrator, and then click check names. Select the user administrator, not the group.
    4. On the left hand panel, select the Server Roles page, and tick sysadmin. Click OK
    5. Right click the database connection in Object Explorer and choose disconnect.
    6. Click Connect in the Object Explorer, choose database engine, and connect to SQL2012 using Windows Authentication, then confirm you can browse objects in the database server.
  4. Now we need to update the server name. If you Click New Query and type
    
    Select @@SERVERNAME
    

    You will notice that the server name is incorrect.

    Click New Query and copy the script

    
    sp_dropserver @@SERVERNAME
    GO
    sp_addserver 'CANNONFODDERSERVER', local
    GO
    

    run the query.

  5. Restart the SQL server service, right click the SQL Server service, right click the database connection in Object Explorer, and choose Restart. You will then get a prompt asking if you want to restart the MSSQLSERVER service. Say Yes.

  6. Right click the database connection again, and choose disconnect.
  7. Click Connect to SQL2012 using Windows Authentication.
  8. Click New Query, and run the following script to confirm the instance name has been changed to reflect your chosen machine name:
    
    Select @@SERVERNAME
    

  9. You can now close SQL Server Management Studio. No need to save the queries.

Now we are past the half way point, and we can now finally start installing SharePoint 2013!

Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 4 – Installing Active Directory


I am doing a collection of blog posts, you can access the other parts of this post below.

Installing Active Directory

In this post I will show you the steps to make your Virtual Machine a Domain Controller.

Giving the Virtual Machine a Static IP Address.

First thing you will need to do is Set the IP of the machine to Static address.

  1. Log on to the Virtual Machine, as administrator | Pa55w0rd.
  2. From Start Menu type CMD and open the command prompt.
  3. Type ipconfig /all
  4. Here you should see what the current dynamic IP address is for your virtual machine.
  5. Back in the start menu, type View Network Connections and under Settings you should see a link.
  6. Right click your network adapter and click Properties.
  7. In the properties windows, select Internet Protocol Version 4 (TCP/IPv4) and then click the Properties button.
  8. Update the properties form to match your current machine configuration.
  9. Click OK. Click Close. After a moment your adapter will reset itself and you should have internet access again.

Change the name of the Machine.

  1. From the Server Manager screen. Click on Local Server.
  2. Where it says Computer Name, click the link.
  3. This will open the System Properties dialog box.
  4. Click on the Change button.
  5. Enter the name of the server. I have called mine CannonFodderServer
  6. Click OK.
  7. Click OK and reboot when asked.

Setting up the Domain Controller.

  • Login to the CannonFodderServer virtual machine using administrator | Pa55w0rd
  • On the Server Manager > Dashboard, click (2) Add roles and features
    • On the Add Roles and Feature Wizard you will be present with Before you begin. Click Next
    • On Installation Type select Role-Based or Feature-based installation
    • On Select destination server accept the default of Select a Server from the server pool with CannonFodderServer selected. Click Next
    • On the Server Roles, select “Active Directory Domain Services
    • Accept the Additional features required, by clicking Add Features.
    • Keep press Next until you reach the Confirmation screen. Then click Install.
      Once it is installed click Close on the Wizard page.
  • Back on the Server Manager Dashboard you will see the item AD DS added to the Roles and Server Groups. Click on the title of AD DS. Note it will say at the top of the screen Configuration required for Active Directory Domain Services at CANNONFODDERSER. At the far right of this message click More…
  • The more link will bring up the All Servers Task Detail dialog. It will show an action of Promote this server to a domain. Click on that link.
  • On the Deployment Configuration screen select Add a New Forest.
    • I named my root domain cannonfodder.local click next. (For some reason if I typed cannonfodder.com when I went onto the next page, the wizard froze, and I could only cancel).
    • Give a password of Pa55w0rd to the Directory Services Restore Mode (DSRM) password. Click Next
    • Ignore the DNS Options warning. Click Next.
    • It then check the NetBIOS domain name. (I had to click inside the textbox for CANNONFODDER to appear) Click Next.
    • Next it will specify the Path locations of the AD DS database, log files, and SYSVOL. Accept the defaults and click Next.
    • The next page allows you to review your selection, and export to a Windows PowerShell script if you wish to automate additional installations. Click Next.
    • Before the actual install of AD, all prerequisites are checked. If all prerequisite checks are passed then click install. You can ignore warnings.
    • The machine will restart automatically after the promotion of the server to a DC has finished.
    • Once the server has rebooted and you logon to it, if you click on Server Manager | Tools, you will notice that the following items have been installed:
      • Active Directory Administrative Center
      • Active Directory Domains and Trust
      • Active Directory Module for Windows PowerShell
      • Active Directory Sites and Services
      • Active Directory Users and Computers
      • ADSI Edit
      • DNS
      • Group Policy Management