Hi all,

We had 2 sharepoint sites and old one and new one, one was sharepoint.domain.com the other sharepoint2.domain.com

sharepoint2.domain.com is the new one and we took down and removed all records(dns) of sharepoint.domain.com.

We now want all the sites within sharepoint2.domain.com to reflect sharepoint.domain.com

I made the changes in iis and dns and with alternate access mappings, however when you go to sharepoint.domain.com the main site is fine, however if you click off into one of the links to go to a sub page, nothing loads.

I am assuming this is because the system is going by root application/site, and if I understand correctly root application is the site name the virtual directory is trying to use.

We are also trying to transition the addresses so the end users dont have to much change at once.

So my question is, how can we get sharepoint.domain.com to work completely for the new sharepoint so users can click around and have the pages load, AND for now still be able to use sharepoint2.domain.com and do the same thing?

I know creating the alternate access mapping is pretty much like a redirect, and that works, however I would like sharepoint.domain.com to be the working site that shows in the URL

This is Sharepoint 2013

I hope someone has any ideas, or at least this makes sense.

could you please share your AAM page screen shot?

also what is your sharepoint infrastructure, i.e app server, wfe, using load balancing?

We are not using Load Balancing for the sharepoint server.

We have IIS in an IIS Cluster.

We are using Sharepoint for document list and reports.

I hope that answered your questions.

The goal will be to make sharepoint.doman the default, however when I did that the site stopped working all together. Again thinking it has to do with the root application or something

according to my little SharePoint Knowledge, just correctly configured the AAM  and Correctly Point your DNS to WebAPP. you all set. 

Only thing worried, if you hard coded the URL in your site, which you have to manually update.

DNS is pointing correctly.

And I believe AAM is currently configured correctly.

The only thing is when I change the default Public URL to sharepoint.domain it does not work. This makes me think there is somewhere else within sharepoint config this needs to be set .

Sorry, I paste the image in, but I guess it didn't take. Here it is again

Also, if I add sharepoint.domain to its own public URL

I can get to sharepoint but get this error:

Error

Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists. Correlation ID: 529a4b9c-28f2-20ad-3d20-ed3488b95ab6.

Restart the Web From Servers and check again

I'll try that tonight. Is this the server that central Administrator is installed on, or the IIS Servers. Central Administrator is on 1 server and we have an iis farm set up on 2 other servers

I rebooted the servers and I am getting the same error

I am little confused, in starting post you mentioned that you delete all DNS for sharepoint.domain and only sharepoint2.domain is there, In the DNS you point it to right server. In IIS did you have any host header info.

But Now you also mentioned that sharepoint.domain throwing error but i believe its deleted.

Sorry, we removed all old records of sharepoint.domain, which were pointing to the old sharepoint.

We added the new records as well as added the new iis settings so sharepoint.domain points to the same location as sharepoint2.domain.I added an AAM record so there is a public URL for the zone so I can now get to the site using sharepoint.domain

However when I go there, the titles load for the libraries but i am getting a web part error on all the pages:

Error

Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists. Correlation ID: 24b44b9c-3842-20ad-3d20-edb69b79863d.

Everything loads fine still on sharepoint2

So I added other public URL, https://sharepoint.domain and the web parts load fine. I don't get that

whats in the ULS log for this Correlation ID "24b44b9c-3842-20ad-3d20-edb69b79863d"