SharePoint Destination

Portqry.exe is a command-line utility that you can use to help troubleshoot TCP/IP connectivity issues. Portqry.exe runs on Windows 2000-based computers, on Windows XP-based computers, and on Windows Server 2003-based computers. The utility reports the port status of TCP and UDP ports on a computer that you select. It can be downloaded from here, http://ss64.com/nt/portqry.html

Instead of Response.End() use, Possible Solution1: Response.Flush(); HttpContext.Current.ApplicationInstance.CompleteRequest(); Note1: Response.End is a bad practice, it aborts the thread to bypass the rest of the operations in the http request lifecycle and it throws an exception Possible Solution2: Also try by giving value "true" in Response.End()     Possible Solution3: Replace Response.End() with HttpContext.Current.Response.End();

I have two site collections both hosted in same web application. But some disabled users are getting resolved in one site and not in other. Typically it should work as the web application can get tied to only one User Profile Synchronization. After analyzing got to know, UserInfo List which is at Site Collection level is not the same for both SiteCollection. Meaning - for one site UserInfo List was updated (Synched up with User Profile) long time back and so it still holds disabled users and so it is resolving the users. Other site - UserInfo List is synched up frequently and so old disabled users are deleted and hence it is not resolving the users. UserInfo List can be found in the url https://SiteName/_catalogs/users/simple.aspx This resolves the issue

Can I restore SharePoint 2010 Site Collection backup into SharePoint 2013 environment? No, it won't work that way. You should do a backup and restore in your SP 2010 environment and put the site collection into it's own database. Then do a sql backup and restore of the database into the 2013 farm and content db attach it for it to upgrade correctly

http://blogs.technet.com/b/meamcs/archive/2013/02/24/sharepoint-provider-hosted-app-walkthrough-part-1-preparation.aspx  

Issue   All of a sudden, when your BCS stopped working and you are getting the below issue, "Cannot connect to LOB system"   Cause of the Issue   BCS files may be referring the wrong connection wrong and you might have changed it in the bcs files. Also BCS files would have been updated in the SharePoint server, but still you are getting the issue.   Resolution Issue is old files are not properly updated and still referring the old connection string. So you need to delete all the BCS files and again need to deploy it in the SharePoint server. This solves the issue.

Steps Configuring Secure Store Service 1.        Go to Central Administration à Manage Service Application à Check Secure Store Service Application is running. 2.        If Secure Store Application is not there, create new Secure Store Service 3.        Then click “New” button to create a new target application using the “Group” type 4.        Give the details for – Target Application Id, Display Name, Contact Email and Target Application 5.        Click Next, Choose “User Name” and “Password” from the dropdown options. Also change the name from Windows User Name to “User Name” and Windows Password to “Password” 6.        Give Service account/(account with admin access) name in the screen and give permission for the user to edit the details if required later 7.    ...