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. Other Discussions
  3. Clever Code
  4. WSS to MOSS migration

WSS to MOSS migration

Scheduled Pinned Locked Moved Clever Code
helpsysadminjavasharepointquestion
2 Posts 2 Posters 3 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.
  • S Offline
    S Offline
    senylity
    wrote on last edited by
    #1

    So I have a WSS 3 SharePoint site set up here at work that people are starting to use and like. Management won't spring (yet) for the full version Microsoft Office SharePoint Server 2007 (MOSS), so I decided to play with it on a virtual machine using my handy dandy MSDNs. I backed up the WSS site, copied the file to the virtual MOSS server, restored the site collection and copied everything from the webroot of the WSS server to the MOSS server. I had some 3rd party assemblies, my own assemblies, and images to copy over. The new site worked. It was functioning fine. So I started enabling the Enterprise features, ie, the stuff that comes with the pay version. Most things worked, but when I enabled the Enterprise Publishing Infrastructure, my site became hosed.:doh: A web search returned one result of something similar, but not the same problem. Also My Sites won't work. Same problem: The DataSourceID of 'TopNavigationMenu' must be the ID of a control of type IHierarchicalDataSource. A control with ID 'topSiteMap' could not be found.:confused: Did you catch the error yet? It was: copied everything from the webroot of the WSS server to the MOSS server. That included web.config. Don't copy and replace web.config. Please. It makes for a hard time finding out what the problem is. To fix the problem, I had to create a new web application, and a new site collection. Then I merged the two web.configs together. Presto, everything works fine. So the point is: Don't replace web.config, just rename it so you can refer to it later if you have to. This is a good rule of thumb that I should have known by now. :sigh:


    Success is the happy feeling you get between the time you do something and the time you tell a woman what you did. --Dibert My left name is Tremendous Savings, Ms. America – Señor Cardgage

    M 1 Reply Last reply
    0
    • S senylity

      So I have a WSS 3 SharePoint site set up here at work that people are starting to use and like. Management won't spring (yet) for the full version Microsoft Office SharePoint Server 2007 (MOSS), so I decided to play with it on a virtual machine using my handy dandy MSDNs. I backed up the WSS site, copied the file to the virtual MOSS server, restored the site collection and copied everything from the webroot of the WSS server to the MOSS server. I had some 3rd party assemblies, my own assemblies, and images to copy over. The new site worked. It was functioning fine. So I started enabling the Enterprise features, ie, the stuff that comes with the pay version. Most things worked, but when I enabled the Enterprise Publishing Infrastructure, my site became hosed.:doh: A web search returned one result of something similar, but not the same problem. Also My Sites won't work. Same problem: The DataSourceID of 'TopNavigationMenu' must be the ID of a control of type IHierarchicalDataSource. A control with ID 'topSiteMap' could not be found.:confused: Did you catch the error yet? It was: copied everything from the webroot of the WSS server to the MOSS server. That included web.config. Don't copy and replace web.config. Please. It makes for a hard time finding out what the problem is. To fix the problem, I had to create a new web application, and a new site collection. Then I merged the two web.configs together. Presto, everything works fine. So the point is: Don't replace web.config, just rename it so you can refer to it later if you have to. This is a good rule of thumb that I should have known by now. :sigh:


      Success is the happy feeling you get between the time you do something and the time you tell a woman what you did. --Dibert My left name is Tremendous Savings, Ms. America – Señor Cardgage

      M Offline
      M Offline
      megaadam
      wrote on last edited by
      #2

      I would rather get my handy dandy hands on K8 MOSS than working with such desk stuff...

      _____________________________________ Action without thought is not action Action without emotion is not life

      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