I recently worked on a signature solution. Now i have this worry, it works fine from Visual studio and signs the document. Now the problem is, when i try the same having deployed to IIS , it just stops along the line, shows the confirmation page, but the worry is, it does not even load the base64 from the Database neither does it print the image on the MS word file as it does on Visual Studio. Anyone noticed something like this?
You are probably using Windows authentication when you are running the project in Visual Studio. You have to switch to SQL Authentication through a Database User specific for SQL Server. You do this by:
Creating a database user in SQL Server. See this documentation on Microsoft SQL docs.
Changing the connection string to the following format: ConnectionString="DataSource=.;Database=Sample;user id = test; password=test"
Related
Currently I was going through Microsoft's ASP.NET Core MVC tutorial and it came to a point where I created a database context class, coming complete with a connection string that I add during the config.
Problem is however, when I check with SQL Server Management Studio, I cannot find the database created; I've logged on to both my local host as well as my PC name (for Windows auth) but the database created doesn't exist on either servers.
MS stated in their docs that when I run the command Update-Database in the PMC it would create it but I cant find it anywhere. I've tried using the name of the server from the connection string (localdb) but I cannot connect because SSMS doesn't recognize the instance.
Any idea why it doesn't show up on the studio but seems to work fine during the application running?
Connection string as follows:
"MvcMovieContext": "Server=(localdb)\\mssqllocaldb;Database=MvcMovieContext-1;Trusted_Connection=True;MultipleActiveResultSets=true"
About the LocalDB location, please, take a look here:
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/sql-server-express-localdb?view=sql-server-ver15#:~:text=User%20database%20files%20are%20stored,add%20tables%20in%20Visual%20Studio.
Your LocalDB should be located on C:\Users\<user>\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\mssqllocaldb, assuming mssqllocaldb is your instance name, based on the connection strig you have provided.
Also, to connect to your LocalDB, follow the answers given on this post, I guess could be helpful on your case:
How to connect to LocalDB in Visual Studio Server Explorer?
So I have been working in SSRS for a while but stopped. Now having a small project in it an issue popped up.
I have SQL server and SSRS already configured from before so it should have no issue there, However in this screen I just... can't select any server because none of them appear as an option. I tried to manually input the connection string and it would give me random errors.
Here is a screenshot that shows what I mean
You don't need to select, just write the servername\sqlinstance in the text box. Then fill the sql authentication credentials or use Windows authentication.
So I have this application that I created via VB.NET, Its a Stand Alone Application , During the Development I was setting the app connection string Data source to a Microsoft SQL Server, if the app was only used by me I wouldn't have any problem , my problem is that I want to install it on other Computers , I tried the Attach Database Method , But when I run my application it generates this exception "the user instance login flag is not supported on this version of sql server , the connection will be closed" , I've searched the internet and found out that Attaching Database File is only supported by sql server Express , I have two questions :
If I have SqlLocalDB installed , the attach Database file thing should be working right ?
if i'm wrong , Can you please how can I installed the app with its database without the need to install SQL Server Management studio and attach the database manually so that I could get my app working ?
I believe the answer is here:
http://www.codeproject.com/Questions/304489/Error-msg-the-user-instance-login-flag-is-not-supp
"If you're not using Express with SQL" ... "then you cannot use user instances. You can create the database manually first and set the connection string to point to that database. Remeber to take away the user instance specification from the connection string."
And if you need help with the LocalDB connection string, you can search this page for "LocalDB":
http://www.connectionstrings.com/sql-server/
I'm a newbie to SQL Server 2012. Here is my condition.
I have a running SQL Server 2012 Business Intelligence SP1. The problem is I cannot deploy a project to my SSAS from another computer.
The error is:
The project could not be deployed to the 'DATABASE-SERVER\MSSQLSERVER' server because of the following connectivity problems : A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
The following is the things that I've tried:
Check the target name on Project > Properties > Deployment > Target server.
Check the server service --> all SQL Server services are running.
The project can be deployed from server.
The connection to server is clear
I can connect to the Database Engine and Analysis Service from another computer from SQL Server Management Studio.
Please help me to fix this problem, I've been search for many days for this problem.
Thank you, sorry for my bad english.
Best regards, Stella.
I had the same problem, for me the solution was to explicitly specify login information on the Impersonation Information tab on the Data Source.
I know this is an old thread, but I had the same issue and I reckon more will run into this buzz saw.
My problem was that the remote installation of SSAS did not have an Inbound firewall rule for SSAS application; msmdsrv.exe.
Resolution:
Log on to the server running SSAS as Administrator
Launch Windows Firewall and advanced Security
Add Inbound Rule, give it a meaningful name like SQL Server - SSAS
Action: Allow the connection
On Program and Services Tab: For 'This Program' use Browse and identify msmdsrv.exe
For SQL Server 2014, it is by default here:
%ProgramFiles%\Microsoft SQL Server\MSAS12.SQLSVR14\OLAP\bin\msmdsrv.exe
(Very similar for 2012 and 2016, the numbers are different)
Click OK; You should see a green dot with check mark
Try your project again; It should connect, did for me.
NOTE: If this also work for you, consider going back to the Inbound Rule and consider adding connection restrictions for security reasons.
I solved mine by right clicking my data source (under Data Sources in Solution Explorer) → Edit in the General tab → In Connection Manager, do two things:
Change Server name from localhost to your computer name
Use SQL Server Authentication as Authentication, as opposed to Windows Authentication, and proceed to enter your user name and password (the "sa" password you use for SSMS).
I have a database set up that is to gather planned vacation time that I need to put on sharepoint asap. It's completely done, except for that the application login is failing for anyone that tries to use it that does not have their corprate login (windows authentication) listed in the security logins folder.
The connection string is fine, as it works properly on my computer and another programmer's computer, but not on my boss's computer. I can also login to sql server using the application login that is listed in the connection string.
I'm using SQL Server Managment Studio 2008, the server is 2005.
Edit#1: Further research led to finding this page: http://sql-articles.com/articles/troubleshooting/troubleshooting-login-failed-error-18456/
And my error is state 11. It's listing a windows authentication in the error log even though I specified otherwise.
Edit#2: My Connection String is this:
Driver={SQL Server};Server=ServerName\ThingIdontUnderstand;Database=ReportingDevDB;Trusted_Connection=FALSE;uid=Derp;pwd=qwerty;
Edit#3: Solved! See comments on this post for answers since I can't answer my own questions yet.
You check for the version when you connect to the instance through SSMS it will show it beside the server name under Object Explorer. Or just use the query SELECT ##VERSION
I would suggest simply creating a corporate windows group and adding those individuals to it, and then simply add this group as a login to your instance of SQL Server.