I'm trying to Get FBA working on SharePoint 2016 BUT I am falling over at the last hurrdle.
The the problem occurs when after i have set all the web configs and machine configs, then set up my web app as for FBA with my role providers/membership providers.
I go into SharePoint site and log in with windows auth but i get the following error Server Error
The Same error is repeated in the event logs and only happens in the web app with FBA active and .net roles and .net users set with a default provider. PLEASE HELP I'm actually going mad now.
Thanks
ROLES
MEMBERS
So it turns out that in Machine Config needs the FBAmembers setting up while in the Web config you need this:-
WEB CONFIG
CODE for Web Config
And this fixed the issue.
Related
I have created a new MVC application with windows authentication and without doing any changes to application, I have deployed to Azure App Service.
When I browse the URL I am getting the message as "You do not have permission to view this directory or page.".
When I check the "DetailedErrors" folder, it was "IIS Detailed Error - 401.0 - Unauthorized".
I have referred many post with this issue. But none of the solution mentioned in the post solved my issue.
Please let me know what configuration I am missing.
Thanks
Windows authentication is not supported in App Service.
In order for IWA to work, the server would need to be AD joined.
You do not have that level of access in App Service.
https://devblogs.microsoft.com/premier-developer/moving-legacy-asp-net-apps-with-windows-authentication-to-azure-app-service-part-1/
You will have to migrate to e.g. Azure AD authentication or host the app on a platform that supports IWA.
I am using Acumatica 2018 R2 build 18.204.0013.
I have created a new instance on my local with Windows Authentication. However, when I launch the application, it gave me below error.
Error: - "Login Failed for user 'IIS APPPOOL\apppoolname"
I have also other instances running different versions with Windows Authentication which are working fine but they are all upgraded from lower versions to the latest.
I have observed that if I create a new instance with SQL Authentication instead of Windows Authentication then it works. This started happening from 2018 R2 I think. Is there anything changed or any recommendation that we should be using SQL authentication always going forward from 2018 R2. Please suggest.
When creating the database using Acumatica ERP Configuration Wizard, an AppPool User is inserted in the database security settings:
The Login for user IIS/AppPool failed error can happen when you backup/restore a database for use with a different website that uses a different AppPool. It is a mismatch between AppPool used by the IIS website instance and the Database User in Security.
Adding the missing IIS/AppPool User in the database security should resolve the error. It is easier to create it from the UI using Microsoft SQL Management Studio. The user requires membership for 'db_datareader', 'db_datawriter' and 'db_ddladmin' role:
Finally found the solution.
Create an instance with SQL Authentication and not Windows Authentication.
I fixed this by adding the IIS AppPool user to the database as DBO in SSMS. Adding it with db_datareader, db_datawriter, and db_ddladmin was causing another error when trying to log in to Acumatica. I was having this issue on 18.115 and 18.116, new instance with no data. It's like the Acumatica install did not set up the database permissions.
Sharepoint Deployment : on premises with local domain address as http://sharepoint , windows server 2008 R2
In Order to deploy my app I added app URL in admin central as apps.mydomain.com
apps.mydomain.com is actually the sub domain I created on my company official website.
After compiling application and running it I am getting following error in output window
Active Deployment Configuration: Deploy App for SharePoint
Skipping deployment step because a pre-deployment command is not specified.
Skipping the uninstall step because the app for SharePoint is not installed on the server.
Install app for SharePoint:
Uploading the app for SharePoint...
App failed to install, cleaning up...
Successfully uninstalled the app for SharePoint.
App installation encountered the following errors:
03/11/2014 07:17:19
#"Error 1
CorrelationId: fc4c3483-a34c-4975-a6cb-c1d84436c8f5
ErrorDetail: The content database on the server is temporarily unavailable.
ErrorType: Transient
ErrorTypeName: Intermittent
ExceptionMessage: The App domain for this site has already been assigned.
Source: AppWeb
SourceName: App Web Deployment
Error occurred in deployment step 'Install app for SharePoint': Failed to install app for SharePoint. Please see the output window for details.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Can you please give me an idea here I am wrong ?
Recently I was working on configuring SharePoint hosted apps for our customer and while testing I saw this issue. After completing the configuration of Apps I uploaded an app to app catalog and added the app to a site. The app worked without any issue but there was one gotcha. I missed to replace an S in App Prefix which was set to Apps so my app url was https://apps-1234.apps.contoso.com but the orignal plan was to use “app” as prefix.
So I removed the app from the site and app catalog. Then went to CA and changed the app prefix to app from “apps”. Uploaded the test app to catalog and then tried to add to the site and it failed with error. “Unable to add the app to the site please retry”
I started ULS Viewer and started live log stream and clicked retry and saw an amazing message. SharePoint app was still using “apps” while I have updated it app. I knew something was goofy and traditionally UI is that good with me when it comes to SharePoint.
SPException thrown: Message: The App domain for this site has already been assigned.. Stack: at Microsoft.SharePoint.Utilities.SPUtility.ThrowSPExceptionWithTraceTag(UInt32 tagId, ULSCat traceCategory, String resourceId, Object[] resourceArgs)
Here is what I did.
Open SharePoint Management Shell as administrator (Farm Account).
Set-SPAppDomain -AppDomain apps.contoso.com
Set-SPAppSiteSubscriptionName -Name "app" -Confirm:$false
Open Command Prompt as Administrator. Run the commands below.
net stop sptimerv4,
iisreset,
net start sptimerv4
Repeat the above 3 on all servers in the farm.
I closed all the browsers and opened the site and click Retry from Site content page. Bingo the app was added without any problem.
https://jerryyasir.wordpress.com/2015/11/06/unable-to-add-the-app-the-app-domain-for-this-site-has-already-been-assigned/
I restarted all services in the server for sharepoint to solve the problem namely:
AppFabric Caching,
Sharepoint serach host controller,
Sharepoint search server 15 ,
Sharepoint Timer Service,
Sharepoint user code host
Services can be restarted from Control Panel-> Administrative tools -> services
It seems one of the service is responsible for the updating configuration in DB, even when I googled people said that by restarting the server and after some time the problem automatically got served.
So I think one of the service when run solves the problem
just restart the sharepoint server will do
I had same issue, I resolved it by just un-provisioning, deleting and re-adding the SPDistributedCacheServiceInstance
When attempting to use hashtags in SharePoint 2013 users see "the tagging service is currently unavailable". I've googled this issue and have tried or validated the following without success:
The application pool for Managed Metadata Service is running with the correct credentials
The Managed Metadata Web Service is running on all WFE's and app servers
In Central Admin the Managed Metadata web service is the default location for keywords
In general this (test) farm looks identical to my production farm. The only difference is that I've applied the new service pack 1 to this test farm, and now this service appears to have broken.
Any help would be greatly appreciated.
Generally after installing a service pack, you are required to run the SharePoint Products Configuration Wizard on each of the servers in the farm (http://technet.microsoft.com/en-us/library/ff806338(v=office.15).aspx). Also, sometimes a reboot may be required after running the configuration wizard. Have you done both/either of those things?
I have an app deployed to Azure and it uses ADFS (Active Directory Federated Services) for authentication.
When the user tries to navigate to the app on Azure, it redirects the user to the ADFS authentication page. User enters their credentials and clicks OK, and ADFS redirects the user to the landing page of my app.
Everything is working fine up to this point. I'm getting a generic server error on the app once the user hits the landing page. PROBLEM: I need to see the detailed errors. I try setting <customErrors="off" />, repackage my app and redeploy, but that doesn't give me detailed errors:
Here's what I've tried: I've tried packaging my app in Debug mode (after Release mode didn't work), I've edited both web.config's (in the root of the solution, as well as in the Views folder, just to cover all bases). Nothing worked.
What am I doing wrong?
A couple of things to try:
Are you SURE the customerErrors attribute is set correctly? The
Identity and Access tooling in Visual Studio seems to like to reset
that back to "Off" (every time you update via the tool).
Are you able to connect to the role instance via Remote Desktop? If
so, you could inspect the web.config settings for the site?
Browsing to the site from the server might also provide a more
friendly error message.
When you RDP into the cloud service, you can look at the Event
Viewer to see the detailed error messages.
I fixed this error by ftp'ing into my azure website and deleting the wwwroot folder and then publishing my website via visual studio.