I am not able to connect to my aws-rds instance from asp.net application
I have been trying to connect my asp.net application with my aws-rds instance i have tried using connection strings setting, its doesn't work, but i am also able to connect to my aws-rds database from sql management studio
i also tried to use migration but when i do update-database from console it create a new database in local db
i have also try to provide all required setting and data and then publish my application with aws toolkit but when opening my site link it gives a error -An error occurred while processing your request.
so any can help me with this issue or provide me the proper steps
Check Inbound and outbound rules for instance.
try to connect it with your instance IP.
refer enter link description here
Related
I'm new to SQL Server. I was a postgres user before. I installed the default SQL Server on my local machine and I'm trying to get an old react with node js application of mine working with a SQL Server. When ever my frontend makes more than 1 call to the backend, if my SQL Server has admin privileges it throws
Error: 17810: Could not connect because the maximum number of '1' dedicated administrator connections already exists.
If not, it throws:
Error 18451: Only administrators may connect at this time.
I checked my database configs and it's set to MULTI_USERS, so I don't understand why I can't login without admin privileges. Can someone help me with this? I wasn't able to find anything online.
My NodeJS backend is using TypeORM to connect to the database
The dedicated administrator connection is a different kind of connection. It's not just "a connection being made by someone with administrative access". You would use the DAC when the SQL instance is having some kind problem, and you can't connect at all because resources are all tied up. SQL will reserve some resources especially for the DAC connection to make sure you can still connect.
A DAC connection can be made by specifying ADMIN: as part of your connection string, which will connect to the assigned DAC port.
You shouldn't use this for "routine" admin work. Just connect using a login with the required administrative server roles (eg, sysadmin). You definitely shouldn't use this as part of a regular application's connection string. You shouldn't be using a SQL Server sysadmin login either. Create a user with the appropriate permissions for your application, and don't use the admin connection.
Regarding your second issue: Make sure the instance wasn't set to start in single user or minimum configuration mode using startup flags. Note that this is for the whole instance, it's not the same as the configuration for an individual database.
I have just finished the development of my application on asp.net mvc connected with SQL server, and I will love to deploy it. I want to use Azure App service, but I got an error "Unable to connect to master or target server 'DATABASE_NAME'. You must have a user with the same password in master or target server 'DATABASE_NAME'". I have tried every thing I found online like modifying the SSDT, but nothing changed.
Please is there any recommendation to fix this issue? If not, Please what are other ways for me to launch the application. The application will be used internally for Sales purpose and I don't need any fancy hosting. Thank you in advance.
Did you setup the sql azure firewall to accept connections from your computer?
Even if you set it up once, it is possible that your internet provider attributed a different IP address to your computer. So you must redo your firewall set up again for your computer to be accepted.
It is important to know that only sql logins/passwords are accepted here. So you must give the login/password of the admin user that you mentioned at the moment of creation of you sql server azure (there is a step that sets it up when you create your azure database), or the login/password of a user you created and granted in this database.
Hi All and thanks in advance.
I have an application developed in WebDev 22, and I was able to successfully upload it to my own personal Home Web server, The Application works fine however it cannot read the data because it does not have the analysis.
This application Analysis uses an MSSQL Server Database via the Analysis utilizing MSQL Server Machine ODBC (Means that I am not using the PCSoft Native MS SQL Drivers).
How can place the analysis when creating the Deployment Setup Install File, and how to configure it so that when I am installing the Application in the Site it will talk to the same database I have installed on the Windows Web Server at Home?
Does anyone knows, can this be possible?
Thanks
Regards,
Carlos
I got my own situation resolved.
It turns out that when a Setup Disk is created in PC Soft WebDev, it will automatically include the Database analysis inside the package, in my case I used the option of creating a Media Setup disk to run it in the Web Server, and install the application there. I thought that a very special configuration was needed to be done to connect the Analysis to the MS SQL Data Server in the Web Server, and is none of that.
Let me explain how I got it solved and I would like to explain that everything
was done in the Analysis connection to make possible this connection.
Open the Analysis and Click Connections.
These are the Parameter:
Name: Your Connection Name.
Caption: Your Connection Name here if you want.
Connection By: SQL Server (Microsoft OLE DB Provider for SQL Server).
Data Source: Your MSSQL Database Server Name.
Database: Your Database Name.
User Name: User you created to connect to this database.
Password: The User Password for the User.
Click on Test, if the Connection is successful you are good to Go.
MAKE SURE YOU HAVE VISUAL ON THE SERVER YOU ARE TRYING TO CONNECT
Save the Analysis and Synchronize.
Create the Setup disk and install on the Web Server.
That is it.!!
Why?
Because of when the WebDev application starts, it will Automatically open the Analysis.
The Analysis will then automatically look at the settings you have provided in the Analysis Connection Settings, and it makes the connection.
That is it, I hope this has help.
Best regards,
Carlos
I've deployed my project to Azure and my login page loads. When I attempt to login, it hangs for a moment and returns an "Access is denied" error. I've double and triple checked my connection string and it matches the one provided by Azure.
I've deployed to Azure in the past but it's been a while. Is there something I need to do in order to make my DB accessible? I read a couple articles about similar problems people had with remote connections. It involved turning on remote connection accessibility in SSMS, but I don't see that being the case in my situation as it's not being accessed thru Sql Server.
Are there modifications I must make to my DB to make it accessible on Azure?
Here's my error:
EDIT - I am using forms authentication for user handling if it makes a difference.
This error indicates that your Azure SQL Database is not configured to accept connections from the service you are trying to connect.
You have to Enable Windows Azure Services to connect to your Azure SQL Database Server.
To achieve that, navigate to your Azure SQL Database Dashboard and click on Manage Allowed IP Addresses, as shown bellow:
Then On this new page, make sure that Windows Azure Services are enabled (YES):
I had the same problem and found that I didn't have the database and the app service in the same location. One was in Australia East while the other was in Australia South East. I moved my app service to be in the same location as the DB and bingo. :)
We are troubleshooting a SQL Server 2005 connection issue on a closed-source third-party ASP.NET application. The application is a .NET application and the developing company is using a custom formatted configuration file that stores the SQL Server authentication information.
The application when trying to connect to our SQL Server box is getting a "Cannot open database 'databasename'. Login failed for user 'username'" error. We have tested connecting to the SQL Server box from the web server using SQL Server Management Studio and the login information provided to their app, it works perfectly.
Is there any easy way that we can sniff/determine the SQL Server Connection information they are trying to use inside their SqlCommand? Debugging their code is not an option, as it is compiled in Release Mode, and we don't have source. We simply need something to be able to identify why their app cannot connect.
run profiler and choose Security Audit: Audit Login, Audit Login Failed and Audit Logout events. choose all columns.
from that you'll get the app name, and the user that tries to log in from the login failed event.
once you get that check which database is default for that user in SQL Server users.
I just asked some of the guys here and they both recommended trying reflector. If you had some hard coded values in the library, you should be able to see something there.