I've recentle installed sharepoint 2019 and I'm very new to this field. I used Infopath to customize a "new Item" page, then published it successfully. but when I click on "new item" in sharepoint list, I get the following error:
The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service. For more information, contact your server administrator.
I made some search, found out that I have to configure State Service Application on the server using command like this:
New-SPStateServiceDatabase –Name "State Service Database" | New-SPStateServiceApplication –Name "State ServiceApplication" | New-SPStateServiceApplicationProxy -DefaultProxyGroup
But there was no such command (or "Get-SPStateServiceApplication") available in powershell. There was another way for enabling a service in central administration, but again there was no such a service there.
I've no idea how to solve this. Thanks for your help.
I solved it myself! using what is described in this Page:
https://social.technet.microsoft.com/wiki/contents/articles/33962.sharepoint-2016-state-service-application-step-by-step.aspx
Related
I am developing with Word Web AddIn by Office.js. Now I want to publish it to my on-premises environment.
After check Deploy and publish your Office Add-in, it seems only SharePoint catalog supports SharePoint on-premises. But for this docuemnt, it shared the steps for Sharepoint Online instead of premises.
Interesting. It seems that when Microsoft renamed "apps for Office" and "apps for SharePoint" to "Office Add-ins" and "SharePoint Add-ins", the UI of SharePoint Central Administration was not changed. But whoever wrote that second article that you linked to thought that it had been changed. (Or maybe it was, but your SharePoint on-premise doesn't have an up-to-date build.) I think that when you get to step 2 of the article you linked to, you will find an "Apps" on the left side of the page instead of a "Add-ins". So just follow the directions in that article but in your mind replace "Add-in" with "App" in all the steps.
Another possibility is this article I found. Try using this, if the suggestion above doesn't work: Manage the App Catalog in SharePoint Server.
I have a question about Sharepoint Online debugging.
I've created a Sharepoint app with Visual 2015, destined to sharepoint-online and it's sharepoint hosted. Inside, I have a very simple workflow.
When I try to debug it, the following message appears:
Is it necessary to have an Azure account to debug a workflow? Are there any other options in workflow development?
If it helps, the deployment environment is Office 365.
It is necessary to have an Azure account to debug SharePoint Online/Office 365 workflows. This is because you can't access certain components that are used for debugging a local SharePoint workflow. Instead Microsoft created the Relay Service component of the Microsoft Azure Service Bus. (A secure component that they charge for hosting)
Before this component was released it does't appear debugging was possible. (See article below)
Debugging Workflows In SharePoint 2013 Online using Azure.
If you have an MSDN subscription or work for a Microsoft partner organization you should receive some free access to Azure.
Workflow debugging for SharePoint Online requires a Windows Azure Service Bus connection.
To enable remote debugging:
With a project selected in Solution Explorer, Right click on the Project menu ans select Properties.
Click the Debug tab.
Select the Use remote machine check box.
In the Use remote machine field, enter the name of the remote machine, using the format \\domain\machinename.
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 was not able to log into the website configured in Sharepoint 2010 due to this error message.
"The trial period for this product has expired"
The log shows that:
Exception thrown while adding control
'Microsoft.SharePoint.Portal.WebControls.SearchBoxEx'
Microsoft.Office.Server.dll
I wasn't able to access any pages in the website other than the site settings page.
I am using Sharepoint Enterprise edition. Please help me to remove this error and to continue the work
Microsoft.sharepoint.portal.dll is used in two features of Sharepoint, they are OSearchBasicFeature and OSearchEnhancedFeature. To fix this issue if you are not using the Search feature you can uninstall these features by
stsadm -o uninstallfeature -name OSearchBasicFeature -force
stsadm -o uninstallfeature -name OSearchEnhancedFeature-force
This will fix the issue :)
Just run the SharePoint 2010 Products Configuration Wizard again. It will solve the error in most of cases.
Other possible causes are AntiVirus program updates or some service pack installation.
Sometime even if Central Administration site’s application pool is running under Network Service account instead of the farm administrator account cause this. In that case just change the application pool identity to the Farm administrator account. You can do this either through the Service Accounts section of Central Admin or through the IIS.
Have you recently applied a service pack to your SharePoint site. I remember this issue happening before when Microsoft released SP1.
Please check the "Manage servers in this farm" (/_admin/FarmServers.aspx) and see if there are pending updates to be applied.
Also
http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/08bdfc4d-f83f-4a74-b53e-b70d91047015
I know its a bit late now however this seems to be an incorrect error
message being thrown.
To resolve simply run stsadm -o activatefeature -name
PublishingResources -url http://
I've just completed an installation of SharePoint Foundation 2010 and I can't get searching to work.
In Central Administration, there is no service application listed for search.
When I go into the Manage Content Database Settings page, the option "Select Microsoft SharePoint Foundation search server" is greyed-out.
In the Services MMC, "SharePoint Foundation Search Service V4" is listed as disabled. I can get this service running for a short time, but eventually it stops and automatically reverts back to the disabled state.
What did we do wrong to make searching completely unavailable in our SharePoint Foundation 2010 installation? How do we get it fixed?
EDIT--->
I changed the log on account for "SharePoint Foundation Search V4" service. The service now starts automatically and is no longer disabled. However, when I go to Central Admin->Manage Service Applications, I still don't see a search service listed. I also still cannot assign a search server to the content databases.
I've tried repairing the SharePoint installation and rebooting the box. I feel like I'm one step closer - but I still don't have search functionality on the site.
EDIT #2--->
I checked the databases on this system and there is no search database listed. On our old WSS 3.0 system there was a database dedicated to search for SharePoint. I'm not sure if this database is missing from the 2010 Foundation server or if 2010 doesn't use a separate database anymore?
I've now got the search service running on my SharePoint Foundation 2010 Installation. Here's what I did:
In Central Administration, go to System Settings->Services on Server. (Note: Prior to this step - no WSS_Search_* database existed on the server)
Select the SharePoint Foundation Search service and click Start
Enter and/or confirm the settings on the Search service page
Press Start to start the service
Go to Manage Content Databases
For each content database in the SharePoint site - assign the correct search server (Note: This option was greyed out until after I started the service in "CA->Services on Server")
At this point search is now enabled on the server. I've verified that search is working correctly. However, I do note that the search service still does not appear in the CA->Manage Service Applications list)
With Sharepoint Foundation you must install Microsoft Search Server http://www.microsoft.com/enterprisesearch/searchserverexpress/en/us/download.aspx