Error 404 with Calendar Overlay across 2 Web Applications (part 1)

Hi all,

Last week, I received a mail asking me if there was an issue with SharePoint.

The reported problem was that the client got an “Error 404” page when opening an item in her Overlay Calendar.

So, first thing first, is to reproduce the issue;

The client is using a calendar in her SharePoint Site (let’s call it TT2013MMA from the shpTeamCalendar Web Application).

Then she added the calendar of another site (let’s call it WW2013MMA from the shpWorkCalendar Web Application).

All is working like a charm, as the items of both calendars are correctly added, named in the TT2013MMA Calendar.

The problem start when you click on one of the items.

If the item is from the same calendar (the TT2013MMA), the details of this item is opened and can be reviewed/modified.

If the item is from the calendar located on the other Web Application (WW2013MMA), we got a nice looking 404-Error page not found.

I made some research, and I notice that doing calendar overlay across multiple Web Application gave the same problem.

http://sharepoint.stackexchange.com/questions/58218/sharepoint-2010-calendar-overlays-acoss-2-web-appllications               

http://www.dotnetspark.com/links/56569-cant-overlay-calendar-from-differnet-web.aspx      

http://social.technet.microsoft.com/Forums/sharepoint/en-US/7ad58dab-a707-4bf6-ac1d-3fbe20fcfe44/calendar-overlay-across-multiple-site-collections

So, at the request of Microsoft, I’ve reproduce with success the issue in my Test Farm with 2 brand new Web Applications.

Server name : test.domain\TestServerName

Tests were done with in both sites: test.domain\MyLogin (Mathot Marc)

Calendar working with Overlay : http://shpWorkCalendar-test.domain/sites/WW2013MMA

Calendar of the second Web App : http://shpTeamCalendar-test.domain/sites/TT2013MMA

The Overlay Calendar is on http://shpWorkCalendar-test.domain/sites/WW2013MMA

And the item added from this calendar are in green.

The overlayed calendar (from the second Web Application), is on this site : http://shpTeamCalendar-test.domain/sites/TT2013MMA

The items from the TT2013MMA calendar are in yellow.

Calendar using the Overlay in the shpWorkCalendar Web Application:

 Calendar from the second Web Application : shpTeamCalendar

Now, let’s check the URL pointing to the different items in the shpWorkCalendar:

                The URL is correct :

-          Web Application of the Calendar : shpWorkCalendar

-          Site (WW2013MMA) is created on the shpWorkCalendar Web Application

The URL of the item is incorrect:

-          Web Application of the calendar is shpWorkCalendar

-          Site (TT2013MMA) is created on shpTeamCalendar and NOT on shpWorkCalendar.

SharePoint is pointing to the source Web Application (shpWorkCalendar) instead of the correct URL where the item was created.

The correct URL must be : http://shpTeamCalendar-test.domain/sites/TT2013MMA/Lists/Calendar/DispForm.aspx?ID=3

Same fort his second item :

                The correct URL must be : http://shpTeamCalendar-test.domain/sites/TT2013MMA/Lists/Calendar/DispForm.aspx?ID=2

And also for the last one:

               The correct URL must be : http://shpTeamCalendar-test.domain/sites/TT2013MMA/Lists/Calendar/DispForm.aspx?ID=1

  

Result on clicking on the NOK item, is a Error-404 page.

My vendor already made testing, and had the same results as mine.

Now, waiting for the Microsoft specialist to make the same tests, and give his feedback.

So, as far as from now, I have no solution, nor workaround.

... to be continued...

Unable to enter the Enterprise Licence on SharePoint Server 2010

Hi all,

This time, I was asked to install the Enterprise Licence into our Standard SharePoint 2010 Server test Farms.

We have 3 Farms in Test environment:

-          Collaboration Farm (4 VM)

-          Application Farm (1VM)

-          Service Farm (2 VM)

So, I tried to add the Licence Key via the Central Admin GUI, and I always got an error : “An error occurred”.

After close work with Microsoft, I set the logs into Verbose mode and reproduce the issue, and then finished by running the Microsoft Diagnostic tool for SharePoint.

Then, I got an explanation of my problem.

This issue happens when the Farm does not have enough resources or the load is too high or a combination of both (VM servers, in a test environment – less CPU and less RAM than in production), the upgrade process wants to upgrade all services (new ones for instance) and so on, on all servers.

It’ll try this 3 times, afterwards it gives a time-out as being impossible because the Farm was too busy.

Then, I’ve executed with success the proposed action, explained hereunder:

Action plan:

========

Please take all necessary measures before executing the action plan in order to be able to restore your Farm from backups.

1. Create a simple console application (code) that does nothing, just returns a success code, call it psconfig.exe (see details below)

2. Backup the original psconfig.exe and replace it with the previously created app.

3. Perform the operation (Enable Enterprise features)

4. Restore the original psconfig.exe

5. Run psconfigui.exe on all servers in the farm

Details:

If you don’t have visual studio installed you can use the compiler to create the exe file. 

Steps:  

1. Create new text file and write this piece of code:

Code sample: 

namespace customapp 

{ 

  class Program 

    { 

      static void Main(string[] args) 

        { 

          System.Environment.ExitCode = 0; 

        } 

    } 

}

2. Save the file as psconfig.cs

3. Open a command prompt by choosing “Run as administrator” 

4. Put the created file in c:\<location>

5. Navigate to C:\Windows\Microsoft.NET\Framework64\v2.0.50727 folder 

6. Run the csc command giving as parameter the source file (c:\psconfig.cs) 

• e.g. C:\Windows\Microsoft.NET\Framework64\v2.0.50727>csc c:\psconfig.cs

7. The file psconfig.exe will be created on path C:\Windows\Microsoft.NET\Framework64\v2.0.50727>csc c:\psconfig.cs

==========================================

And that’s it!

Now, I have to plan a technical activity to add the Enterprise Licence into my production Farm.

According to Microsoft specialist, I’ll not facing the same issue as my production Farm has enough CPU/RAM.

But in case of, I have this procedure, tested and approved.

Job’s done.