Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. WebPartManager Control

WebPartManager Control

Scheduled Pinned Locked Moved ASP.NET
sysadmindatabasesql-serverhelp
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    Kamal Afridi
    wrote on last edited by
    #1

    I have drop just one WebPartManager Control on page, and i am getting following error message, eventhough i did not write any code. An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Any idea please.

    Know Yourself Then Grow Yourself.

    S 1 Reply Last reply
    0
    • K Kamal Afridi

      I have drop just one WebPartManager Control on page, and i am getting following error message, eventhough i did not write any code. An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Any idea please.

      Know Yourself Then Grow Yourself.

      S Offline
      S Offline
      Sebastien Lachance
      wrote on last edited by
      #2

      You need a database back end for the personalization feature. If you do not need it you can add personalization-enabled=false to your WebPartManager. Hope it helped you.

      My Blog

      K 1 Reply Last reply
      0
      • S Sebastien Lachance

        You need a database back end for the personalization feature. If you do not need it you can add personalization-enabled=false to your WebPartManager. Hope it helped you.

        My Blog

        K Offline
        K Offline
        Kamal Afridi
        wrote on last edited by
        #3

        Thanks Dear its working now.

        Know Yourself Then Grow Yourself.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups