We just upgraded our MS Access to 2013 and I'd like to know why I am encountering an error message when trying to create a blank custom web app in access 2013.
ERROR:
"an error occured in the client while attempting to communicate with the server"
I find it very weird as I have tried to export a table on my Access desktop Db and it successfully created a list in sharepoint using the same sharepoint path.
I provided the same sharepoint path when creating the new custom web app, anyone encounters the same issue? Our sharepoint is 2010.
It sounds like you are using an on premise SharePoint setup within your organization, correct? And your SharePoint Server is SharePoint 2010, correct? If that is indeed correct, you can't create or edit Access 2013 web apps on that server. In order to create and edit Access 2013 style web apps, you need several elements: Access 2013, a SharePoint Server running SharePoint 2013 (not 2010), the appropriate licenses for Access Services (the 2013 service that can come bundled with SharePoint 2013), and SQL Server 2012 or higher.
If you are using Office 365 to host your Access web apps, most of the existing plans include Access Services where you can create and edit Access web apps.
Related
On my Visual Studio 2012 software I need to create new web page for my Office 365 SharePoint as a Landing Page for my site. The Page has to contain some logic related to the SharePoint which is to be developed in Visual Studio itself.
The Question is what is the best way to achieve this, what should the project type be (should it be ASP.NET empty Web Application, if so what else would be required to setup) and How to pakage it and deploy on the Cloud (Office 365 account).
You will need to create App(Now called as SharePoint Add-In), then use the app-catalog to deploy and Install app on SharePoint office 365 site.
Below are some reference which will be helpful to you:
Buliding SharePoint Apps
Add a custom page and style to a SharePoint-hosted SharePoint Add-in
Use the App Catalog to make custom business apps available for your SharePoint Online environment
Hope this helps
Question 1: I have made my application in office 365 Sharepoint using Napa.I want to host my application on central administration now to make it on premise. How do I do it please guide me.
Question 2: My other question is how can other user access my application add-in.Do I need to publish it in SharePoint app store so that when one open their share point they add their application and then ready to go.
Question 3: Is Sharepoint app store for on-premise in central Administration and In office 365 -->Sharepoint-->app store is same.If I publish my application in Office 365 SharePoint app store would it same available in SharePoint app store which is in central administration means on premise.
If any tutorial or link will seriously help me a lot.
Answer 1: If you used Napa tool to build an app you can open the same in VS as well. Package the same and deployed the same on your on-premise system. To verify that your app is working correctly please deploy the same on developer site (create a site collection via choosing developer template).
Answer 2: Yes you need to publish your app (having extension .app) in SharePoint via app catalog so that other users will able to access the same.
Answer 3: Both SharePoint app catalog for On-Premise app and office 365 SharePoint app store are different. For local(on-premise) user you have to publish your app on-premise and for other you have to publish it on office 365 SharePoint app store.
Below mentioned links will help you to publish your app
1. For office 365 :- Submit Office and SharePoint Add-ins and Office 365 web apps to the Office Store
https://msdn.microsoft.com/en-us/library/office/jj220037.aspx
For on-premise:-
https://blogs.msdn.microsoft.com/how24/2013/06/14/prepare-your-sharepoint-2013-farm-for-app-development-and-debugging/
I have made An App part using Napa in outlook365 which shows one URL of my external Application which I have made with that the current user name is there as in pic no.1{Devlopement code successfully Made}
Now I have made another outlook account in which SharePoint will open through office 365 which will be of End-user.I need to give some rights in such a way when user Open his SharePoint in outlook 365 on Main page the above App part will open with his name and above URL.I need to give some rights or permission so that his dashboard on login show that App part.
I don't know how to connect the above developer code with End user in such a way that App part will open in end user dashboard.
There are two parts to deploying from Napa to SharePoint 2013 On Premises.
Publish the App and download the .app file locally
Upload the App to the App Catalog in SharePoint 2013 On-Premises
Note: Double check that the Enabled box is checked when adding the app to the App Catalog. Only when enabled is checked can users can see the app in their sites.
Note 2: If you don't have an App Catalog in your On-Premises SharePoint 2013 Farm, one must be created through Central Administration first.
Reference
Manage the App Catalog in SharePoint 2013
Package your add-in using Napa or Visual Studio to prepare for publishing
Problem summary:
I have just built a new TFS 2013 environment for my organization. On my first attempt\test creating a new team project using Visual Studio 2013, I receive the following error at the final stage (Finish button):
"TF218017: A SharePoint site could not be created for use as the team project portal. The following error ocured: Server was unable to process request. ---> The user does not exist or is not unique.---> The user does not exist or is not unique."
I have found several other posts with folks encountering this same error but the proposed solution seems to always be to change the authentication mode in SharePoint to classic which is not available in SharePoint 2013.
The error message implies that this is permissions related. However, it is a little baffling due the fact that when I created a new TFS Project collection using the TFS Admin console it created a new site collection in SharePoint with no issues. I don't understand how my permissions would allow me to create a site collection but not place sites under the site collection.
Here are some details about my setup:
TFS 2013 running on Windows Server 2008 R2 Enterprise
SharePoint 2013 Foundation (separate server within same domain as TFS
server)
TFS Service account is a Site collection admin on the SharePoint site
collection
My AD account is a Site Collection admin on the SharePoint site
Collection
TFS Service account is a Farm Admin in SharePoint
My AD account is a Farm Admin in SharePoint
The TFS2013 Server is also a Farm Admin in SharePoint
No problems were encountered during installation of TFS 2013
TFS Server is used solely for TFS - nothing else is hosted here.
TFS Extensions For SharePoint have been installed on all servers in
the SharePoint 2013 Farm
TFS Server fully updated as of 1/17/2014
workstation fully updated as of 1/17/2014
Details on what I have attempted/researched so far:
Confirmed with my networking staff that there are no firewall\blocked ports
issues between TFS Server and SharePoint Servers
For the time period in which I was trying to create the new team
project there are no errors\warnings in the event viewer on my local
machine, SharePoint servers, or the TFS Server
When running Fiddler on the TFS server while trying to create the new
Team Project - I am seeing no traffic at all between the TFS server
and the SharePoint server.
my workstation has no open connections to any of the servers in question when trying to create the Team project
Cleared cache on my workstation at: C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\4.0\Cache and C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\5.0\Cache
Verified nothing in cache on TFS Server at: C:\ProgramData\Microsoft\Team Foundation\Web Access\Cache_v12.0
Performed IIS reset on TFS Server
Re-start on TFS Server
Team Foundation Server Best Practices Analyzer (it says "SharePoint products is not installed", I'm suspecting this is because SharePoint is installed on another server)
Installed Visual Studio 2013 Update 1.
I apologize if this is in bad form but I have also posted this on the msdn forum: http://social.msdn.microsoft.com/Forums/vstudio/en-US/0758f52d-bf03-44e4-96aa-b60468395914/tf218017-cannot-create-sharepoint-2013-site-from-tfs-2013?forum=tfsgeneral
I am reaching the bounds of my skill set on this one. Any help\ideas would be greatly appreciated. Thanks!
Update:
Well, unfortunately I had to break down and call tech support from an un-named large tech company for assistance on this. Some changes were made to our SharePoint environment in the process which coincided with the SharePoint farm "going down". I am not sure if the problem on the farm was a coincidence or related to my changes but the end result is that my SharePoint people are now skeptical of my TFS integration etc... so I was forced to do a default install of SharePoint on the TFS box. I will leave this post up for others with similar issues to discuss unless that is in bad form. Thanks to all who tried to help with this.
Here are some additional items I would check:
Make sure you start VS 2013 elevated (Right-click when opening and choose 'Run As Administrator') when creating a team project.
If possible, see what happens if you try from a different computer or the server itself using Team Explorer.
Ensure that the user that you are attempting to create the team project with has enough permissions in SharePoint (you can make the account a site collection admin on the site collection in question).
The user should be a TFS Server Administrator or Team Project Collection Administrator.
Make sure that user account has Content Manager rights in the related Reporting Services folder as well, just in case.
Go to the your SharePoint site collection and attempt to create a site in it manually as the account that you are trying to create the Team Project with; when you perform this, make sure you create it with one of the team site templates that TFS installed (like the Agile or CMMI); If you encounter errors this way it may help you narrow down the problem.
Don't forget to review the event logs on the machines involved.
Okay, I finally go to take another crack at this against my SharePoint enterprise environment and got it to work: The key was to simply remove Anonymous Authentication from the SharePoint web application and it worked!
Access the SharePoint web site collection (for example server/site/DefaultCollection) and add your user or group on Site Collection Administrator.
I've noticed Microsoft has released a new version of Office Web Apps Server 2013, which is a standalone product now.
I'm looking for an engine that I can convert Word/Excel and PowerPoint documents into web-friendly versions (HTML5) for an application I've built that uploads these documents to S3 and I thought Office Web Apps Server 2013 standalone would work.
I don't want to use Google Docs, but rather use a solution that I'm hosting myself.
Reading the Office Web Apps Server documentation, it doesn't specify whether or not I need to have a SharePoint server license. I've tried deploying Office Web Apps Server on a Windows 2012 server on Microsoft Azure, and while the software installs, it is unable to render any documents that I'm pointing to it from an external URL (a publicly accessible S3 bucket).
Does anyone know the particular requirements of Office Web Apps Server 2013 to work properly? The website does state that it can be used to view documents from an external URL which is how I'm trying to use it. But since its a new product, there isn't that much information I was able to find on it other than Microsoft's deployment instructions.