Hi Rahul, Thanks for the detailed resolution but I'm keen to resolve this in a supported manner if at all possible.
It has been suggested to me that running the sync -listolddatabases [n] followed by sync -deleteolddatabases may provide a resolution. I never ran the preparetomove command when migrating these sites but as they are all within the same web app I don't think I was required to. Anyone familiar with running these commands and what I might expect? Are the db references rebuilt after the next sweep? Regards, Paul Online Developer, ICT CEO Sydney From: [email protected] [mailto:[email protected]] On Behalf Of Rahul Desai Sent: Tuesday, 28 July 2009 3:51 PM To: [email protected] Subject: RE: Synching issues [SEC=UNCLASSIFIED] With all the disclaimer(s) in place, try this at your own risk. We had an issue with our SharePoint Admin content Database and here are the steps we took to repair the suspected SQL Server Database (thanks to one of our senior developers): - Connect to the SharePoint machine (RDP/VNC or physically) - Open the SQL Server Management Studio - Connect to the server and make sure that you have the administrator rights/privilege - Run the following statements one at a time in the query window of SQL Server Management Studio * EXEC sp_resetstatus [DBName] * ALTER DATABASE [DBName] SET EMERGENCY * DBCC CHECKDB('DBName') * ALTER DATABASE [DBName] SET SINGLE_USER WITH ROLLBACK IMMEDIATE * DBCC CHECKDB('DBName', REPAIR_ALLOW_DATA_LOSS) * ALTER DATABASE [DBName] SET MULTI_USER Hope this helps (and works for you). Best regards Rahul Desai, PMP Microsoft Certified Technology Specialist (MCTS) | WSS, MOSS, SQL Server 2008 +61 408699686 | http://RahulBlog.NationalCom.Com From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Tuesday, 28 July 2009 2:02 PM To: [email protected] Subject: RE: Synching issues [SEC=UNCLASSIFIED] Yeah, it's definitely tied to the content DBs but not sure how to fix it. Other related errors we're getting include: 07/23/2009 09:55:51.12 w3wp.exe (0x2B1C) 0x29D8 Windows SharePoint Services General 8e2r Medium Possible mismatch between the reported error with code = 0x81070504 and message: "There is no Web named "/<sitename>/Shared Documents/Forms/AllItems.aspx"." and the returned error with code 0x80070002. And: 07/23/2009 10:35:01.54 OWSTIMER.EXE (0x06F0) 0x0D34 SharePoint Portal Server User Profiles 791w Medium SweepLog61978000000001 WebApp CEO MySite(f14f10b3-2cd7-42dd-9f5e-8b8bb9c287e8), ContentDB WSS_Content_mysite (f46739f1-4370-4c35-8e6a-9d4ac10854d1), Site http://<server>/personal/<first_last>, User DOMAIN\first.last(91e1b5e9-010f-46b7-a5b1-9bde7c290d75): failed to synch portal property FirstName during sweep synch. Likely this is a new site that doesn't have its schema pushed yet (will occur at the next synch for this ContentDB). Exception follows: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Server.UserProfiles.ProfileCopier.CopyProfileToList(UserProfile up, SPListItem itm) Regards, Paul Online Developer, ICT CEO Sydney From: [email protected] [mailto:[email protected]] On Behalf Of Noja, Fadi Sent: Tuesday, 28 July 2009 1:54 PM To: [email protected] Subject: RE: Synching issues [SEC=UNCLASSIFIED] Our's was caused by deleting and reattaching the DB. Not sure if doing that again will fix the problem though. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Tuesday, 28 July 2009 1:52 PM To: [email protected] Subject: RE: Synching issues [SEC=UNCLASSIFIED] Weird. Seems tied to the local WSS profiles and those in the SSP. Last time this occurred it just mysteriously fixed itself one day. Some people suggest running the synch jobs while others point to deleting and reattaching the content DBs. Would love to know if this is a known bug or just something we're experiencing again. Regards, Paul Online Developer, ICT CEO Sydney From: [email protected] [mailto:[email protected]] On Behalf Of Noja, Fadi Sent: Tuesday, 28 July 2009 1:12 PM To: [email protected] Subject: RE: Synching issues [SEC=UNCLASSIFIED] I've come across it before and the only way I could get the accounts to sync properly was to delete them from SSP and do a re-import. A full import didn't fix it. BUT the issue is still there, so whenever an account has been modified, we have to manually delete and re-import. Never had the time to look into it though, so would like to know a possible solution. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Tuesday, 28 July 2009 1:11 PM To: [email protected] Subject: Synching issues Hi all, I recently created two site collections using createsiteinnewdb. All appears to have gone well but we're in the same boat as we were in a few months back with profile synching, membership links etc. Both sites were created within the same parent web app which includes two other site collections (with their own DBs) that do not suffer from this issue. I used the OOTB team site template. I've pored through the logs and come across some obvious errors but can't find anything online. Has anyone come across this or know of a solution? Only difference I can see between these sites and the functional ones is that SearchServiceInstance isn't defined. Could it be that simple?? e.g. ProfSynch: The site with ID 8bf9c44e-ccf2-46dc-9631-bdc9da7977d9 cannot be synchronized due to an unprovisioned root web at Microsoft.Office.Server.UserProfiles.SiteSynchronizerCollection.GetSynchInfoForSite(SqlDataReader dr, SynchInfo info) at Microsoft.Office.Server.UserProfiles.SiteSynchronizerCollection.<get_Elements>d__0.MoveNext() Regards, Paul Online Developer, ICT CEO Sydney ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
