Paul Sturrock wrote:
Are you using the correct credentials?
Paul Sturrock wrote:
If so, does your SQL Server instance support TCP/IP? SQL Server 2000 should have this turen on by default, but you may have turned it off.
Paul Sturrock wrote:
Is your server configured to allow SQL Server authentication? By default, SQL Server uses only Windows integrated authentication.
Paul Sturrock wrote:
(NB: you seem to be using very old versions of various JDBC drivers. Not likely to be the cause of the issue, but asking for trouble long term.)
Paul Sturrock wrote:
Are you using the correct credentials?
for this part, if this is true that already i used Data Sources (ODBC) many times, so is this means that TCP/IP has not turned off? and i just having problems with connecting driver ....
this is the part i must say i didn't now at all how to configure this, is your mean jboss-3.2.5\server\default\conf\login-config.xml? if so, how can i do then for SQL Server 2000...
Paul Sturrock wrote:
This is nothing to do with JBoss, its your SQL server instance that I am talking about. Check the properties of your database server, specifically if it allows SQL Server authentication.
Paul Sturrock wrote:
That looks OK. There was an issue with very early versions of the networking dll - if your SQL Server instance is unpatched there may still be an issue, but I think that looks OK.
Paul Sturrock wrote:
So all thats left is if your SQL Server instance is configured to allow SQL Server authentication (like I said early, by default it is not).
dear Paul, sorry but, i'm very new fresh computer programmer if i can call it, what i have to do now, i'm loosing my power with these all disconnection, how to find this networking dll? how patch my SQL Server? these all are very important to me in a clear way
so please lemme do this configuration step by step,
Paul Sturrock wrote:
This is a long shot. Its far more likely your server is not configured to support SQL Server authentication, since this is the default setting for SQL Server. Just right click on your server in management studio and see what the version number is.
Paul Sturrock wrote:
Afraid I can't remeber off the top of my head for SQL Server 2000. You probably want to start by looking at the properties of the server (as mentioned above) and see if you can find the security settings from there. If you don't want to guess your way around, this is all covered in the SQL Server documentation on MDSN.
Paul Sturrock wrote:What you've got is the version of enterprise manager (which is a sql client), not the SQL Server server instance. Like I said, that suggestion is very much a long shot. You would need to have a very old version of SQL Server 2000 for it to be a problem (the only time I've seen it the tcp/ip DLLs were dated 1998).
As I've said a few times now, the more likely source is your SQL Server is not configured to allow SQL Server authentication, since this is the default. Try looking at the properties of the server. If you are not sure how to do that, MSDN includes product documentation - I'm sorry I can't remember (SQL Server 2000 is a good few years past being a supported platform).
Sometimes you feel like a nut. Sometimes you feel like a tiny ad.
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|