We have created SharePoint 2013 Auto hosted app. In that, we have created near about 50 lists from the solution in visual studio. but when i deploy it, it gives following error:
"there was a problem with activating the app web definition."
What is the reason? any limit for creating lists in Auto hosted app?
Please suggest me...
Related
I am trying to publish a django app on azure using Visual Studio 2015 Pro. and the azure tools. The publishing completes successfully but when I try to access the application online; I get this:
When I run my local server, the app runs with no problem and I can see the contents without exceptions or errors, but the published version of the app is giving me that error. Please help me solve this problem
I recently installed Sitecore Rocks (1.2.6.0) into Visual Studio 2012 and connected it to my existing Sitecore 6.5 instance. I can see all my objects in the master database, but when I hover over them, the "Template" value is blank, and the "Template ID" is {00000000-0000-0000-0000-000000000000}. Am I missing a step in order to get the template information into Rocks?
As far as it seems you are using the Good Old Web Service to connect to the Sitecore Service which won't provide you with template information. To resolve the issue you should start using the new Hard Rock Web Service when you try to connect to your Sitecore Instance. Keep in mind that that the Hard Rock Web Service requires .NET CLR v4.0 and Sitecore 6.5 runs on v2.0 by default. Tested this on my local and everything seems to work fine on a Sandbox Instance.
I encounter problems trying to deploy custom workflows designed in SharePoint Designer 2013 on a SharePoint 2013 host. The steps I've taken are:
On SiteCollection1, create reusable list workflow in SharePoint Designer 2013, one activity: log a message to the history list.
Save the workflow and save it as a template
Upload the *.wsp template in the solutions gallery on SiteCollection2 and activate the feature
Result: then trying to add manually the workflow to a document library or a list, my template is not in the list of available templates. What am I missing?
Note: SharePoint 2013 installed on-premises, WF Manager is deployed and registered for both site collections. The workflow itself is a SharePoint 2013 workflow.
Solved after discovering that the master page file was referencing SP.Runtime.js and SP.Workflowservices.js ; I removed those references and everything works as expected
Summary:
I have an Office 365 E3 account where I'm trying to deploy a Word task pane app that will read some SharePoint list data. Right now, I'm just trying to get the task pane app to load, however, it shows the Office 365 login page (in the pane) but does not do anything after clicking Login.
Details:
I went through the instructions provided here:
http://msdn.microsoft.com/en-us/library/office/fp179815.aspx
Basically, I create an App for SharePoint configured as SharePoint-hosted, then in the same project, added an App for Office (Task Pane App for Word only). The SharePoint app also has a custom document library.
I am able to install the app to my App Catalog, and it correctly shows up in Site Contents where I see it being provisioned to the app web. I can also launch Word 2013 with the Trusted App Catalog configured correctly, and I am able to see my Task Pane App and insert it. When I click Insert, it loads it but prompts for credentials.
I am using the same credentials all throughout this exercise so by virtue of being able to install and deploy the SharePoint app, you can trust that I'm providing the right credentials.
It also appears the custom document library is never created - I wonder if both suffer from the same underlying issue.
I encountered the same problem and the solution provided in the answer below did not help.
After some desparation i created a taskpane app using the Napa Cloud App, opened the application in Visual Studio and went looking for differences.
In the Taskpane app manifest.xml file i found the following entries which were missing in my own application manifest:
<AppDomains>
<AppDomain>https://login.microsoftonline-int.com</AppDomain>
<AppDomain>https://login.microsoftonline.com</AppDomain>
</AppDomains>
This solved my problem and cured one horrible friday.
I was able to get this to work. It turns out doing a Deploy from Visual Studio (whether you right-clicked Deploy or F5-debug), the installation of the app isn't enough.
To make it work, I skipped doing a Deploy all together, but instead published my app. I then took the .app file and loaded it in my App Packages folder, and then deployed it from there.
Unfortunately, I don't know the difference between the two, but I'm assuming it has something to do with provisioning the app web for the Office App.
I'm a new to sharepoint and IIS. recently, I've got a SP solution bundle which has got a web service located in Layouts folder. I managed to successfully deploy the solution.
The problem is I'm not able to access the webservice in solution, as I guess I might missing some stages in deployment.
I deployed the Solution directly from visual studio to my desired web application on sharepoint server. The service file has already been placed at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\template\layouts\MyFolder\ServiceName.asmx
However, once I try to call it cannot being accessed via application url:
http://localhost:9999/_layouts/MyFolder/ServiceName.asmx
Do I need to set anything in order to be able to access the service via desired url?
I just got it. I did deploy Bundle on Sharepoint 2013 and I just realized it goes under _layout/15/MyFolder!
I have fixed my problem anyway