+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Unknown server tag 'asp:ScriptManager'.

Unknown server tag 'asp:ScriptManager'.

3 posts, 0 answered
  1. E
    E avatar
    2 posts
    Registered:
    19 May 2015
    21 May 2015
    Link to this post

    Hi,

    I was wondering if ​anyone could help me with the following issue:
    Two days ago the gallery page of this simple website (moniportraits.com) started giving this message:

    "Server Error in '/' Application.
    Parser ErrorDescription: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. 
    Parser Error Message: Unknown server tag 'asp:ScriptManager'.
    Source Error: 
    Line 160:<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
    Line 161:
    Line 162: <asp:ScriptManager ID="ScriptManager1" runat="Server"></asp:ScriptManager>
    Line 163:
    Line 164:<!-- begin -->

    Source File: /Gallery.aspx    Line: 162 
    Version Information: Microsoft .NET Framework Version:2.0.50727.4253; ASP.NET Version:2.0.50727.4257 "

    Could anyone help me identify and fix the issue please? 
    Many thanks in advance for any help!

  2. Svetoslav Manchev
    Svetoslav Manchev avatar
    735 posts
    Registered:
    29 Nov 2016
    26 May 2015
    Link to this post
    Hi,

    Do you still have the issue as I can not reproduce it?

    From other hand, you can take a look on that forum discussion.

    Regards,
    Svetoslav Manchev
    Telerik
     
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
     
  3. E
    E avatar
    2 posts
    Registered:
    19 May 2015
    01 Jun 2015 in reply to Svetoslav Manchev
    Link to this post

    Hi,

    Thanks for looking at the issue. It no longer exists, as the hosting company sorted it out.

    Regards

3 posts, 0 answered