4

That's the right approach to take, but you'll need to do a couple of other things as well: When you've restored the DB to the new SQL server, run EXEC sp_chagedbowner 'domain\user' to change the owner of the content database to the farm admin (also known as the database access account) for the new farm. Ensure that the authentication mechanism of the web ...


4

I recommend you get an understanding of what you have in your current SharePoint environment. Two tools to consider: Microsoft Assessment and Planning Toolkit Ledger


3

Yes. It is possible. The sample code given below will read data from Blog list from host web and display data in your app. <script type="text/javascript"> // Set the style of the client web part page to be consistent with the host web. (function () { 'use strict'; var hostUrl = ''; if (document.URL....


3

Check this: Things to do before migrating I would also, by my experience, recommend that you audit all your SharePoint and check what you are really using. We found stuff here that nobody modified for 12 years! Ok, it may take a while to verify what you can or can't throw away but it's a long term benefit. I used this code(SP 2010) to run trough all the ...


2

This could be done with SP.WorkManagement.js , if I understands you correctly. Example code: RegisterSod('SP.WorkManagement.js', '/_layouts/15/SP.WorkManagement.js'); SP.SOD.loadMultiple(['sp.js', 'SP.WorkManagement.js'], function() { var context = new SP.ClientContext.get_current(); var userSessionManager = new SP.WorkManagement.OM....


2

The best strategy to avoid mixed content blocking is to serve all the content as HTTPS instead of HTTP. For your own domain, serve all content as HTTPS and fix your links. Often, the HTTPS version of the content already exists and this just requires adding an "s" to links - http:// to https://. For other domains, use the site's HTTPS version if available. ...


2

Multiple-Column Lookup value is represented as an array of SP.FieldLookupValue objects. How to read multi-valued lookup field using SharePoint 2013 REST Assume Employee list with a multi-valued lookup field Departments Then the query: /_api/web/lists/getbytitle('<list title>')/items returns an array of lookup ids, for example: getListItems(...


2

dstarkowski got me on track, sp.requestexecutor.js had not been initialized properly. This worked out for me: $(function () { $.getScript(scriptbase + "SP.RequestExecutor.js", execCrossDomainRequest); }); function execCrossDomainRequest() { var context = new SP.ClientContext(appWebUrl); var factory = new SP.ProxyWebRequestExecutorFactory(appWebUrl); ...


2

If you use JavaScript code loaded from Web app A, cross-domain Policy will prevent you from accessing data hosted in Web app B (different domain). One option would be to host/load your script file from Web app B (i.e. linking from page in Web app A to a script file residing in Web app B).


2

To access the SharePoint resources located in remote server you need to use the C# client object model. It is irrespective of version. You might need to understand the SharePoint 2010 client object model and try samples before start with the actual solution. SharePoint 2010 client object model SharePoint 2010 Client Object Model samples If you want to ...


2

Evantually we successfully used the URL Rewrite module, evaluating and inserting CORS headers when requests come in. This is happening outside SharePoint, as part of IIS request processing.


1

I'm assuming you're writing web parts deployed to the abc.com farm. If so, you're probably experiencing a classic double-hop issue. The code on abc does not access xyz using the current abc user's login, it does so using the app pool identity of the abc web application. If you have very basic security requirement, you can add grant that identity access to ...


1

You can create a new CSOM context by providing credentials: var clientContext = new ClientContext(SITE_URL); clientContext.AuthenticationMode = ClientAuthenticationMode.Default; clientContext.Credentials = new DefaultNetworkCredential(USER, PASSWORD.GetSecureString()); Web web = context.Web; context.Load(web); context.ExecuteQuery(); Console.WriteLine("...


1

I can think a couple of reasons, The image is saved using the CMYK model. Try edit one image and save in RGB mode and see if helps. Maybe has to do with image DOM lifecycle. Is the image gets loaded via script or is it defined in html?


1

I've done something similar using the AllowFraming web part on SharePoint pages I can modify (https://dev.office.com/sharepoint/docs/sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in). To solve your problem technically you should be able use remote provisioning patterns to push a Site Scoped Custom Action that lazy loads a script from ...


1

Got this working using a Custom Page Proxy, RequestExecutor, on an app that has full control of the site collection on a separate domain. See the following KB articles & code sample for basics of the technique: https://msdn.microsoft.com/en-us/library/office/fp161183.aspx https://code.msdn.microsoft.com/sharepoint-2013-get-data-10039ff1 We're using a ...


1

If you are developing for Sharepoint Online, you could use the new StartUpload/ContinueUpload/FinishUpload API. With this API, you can divide your Upload into chunks and upload every chunk separately. If you are developing an on Premise Solution you could write a Mediator WebService, which performs the upload for you. The Mediator Webservice would be a ...


1

You'll want a domain trust in place. Create a new farm as you plan on doing, and restore the content databases/service application database as applicable to the new farm. For users, are you migrating them between domains with SID History? If so, the source account must be disabled, otherwise you break the Microsoft security model by having more than one ...


1

In Windows Authentication (NTLM), getting two 401 before one 200 is completely expected: this is the way challenge/response works. You usually don't notice it with same-domain calls since you're already authenticated with a session cookie.


1

Actually it is not possible, as it is a cross domain request the two pages fall in different security zones and hence proxy page that is required is not loaded in sharepoint. This has been done for security purposes by the browsers. The cookies fall in different security zones of the browsers of respective pages, and when the zones don't match the data ...


1

Tried it with the authorization header but it still dont work, i think its maybe because i got some error when trying to install an app (some interface problem) and only get the app installed due to some kind of bug :D and then i wont be asked if i trust this app... I think that could be the reason If you think that's your problem, try removing one of ...


1

According to this article, SP.ProxyWebRequestExecutorFactory is located in sp.requestexecutor.js file. Is it included in your application?


1

I think it would be difficult for someone outside of the product team to give an accurate reason as to why they implemented this using a technology other than CORS... I would guess that in addition to any technical reasons though, CORS was not a reommended standard until January 2014, pre-dating the implementation of the App Model and SharePoint 2013.


1

To summarize, you have the following scenario: You have a SharePoint add in (SharePoint App). A page on the add in web (app web) needs to call an external service. You have an external service implemented using ASP.NET Web Api. The external service needs authentication. The first issue you need to address is the Same Origin Policy. To overcome this issue, ...


1

You do not need to add the SP servers to domain of external customers AD. You can configure ADFS to use claims between SP and the external customers AD. https://msdn.microsoft.com/en-us/library/hh446526.aspx


Only top voted, non community-wiki answers of a minimum length are eligible