I want to change the SQL DB password after installing Acumatica instance. For instance, want to change the default SQL sa password or just create a new user account for Acumatica. Can I change it? Will Acumatica work after that? What other changes I have to make in order Acumatica to work back again?
Any suggestions?
Credentials used by Acumatica ERP to connect to the database are stored in the connectionStrings section of the web.config file. You can either update connectionString in web.config manually or use the Acumatica ERP Configuration Wizard (Perform Application Maintenance -> Change Database -> ... -> until you reach the Database Connection step):
If using the Acumatica ERP Configuration Wizard, as shown in the screenshot above, you have an option to use an existing login from your SQL Server or MySQL database or create a new login right from the configuration wizard.
You would have to change the connection string attribute in the 'web.config' file. This is similar to changing any ASP.Net website connection string.
Reference:
https://msdn.microsoft.com/en-us/library/jj653752(v=vs.110).aspx
To locate the 'web.config' file on disk you can run IIS Manager 'inetmgr.exe' then right click on the Acumatica website instance in the left tree view and select 'Explore'.
Changing the password is a non destructive operation. If you encounter any issues, you can rollback to the last password. I suggest you also check if 'Acumatica ERP Configuration Wizard' 'Perform Database Maintenance' feature is properly scanning the database entry after the change.
Related
I'm having an issue when I try change settings to Sql Azure Database at Azure, I see:
"This asset was not found, it may have been deleted"
But the access to database by Management Studio is working.
After moving my SQL Server (and it´s only database) between resource groups I had the exact same issue.
SQL Server was listed under "All Resources".
SQL Database had disappeared and was not listed undier "All Resources".
I could see my database if I clicked my SQL Server -> SQL Databases. status was "Online".
If I clicked the database I got the exact same error.
My database was always accessible from SQL Management Studio. Renaming the database in Management Studio to something different and then back to it´s previous name fixed the problem. Now it´s visible again under "All Resources".
This error will usually happen,
when you delete the resource and forget to refresh the page for a while
The issue is usually related to invalid operations with the resource group. For example, assigning a server/database to a resource group that doesn't exist.
Go on your dashboard and delete any shortcut to your database and its server.
Go to the All resources tab on the left blade of the Azure portal and search for your database. Click on it.
Pin the database to the dashboard again by clicking on the pin icon on the top right corner.
Thanks to all who tried to help me, I did not understand at all because, but it seems that maybe it was a problem in azure as such, this problem was presented to me by 3 database, what I did was try a "madness" and was renombrar the database through the Management Studio and once completed was presented in the Azure dashboard.
What I've done was created a new cube inside an existing Analysis Services Multidimensional project and paralleled it with an existing cube. I also changed the target deployment database (test_db_1) to that other than what SharePoint is currently directed towards (prod_db_1) in the reports under Performance Point. The new cubes built and deployed just fine and I see the new cubes in the new database test_db_1 under the current server.
I've then opened PerformancePoint and added the new DB as a new data source. Tested the connection and it passes. Then I try to create a new report, an analytic chart, and that's when I get the error
The Unattended Service Account "domain\user" does not have permissions to see this data. Additional details have been logged for your administrator.
But I'm unable to see these additional details because I lack access.
My administrator has told me it has something to do with the new cubes because the existing cube within the test_db_1 database works. But I see no settings, properties, options for anything that has to do with permissions.
I've been searching all over the web since yesterday trying to understand the reason behind this error.
Under SSMS, ask the administrator to connect to the Analysis services engine. Under "Roles" look at the user there and right click > properties.
In the window go to Cubes on the left hand navigation pane and see if your new cube is listed. If not add it in then that should do the job.
This should be simple..
I have done this.
Create default MVC 4 template and publish site to Azure web site. No problem.
Create a Contact model
Create a view/controller and for the model. Now basic CRUD works on the site with the localDB
Enable migrations, add migration, create test data in seed and update migration. Everything works locally. great!
Now how do I get that database into SQL Azure? I thought it was..
Publish and set ContactContext to SQL Azure string. Test connection. Works. Check 'Use this connection at runtime' .( I assume that means when it is copied it will use that connection).. So now I publish.. then goto /Contacts ... it should automatically create the new DB in Azure... but instead I get
Invalid object name 'dbo.Contacts'.
Where did I go wrong ? Is there another way.. Should I just make a script with schema and data and run that on my SQL Azure table instead? I could do that but it seems the 'publish' way would be easier..
When publishing, check your publish settings and see if it executes the code-first migrations.
This fixed it form me ;)
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.
The DBA's want to know which databases I'm supporting. I haven't found what database servers these are on.
I have tried the following approaches:
I have read that the default is the directory, C:\Program Files\MS SQL\Data, according to this blog Content Database – Changing Default Location. I didn't find an mdb file.
I have looked in Sharepoint Central Administration > Application Management > Content Databases and found a content database name, but I couldn't find that in SharePoint's Central Configuration Web.config.
If it's in the instance's Web.config, I haven't found it.
The DBA's think that I have a different database for each site, but I cannot confirm this. Thanks in advance for any direction you can give me.
The default location you are referring to is the default location for SQL databases.
Go to Sharepoint Central Administration > Application Management > Content Databases
Change the Web application (on the right hand side of the screen) to the site you are looking for
Click on the Database Name
This page should tell you the database name and the database server. Copy both the Database server and the SQL server database name.
This should be the information the DBA's are looking for.
At a minimum you will have a Database per Web Application, but you can also have more than one, depending on how your SharePoint environment has been configure. You will see how many content databases you have per site on the "Manage Content Databases" site from step 2.
These steps show you the Content Databases, but SharePoint also uses additional databases for config and shared services.
Hope this helps!
UPDATE:
PROD_APPNAME_Search - I think this is your serach DB. To confirm go
to Central Administration > Operations > Services on Server > Windows
SharePoint Services Help Search
PROD_APPNAME_SharePoint_Config - Config DB for sharepoint. See this in the SharePoint Products and Technologies Configuration Wizard on the SharePoint server
PROD_APPNAME_SSP_DB - SSP Database (should be able to confirm this
from the step below)
PROD_APPNAME_SSP_Search_DB - Search Database
(should be able to confirm this from the step below)
PROD_APPNAME_SSP_WEB_APP - probably the content DB for the SSP
(should be able to see this in the steps from my original reply)
PROD_APPNAME_WEB_APP - content DB? (should be able to see this in the steps from my original reply)
PROD_APPNAME_MY_SITES - content DB? (should be able to see this in the steps from my original reply)
It looks like whoever setup your farm setup the DBs with the naming format PROD_APPNAME_, which is recommended.
To see the SSP DB's go to http://[servername]/_admin/managessp.aspx. For each SSP (you will probably only have one) click edit properties.
You most likely have one Content Database per Web Application.
Too see them, go to http://CENTRAL_ADMIN/_admin/CNTDBADM.aspx and choose the Web Application you want the info for. When you click the Content Database name, you get details such as:
Database server
SERVER_NAME
SQL Server database name
WSS_Content_WEBAPPDATABASE
With that info, you can trace the physical files from SQL Server, go to Properties > Files on the SQL Management Studio.
You can tell which database server your databases are on by
Opening Central Admin > Application Management > SharePoint Web Application Management > Content Databases
From the Web Application drop-down choose the web application you are interested in
Click the database you are interested in
Take not of the Database server and SQL Server database name
You can tell where the files for this database is located by
Opening SQL Server Management Studio
Connect to the Database server you identified in Step 4 above
Right-click the SQL Server database name you identified in Ste 4 above and choose Properties
In the Database Properties windows choose Files from the Select a page section
Take not of the Path and FileName for each of the files listed