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.
Related
After I installed Automation Anywhere 11 with SQL Server 2017 on windows server 2012, I could not launch the control room getting bad gateway message.
Could anyone help identifying the problem??
There are several possible reasons for this to happen, the one most easy to miss is your SQL login not having permissions to access your DB.
Open your SQL Management Studio and check that your have login logging enabled (Server Properties -> Security -> Login auditing). It is set to Failed only by default, you can change it to Both successful and failed if you wish.
Then attempt to login to Control Room and then check the logs.
You are most likely going to see an account trying and failing to connect to the DB. Give that account sufficient privileges and try again.
I was experiencing something similar after I restarted my Automation Anywhere Control Room Service from services.msc as adviced in AA forum for getting this error.
grid is invalid state...contact administrator
But, after I restarted the Automation Anywhere Enterprise Auto Login Service V11 service the control room worked fine.
I am using Visual Studio Community 2013, SQL Server 2008 R2 Express Edition for an MVC web application using entity framework code first migrations for my database.
I am trying to get my local application hosted on the Microsoft Azure platform.
I have registered for a trial account which expires in 30 days, and deployed my MVC5 app out which has been successful.
However, this app requires a database which I am struggling to deploy.
What is the easiest way to get my database deployed out to Azure as I do not seem to have the :
"Tasks" -> "Deploy Database to Microsoft Azure SQL Database" option available to me in SSMS.
I have extracted a Data-tier Application of my local database and have it stored on my C drive, however if I connect to my Azure Account in a second window, and right click the server then select Deploy Data-tier Application, it fails on "Creating schema object in database" with the following error:
TITLE: Microsoft SQL Server Management Studio
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------ ADDITIONAL INFORMATION:
Users cannot be mapped to certificates, asymmetric keys, or Windows
logins in this version of SQL Server. (Microsoft SQL Server, Error:
40528)
I'm assuming its tried to create my local account plus the IIS APPPOOL account I had to set up to host the website on my local network, however I do not see a way of removing them from the .dacpac export.
When I refresh the Databases node, there is still no database, I'm fairly lost now as to how I might get my db deployed to this server?
If you can extract a compatible Data-tier application and then Deploy it to your target server using your current version of Management studio, then this approach should work, see this link for more reading on ensuring your database is compatible.
Failing this, as was in my case. I downloaded Management Studio 2015, which gave me the option to deploy database to Azure by simply right clicking the required database.
Again, this threw up the error regarding my database level IISAPPOOL user, but not my server account user. As a way around this, I took a backup/restore of the database and removed this user then deployed the copy database obviously minus the problem account.
Now all that was left to do was add a transform to my Release web.config with the Azure connection string as provided on the Azure dashboard, and re-deploy the website.
Problem solved.
I have sharepoint 2013. I have one SQL instance in sharepoint integrated mode and another instance in SSRS native mode on my server.
I get the login failure error.
I am dealing with this failure that is explained in the following solutions. But non of them solved my problem:
I did this solution:
https://stackoverflow.com/a/1445068/779408
and this:
http://ybbest.wordpress.com/2011/08/04/how-to-fix-%E2%80%9Cnot-able-to-deploy-report-to-sharepoint-2010-in-integrated-mode%E2%80%9D/
then I tested this solution:
http://www.thorntontechnical.com/tech/sharepoint/sharepoint-2010-ssrs-integrated-mode-deploy-login-prompt#.U5vQj7EmFKb
and implemented the solution in this:
https://sharepoint.stackexchange.com/questions/16656/not-able-to-deploy-report-to-sharepoint-2010-in-integrated-mode
Now I have the following web application and its Document library
http://test.local:44444/sites/sc1/Reports
But I can not deploy my reports on it.
What should I do now??
This issue normally occurs due to incomplete installation. Ensure that SQL Server Reporting services Add-in for sharepoint is installed. If not, run SQL Server setup again to install the missing add-in. If SharePoint 2013 is missing service pack 1, it may cause errors during configuration.
I would suggest you make use of the release configuration manager. You can create releases such as
LOCAL
REPORT_TESTING
REPORT_STAGING
PRODUCTION
SOME_SHAREPOINT_DEPLOYMENT
Each release type contains it's own instance of configuration values. This would allow the release type to control the deployment. If you are not using SharePoint locally then you can set the LOCAL release configuration to the standard SSRS values on your local machine.
this issue happening when you deployment the SSRS reports on SharePoint mode and configure FBA on the SP server
To solve this issue you must extend the Web Application that include BI Center
I have been facing the same issue,
When creating a new service application in SharePoint using SQL Server Reporting Services Service Application, I forgot to check the Web Application to be Associated.
Solution:
After I checked the Web Application & updated the service application properties, its Working.
Hope it helps someone...
I want to use a separate/ named schema in an Azure WebSite app to implement a multi-tenancy in separate schemas pattern with Azure SQL. My app runs correctly in Visual Studio but not on Azure. I searched StackOverflow for similar issues, and found:
This answer suggests it can't be done: Multi-tenant application on Windows Azure. This question does not apply directly to named schemas: Azure SQL database working when ran locally but not when published to Azure.
For the MVC4 app I am developing I configured the Azure SQL database to use a named schema and modified the Connection String login name and password. When I tried to register the first user it threw the error message "Invalid object name 'UserProfile'" from Azure SQL. I checked the stack trace and everything looked reasonable so I reviewed the code for the SimpleMembershipProvider and did not see anything that should break when using a named schema.
As a Proof of Concept, I opened Visual Studio 2012 and created a new MVC4 app with .NET Framework 4.5 using the Internet Application template, which of course implements the Simple Membership Provider. I opened the Azure console and created a new web site with new database, then published the app to Azure. I ran the app and clicked the Register link to add the first user. This was successful, and I was able to logout, login, etc.
I then modified the PoC app's Azure SQL configuration by creating a new named schema, login and user. I added the db_owner role for the new user in the new database. I altered the user's default schema and transferred the tables created by the initial run into the named schema. I confirmed that the user's default schema is correct and the tables are in the named schema. I changed the user name and password in the Connection String section of the Publish dialog and again published the app from Visual Studio. I opened the website in Chrome and clicked the Register link. I entered a user name and password and got the error message "Invalid object name 'UserProfile'". I got the same error when atttempting to login with the user created in the first run.
I am looking for ideas about what to check next. I can work around this issue, but if I missed anything simple I would rather fix things the efficient way. Any ideas?
It seems I found a bug in Azure WebSites that causes the Connection String to not be updated by publishing the web site.
There is a connection string on the Azure Management portal's Configure page for the web site. This connection string is used to connect to the web site's database. It initially contains the User Id and Password used to create the database. Entering a different User ID and Password in the Visual Studio web site project (in Web.config or in the Publish Web dialog) has no effect on the connection string in Azure. This caused a problem in my specific situation, but would also be an issue for anyone who does not use the sa-like server-level user for accessing the database from the web site.
The workaround I found for this issue is to directly modify the Connection String in Azure on the web site's Configure page, instead of relying on effectiveness of a change in the Visual Studio project. This resolved the problem and now the named schema is working correctly.
I have an ASP.NET WebForms application which uses EF 4.1 Codefirst.
Running my application the first time creates a new database, tables etc.
Everything has been working fine so far.
But after adding my application as a WebRole to an Azure Project I got an error message when I first hit the database (CREATE DATABASE permission denied in database 'master').
Obviously it makes a difference if I start my application inside the VS Development Webserver or inside the Azure Emulator.
Here is some additional information which I believe could be relevant:
The database does NOT exist when I run the application
Visual Studio 2010 run as Administrator
Trust level of my web role: Full trust
SQL Server service (MS SQL 2008 R2 Express) is up and running
The connection string in my web.config looks like this:
<add name="dbContext" connectionString="server=(local)\SQLEXPRESS;database=myDB;Integrated Security=True;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
I also tried using a real user instead of "integrated security". And that user had all possible database roles assigned, including sysadmin, serveradmin etc.
How I can I grant the necessary permissions to my application in order to allow creating a database while running inside the Azure emulator?
Thanks so much for your help!
Azure emulator runs with the credentials of "Network Service" account. You need to add credentials for "Network Service" account on master database.