 |
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
LeeD
Joined: 17 May 2007 Posts: 311 Country: New Zealand |
|
Database profile domain authentication/errors |
|
When I try to set up a database profile to a sql server I only seem to be able to use sql authentication, can 24x7 not use windows domain authentication? It says login incorrect
Also a basic execute command functions (using sql auth) but throws up the error
This is a database job not a script job.
Also are there any issues with using database profiles with 24x7 running as a service?
[/img]
|
|
Mon Sep 10, 2007 1:00 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7955
|
|
|
|
Looks like you have a problem with SQL Server client installation. Is You should be able to able to use both SQL and Windows authentication if your SQL Server is configured to accept these. You can also try using ODBC connection type. This method is more flexible and provides more connectivity options.
|
|
Mon Sep 10, 2007 2:00 am |
|
 |
LeeD
Joined: 17 May 2007 Posts: 311 Country: New Zealand |
|
|
|
I've tried it with all the database servers I have access to with my domain account and none of them work.
Should I be putting DOMAIN\username in the login? I've tried it with and without
|
|
Mon Sep 10, 2007 5:31 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7955
|
|
|
|
If you use native driver connection, you can use SQL authentication only, the native interface doesn't support trusted connections. If you use ODBC connection, in ODBC profile properties, you can specify Windows authentication. In the latest case, it doesn't really matter what you enter for the user and password. These values are simply ignored.
|
|
Mon Sep 10, 2007 5:49 pm |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|