Skip to main content

VB.NET Sql Server Cannot Login




I had database application which works fine if it runs locally.

But running the program on other computer or via network, it fails.

It shows the error "Unhandled exception has occured in your application"; "Cannot open database db_name requested by the login."

On my application the issue was the connection string on the code.

This code below runs fine on my application. I'm using VB 2010 for my program.

con.ConnectionString = "Data Source=192.168.1.150,1433;Database=MyDBx;User ID=dbsa;Password=db007"

1433 is the default port for Microsoft SQL; if this was changed you need to enter the correct port.

To check if port 1433 is listening for connections, open a command prompt and type:

netstat -an | find "1433"

If everything is set correctly output will show like this:

TCP    0.0.0.0:1433           0.0.0.0:0              LISTENING
TCP    [::]:1433              [::]:0                 LISTENING

The string connection below was the one messing up the application that caused the program to fail and unable to login to the database remotely or using other computers on the network.

con.ConnectionString = "Data Source=DB7\SQLSRv;Database=DBx7;Integrated Security=True"

There are other possibilities that can cause this error to happen, like:

If the firewall is not configured properly to allow the traffic for the SQL, the “Authentication method” settings on the SQL server, if the username and password does not match on the login database; this scenarios can cause the application to fail.

Hope it helps.. Cheers..
 

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more