Go Premium for a chance to win a PS4. Enter to Win

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

Migration SBS 2003 to SBS 2008 - Problems backing up Sharepoint site

Hi!
I'm in the middle od migrating a Swedish SBS2003 to an english SBS2008, and I'm at the task of migrating the companyweb.

All task on source server (ALTFTSBS) went without problems.

On destination server (FTSRV) I ran into authorization problems accessing parts of Sharepoint Central Administration, but finally I found a way through that, not clear on exactly what worked, but now I can access it through the external address http://remote.fargtrend.se:4721.
Access through local address http://ftsrv:4721 still dosn't work, it asks for authorization which fails whatever user I try with.

However, I have done the steps in SCA to prepare for migration, but when I try to export the upgraded OldCompanyWeb site, I get this error message:

[3/7/2011 4:40:46 PM]: Start Time: 3/7/2011 4:40:46 PM.
[3/7/2011 4:40:46 PM]: Progress: Initializing Export.
[3/7/2011 4:40:47 PM]: Progress: Starting Export.
[3/7/2011 4:40:47 PM]: Progress: Calculating Objects to Export.
[3/7/2011 4:40:47 PM]: Error: The object with Id 1444f99a-059b-495e-8914-cbf1020c6f8d that was configured as part of the Export Settings no longer exists.
[3/7/2011 4:40:47 PM]: FatalError: The object with Id 1444f99a-059b-495e-8914-cbf1020c6f8d that was configured as part of the Export Settings no longer exists.
   at Microsoft.SharePoint.Deployment.SPExport.AddExportObjectToTempTable(SqlCommand command, Guid siteId, Guid objectId, String url, SPDeploymentObjectType objectType, SPIncludeDescendants includeDescendants, Boolean isLink, Boolean isSelected)
   at Microsoft.SharePoint.Deployment.SPExport.SeedExportObjectsTable()
   at Microsoft.SharePoint.Deployment.SPExport.CalculateObjectsToExport()
   at Microsoft.SharePoint.Deployment.SPExport.Run()
[3/7/2011 4:40:47 PM]: Progress: Export Completed.
[3/7/2011 4:40:47 PM]: Finish Time: 3/7/2011 4:40:47 PM.
[3/7/2011 4:40:47 PM]: Completed with 0 warnings.
[3/7/2011 4:40:47 PM]: Completed with 2 errors.

I cannot browse the OldCompanyWeb either from the internal or the external address, so it's probably due to the same authorization error.

Now what, any ideas?
0
TBerglund2
Asked:
TBerglund2
1 Solution
 
sabby447Commented:
Interesting issue, Here is what i could find online:
http://social.technet.microsoft.com/forums/en-US/sharepointadmin/thread/ac6371b5-11ee-4791-bf07-66ace2ca6fdc/

Looks like you need to apply all the latest updates for 2003 edition first
0
 
TBerglund2Author Commented:
I'm not sure it applies, since the export from the old server worked fine.

I am now solely on the destination server, and the import and upgrade of the old Companyweb from the SBS2003 server has also worked fine.

The current problems are:
1. I cannot browse the site for the old companyweb: http://OldCompanyWeb.
The new companyweb site works fine, always has.

2. I cannot export the oldcompany site.
When I try I get the error message above.

It is most likely a problem with authorization, but what?
0
 
screen-nameCommented:
You should probably be doing a DB migration, not an import/export.  I not super familiar with Sbs, but I am fairly sure you can't do that with moss.
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
TBerglund2Author Commented:
I am only following the migration guide, are you saying that is not the way to go?
I have searched around a little, and it seems like many have solved the problem by just deleting the OldCompanyWeb site and recreate it.
I'm trying that as we speak, will let you know how it goes.
0
 
screen-nameCommented:
Can you link me the migration guide you are using?
0
 
TBerglund2Author Commented:
It's the one on the server locally, cannot link that.
It seems, when I read the fine print, that you cannot browse to local websites from the server without installing "Desktop Experience".
However, there's no problem browsing it from a client.

But, I still had problems importing the old companyweb into the new companyweb, due to different languages.
I the set up a sub-site under companyweb with the same language as the old companyweb, but it stopped with an error saying something about "that name has already been used".

So, since the imported and converted OldCompanyWeb-site was up and running fine, I simply redirected CompanyWeb to OldCompanyWeb and that is how it will be from now on. :)
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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