While crawling content from Moss 2007 to Sp2013 its throwing error

hi,
When i am trying to crawl the Moss 2007 site content in SP2013 serach I am getting below Error in the Crawl error log.
I have provided owner access for the Moss 2007 content DB,to the user accout which i am using in SP2013 serach.And also provided read access for this account to the Moss 2007.But still i am unable to crawl.
1 The URL of the item could not be resolved. The repository might be unavailable, or the crawler proxy settings are not configured. To configure the crawler proxy settings, use Search Administration page.
2 This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might
also want to crawl this repository during off-peak usage times.
3 The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error.
4 Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using
has "Full Read" permissions on the SharePoint Web Application being crawled.
Thanks & Regards, Krishna

Try to use website as content source to crawl it
Create disableloopbackcheck registry on all sharepoint servers
Are you able to browse sharepoint sites from crawl server.
check
http://blogs.technet.com/b/josebda/archive/2007/03/19/crawling-sharepoint-sites-using-the-sps3-protocol-handler.aspx
http://sharepoint.stackexchange.com/questions/93691/using-sharepoint-2013-to-crawl-sharepoint-2007
If you are still struggling you can watch the requests by using Fiddler as a proxy for the crawl process. Then you can kick off the crawl and watch the requests and the response from the 2007 server.

Similar Messages

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"

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

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

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]

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.

MOSS 2007 Vs. SP2013 Mobility

What is big difference between these MOSS 2007 and SP2013 on the Mobility Subject
Hai

Paul has it covered perfectly. SharePoint 2007 was built in an era before Responsive Web Design was widely "in the know", the mobile view was generally text heavy and didn't play well on all devices. It also used HTML / CSS standards that aren't as
friendly as the HTML5 / CSS3 that SharePoint 2013 uses.
There is a CodePlex project, that is set-up by one of the well known members of the community which might be worth looking at. Even if you don't use it, the documentation provided is still a very good educational resource.
https://responsivesharepoint.codeplex.com/
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

Content movement from MOSS 2007 to SP 2013

Hi,
I have a site collection in MOSS, a site has a document library with OOB Approval workflow, and the library has documents too.
Now, I have requirement wherein I need to move the documents from Moss to SP 2013, and the document should persists the workflow state whatever was existing in MOSS.
Thanks
Senthu

ou cannot upgrade directly from the server products in the Office 2007 release to SharePoint 2013. The changes between versions are too great, and the hardware requirements differ so much between versions that a direct upgrade is not possible
or supported. However, you can perform a series of database-attach upgrades to first upgrade your content to SharePoint 2010 Products and then to SharePoint 2013
Follow below article:
http://technet.microsoft.com/en-us/library/ee947141.aspx

Error while sending email from MOSS portal

Hi,
I have configured email settings on my MOSS central admin, still MOSS throws error while trying to send emails to AD users. I tried to give permission for a user in a site and it threw this error:
The user or users have been added successfully, but there was an error in sending the e-mail message. The server may not be set up correctly to send e-mail. To verify that e-mail is configured correctly, contact your server administrator.   at Microsoft.SharePoint.ApplicationPages.AclInv.SendEmailInvitation(PeopleEditor picker, String subject, String message)
   at Microsoft.SharePoint.ApplicationPages.AclInv.BtnOK_Click(Object sender, EventArgs e)
   at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
   at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
I have provided outbound smtp server address and the email addresses as well.
Regards,
Manoj

Ok, issue solved!! The issue was that I had to set anonymous connection directly to server. Error provided by SharePoint didn't help at all. After hours of hair-pulling and head-banging, I found a nice article that detailed how to troubleshoot e-mail issues:
http://www.tonytestasworld.com/post/2009/04/09/SharePoint-2007-Outgoing-E-mail-Troubleshooting-Tips.aspx
In the above article, the troubleshooting step 5 was the breaking point. As suggested in the blog:
http://www.sharepointblogs.com/johnwpowell/archive/2007/07/10/alerts-failing-cannot-connect-to-smtp-host.aspx
I created a C# console application and it gave me the correct error:
The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.1 Client was not authenticated
So I used this code to create an SMTP test application:
using System;
using System.Collections.Generic;
using System.Text;
using System.Net.Mail;
public class Program
public static void Main(string[] args)
try
// Check arguments
if (args.Length != 3)
ShowUsage();
return;
// Create message
MailMessage mmMessage = new MailMessage();
mmMessage.To.Add(new MailAddress(args[2] as string));
mmMessage.From = new MailAddress(args[1] as string);
mmMessage.Subject = "TestMail";
mmMessage.Body = "This is a test";
// Send message
SmtpClient sc = new SmtpClient(args[0] as string);
sc.Send(mmMessage);
catch (Exception ex)
Console.WriteLine(ex);
finally
//Pause
Console.WriteLine();
Console.Write("Press a key >");
Console.ReadKey();
private static void ShowUsage()
Console.WriteLine("Usage");
Console.WriteLine("TestMail [SmtpServer] [FromAddress] [ToAddress]");
} // end Program
This command saved lots of trouble for me and solved the email issue:
http://forums.msexchange.org/m_1800412705/mpage_1/key_/tm.htm
set-ReceiveConnector "default sfzcombx" -permissiongroups:"ExchangeUsers,ExchangeServers,ExchangeLegacyServers,AnonymousUsers"
Hope this helps somebody!
Regards,
Manoj

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.

Cannot locate Orphaned Content in MOSS 2007 prior to updgrade to SharePoint 2010

I will soon be upgrading my MOSS 2007 farm to SP2010, so I had run the preupgradecheck command to check for any problems. It fails on "Issue: Orphan objects in Content Database" in 4 databases. It doesn't give Site IDs, only the SQL instance, the
database name and this "Integrated Security=True;Enlist=False;Connect Timeout=15" after the database name.
To try to resolve this problem, I have tried locating these using the stsadm databaserepair command, which brings back "OrphanedObjects Count="0"" for all the content databases. So after this, I tried using the enumallwebs command,
and exported this to a txt file, all fields for "InSiteMap" came back as "True" so there doesn't seem to be any orphaned site collections.
I've had a look around online, but the two options I've tried seem to be the way to locate them, and I can't find anything else.
Has anyone had this problem before? Is there another way that I can try to locate these orphaned objects? Are they likely to be sites, features, lists etc?
Thanks in advance for any help!

Content Database, this is most important stuff.
if you have mysite and User profiles then you need to move the SSP to 2010. check the below blog for steps and understanding:
http://blogs.msdn.com/b/alimaz/archive/2009/11/08/upgrading-moss-2007-ssp-user-profiles-and-mysite-content-to-sharepoint-server-2010-using-db-attach-method.aspx
Yes you dont need the Central admin.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

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.

I have mac air , i am unable to download latest OS yosemite from App store. Everytime its shows errors . Pls advice how to download

I have Mac Air , I am trying to download latest OS yosemite from App store . But i am unable to download as its showing error. Pls advice is there any other options to download . Thanks

get an error message.
Care to share what the error says? My mind reading skillz are nill this early in the morning.

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

Prevent Text Boxes to shrink as big as the text in it - move existing InfoPath form from SharePoint 2007 to SP2013

Hello Together,
we have some simple InfoPath forms in place. With SharePint 2007 they are working well. Now we will move to SharePoint 2013.
It was easy to re-publish them on a SharePoint 2013 Site and to work with, but i have an optical / technical error and i don't find the solution.
We use Text Boxes to collect the data from the user. After the user has filled the form we will submit them via mail.
I will you show you the problem.
on SharePoint 2007 --> it looks okay
on SharePoint 2013 --> not okay - the Text Box is shrinked to the text Size and the design is defect
How can i prevent this?
Thanks in advance
Sebastian
I can provide Screenshots, bit at the moment my account is not verfied...

Can you please share screen shot.
Before try removing the field form View and Add it again - check it
Velu K

While crawling content from Moss 2007 to Sp2013 its throwing error

Similar Messages

Maybe you are looking for