Issue:

On a SharePoint farm: When clicking on an event in a Bamboo Calendar Plus Webpart page, then clicking close on the even. User is redirected to the actual calendar and not the page with the Bamboo Calendar Plus WebPart on it.

On a different SharePoint farm: When clicking on an event in a Bamboo Calendar Plus Webpart page, then clicking close on the even. User is redirected to the page with the Bamboo Calendar Plus WebPart on it.

Expected behavior is to be taken back to the page with Bamboo Calendar Plus WebPart page on it.

 

Identification:

Opened Notepad and reviewed the URL of the Bamboo Calendar Plus Web Part page.
Original Web Part URL:

http://myspsite/sites/testpage/SitePages/bambootest.aspx

Item URL on non-working Site:
http://myspsite/sites/testpage/Lists/BambooTest3/DispForm.aspx?ID=1&Source=http%3A%2F%2FIMASHAREPOINTSERVER%2Fsites%2Ftestpage%2FSitePages%2Fbambootest%2Easpx%3FCalendarDate%3D11%2F9%2F2016%26CalendarView%3DMonthView%26wpGuid%3Dg%5F671100a8%5F2026%5F4665%5F94ea%5F02b7b0809521&ContentTypeId=0x0100F10BEFEE614D1A4F901921532063D964&RootFolder=%2A

 

Item URL on working site:
https://wellbehaving.happydomain.com/projects/LOOKATME/IMPORTANT/Lists/Calendar/DispForm.aspx?ID=911&Source=https%3A%2F%2Fwellbehaving%2Ehappydomain%2Ecom%2Fprojects%2FLOOKATME%2FIMPORTANT%2FSitePages%2FEvent%20Calendar%2Easpx%3FCalendarDate%3D4%2F1%2F2016%26CalendarView%3DMonthView%26wpGuid%3Dg%5Fa0df6487%5F0c69%5F4ff3%5F8ff1%5Fcbedae910f75&ContentTypeId=0x01020078724FAFD8AA094094F61C7DC273E72F&RootFolder=%2A
Cause:

When you look at the &Source=  URL of the working vs non-working, you see the source on the working farm points to the same web application name as the webpart URL, while on the non-working the source name is different. In my case the server name.  This is caused by an incorrect configuration with the AAM for the Web Application on the farm.
Resolution:

I checked Central Administration -> System Settings -> Configure alternative access mappings.
Changed the Alternative Access Mapping Collection to my problematic web application.

aam_clean

Then I see multiple AAM’s all set at the Default Zone. There should be 1 URL per zone. So to remove the problematic AAM’s, click on the Internal URL of the AAM you want to delete. Then Click Delete. In my case the IMASHAREPOINTSERVER AAM was not used, I don’t even know why it was created, but there it was in all of it’s gloriously redirect breaking glory.

Hope this helps someone.

Happy SharePointing

TRM

(82)