Wednesday, January 23, 2013

"Your Changes were saved but could not be uploaded because of an error. You may be able to upload this file using the server web page."

When you are using Office 2010 with Sharepoint 2010, I recently noticed one of the users in our environment got this error message. The user was trying to make changes to a document in a Sharepoint document library and trying to save it

"Your Changes were saved but could not be uploaded because of an error. You may be able to upload this file using the server web page."

The error was due to documents getting upload by Microsoft Office Upload Center. Microsoft Upload Center is and add-on that gets install with Office 2010 suite. This probably is saving document to its drafts and not letting it upload the changes.

To fix this, what worked for me was to :

1) Check-Out the document you wish to edit.
2) You will be prompt for saving it to your local drafts.
3) Enable it (check that box) and click OK
4) Now edit the document and save it.
5) You will be asked to check in your changes
6) Put in the comments and click OK

Alternatively , I read somewhere, to disable the Microsoft Office Upload Center and try saving your document.

Open task manager and kill MSOSYNC.EXE and OSPPSVC.EXE

Tuesday, January 22, 2013

Custom Path in Environment Variables for running STSADM

1) Browse to My Computer ->Right Click -> Properties

2) Click on Advanced Settings

3) Click on Environment Variables

4) Under System Variables->Path ->Edit

From a Sharepoint perspective, if we want to run the stsadm command, we would have to run the command in the below folder from command prompt:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
So to run stsadm in command prompt without browsing to the BIN folder every time, we will append this path to Environment Variables. I am pasting this to the existing value
For Sharepoint 2007, it would be:
;C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\
For Sharepoint 2010, it is :
;C:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN\

5) Click OK.

Implementing Managed Metadata in a Sharepoint List

This is a continuation from Creating Managed Metadata Group, Term Set and Terms. In this post I will be using the Term Set created in the previous post in a Sharepoint List.

1) To begin with, I am creating a new Sharepoint list. (MMD Sample List

2) The next step would be to create a new column. Browse to List Settings-> Create column

3) I am giving the Column Name as MMD Column and the type of the column as Managed Metadata.

4) In the Term Set Settings, select numbers (Term Set) from the MMDGroup1 (Group) by clicking on ManagedMetadata-F (Managed Metadata Service Application).

5) Click OK. Now browse to the list and create a new item

6) Enter the details. You would see that you are given suggestions for the MMD Column.

7) Alternatively, try clicking on the tag symbol for that column.

Creating Managed Metadata Group, Term Set and Terms

To implement Managed Metadata, I will post two entries.The first one would be :

In this post I would be creating Managed Metadata Group, Term Set and Terms.I am trying out this activity at a site collection and not from Central Administration.

1) Go to the site collection Site settings page. Browse to Term Storage Manager page by clicking on Term Store Management.

2) Here you see that the Managed Metadata Service Application (ManagedMetadata-F) is already available. (I created this in a different post).

3) Create a new group under the Managed Metadata Service application by doing a right click ->New Group.   

4) I am naming it as MMDGroup1. I can create permissions for users for managing this group.

5) Under this I would be creating a New Term Set and call it as numbers.

6) Below the Term Sets, I would be creating Terms.

7) In this case it would be the numbers one, two, three, four, and five.

8) Now we have created a New Group, Term Set and Terms. Click Save. Next step would be using this in a SharepointList.

Friday, January 18, 2013

Creating a new SiteCollection in a new database using STSADM

Creating a new site collection in a new database

stsadm -o createsiteinnewdb -url  http://sitecolelctionURLxyz 
                                          -ownerlogin domain\username 
                                          -owneremail emailid     
                                          -lcid 1033 
                                          -sitetemplate STS#0  
                                          -title sitecollectiontitle 
                                          -description sitecollectiondescription
                                          -databasename DB-xyz

Creating a new WebApplication using STSADM

Creating Web application using STSADM

stsadm -o extendvs -url http://webapplicationxyz 
                             -ownerlogin domain\username 
                             -owneremail emailid                  
                             -databasename DB-xyz
                             -apidname apppoolxyz 
                             -apidlogin domain\farmaccount 
                             -apidpwd passwordxyz

Specifies to exclusively use NTLM authentication instead of Negotiate (Kerberos). Kerberos requires the application pool account to be a network service and to be configured by the domain administrator. NTLM authentication works with any application pool account and the default domain configuration.

If this parameter is present, no corresponding site collection will be created for the Web application.

Monday, January 14, 2013

Sharepoint 2010 Load Balance Configuration

Happy new year guys. Finally I got out some time to post this. I wanted to post this exercise in December itself. Anyways it is better to be late than never.

                   Sharepoint has single server installations and multiple server installations. In medium or large farms there are 3 tiers in Sharepoint Farm.

Database Server

Application Server and

Web Front End Server (WFE)

As the number of users for Sharepoint increase we should add more WFE servers to the farm as the user requests are handled by the WFE server. Multiple WFE servers in the farm help to distribute the load. In order to achieve this we would have to load balance the WFE servers. The below post would be a detailed configuration on how to do this. 
At a higher level we would be doing the following steps as a part of this exercise

I) Adding a WFE server to the Sharepoint Farm.

II) Enable the Network Load Balancing feature and configuring the cluster

III) DNS entry for the cluster

I) Adding a WFE server to the Sharepoint Farm.

We are beginning this exercise assuming that one WFE is already existing in the farm.

1) I am installing Sharepoint in another WFE and connecting it to the existing farm. Click Next.

2) Enter the database server (Click Retrieve Database Names) and the database name

3) Enter the passphrase and click Next.

4) Click the Advanced Settings and choose Use this machine to host the web site. Click OK.

5) Click Finish

II) Enable the Network Load Balancing feature and configuring the cluster

1) Now we will proceed with Network Load Balancing installation in the two WFE (web front end) SharePoint servers.

2) We will configure NLB and create a cluster. Start -> Administrative Tools -> Network Load Balancing Manager

3) Right-click Network Balancing and select New Cluster.

4) Connect to one host and add the cluster IP address.

5) Select Multicast. By default this is Unicast.

6) We can define the port rule, but I left it as default.

7) Add the second WFE server to the cluster.

8) Enter the second host name that needs to be part of the new cluster.

9) Set the priority to be 2

10) Click Next,and complete the configuration.    


III) DNS entry for the cluster

1) Create an entry in DNS for the cluster.

2) Set the binding for the site.

3) Modify Alternate Access Mapping for the default site collection from http://xxxxxwfe1 to http://cluster.

The configurations has completed, We can access our site with URL http://cluster.