Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 698
  • Last Modified:

Windows SharePoint Services 3.0 move to new server

I just finished moving everything over to our new server and have demoted old server as domain controller.  And I forgot to backed up our WSS 3.0 databases prior to starting the move process, now I can't access sharepoint or the central admin.  And the server names are different,  is there any way to get sharepoint up and running on the new server either by getting the old server up and running again to backup sharepoint without losing data or just to move the content database over to the new server and somehow reattach them to the new server.  Thanks,
0
WolfManBN25
Asked:
WolfManBN25
  • 5
  • 3
1 Solution
 
JarrodCommented:
Hello

You might want to check out

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/MS-SharePoint/Q_21903237.html

Ive done a similar backup and restore using stsadm like the link above but the server was still running prior to me doing the migration. I would think you would need to have the same server name on your old server if possible to get the database services to come up correctly, is this a possibility ? Hope this helps
0
 
zephyr_hex (Megan)DeveloperCommented:
depending on the state of your old sharepoint site, you may be able to do this by moving the content database over.

http://msmvps.com/blogs/cgross/archive/2007/05/09/moving-a-wss-3-0-site-to-a-new-farm.aspx

some of those steps aren't very specific, so please ask if you need clarification.
0
 
WolfManBN25Author Commented:
I have looked at the link but, yes I need clarifications/steps to follow.
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
WolfManBN25Author Commented:
ok zephyr_hex, i just read and that looks like what I would need, but more info(steps) would be helpful for me to restore my WSS 3.0 site.
0
 
zephyr_hex (Megan)DeveloperCommented:
so i assume you don't need help with copying the mdf and ldf files.

the easiest way to attach a db in SQL is to use SQL Management Studio.  just right click Databases and select Attach.

i guess the other generic step is the one that says you should create a new web application.  but that really isn't too hard since it's a configuration in central admin.  you can read more here, if you need: http://technet.microsoft.com/en-us/library/cc287954.aspx

if you have other questions, please ask.
0
 
WolfManBN25Author Commented:
help i don't know where i need to go from here once the databases are attached.

I opened the WSS Central admin and it said i needed to run the setup wizard and it gave me the error message below(db5.png pic)
db.PNG
db2.PNG
db3.PNG
db4.PNG
db5.PNG
db6.PNG
0
 
zephyr_hex (Megan)DeveloperCommented:
you will need to have sharepoint completely installed on the new server.  this means you need to run the config wizard, which creates central admin.

also... you're not going to be able to move your config database.  well, you can try... but it's a nightmare.  you should focus on moving your content db...  and recreate the config from scratch.

also, in case i haven't mentioned... it's really important that the new sharepoint is the exact same patch / service pack level as the original sharepoint.

it looks to me like you're doing a standalone install of sharepoint, which is using the embedded sql.

if that's the case...
then you have a couple of issues.  #1 issue is that the sql instance isn't running.  check services.msc to see if it's running there (or if you can start it from there).  if you can, try a server reboot to see if that gets the sql instance running.  if neither of those works, i'd suggest complete uninstall of sharepoint, and re-install (assuming this is a brand new sharepoint with no content).

by the way, connecting to the embedded sql with management studio is a little different than usual:
http://blogs.msdn.com/dhirajm/archive/2009/01/26/how-to-connect-sql-embedded-edition-to-sql-management-studio.aspx

(and...  if you have full sql installed... why are you using the embedded sql???  but that's another topic for another day)

once you get the sql instance running....
you need to attach those databases to the embedded sql instance.. assuming you're not moving sharepoint to full sql.  gosh... now that i'm writing this... i really think you should consider moving to full sql.  if you choose to do this, the restore process is basically the same.  the difference is the way you install sharepoint.  you'd install it taking the Advanced / Farm option.  then, attach your databases to the appropriate sql instance.  i think that's your best option.

once you have your databases attached to the appropriate sql instance...
create a web app in central admin.  this will create new/blank content database.  so, remove that content db from the web app using central admin.  then associate the web app with your original content db using central admin.  then iisreset.
0
 
WolfManBN25Author Commented:
ok i uninstalled WSS 3.0 and reinstalled with advanced option for server farm.  I only installed front end and that went great.  I was able to get to central admin, and created a site that completed successfully. I deleted the content database and added orginial content database, but when I goto the WSS site I get an error.



Server Error in '/' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>
 

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>
 

0
 
WolfManBN25Author Commented:
i did an iisreset, but that didn't work.
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now