SP 2010 migration to SP 2013 does not show webpart - sharepoint-2010

I migrated SP 2010 site collection to my new SP 2013 using db backup process from here. Site is working fine but the custom web parts I created in SP 2010 is not visible in SP 2013. Below error is shown in place of my web part.
[Web Part Error: A Web Part or Web Form Control on this Page cannot be displayed or imported. The type DemoSharePointUserControl.LyncWebPart.LyncWebPart, DemoSharePointUserControl, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3656b399b713ff03 could not be found or it is not registered as safe. Correlation ID: 2d9c179c-2f58-5051-5762-87aea7d1d9ef]
How can I solve it??
Rohit

Looks like the "safecontrols" directive is now missing from web.config file. Either re-deploy the solution which contains the feature of this web part or add it manually (not suggested on live servers)

There are number of Commercial content migration tools that migrate from sharepoint 2010 to 2013. Some them are metalogix,Tzunami and other. I am using tzunami tool which migrate webpart and other content.

Related

TFS 2015 on-prem licensing issue on REST API

We have recently upgraded our TFS 2012 to TFS 2015 Update 1 and I would like to use the new TFS REST API to retrieve tests cases/plans for instance.
So I made a quick test with my browser using the following URL and everything went well : http://.../DefaultCollection/_apis/projects?api-version=1.0
But when I tried to get the test plans in particular using that url :
http://.../DefaultCollection/ProjectXYZ/_apis/test/plans?api-version=1.0
I obtained the following error :
{"$id":"1","innerException":null,"message":"TF400409: You do not have licensing rights to access this feature: Web-based Test Case Management","typeName":"Microsoft.TeamFoundation.Server.Core.MissingLicenseException, Microsoft.TeamFoundation.Server.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a","typeKey":"MissingLicenseException","errorCode":0,"eventId":3000}
So how do I activate that "license" ?
Ok problem solved by following the following instructions : http://www.alexandervanwynsberghe.be/tf400409-you-do-not-have-licensing-rights/
So basically I only had to set the "default access level" to advanced in the web control panel.

Error when start new SharePoint project in visual studio 2010

I am a new administrator to a SharePoint farm and I want to start developing web-parts for our sites.
In our company we have installed SharePoint 2010 on Windows Server 2008 R2.
And we have installed Microsoft visual studio 2010 on that server.
We also have Microsoft SQL server management studio installed in the same server.
In my computer (Windows 7 professional), I have used remote desktop connection to access that server.
From SharePoint central administration, I have created new application, new site collection and new site.
I started VS with admin rights.
From File => New => Project =>Visual basic => SharePoint =>2010 => Empty SharePoint project => ok
Then I got a dialog box asking me to enter the local site that I want to use for debugging.
I entered: "http://sharepoint:21029/team1/"
I chose deploy as a farm solution checkbox.
Click Validate.
The problem is:
When I click Validate, I get the following error:
Cannot connect to the SharePoint site: "http://sharepoint:21029/team1/" Make sure that the Site URL is valid, that the SharePoint site is running on the local computer, and that the current user as the necessary permissions to access the site.
I made a lot of searches on the internet and finally I found this link:
http://www.sharemuch.com/2010/03/19/resolving-vs-2010-solution-deployment-issues-for-sharepoint-2010-projects/
When I tried to solve my problem as described in the previous link, I could not find the following databases:
SharePoint_Config
SharePoint_AdminContent_[guid]
SharePoint Site Content DB
Why I could not find the databases in the SQL Management Studio?
And why I get the error?
I want to start developing web-parts in visual studio... Any help please!!
Thank you
I got the solution finally :)
I found this critical in Event Viewer:
SQL database log in for 'SharePoint_Config' on instance 'sharepoint' failed.
I did the following steps and it solves my issue and I can now connect visual studio to my SharePoint site successfully ^_^
Grant correct permissions to the database access account
To resolve this issue, assign the database access account and then verify that the account has correct permission in SQL Server.
To assign the database access account:
On the Central Administration Web page, on the Quick Launch, click Security, and in the General Security section click Configure service accounts.
In the Credential Management section, in the upper drop-down list click the correct Web application pool for your Web application.
In the Select an account for this component drop-down list, click the domain account with which you want to associate this Web application pool, or click Register new managed account to associate a new domain account with this application pool.
Click OK to save changes.
Thank you all
What is team1? a sub site?
Try using the root site collection:
http://sharepoint:21029/
If you install sp in standalone mode read here about the connection string because sp uses an embedded edition of SQL server

Migrating MOSS 2007 to sharepoint 2010 giving the error “Invalid Object Name sites”

I am migrating sharepoint 2007 publishing site to sharepoint 2010. These are the steps I have followed
Backup the content database from the SP2007 machine.
Restore that database in sql server 2008 (SP2010 machine).
Create a new web application in SP2010 and create a site collection type of publishing template.
I have run the following stsadm command for adding the content database to the web application
stsadm -o addcontentdb -url http://testsite -databasename WSS_Content_test
But I am getting the Invalid object name sites error. Could anyone help me to resolve this issue ?
Did you follow correct procedures? Did you do a pre-upgrade check?

Migrating to SharePoint 2010

I was tasked to research migrating a 2007 MOSS to ShrePoint 2010. Got two servers, one is runing a SQL 2008, and the other has SharePoint 2010 already installed. I need to migrate several publishing and team sites and their corresponding databases. I started reading this article on Upgrade and Migration for SharePoint Server 2010
, then another at Migrate an existing server farm to a 64-bit environment but have a little confusion about wheather I'm migrating, upgrading, or moving the system, as each article defines steps to do this.
Current 2007 MOSS and SQL 2005 are on Windows 2003 32-bit OSs. The new system which at this point in not part of the farm but is in the same domain, are a 64-bit blades running Win 2008 OS with SQL 2008 and SharePoint 2010 - all already instaled / Central Admin site already running. The whole farm consists of 2 severs I just described.
Thanks for reading my post and appreciate any pointers!
Risho.
I just went through this exact scenario. The documentation on the various methods can get confusing. Note, for simple farms (no BDC, etc.), all you really need is the content databases. Here's a simple way to accomplish your goal:
On existing, 2007 farm, make sure it's Service Pack 2
On existing 2007 farm, run stsadm -o preupgradecheck
Fix any errors identified by the upgrade checker
Backup the Content database(s) you want to migrate (old 2007 farm)
Restore Content database(s) to new SQL server
Create a new Web Application on the new 2010 farm. A new WebApp will need to create a Content DB, so name it something like WSS_Content_Temp. This will be the WebApp that you will restore your Content to, so name the WebApp appropriately. You'll remove the content DB, so name it whatever you want.
From PowerShell, run: Test-SPContentDatabase -name <NameOfMovedContentDB> -webapplication http://yourNewWebApp
Fix any errors identified
From PowerShell, mount the newly restored/moved database. Run Mount-SPContentDatabases -name <NameOfRestoredContentDB> -webapplication http://yourNewWebApp. You should see a progress % number that is incrementing. Depending on how big your content databases are, this could take a while (30+ minutes)
From Central Admin -> Application Management, select/highlight your new Web Application.
The go back to Central Admin -> Manage Content Databases, and remove the original, temp Content DB (WSS_Content_Temp)
At this point, if all went well, you should be able to browse to http://yourNewWebApp and see all your content.
Rinse and repeat as needed.

Migrating MOSS 2007 to sharepoint 2010 giving the error "Site collection could not be restored"

I am trying to migrate MOSS 2007 to sharepoint 2010 and I got the error while restoring the backup. The steps I followed are
I have the back up file and all solution pakcages from MOSS 2007.
I have a brand new server setup with sharepoint 2010 and Sql server 2008(64 bit) and windows server 2008 (64 bit).
3.I have created a new web application and new site collection.
4.Successfully Deployed the solution packages using powershell command.
5.trying to restore the backup and got the error
Restore-SPSite: THe site collection could not be restored, If this problem persists please make sure the content databases are available and have sufficient free space.
CAn anyone help me how to resolve this. I tried following some suggestions I got through google, but nothing worked for me.
Thanks
You can't directly restore the moss2007 backup to sharepoint 2010. You need to restore it back to SharePoint 2007 and then migrate it. If you have a database backup of the content database, then you could follow the steps given:
Take the backup of the content database from the SharePoint 2007
database server.
restore it to the database server of the 2010 environment.
Run the cmdlet Test-SPContentDatabase –Name -WebApplication using powershell to make sure that all the required dependencies are available on the 2010 server.
create a new web application on the 2010 server and add the content
database to it. upgrade the visual look of the web application by
doing to the site settings.
I hope this will help you out.