Printable View
Hi everyone
The error appears when testing the odbc
http://img841.imageshack.us/img841/8416/sql5.png
I tried any kind of solution, but the error still appears
I had to reinstall all and start from cero but the error same appears.
Here is a video of my problem:
problemas para probar las odbc - YouTube
If anyone has any idea of this problem, help me!
ODBC Server = (local) or the server name from mssql.
and enable the Named Pipes in the configuration.
That's what I did
Right now I'm loading the other video
Give me a moment
problemas para probar las odbc 2 - YouTube
again. Enable the named pipes. and check the user atum for db_owner rights.
atum2_db_1 & atum2_db_account > security > users > atum double click it and check if they have on Owner Schemas & Role members the db_owner.
The Named Pipes did you find in the Configuration Manager where you have the TCP/IP settings.
I haven’t luck
Hello again
Today, I turned on the computer hoping to run the server, but when I tried to connect the SQL server this error appears
http://img823.imageshack.us/img823/7720/captura2oq.jpg
Restart all the services but with same error
An error after error :grr:
Without a little luck
mhm... you should change ip3 not ip4 in the sql configuration
WHAT THE FUCK you guys talking about...Quote:
Originally Posted by Silenzium
Doesnt matter in SQL Configuration Manager at TCP/IP, where you put the freakin ip and port to work.
It needs only to be enabled and active. Got IT?
So if i want to run the server on lets say 192.165.225.2 with port 1433 Its Not necessarry to put it on ip3 or ip4. If i put it on ip14 (for example) and i activate it and enable it, and after I restart mssqlserver, it will work.
well, in the tutorial its at ip3...
I will have to erase everything and start from cero, to see if can with what he said mKeey
I will record my steps, and see if there is a mistake in some steps
Tomorrow I will have the video ready
Here are the videos
Part1
has errors.
repairing
Part2
in process
I find my problem
I propose finish my videos from my server
finally
I test the odbc