Search not working in site collections migrated from MOSS 2007 to SharePoint Server 2013

I have few site collections migrated from MOSS 2007 to SharePoint Server 2013 using database attach (first to 2010 and then to 2013).
When I search for anything in these migrated sites, I get "Nothing here matches your search".
Checked the crawl log for these sites and see this error for all items.
The content processing component failed to process the security descriptor of the item. ( The input ACL is invalid (1210 / 2072).; ; SearchID =
Some-Random-GUID )
Search works fine in newly created sites in 2013 environment.
Please help.

Hello
Did you migrate your users to claims when you migrated the databases?
$wa = Get-SPWebApplication http://yourdom.com
$wa.MigrateUsers($true)
$wa.ProvisionGlobally()
I assume the sites that work and the migrated content are in the same database?
MCITP-EA | "Never test how deep the water is with both feet"

Similar Messages

Data Migration from MOSS 2007 to SharePoint 2010

Hi,
We have done a migration project for one of our client.
This migration was done from MOSS 2007 to SharePoint Enterprise Server 2010.
After the migration was completed we developed lot of new webparts, lists ,application pages in this newly migrated farm in SharePoint Enterprise Server 2010.
However the entire project took around 1 year due to some unavoidable delays. During this one year our client was using MOSS 2007 sites for there work. hence the data in MOSS 2007 farm/sites was continuously updated.
Our client needs to go live in next month and also needs the sites/lists/libraries which are migrated in new SP 2010 farm to be updated as per the MOSS 2007 farm.
Kindly suggest best possible way to achieve this data migration since last 1 year from MOSS 2007 to newly migrated SharePoint Enterprise Server 2010 farm.
Kindly note we have done lot of customization and new developments in newly created SP 2010 farm.
Thanks and regards,
Amien

Hi there,
If you have already taken care of customization on SP2010 server. Then use any of the migration tools available in market to migrate data to target SP server.
Content Matrix gives free 25 GB to migrate your SharePoint data (https://www.metalogix.com/Resources/Promotions/Content-Matrix-Migration-Express-Download.aspx).
If you don't know what is changed in last 1 year, then best thing to do is add new content database and migrate your data into it.
Hope that helps.
Regards,
Tapan

Losing out custom metadata info of few documents of a document librarby when migrated from MOSS 2007 to Sharepoint 2010

We have recently migrated from moss2007 to sharepoint 2010.We have a document library containing large no. of documents in it & for those documents there are some custom metadata columns apart from OOB library columns . We have user content DB attach
migration and after that we can see blank value under the custom columns for some records. However interesting point is we can see this metadata is showing for few documents.
Please suggest.

Hi,
What is your Office edition? When we create a managed metadata column in a Document Library, it will prompt that ‘Earlier versions of client programs might not support this type of column’. You should use Office 2010 to edit and create a document then save
to document library .
For detailed information ,please refer to this article:
http://rules.ssw.com.au/SoftwareDevelopment/RulesToBetterSharePoint/Pages/2010-Managed-Metadata-with-Office-2007.aspx
Beside, here are similar posts, you can use as a reference:
https://social.technet.microsoft.com/forums/sharepoint/en-US/1b115343-20e5-4962-af97-793194f07637/metadata-missing-when-revising-document
https://social.technet.microsoft.com/Forums/office/en-US/a65f9828-6e2f-4eb7-bde6-bd0600e3b1a2/migrating-documents-from-moss-2007-to-sharepoint-2010?forum=sharepointadminprevious
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Migrating from Moss 2007 to SharePoint 2013

I am reaching out here as we require some inputs around migrating the SharePoint based application from MOSS 2007 to 2013.Please find more details from below
Requirement:
Migrating SharePoint site collection (which contains just 1 Top level site and 2 libraries with in it and no item level/library level permissions exists) which is on MOSS 2007 with size of 500GB to SharePoint 2013, hence we like to know your inputs in related
to this
Note:
1) The site collection has its own separate content database
2) There are nearly 200 thousand documents where the document with higher version is 90
3) The documents are stored in the libraries with up to third level of folder structure
4) The site collection is created based on custom site definition (created using visual studio)
Few things that I like to mention/ask here
a) Having 500GB data in one single content database inj the MOSS 2007 environment does it impacts the site performance?
b) Migrating the site collection as is onto single content database (all 500 GB into one content database) into destination SharePoint 2013, does it will be a good practice? Hope SharePoint 2013 content database limit is 200 GB, hence moving 500GB
as is into one database will it be good practice?
c) Does database attach and detach works for the databases which are of size 500GB?
d) Can we do database attach and detach directly from MOSS 2007 to directly onto SharePoint 2013, without hopping onto SharePoint 2010 in between and then later to SharePoint 2013?
e) If moving 500GB data into one content database will not be a good approach, can we split it onto multiple databases?
f) If database attach and detach doesn’t help for databases which are of size 500GB, should we go for any tool based approach? If yes, which tool does best fit?

a) Having 500GB data in one single content database inj the MOSS 2007 environment does it impacts
the site performance?
Inder: Yes, it will impact site performance at large extended, recommended is 200 gb only. Check it IO of your disk to analyze performance issue
b) Migrating the site collection as is onto single content database (all 500 GB into one content
database) into destination SharePoint 2013, does it will be a good practice? Hope SharePoint 2013 content database limit is 200 GB, hence moving 500GB as is into one database will it be good practice?
Inder:
Content database size (all usage scenarios)
4 TB per content database
Supported
Content databases of up to 4 TB are supported when the following requirements are met:
Disk sub-system performance of 0.25 IOPs per GB. 2 IOPs per GB is recommended for optimal performance.
You must have developed plans for high availability, disaster recovery, future capacity, and performance testing.
http://technet.microsoft.com/en-us/library/cc262787%28v=office.15%29.aspx#ContentDB
c) Does database attach and detach works for the databases which are of size 500GB?
Inder: Yes it does work
d) Can we do database attach and detach directly from MOSS 2007 to directly onto SharePoint 2013, without
hopping onto SharePoint 2010 in between and then later to SharePoint 2013?
Inder: No, you need to pass through 2010 and then 2013
e) If moving 500GB data into one content database will not be a good approach, can we split it onto
multiple databases?
Inder: you can go with 500 gb
f) If database attach and detach doesn’t help for databases which are of size 500GB, should we go for
any tool based approach? If yes, which tool does best fit
Inder: Below are few tools you can try
http://www.metalogix.com/Products/Content-Matrix.aspx
http://en.share-gate.com/
http://www.avepoint.com/sharepoint-migration-tools/
http://www.quest.com/sharepoint/migration.aspx
If this helped you resolve your issue, please mark it Answered

Alerts are not working for Site collections in a content database

Hi,
We have been into a strange issue that alerts are not working for site collections from a particular content database. When user subscribed for the alerts, they are getting mail about their subscription but not after that for any new items/documents added
or changes happen in the list/document library.
We have tried with Immediate as well as scheduled alerts both are not working.
FYI, Alerts for all other site collections from different content database for the same web application are working without any issues.
Any help would be appreciated.
Thanks
Ramkumar

Looks like an Timer job Issue for your web application. Can you please check if these jobs are enabled and check error log for the alerts Timer jobs .Check whether the "Immediate Alerts" job is enabled for your web application.
job-immediate-alerts
job-daily-alerts
job-weekly-alerts
Please check this wiki -
Troubleshooting Steps for SharePoint Alert Email Does Not Go Out
Thanks
Ganesh Jat [My Blog |
LinkedIn | Twitter ]
Please click 'Mark As Answer' if a post solves your problem or 'Vote As Helpful' if it was useful.

Sharepoint 2013 discussion board item view (flat.aspx) throws js error after being migrated from moss 2007

After preforming a migration from moss 2007 to 2013 on-prem we have noticed that html tags are showing up in the discussion board posts. I have tracked the problem down to the flat.aspx page throwing a js error.
'SPAnimationUtility' is undefined - coming from the sp.ui.discussions.js file
this is what I see on the page:
The reply and edit buttons function fine. Its just that the html is exposed.
Anyone seen this before or have a clue as to how to solve?
Thanks,
-Alex

As I remember there are a couple managed properties (metadata) that are used by the views that don't get created when you migrate a discussion board from a previous version. I don't remember the specific properties, but take a look at a new discussion
board in 2013 and compare the properties in the views and you will find them.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Migrate Infopath forms from MOSS 2007 to SharePoint 2010

Hi,
Please provide help
Migrate infopath 2007 forms in MOSS 2007 to SharePoint 2010

How many forms do you have that needs to migrate from 2007 to 2010?
You can also open the 2007 forms in Designer mode of InfoPath 2010, save as 2010 filler or browser.
You need to make sure data connections are updated to point to new sites/document libraries/lists etc.
Any custom code that may contain data connections should be updated.
Inspect Rule Inspector to see if you find any connections hardcoded anywhere.

How to upgrade the extended web application for FBA from MOSS 2007 to SharePoint 2010?

Hi All,
Currently my farm version is MOSS 2007 with SP3.
I have a web application on port 80, and is based on windows authentication, and i extend it on the port 90, and the authentication is FBA with SqlServer.
I know that SharePoint 2010 has a new claims based authentication, and in a single web application you can do both windows authentication and FBA.
Now i want to know, when i migrate the MOSS 2007 port 80 and port 90, which method should i choose?
1. in SharePoint 2010 farm, Create a classic based web application on port 80, and extend it on port 90, enable FBA on port 90. It is the same as MOSS 2007.
2. in SharePoint 2010 farm, Create a claims based web application, and enable both windows authentication and FBA.
Thanks.

FBA requires claims so you'll need to create a claims based web application. Whilst you might extend the site to give you a FBA portal the web application itself will have to be claims based.
I would definitely be looking at using a database attach upgrade path in your case to give you the opportunity for testing as moving between authentication providers can be painful.

Activate button not working in Site Collection features

I just created a new web application and then Site Collection with "Team Site" template. Now when I want to activate "Publishing infrastructure" the "ACTIVATE" button is not working ..even not any button is working..whenever
click on any button the page scrolls on the top.

Hi,
According to your post, my understanding is that you could not activate the “Publishing infrastructure” feature.
To narrow the issue, you can check with the following steps.
Did the issue occur in other browsers? You can use other browsers, such as Firefox or Chrome, to check whether it works.
Did the issue occur in other site collections? You can create a new site collection or use other site collections in other web applications to check whether it works.
You can also check the event log and ULS log to see if anything unexpected occurred.
To check event log, click the Start button and type “Event Viewer” in the Search box.
For SharePoint 2013, by default, ULS log is at
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Custom Auto Attendant Prompts through TUI not working for users who migrated from 2010 to 2013

In Exchange 2010, we started using unified messaging and set up Auto Attendants. We setup a admin role/RBAC for people of a security group to be able to update the message on the auto attendants. They have the UMPrompts assigned role. All of this is working
great in 2010. We have now migrated to 2013, and the users who were migrated from 2010 to 2013 can no longer update the messages through TUI. Newly created 2013 users can and are assigned the EXASCT same permission as the users who have been doing this for
well over a year on 2010. When they call the AA and press #,* they are asked to provide their extension, after doing so the system tells them that extension is not correct. and asks for the extension again. Newly created users with the same permissions
get prompted for their PIN and can log in and change the message just fine.
Confirmed Bug? anybody else having this issue?
What would be different for this process between a user who was migrated from a previous version like 2010 compared to a newer user who has only ever existed on 2013?

What if the migrated 2010 users are in the same DB as the system mailbox? I had a similar issue during a migration; http://www.skypeadmin.com/2014/11/10/known-issue-um-automated-attendant-tui-editing-broken-migration/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Move A Site From Moss 2007 To Sharepoint 2010

i have a site in sharepoint 2007 and i want to move it to a sharepoint 2010 server
not too sure what is the best method to do this ?
thanks

I landed in this thread because I had a similar need to Muthuvel's. I am wanting to bring over just one subsite out of several. My database in 2007 is around 7GB, and all I really want is just one site out of the many in it.
Ahmed's Ammar's steps were just right, and worked well for me in order to get the complete 7GB database over to SharePoint 2010, and later export\import that single site I was looking for.
For Muthuvel, here are my updated steps, starting with Ahmed's text (sorry for plagiarizing!). Steps 7 and 9 are for subsites. See links at the bottom for dealing with site collections.
1) Find the content Database; These are listed under Central Admin->Application Management->Site Collection List
2) Backup the content database. Just doing a backup in SQL Server Management studio.
3) Restore content database to the new server, I mean the DB server for your SP2010
Copy the BAK file to new server. Create an empty DB in Management Studio, restore from backup, you may need to change an option in the "options" tab of the restore dialog to get it to work. (Overwrite db).
4) Create a new Web App on SharePoint 2010
For Step 4, I created a new Web App, choosing to create it with a suggested port number, such as 4072. This was a temporary web application that I ended up deleting later.
5) Remove Content Database from the new web app.
I didn't find that you neeed to remove the Content Database first. You can add the content database by Central Admin or by STSADM, or by Powershell.
Central Admin would be Application Management > Web Applications > Manage Content DAtabases > Set the web application to your newly created web app > Add Content Database > specify the name of the database you just restored
STSADM is as Ahmed gave:
Now use STSADM to add restored DB to this web app
c:\program files\common files\microsoft shared\web server extentions\14\bin on new server is where you can find the STSADM.
run this command from there. Which will upgrade the content db to 2010?
stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver
Powershell would be this command below. Be sure to run the "SharePoint 2010 Management Powershell" console, found under Programs\SharePoint 2010 Products. If you run just regular powershell this won't work.
Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication
http://sitename:port
6) Run ISSRESET from command prompt
I'm not sure this was necessary, but I did it anyway.
NOW, the rest of the part about getting that subsite you want.
7) Export the subsite. I did this with Powershell.
Export-SPWeb http://sitename:port/sites/subsitename –Path "subsitename.cmp"
8) Create a new site for you to import this subsite into, in the Web Application where you want it to go. This would be done with the regular Site Actions > New Site command. You can also do it from Powershell, but that requires knowing
site templates by name, something I'm just learning myself. The other thing here is that you have to create the subsite using the same template as the site you just exported. So if that was a Team site, be sure to use a team site when you create
this new area.
9) Import the subsite to where you want it to land permanently. Here I'm saying port 80 because that's the requirement Muthuvel mentioned.
Import-SPWeb http://sitename:80 –Path "subsitename.cmp" -Overwrite
10) Even after things say they are done on the server, the site may take an extra minute or two to come up when testing from a client. Give it a little time. Once it comes up, somehow I found a way to change the visual appearance from the old SharePoint
2007 to SharePoint 2010, but now that I flipped that switch, I can't find the option again. So I'm sorry that I am not documenting that here.
11) Delete that temporary web app you created in step 4. Again you can do this with Central Admin or Powershell. Here's the Central Admin way:
Central Admin would be Application Management > Web Applications > Manage Web Applications, land on the temporary web app, click Delete. Choose Yes to deleting the content database and the IIS web site.
GROAN!! I'm sorry, I just wrote all this out and realized Muthuvel was asking about a site collection, not a subsite. Then for Steps 7 and 9 you'd want to use
Backup-SPSite
http://technet.microsoft.com/en-us/library/ee748617.aspx
and
Restore-SPSite
http://technet.microsoft.com/en-us/library/ee748655.aspx
Good luck, hope someone else finds this as useful as I did!
Lady_M MCITP SharePoint 2010

Migrating from POP/IMAP to Exchange Server 2013

Hi all, I have a system
my email accounts on an external system to which
I have no administrative access.
It is a Linux system.
I will migrate my email accounts from
Linux system to a Exchange 2013 mail system
in my CPD I'll ride.
How I can migrate the mailbox contents?
without the user being affected.
regards
Microsoft Certified IT Professional Server Administrator

How many users do you have on Linux Messaging Server?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Migrating From BizTalk 2009 To Biztalk server 2013

Hi All,
My current solution is on BizTalk 2009 and my client is thinking of migrating to BizTalk 2013 . Please suggest me is it a good idea to migrate to BizTalk 2013.
Please provide me a difference between 2009 to 2013
Difference between 2009 to 2013 and main features.
Thanks and Regards
Dhanavel S

Hi Dhanavel,
Why don’t you think about migrating to BizTalk 2013 R2 which is available now. Anyway
First and foremost thing, BizTalk Server 2009’s mainstream support from Microsoft has ended on 08-July-2014. After mainstream support, customer will get extended support until
09-July-2019. So you're are in extended support phase now. Find out the following blogpost where you will know more about what you can get and what you’re going to miss from Microsoft support for BizTalk Server 2009. And also about what you have to do next.
Why you have to migrate to the latest version.
BizTalk Server 2009 mainstream support ends.What to do next?
Apart from losing the benefits of mainstream support against the extended support and apart from getting the benefits of latest offering/features of the newer version of the
product, BizTalk server 2009 is closely dependent on its underlying platforms like Windows Server 2008 (or Window server 2003/Windows XP-SP3/Windows Visa SP1), SQL Server 2008 (or SQL Server 2005 SP2) and Visual Studio 2008. So its high time to migrate.
BizTalk Server 2009 mainstream support ends. What to do next?
Some of the benefits of migrating from BizTalk 2009 to BizTalk 2013.
Platform upgrades:
BizTalk 2013 uses following, so when you upgrade from BizTalk 2009 to 2013, you will get the benefits by upgrading your platforms.
Windows Server 2012 (BizTalk 2009 uses Windows Server 2009)
Visual Studio 2012(BizTalk 2009 uses Visual Studio2008)
.NET Framework 4.5 (BizTalk 2009 uses .NET 3.5)
SQL Server 2012(BizTalk 2009 uses SQL 2008)
Virtualization support for Hyper-V (this feature is available from BizTalk 2010 onwards)
Some of the other benefits include
Better support to could
Azure Service Bus. And support for
BizTalk Server running on Azure IaaS
BizTalk Server 2013 Support for RESTful Services
More support towards WCF-based adpaters.
Secure FTP with new FTPS Adapter and an improved FTP Adapter
Out-of-box support to SFTP Adapter
Enhancements to the IBM Hosts Systems adapters
Update to BizTalk mapper
Updated Trading Partner Management (TPM) Capabilities.
Updates to industry schemas like HIPPA, HL7, SWIFT and SWIFTNet
Seamless ability to leverage BizTalk capabilities from SharePoint 2010 Business Connectivity Service to Line-of-Business systems
BizTalk Server setting dashboard for setting to
configuring the key performance, throttling, and tracking settings of your entire BizTalk group while offering fine grained control all the way down to the Host
Instance level.
ESB toolkit part of BizTalk installation.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Global navigation not working after SP 2010 upgrade from MOSS

We are upgrading a MOSS site to SP2010, using in-place upgrade and keeping the MOSS UI.
The in-place upgrade seems to have worked well and most of our work is coming over pretty well.
The one immediate exception is that the global navigation is not showing its drop-downs. I can hover over a global nav item and click it and get to the page. However, it won't show the options underneath the global nav.
Has anyone seen this before?
[Update: The global nav works the way we expect when we're on an application page, such as _layouts/viewlsts.aspx. This clearly points to an issue with the master page or page layout itself (though prob the master page since there are 3 diff
page layouts and all show the same behavior.]
--Paul Galvin, Computer Generated Solutions (CGS)
  Microsoft MVP - SharePoint
  Blogging @ http://www.mstechblogs.com/paul
  Twitter @ http://www.twitter.com/pagalvin

Hello Paul Gavin,
If I understand your issue properly then what you see is by design. However there is a workaround, first please backup get yourself a backup (just inc ase). The follow these steps:
1.
Open the page in SPD and look for the following code, and delete it:
<style type="text/css">
body #s4-leftpanel {
        display:none;
.s4-ca {
        margin-left:0px;
</style>
2.
Look for the following line and delete it:
<asp:Content ContentPlaceHolderId="PlaceHolderLeftNavBar" runat="server"></asp:Content>
Hope this helps, post back.
Chris Weaver
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Migrating from Exchange 2007 to Exchange 2013 Public Folders coexistence

Hi all, I'm migrating from Exchange 2007 SP3 to Exchange 2013 SP1.
I have an Exchange 2007 server (Client Access, Hub Transport and Mailbox Server) in Site A, mailboxes and Publics Folders
In another Site in Site B, I have already installed (Client Access and Mailbox Server) Exchange 2013 server.
I am migrating test users, the fact is that users who migrated to Exchange Server 2013 Public folders do not see.
How I can make the migrated users from viewing the Exchange 2007 Public Folders duration coexistence?
Is there a "how to" to migrate Public Folders from Exchange 2007 to Exchange 2013?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

Search not working in site collections migrated from MOSS 2007 to SharePoint Server 2013

Similar Messages

Maybe you are looking for