Share
ReportWe are in the process of upgrading from CRM 2011 on premise to 2016 on premise (version 8.0.1.97)
Our 2011 environment is connected to 2010 SharePoint on premise and we plan to have our 2016 environment also connected to the 2010 SP on Premise.
We have a 2016 DEV/Test environment that was an upgrade copy from 2011 production and are attempting to connect it with our 2010 on premise SP DEV environment which is also a copy of the 2010 prod SP environment. When we attempt to update the absolute URL for the Default SiteCollection to the URL for the dev SP site the wheels spin and eventually a sql timeout error occurs with no other real information. We have one plugin on the update or create of that entity to encrypt the password field but whether on or turned off the error still occurs. Making the same update in a developer sandbox works just fine. However those are not copies of production data . My guess is updating the URL causes some kind of updates to occur somewhere else in other AIM records but not sure. I turned on auditing for other record types I thought might be culprits (documention locations etc) but nothing has shown up. I'm not sure what it might be attempting to do behind the scenes.
Thank you,
*This post is locked for comments
All responses (
Answers (
291,280
