Forums

System can't start Cancel The title field is required!

1. IT Admin

   

   11 posts
   Registered:
   24 Sep 2021
   29 May 2022

   Link to this post

   Hi there,
   
   We have met a problem when deploying our system to Production. Could you please provide support? Thank you.
   
   The problem we have encountered as follow:
   1. We have successfully setup the portal on Azure App Service.
   2. Uploaded the license file provided by TPC, as requested by setup page.
   3. Portal restarted and stuck as "Please wait a moment. We'll be back shortly"
   4. We have tried many ways to resolve this issue including reupload the website, checking the web configure etc.
   
   There is no error log show. Our current portal version is 14.1.7800.0 and Portal Connector version v6.1.141.126.
2. Brady Ward

   

   92 posts
   Registered:
   19 Aug 2021
   30 May 2022 in reply to IT Admin

   Link to this post

   Hello IT,
   
   There should hopefully be some error generated if it's stuck on site initialization. Using Azure App service you have 2 options. You can either:
   
   1. Grab the FTP information by going to the issue app service and clicking "Get Publish Profile" and then FTP to the server and go to ~/App_Data/Sitefinity/Logs/Error.log
   2. Use the Kudu service to view your file system and go to ~/App_Data/Sitefinity/Logs/Error.log
   
   Let me know if that is not the case,
   
   Brady
   TPC Web Developer
3. IT Admin

   

   11 posts
   Registered:
   24 Sep 2021
   31 May 2022 in reply to Brady Ward

   Link to this post

   Hi Brady,
   
   Thanks for the information and we can retrieve the error log finally.
   Refer to the log, I can found the following message. May I know is it means the key is already added, so the Production system can't be up?
   
   Message: System.ArgumentException: An item with the same key has already been added.
   
   Best regards,
   Eric
4. Brady Ward

   

   92 posts
   Registered:
   19 Aug 2021
   Answered

   31 May 2022 in reply to IT Admin

   Link to this post

   Hello Eric,
   
   I would need to see the full error message/stack trace to get a better idea but most likely that is what is causing your issue. During the upgrade/initialization, there is likely a database item that has already been added.
   
   As general troubleshooting, you can try forcing a re-upgrade using this article (always back-up before): https://community.progress.com/s/article/an-item-with-the-same-key-has-already-been-added-during-upgrade
   
   All the best,
   
   Brady
   TPC Web Developer
5. IT Admin

   

   11 posts
   Registered:
   24 Sep 2021
   31 May 2022 in reply to Brady Ward

   Link to this post

   Hello Brady,
   
   We have identified the issue after further investigate on the error log. It seems developer had made a mistakes on the credential during deployment to Azure which cause deploy to incorrect site and cause the issue. Thanks for your help.
   
   Best regards,
   Eric
6. Brady Ward

   

   92 posts
   Registered:
   19 Aug 2021
   01 Jun 2022 in reply to IT Admin

   Link to this post

   Hey Eric,
   
   Lots of moving pieces! Glad to hear you were able to get it resolved.
   
   All the best,
   
   Brady
   TPC Web Developer