locked
SharePoint master page custom web control (web part) not working for few users RRS feed

  • Question

  • We are facing an issue with the newly added visual web part as web control in the SharePoint master page, It is working for most of the users but giving web part maintenance page error for few users. It is again working after the users restarted their computers. web part is a visual web part added in master page through the SharePoint designer 2010. Have tried with removing cache and delete the history from the user machines but it is working only after one or two restarts. Web part created to display some information of the user from a list to asp.net labels .  Please help me to find what went wrong in the process. 

    Thursday, January 21, 2016 9:45 AM

Answers

  • Hi,

    1. Go to the web config navigation C:\inetpub\wwwroot\wss\VirtualDirectories\port Open the web file and find for call stack and customerror mode change call stack = "true" and customerror mode = "Off", then we can see the detail error message for you to resolve the issue.

    2. Try to use another computer to login SharePoint site to check whether it works or not.

    3. Add some try catch logic in your code and write exception to a log file.

    4. Or try to use the user who meet this issue to debug your code.

    Best Regards,

    Dennis


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, January 22, 2016 8:41 AM

All replies

  • Hi,

    1. Go to the web config navigation C:\inetpub\wwwroot\wss\VirtualDirectories\port Open the web file and find for call stack and customerror mode change call stack = "true" and customerror mode = "Off", then we can see the detail error message for you to resolve the issue.

    2. Try to use another computer to login SharePoint site to check whether it works or not.

    3. Add some try catch logic in your code and write exception to a log file.

    4. Or try to use the user who meet this issue to debug your code.

    Best Regards,

    Dennis


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, January 22, 2016 8:41 AM
  • Thanks, I found the error

     

     


    Tuesday, January 26, 2016 2:21 PM