I have created mulitple calender lists  in my sharepoint site and I have used this feature to overlay different calenders views on main calendar list and added this calender list  as a list view webpart to a page. Issue I came accross is when I migrate my site one environment to another using site backup and restore operation. After site is restored to different environment,  my calender view webpart does not show up any calendar data and throws up below error

 "The Web application at https://spsites.com/sites/ical could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application. (2c52a67a-95df-44d3-8055-2a6b049ba1fb)"

Later I realised that every calender view has "CalendarSettings" property which holds the calendar overlay configuration data(in the form of XML) such as  weburl, list name , calendar view name and url. Some how the  Sharepoint saves WebURL property as is i.e. if you are working dev environment and you specified the "WebURL" of site, this URL is saved as is and it persists.

Below is the calendar settings

<AggregationCalendars>
    <AggregationCalendar Id="{99ddb82c-9g2k-4d5c-9b7f-3ee27cf5c972}"
                         Type="SharePoint"
                         Name="Calendar"
                         Description=""
                         Color="3"
                         AlwaysShow="True"
                         CalendarUrl="/Lists/Calendar/calendar.aspx">
        <Settings WebUrl="https://spsites.dev.com"
                  ListId="{C539CE83-EFAF-4AC8-B725-F8D41C9FDB2C}"
                  ViewId="{A8A9D082-2C61-44D3-BB8A-C855919AB45D}"
                  ListFormUrl="/Lists/Calendar/DispForm.aspx" />
    </AggregationCalendar>
</AggregationCalendars>

 So even when the site is restored to the other environment, "WebURL" value will still point to old environment which cause this above mentioned error.

Solution 

   I have programmatically accessed the "CalendarSettings" and replaced the "WebURL" property and also remapped existing calendar view UR

XmlDocument  xml = new XmlDocument()

xml.LoadXml(view.CalendarSettings.Replace("https://spsites.dev.com/sites/ical", ""https://spsites.prod.com/sites/ical"));            

  XmlNodeList calendars = xml.SelectNodes("/AggregationCalendars/AggregationCalendar");             

   if (calendars != null)

      count = calendars.Count;            

   foreach (XmlNode node in calendars)

     {               

     if (node.Attributes["Name"] != null && node.Attributes["Name"].Value == "ROB Calendar") // check for list name

         {

                      XmlElement parentElement = (XmlElement)node;                     

                      string calendarurl = node.Attributes["CalendarUrl"].Value;

                        calendarurl = calendarurl.Substring(calendarurl.LastIndexOf('/') + 1);

                        parentElement.SetAttribute("CalendarUrl", site.ServerRelativeUrl + "/Lists/ROBCalendar/" + calendarurl); //set the calendar url

                       XmlElement childElement = (XmlElement)node.ChildNodes[0];

                        childElement.SetAttribute("ListId", "{" + robList.ID.ToString() + "}");         //list id            

                         SPView robView = checkView(robList.Views, view.Title.ToLower());            //check whether view exists         

                        if (robView != null)

                            childElement.SetAttribute("ViewId", "{" + robView.ID + "}"); // if view exists set the view id otherwise set the default id

                       else

                           childElement.SetAttribute("ViewId", "{" + robList.DefaultView.ID + "}");

                           childElement.SetAttribute("ListFormUrl", site.ServerRelativeUrl + "/Lists/ROBCalendar/DispForm.aspx"); //list form url

                           childElement.SetAttribute("WebUrl", siteURL);//set weburl

                    }   

view.CalendarSettings = xml.OuterXml;

            view.Update();  // Update the view

 Finally Calendar shows up data

</

//code to create MMC column

 TaxonomySession currentSession = new TaxonomySession(site);

var termStore = currentSession.TermStores["ManagedMetaDataService"];

var group = termStore.Groups["Industry"];

var termSet = group.TermSets["Engagement Phase"];

TaxonomyField field = new TaxonomyField(site.RootWeb.Fields, "TaxonomyFieldTypeMulti", column);

field.SspId = termStore.Id;

field.TermSetId = termSet.Id; 

//Based on some configuration file I was setting fields “AllowMultipleValues” property

if (columnNode.Attributes["allowmultiplevalues"].Value.Equals("yes"))

     field.AllowMultipleValues = true;

   field.Group = MMSConstants.groupName;

   rootWeb.Fields.Add(field); // Created a site column and later on programmatically added to content types and to document library 

MMC column got added to one of the document library. Below code is do "Group By" on created column  for the respective library

//Code to set the document library default view. I was doing “Group By” on created MMC column 

SPView allDocumentsView = spList.Views["All Documents"];

SPViewFieldCollection allviewFields = allDocumentsView.ViewFields;

// Setting the “Group by” query

string viewQuery = "<GroupBy Collapse=\"TRUE\" GroupLimit=\"100\"><FieldRef Name=\"Engagement_x0020_Phase\" /></GroupBy>";

allDocumentsView.Query = viewQuery;

allDocumentsView.Scope = SPViewScope.Recursive;

allDocumentsView.Update(); 

After execution of this code, MMC column got added to document libraries successfully but then I saw strange issue with the “Group by” on created MMC column.

As I understand “Group By” on MMC column with “AllowMultipleValues = true;” will not work properly but I was not setting this property I went to column properties and verified. Allow multiple values checkbox is unchecked.

But still created MMC column was behaving as a column with “Allow multiple values” property turned on.

After some investigation I have realised that we need to explicilty  set "Allow multiple values"  to "false". 

//modified code added else blog

//Based on some configuration file I was setting fields “AllowMultipleValues” property

if (columnNode.Attributes["allowmultiplevalues"].Value.Equals("yes"))

    field.AllowMultipleValues = true;

else  // added else block

  field.AllowMultipleValues = false; 

I was thinking that by default “AllowMultipleValues” is set to “false” but  that was not the case. And at the end “Group By” worked out properly (see below).

Later on I realised  that TaxonomyField inherits from SPFieldLookup

public class TaxonomyField : SPFieldLookup (Ref : https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.taxonomy.taxonomyfield.aspx#Y228

Value to be set to field to be formed in below format

For multiple value : id;#name|guid;#id;#name|guid  here “id” is nothing but the ID column value in the TaxonomyHiddenList(/Lists/TaxonomyHiddenList)

and  code is

var multipleterms = new List<string>();

for(int i = 0; i < multiplevalues.Count; i++){TermCollection terms = termSet.GetTerms(multiplevalues[i].ToString().Trim(), true); 

if (terms.Count >= 1){

int[] ids = TaxonomyField.GetWssIdsOfTerm(listfield.ParentList.ParentWeb.Site, termSet.TermStore.Id, termSet.Id, terms[0].Id, true, 1); 

int WssId = -1; 

if (ids.Length >= 1)

WssId = ids[0];

multipleterms.Add(WssId + ";#" + terms[0].Labels[0].Value + TaxonomyField.TaxonomyGuidLabelDelimiter + terms[0].Id.ToString());

}

if(multipleterms.Count >= 1){

string allvalues = String.Join(";#", multipleterms.ToArray());

log.WriteErrorTrace("Default(multiple) value: " + allvalues + " for the column: " + listfield.InternalName, "", false); 

SPFieldLookup lookup = (SPFieldLookup)listfield;

lookup.DefaultValue = allvalues;

lookup.Update();

}

 Add a below attribute on the class

[SoapDocumentService(RoutingStyle = SoapServiceRoutingStyle.RequestElement)]

Class MyService{

 // [WebMethod]

 }

1. Enable the "Named Pipes"--> Go to  SQL Server Configuration Manager-->SQL Server Network Configuration-->Protocals for "sqlserver"

2. Specify TCP Port

Now run below command

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>stsadm -o activatefeature -name DataConnectionLibrary -url  https://../

Now we can see DCL option available for library creation