Help for SQL 2000 connection!

Hi, I just install SBS 2003 with SQL 2000 on my server, but when I try to
use another PC (OS is WinXP) connect the SQL server throgh ODBC, it pop up a
error msg:
connection failed
SQL state '28000'
SQL server Error: 18452
Login fail for user 'XXX', reason : Not associated with a trusted SQL server
connection.
Can you tell mm how should I do to fix this problem'
Thanks!
DannyYou may be able to resolve your problem through one of the workarounds
provided in this KB article: http://support.microsoft.com/kb/889615/en-us
Nathan H. Omukwenyi
"Danny" <dannyf@.deny.com> wrote in message
news:uOo%23XR3fGHA.1320@.TK2MSFTNGP04.phx.gbl...
> Hi, I just install SBS 2003 with SQL 2000 on my server, but when I try to
> use another PC (OS is WinXP) connect the SQL server throgh ODBC, it pop up
> a
> error msg:
> connection failed
> SQL state '28000'
> SQL server Error: 18452
> Login fail for user 'XXX', reason : Not associated with a trusted SQL
> server
> connection.
> Can you tell mm how should I do to fix this problem'
> Thanks!
> Danny
>|||It's helpful!
Thanks much!
Danny
"Nathan H. Omukwenyi" <nathan@.e-tools.com> wrote in message
news:OwA4S$4fGHA.3996@.TK2MSFTNGP03.phx.gbl...
> You may be able to resolve your problem through one of the workarounds
> provided in this KB article: http://support.microsoft.com/kb/889615/en-us
> Nathan H. Omukwenyi
> "Danny" <dannyf@.deny.com> wrote in message
> news:uOo%23XR3fGHA.1320@.TK2MSFTNGP04.phx.gbl...
>

help creating linked server to Unify ELS on SCO unix

hello,
I'm trying to create a linked server from an SQL2000 to a Unify ELS
(very old, odbc is version 1) database on SCO unix.
The odbc driver is old but it works fine when used by applications for
creating reports.
What I want to do is make a linked server from the SCO box to the win2k
box. So, I'm using enterprise manager to create the linked server.
The DSN of the unify database is CORE_OFFICE1
I'm getting 'Error 7399: OLE DB provider 'MSDASQL' reported an error.
Datasource name not found and no default driver specified.
When I create the linked server I chose the OLE DB for ODBC drivers.
I put 'CORE_OFFICE1' for the Data Source name. I also setup the
security with the name of a unix account for login/password.
What else should I have?
I'm new at this linked server stuff!
Product Name:
Data Source:
Provider String:
Location:
Catalog:
Thanks,
Oskar
Did you install the ODBC driver on the SQL Server box - not
just your PC - and create a system DSN on the SQL Server
box?
-Sue
On Sun, 15 Aug 2004 22:03:00 -0500, pheonix1t
<nothing@.nothing.gone> wrote:

>hello,
>I'm trying to create a linked server from an SQL2000 to a Unify ELS
>(very old, odbc is version 1) database on SCO unix.
>The odbc driver is old but it works fine when used by applications for
>creating reports.
>What I want to do is make a linked server from the SCO box to the win2k
>box. So, I'm using enterprise manager to create the linked server.
>The DSN of the unify database is CORE_OFFICE1
>I'm getting 'Error 7399: OLE DB provider 'MSDASQL' reported an error.
>Datasource name not found and no default driver specified.
>When I create the linked server I chose the OLE DB for ODBC drivers.
>I put 'CORE_OFFICE1' for the Data Source name. I also setup the
>security with the name of a unix account for login/password.
>What else should I have?
>I'm new at this linked server stuff!
>Product Name:
>Data Source:
>Provider String:
>Location:
>Catalog:
>Thanks,
>Oskar
|||Sue Hoegemeier wrote:
> Did you install the ODBC driver on the SQL Server box - not
> just your PC - and create a system DSN on the SQL Server
> box?
Yes, the odbc driver is installed on the sql server box. However, I had
it as a User DSN instead of a System DSN. I changed that and now I get
this error:
Error 7399, authentication failed. Data source rejected connection attempt.
I put the 'sa' user as the local account on the linked server security
tab and I put the unix user/password as the remote account.
I think this is getting closer, but it's still not there!
Thanks,
Oskar

> -Sue
> On Sun, 15 Aug 2004 22:03:00 -0500, pheonix1t
> <nothing@.nothing.gone> wrote:
>
>
|||Yeah...it's closer. Your just stuck on the authentication from SQL to
Unify. You may want to try first by just setting the security context
so that anyone accessing the linked server uses the same login - that
will at least eliminate who you are logging in as for now.
As you are doing this in enterprise manger, on the security tab,
remove the stuff you put in. Then select the last option "Be made
using this security context" and then enter the login and password
needed to access Unify.
-Sue
On Mon, 16 Aug 2004 09:00:08 -0500, pheonix1t <nothing@.nothing.gone>
wrote:
[vbcol=seagreen]
>Sue Hoegemeier wrote:
>Yes, the odbc driver is installed on the sql server box. However, I had
>it as a User DSN instead of a System DSN. I changed that and now I get
>this error:
>Error 7399, authentication failed. Data source rejected connection attempt.
>I put the 'sa' user as the local account on the linked server security
>tab and I put the unix user/password as the remote account.
>I think this is getting closer, but it's still not there!
>Thanks,
>Oskar
|||update
I found out that the unify driver only works in the USER DSN, not the
SYSTEM DSN. So, after a bit of research I've found that it's possible
to do a kluge by using an Access MDB file to connect to the Unify
database via linked table manager. Then, make the linked server using
the Access driver on the SYSTEM DSN.
How does this sound to you? Kinda wild, huh?
Now, I'm in the process of trying to make it work.
Ah, job security!!
Oskar
ps. Any and all advice welcome

help creating linked server to Unify ELS on SCO unix

hello,
I'm trying to create a linked server from an SQL2000 to a Unify ELS
(very old, odbc is version 1) database on SCO unix.
The odbc driver is old but it works fine when used by applications for
creating reports.
What I want to do is make a linked server from the SCO box to the win2k
box. So, I'm using enterprise manager to create the linked server.
The DSN of the unify database is CORE_OFFICE1
I'm getting 'Error 7399: OLE DB provider 'MSDASQL' reported an error.
Datasource name not found and no default driver specified.
When I create the linked server I chose the OLE DB for ODBC drivers.
I put 'CORE_OFFICE1' for the Data Source name. I also setup the
security with the name of a unix account for login/password.
What else should I have?
I'm new at this linked server stuff!
Product Name:
Data Source:
Provider String:
Location:
Catalog:
Thanks,
OskarDid you install the ODBC driver on the SQL Server box - not
just your PC - and create a system DSN on the SQL Server
box?
-Sue
On Sun, 15 Aug 2004 22:03:00 -0500, pheonix1t
<nothing@.nothing.gone> wrote:

>hello,
>I'm trying to create a linked server from an SQL2000 to a Unify ELS
>(very old, odbc is version 1) database on SCO unix.
>The odbc driver is old but it works fine when used by applications for
>creating reports.
>What I want to do is make a linked server from the SCO box to the win2k
>box. So, I'm using enterprise manager to create the linked server.
>The DSN of the unify database is CORE_OFFICE1
>I'm getting 'Error 7399: OLE DB provider 'MSDASQL' reported an error.
>Datasource name not found and no default driver specified.
>When I create the linked server I chose the OLE DB for ODBC drivers.
>I put 'CORE_OFFICE1' for the Data Source name. I also setup the
>security with the name of a unix account for login/password.
>What else should I have?
>I'm new at this linked server stuff!
>Product Name:
>Data Source:
>Provider String:
>Location:
>Catalog:
>Thanks,
>Oskar|||Sue Hoegemeier wrote:
> Did you install the ODBC driver on the SQL Server box - not
> just your PC - and create a system DSN on the SQL Server
> box?
Yes, the odbc driver is installed on the sql server box. However, I had
it as a User DSN instead of a System DSN. I changed that and now I get
this error:
Error 7399, authentication failed. Data source rejected connection attempt.
I put the 'sa' user as the local account on the linked server security
tab and I put the unix user/password as the remote account.
I think this is getting closer, but it's still not there!
Thanks,
Oskar

> -Sue
> On Sun, 15 Aug 2004 22:03:00 -0500, pheonix1t
> <nothing@.nothing.gone> wrote:
>
>|||Yeah...it's closer. Your just stuck on the authentication from SQL to
Unify. You may want to try first by just setting the security context
so that anyone accessing the linked server uses the same login - that
will at least eliminate who you are logging in as for now.
As you are doing this in enterprise manger, on the security tab,
remove the stuff you put in. Then select the last option "Be made
using this security context" and then enter the login and password
needed to access Unify.
-Sue
On Mon, 16 Aug 2004 09:00:08 -0500, pheonix1t <nothing@.nothing.gone>
wrote:
[vbcol=seagreen]
>Sue Hoegemeier wrote:
>Yes, the odbc driver is installed on the sql server box. However, I had
>it as a User DSN instead of a System DSN. I changed that and now I get
>this error:
>Error 7399, authentication failed. Data source rejected connection attempt
.
>I put the 'sa' user as the local account on the linked server security
>tab and I put the unix user/password as the remote account.
>I think this is getting closer, but it's still not there!
>Thanks,
>Oskar
>|||update
I found out that the unify driver only works in the USER DSN, not the
SYSTEM DSN. So, after a bit of research I've found that it's possible
to do a kluge by using an Access MDB file to connect to the Unify
database via linked table manager. Then, make the linked server using
the Access driver on the SYSTEM DSN.
How does this sound to you? Kinda wild, huh?
Now, I'm in the process of trying to make it work.
Ah, job security!!
Oskar
ps. Any and all advice welcome

Help - the replication Failed to Run

error i get from replication when i force them to run the process.
mircosoft sql - DMO(ODBC sql state:42000)
Error 14258: Cannot perform this operation while sqlserveragent is
starting.try again.
But i not restart any sqlserveragent And the sql server servies manager show
that all running.
hope can get asnwer as soon as posible .
thanks.
does this help?
http://support.microsoft.com/default.aspx/kb/303287
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"sam" <sam@.discussions.microsoft.com> wrote in message
news:04A2D6ED-C57E-49EF-8952-50E082F5109F@.microsoft.com...
> error i get from replication when i force them to run the process.
> mircosoft sql - DMO(ODBC sql state:42000)
> Error 14258: Cannot perform this operation while sqlserveragent is
> starting.try again.
> But i not restart any sqlserveragent And the sql server servies manager
> show
> that all running.
> hope can get asnwer as soon as posible .
> thanks.

Help - SQLExecDirect

I could really use some help, I have a system dsn and am
using the Sql Server 2000 odbc driver. I am getting an
error S1000: [Microsoft][ODBC SQL Server Driver]
Connection is busy with results for another hstmt.
When I look at the dsn settings, there is a check box to
turn off SQLPrepare. The problem is it is checked and the
box is greyed out and will not let me turn this off. Does
anyone know why this is like this, and how can I turn it
off?
Will I have to write my own driver?This has nothing to do with SQLPrepare. By default MS SQL Server and
Sybase allow only one statement per connection at a time. It requires
that you close one statement before you open another one. If you try to
open another statement, you get this error. You can change this default
behavior by using Server Side Cursors. Here is some sample code.
nResult = SQLSetStmtAttr(hstmt, SQL_ATTR_CURSOR_TYPE,
(SQLPOINTER)SQL_CURSOR_DYNAMIC, 0);
if(nResult != SQL_SUCCESS && nResult != SQL_SUCCESS_WITH_INFO){
// Handle error
}
nResult = SQLSetStmtAttr(hstmt, SQL_ATTR_ROW_ARRAY_SIZE,
(SQLPOINTER)10, 0);
if(nResult != SQL_SUCCESS && nResult != SQL_SUCCESS_WITH_INFO){
//Handle error
}
Hope this helps.
Pete.
anonymous@.discussions.microsoft.com wrote:

quote:

---

>I could really use some help, I have a system dsn and am
>using the Sql Server 2000 odbc driver. I am getting an
>error S1000: [Microsoft][ODBC SQL Server Driver]
>Connection is busy with results for another hstmt.
>When I look at the dsn settings, there is a check box to
>turn off SQLPrepare. The problem is it is checked and the
>box is greyed out and will not let me turn this off. Does
>anyone know why this is like this, and how can I turn it
>off?
>Will I have to write my own driver?
>

---

You don't pay to get spam, why pay to clean it?
Visit http://www.spammarshall.com to create an account for free
<http://www.spammarshall.com>|||This does not answer the question. I am not programming a
sql statement. I am setting up a DNS and I am unable to
uncheck the Prepare box when setting up the data source.
But thanks, anyway

quote:

---

>--Original Message--
>This has nothing to do with SQLPrepare. By default MS SQL

---

Server and

quote:

---

>Sybase allow only one statement per connection at a time.

---

It requires

quote:

---

>that you close one statement before you open another one.

---

If you try to

quote:

---

>open another statement, you get this error. You can

---

change this default

quote:

---

>behavior by using Server Side Cursors. Here is some

---

sample code.

quote:

---

>
> nResult = SQLSetStmtAttr(hstmt,

---

SQL_ATTR_CURSOR_TYPE,

quote:

---

ed">
>(SQLPOINTER)SQL_CURSOR_DYNAMIC, 0);
> if(nResult != SQL_SUCCESS && nResult !=

---

SQL_SUCCESS_WITH_INFO){

quote:

---

kred">
> // Handle error
> }
> nResult = SQLSetStmtAttr(hstmt,

---

SQL_ATTR_ROW_ARRAY_SIZE,

quote:

---

rkred">
>(SQLPOINTER)10, 0);
> if(nResult != SQL_SUCCESS && nResult !=

---

SQL_SUCCESS_WITH_INFO){

quote:

---

kred">
> //Handle error
> }
>Hope this helps.
>Pete.
>
>
>anonymous@.discussions.microsoft.com wrote:
>
the[QUOTE]
Does[QUOTE]
>--
>You don't pay to get spam, why pay to clean it?
>Visit http://www.spammarshall.com to create an account

---

for free

quote:

---

><http://www.spammarshall.com>
>
>

---

|||Exactly what option are you referring to? There is an option with the text:
"Create temporary stored procedures for prepared SQL statements and drop the
stored procedures: ...". Why do you want to uncheck this option?
If you are not programming a SQL statement, then how are you getting that
error you reported? ("S1000: [Microsoft][ODBC SQL Server Driver]Connection
is busy with results for another hstmt.")
Brannon Jones
Developer - MDAC
This posting is provided "as is" with no warranties and confers no rights.
<anonymous@.discussions.microsoft.com> wrote in message
news:080a01c3be5f$e8847030$a001280a@.phx.gbl...[QUOTE]
> This does not answer the question. I am not programming a
> sql statement. I am setting up a DNS and I am unable to
> uncheck the Prepare box when setting up the data source.
> But thanks, anyway
> Server and
> It requires
> If you try to
> change this default
> sample code.
> SQL_ATTR_CURSOR_TYPE,
> SQL_SUCCESS_WITH_INFO){
> SQL_ATTR_ROW_ARRAY_SIZE,
> SQL_SUCCESS_WITH_INFO){
> the
> Does
> for free|||This is the option I am speaking of, if this option is
unchecked then it will execute directly and not use
prepare and execute. I am getting the error when I use the
dsn connection.

quote:

---

>--Original Message--
>Exactly what option are you referring to? There is an

---

option with the text:

quote:

---

>"Create temporary stored procedures for prepared SQL

---

statements and drop the

quote:

---

>stored procedures: ...". Why do you want to uncheck this

---

option?

quote:

---

>If you are not programming a SQL statement, then how are

---

you getting that

quote:

---

>error you reported? ("S1000: [Microsoft][ODBC SQL Server

---

Driver]Connection

quote:

---

>is busy with results for another hstmt.")
>--
>Brannon Jones
>Developer - MDAC
>This posting is provided "as is" with no warranties and

---

confers no rights.

quote:

---

>
><anonymous@.discussions.microsoft.com> wrote in message
>news:080a01c3be5f$e8847030$a001280a@.phx.gbl...
a[QUOTE]
SQL[QUOTE]
time.[QUOTE]
one.[QUOTE]
am[QUOTE]
to[QUOTE]
it[QUOTE]
>
>.
>

---

|||If you use SQLExecDirect() then the driver will not prepare the statement,
the driver will send the query directly to the server.
That option only applies when you are calling SQLPrepare() and SQLExecute().
As for the error, you are getting the error because you are not consuming
all of the results from an execution, before trying to perform another
execution. The easiest way to ensure you have consumed all of the results
is to call SQLMoreResults() until it returns SQL_NO_DATA. You can create as
many statements per connection as you want, but you need to make sure you
are completely done with a statement, before using another statement that
shares the same connection. If you need to use multiple statements on a
connection at the same time, then you need to use server-side cursors.
Brannon Jones
Developer - MDAC
This posting is provided "as is" with no warranties and confers no rights.
<anonymous@.discussions.microsoft.com> wrote in message
news:066801c3bf2e$7d1e6290$a001280a@.phx.gbl...[QUOTE]
> This is the option I am speaking of, if this option is
> unchecked then it will execute directly and not use
> prepare and execute. I am getting the error when I use the
> dsn connection.
>
> option with the text:
> statements and drop the
> option?
> you getting that
> Driver]Connection
> confers no rights.
> a
> SQL
> time.
> one.
> am
> to
> it|||I know why I'm getting the error, I cannot get it to go
away. I am using a System DSN connection. This is my only
option, I am a developer stuck in the middle. Lotus LEI
tells me it's an MS problem. I do not have control over
the statements being executed. The only control I have is
with the ODBC Data Source. That option I am refering, if I
uncheck the box then it will use SQLExecDirect and my
problem will go away from what I am told.
I suppose I found a bug with ODBC Data Sources.
Thanks any way

quote:

---

>--Original Message--
>If you use SQLExecDirect() then the driver will not

---

prepare the statement,

quote:

---

>the driver will send the query directly to the server.
>That option only applies when you are calling SQLPrepare

---

() and SQLExecute().

quote:

---

>As for the error, you are getting the error because you

---

are not consuming

quote:

---

>all of the results from an execution, before trying to

---

perform another

quote:

---

>execution. The easiest way to ensure you have consumed

---

all of the results

quote:

---

>is to call SQLMoreResults() until it returns

---

SQL_NO_DATA. You can create as

quote:

---

>many statements per connection as you want, but you need

---

to make sure you

quote:

---

>are completely done with a statement, before using

---

another statement that

quote:

---

>shares the same connection. If you need to use multiple

---

statements on a

quote:

---

>connection at the same time, then you need to use server-

---

side cursors.

quote:

---

>--
>Brannon Jones
>Developer - MDAC
>This posting is provided "as is" with no warranties and

---

confers no rights.

quote:

---

>
><anonymous@.discussions.microsoft.com> wrote in message
>news:066801c3bf2e$7d1e6290$a001280a@.phx.gbl...
the[QUOTE]
this[QUOTE]
are[QUOTE]
Server[QUOTE]
programming[QUOTE]
to[QUOTE]
source.[QUOTE]
MS[QUOTE]
and[QUOTE]
getting an[QUOTE]
box[QUOTE]
and[QUOTE]
off.[QUOTE]
turn[QUOTE]
account[QUOTE]
>
>.
>

---

|||That option is for SQL 6.5 servers and older. If you are connecting to a
SQL 6.5 server, then you should have the option to disable it. With SQL 7.0
and newer we use a completely different way to prepare your statements. The
option is disabled, because it is not applicable to newer SQL Servers.
I want to help you, but I need to understand exactly what the problem is
that you are reporting. If you are getting an error that the connection is
busy, then this is a problem with the application that is using the driver.
If you still believe this is a problem with the driver, then you can contact
Microsoft Product Support and they will try to reproduce your problem and
figure out what is going on.
Brannon Jones
Developer - MDAC
This posting is provided "as is" with no warranties and confers no rights.
<anonymous@.discussions.microsoft.com> wrote in message
news:1531501c3c41c$ac765370$a601280a@.phx
.gbl...[QUOTE]
> I know why I'm getting the error, I cannot get it to go
> away. I am using a System DSN connection. This is my only
> option, I am a developer stuck in the middle. Lotus LEI
> tells me it's an MS problem. I do not have control over
> the statements being executed. The only control I have is
> with the ODBC Data Source. That option I am refering, if I
> uncheck the box then it will use SQLExecDirect and my
> problem will go away from what I am told.
> I suppose I found a bug with ODBC Data Sources.
>
> Thanks any way
>
>
> prepare the statement,
> () and SQLExecute().
> are not consuming
> perform another
> all of the results
> SQL_NO_DATA. You can create as
> to make sure you
> another statement that
> statements on a
> side cursors.
> confers no rights.
> the
> this
> are
> Server
> programming
> to
> source.
> MS
> and
> getting an
> box
> and
> off.
> turn
> account

HELP

Error Message "unable to load sql server odbc driver resource DLL.The
Application cannot continute"
Please help me !
You might try reinstalling MDAC
http://msdn.microsoft.com/data/downl.../default.aspx. The latest
version is 2.8.
Hope this helps.
Dan Guzman
SQL Server MVP
"??H" <lemel@.hungnet.idv.tw> wrote in message
news:eryrMLU$EHA.2700@.TK2MSFTNGP14.phx.gbl...
> Error Message "unable to load sql server odbc driver resource DLL.The
> Application cannot continute"
> Please help me !
>

HELP

Error Message "unable to load sql server odbc driver resource DLL.The
Application cannot continute"
Please help me !You might try reinstalling MDAC
http://msdn.microsoft.com/data/down...s/default.aspx. The latest
version is 2.8.
Hope this helps.
Dan Guzman
SQL Server MVP
"??H" <lemel@.hungnet.idv.tw> wrote in message
news:eryrMLU$EHA.2700@.TK2MSFTNGP14.phx.gbl...
> Error Message "unable to load sql server odbc driver resource DLL.The
> Application cannot continute"
> Please help me !
>

HELP

Error Message "unable to load sql server odbc driver resource DLL.The
Application cannot continute"
Please help me !You might try reinstalling MDAC
http://msdn.microsoft.com/data/downloads/updates/default.aspx. The latest
version is 2.8.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"¶Ë¤ß¤H" <lemel@.hungnet.idv.tw> wrote in message
news:eryrMLU$EHA.2700@.TK2MSFTNGP14.phx.gbl...
> Error Message "unable to load sql server odbc driver resource DLL.The
> Application cannot continute"
> Please help me !
>