Yeah, no issues detected nor found.
Have also run it though Test-SPContentDatabase and come up with nothing, all checks and passes. -DB From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Michael Nemtsev Sent: Saturday, 9 April 2011 4:29 PM To: 'ozMOSS' Subject: RE: WSSv3 -> SPF2010 addcontentdbfail Did you try to run stsadm –o preupgradecheck to identity if site can be migrated? See details there http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d-183c-4fc2-8320-ba5369008acb <http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d-183c-4fc2-8320-ba5369008acb&ID=238> &ID=238 Michael Nemtsev Microsoft MVP B: http://msmvps.com/blogs/laflour S: http://www.sharepoint-sandbox.com From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Daniel Brown Sent: Saturday, 9 April 2011 2:37 PM To: ozmoss@ozmoss.com Subject: WSSv3 -> SPF2010 addcontentdbfail Howdy all, Have run into a bit of a brick wall when adding/upgrading a WSSv3 db to a SPF site. Have followed the backup/restore/attach process. In all instances, simplying running stsadm –o addcontentdb should foce an upgrade and all is well…. Howveer not in this instance and im hitting a brick wall When running stsadm –o addcontentdb, it either returns the following error: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20110409-051113-176 was updated by COMPANY\spsetupuser, in the STSADM (3392) process, on machine IP-0A82874C. View the tracing log for more information about the conflict. Regardless of what permissions, security or settings or even what account I’m logged in as! Logs are up at: http://pastebin.com/EgPU3GqU If anyone has any thoughts or ideas or suggestions to try, im out of them…. Checking out the logs, its complaining about the [proc_GetDatabaseInformation] getting supplied more than it should, Checking out the stored proc in the non upgraded vs upgraded contents database does show that the upgraded content database has the extra parameter of @RequestGuid uniqueidentifier = NULL OUTPUT, however modifying this stored proc produces no change in the upgrade process and it something which shouldn’t really need to happen. If anyone has any insight or could take a look, it would be greatly appreciated. Thanks, Daniel
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
