ODBC changes at random...help

Hi All,
Strange thing going on here.....I have an application that uses 2 ODBC
connections, 1 for SQL and 1 for an Access Database. They are configured as
System ODBCs that connect to the databases through a mapped drive to the
server. Everything works fine on all users except 4 of them....whose ODBC
for the Access database will randomly (maybe once a month or less) change
from the one mapped drive to another...where there is no database. 3 of
these users are running XP pro and the other is running Win 2000.
I have deleted the ODBCs and recreated them, disconnected the drives and
re-mapped them....it still does it periodically.
Any idea why this is happening and how to stop it?
Thanks!!
Troubleshooting random events that you can't repro is very difficult.
I'd suggest getting rid of the DSNs you are using and connect
programmatically by supplying the ODBC connection string information
in code when the user connects. You can get the syntax for valid ODBC
connection strings for both Access and SQL Server at
http://able-consulting.com/ADO_Conn.htm and
http://www.connectionstrings.com. DSN's are notoriously difficult to
support and troubleshoot.
--Mary
On Wed, 23 Feb 2005 11:32:40 -0700, "Dan B" <none@.none.com> wrote:

>Hi All,
>Strange thing going on here.....I have an application that uses 2 ODBC
>connections, 1 for SQL and 1 for an Access Database. They are configured as
>System ODBCs that connect to the databases through a mapped drive to the
>server. Everything works fine on all users except 4 of them....whose ODBC
>for the Access database will randomly (maybe once a month or less) change
>from the one mapped drive to another...where there is no database. 3 of
>these users are running XP pro and the other is running Win 2000.
>I have deleted the ODBCs and recreated them, disconnected the drives and
>re-mapped them....it still does it periodically.
>Any idea why this is happening and how to stop it?
>Thanks!!
>

ODBC changes at random...help

Hi All,
Strange thing going on here.....I have an application that uses 2 ODBC
connections, 1 for SQL and 1 for an Access Database. They are configured as
System ODBCs that connect to the databases through a mapped drive to the
server. Everything works fine on all users except 4 of them....whose ODBC
for the Access database will randomly (maybe once a month or less) change
from the one mapped drive to another...where there is no database. 3 of
these users are running XP pro and the other is running Win 2000.
I have deleted the ODBCs and recreated them, disconnected the drives and
re-mapped them....it still does it periodically.
Any idea why this is happening and how to stop it?
Thanks!!Troubleshooting random events that you can't repro is very difficult.
I'd suggest getting rid of the DSNs you are using and connect
programmatically by supplying the ODBC connection string information
in code when the user connects. You can get the syntax for valid ODBC
connection strings for both Access and SQL Server at
http://able-consulting.com/ADO_Conn.htm and
http://www.connectionstrings.com. DSN's are notoriously difficult to
support and troubleshoot.
--Mary
On Wed, 23 Feb 2005 11:32:40 -0700, "Dan B" <none@.none.com> wrote:

>Hi All,
>Strange thing going on here.....I have an application that uses 2 ODBC
>connections, 1 for SQL and 1 for an Access Database. They are configured a
s
>System ODBCs that connect to the databases through a mapped drive to the
>server. Everything works fine on all users except 4 of them....whose ODBC
>for the Access database will randomly (maybe once a month or less) change
>from the one mapped drive to another...where there is no database. 3 of
>these users are running XP pro and the other is running Win 2000.
>I have deleted the ODBCs and recreated them, disconnected the drives and
>re-mapped them....it still does it periodically.
>Any idea why this is happening and how to stop it?
>Thanks!!
>

ODBC Call fail - Strange behaviour

Hi.
I just installed Sql server (in fact MSDE) and exported my Access 2002
projet to this database instance.
I then linked my Sql server tables within my access project.
I get a strange behaviour for some queries. I receive the message 'ODBC -
Call fail'. It seems to be a timeout pb.
The query involves two tables.
I checked my query. Everithing is ok.
I checked the first table. I can read data and filter it.
I checked the second table. I can read data, but if I want to filter any
column, I get an ODBC call fail. The table contains only 802 records.
Any idea ?
Configuration :
MSDE Rel A on XP home SP1.
Access 2002 client, MDAC 2.8, on XP Pro.
Check your data on the SQL server. You may have some data that is null and
the SQL server table def is not allowing nulls? Just a thought. Usually
these errors are caught during the import process...
I would start by creating a brand new query and only add one column at a
time. See if you can then sort on that column. Carry on like this - adding
new columns each time until the error happens. Then check that columns data
on the SQL server so see if there happens to be null values present...
"Alain" <alain.roghi_nospam@.laposte.net> wrote in message
news:uU5H9BEmEHA.2180@.TK2MSFTNGP12.phx.gbl...
> Hi.
> I just installed Sql server (in fact MSDE) and exported my Access 2002
> projet to this database instance.
> I then linked my Sql server tables within my access project.
> I get a strange behaviour for some queries. I receive the message 'ODBC -
> Call fail'. It seems to be a timeout pb.
> The query involves two tables.
> I checked my query. Everithing is ok.
> I checked the first table. I can read data and filter it.
> I checked the second table. I can read data, but if I want to filter any
> column, I get an ODBC call fail. The table contains only 802 records.
> Any idea ?
> Configuration :
> MSDE Rel A on XP home SP1.
> Access 2002 client, MDAC 2.8, on XP Pro.
>

ObsoletedSprocException is being thrown

I have run into a strange problem with SQL Server 2000 (SP4). I am
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsa
geHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegroups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsa
geHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David

ObsoletedSprocException is being thrown

I have run into a strange problem with SQL Server 2000 (SP4). I am
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegroups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David

ObsoletedSprocException is being thrown

I have run into a strange problem with SQL Server 2000 (SP4). I am
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,
"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegr oups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David

Objects dissappearing from SQL Server database

I wasn't sure if I was going mad or if something strange was happening with
my SQL Server 2005. I was convinced that changes I had made to
tables/views/procs etc were 'dissappearing' from time to time.
I have just written (couple of days ago) a ddl trigger that audits ddl
changes to an audit table.
This morning I looked at my database and noticed that a couple of objects
that I create yesterday were no longer in my db. I checked in my ddl audit
table to find that I had created the objects and I wasn't going mad.
Could someone advise me on how to find out what is going on.
Terry,
in Management Studio you can view a report "Schema Changes History"
which shows you which objects have been created, altered or dropped
and by which user. You need to select your server name and then either
go to the reports tab of the Summary page (pre SP2) or right click the
server and go to standard reports (SP2).
Markus

Objects dissappearing from SQL Server database

I wasn't sure if I was going mad or if something strange was happening with
my SQL Server 2005. I was convinced that changes I had made to
tables/views/procs etc were 'dissappearing' from time to time.
I have just written (couple of days ago) a ddl trigger that audits ddl
changes to an audit table.
This morning I looked at my database and noticed that a couple of objects
that I create yesterday were no longer in my db. I checked in my ddl audit
table to find that I had created the objects and I wasn't going mad.
Could someone advise me on how to find out what is going on.Terry,
in Management Studio you can view a report "Schema Changes History"
which shows you which objects have been created, altered or dropped
and by which user. You need to select your server name and then either
go to the reports tab of the Summary page (pre SP2) or right click the
server and go to standard reports (SP2).
Markus

Objects dissappearing from SQL Server database

I wasn't sure if I was going mad or if something strange was happening with
my SQL Server 2005. I was convinced that changes I had made to
tables/views/procs etc were 'dissappearing' from time to time.
I have just written (couple of days ago) a ddl trigger that audits ddl
changes to an audit table.
This morning I looked at my database and noticed that a couple of objects
that I create yesterday were no longer in my db. I checked in my ddl audit
table to find that I had created the objects and I wasn't going mad.
Could someone advise me on how to find out what is going on.Terry,
in Management Studio you can view a report "Schema Changes History"
which shows you which objects have been created, altered or dropped
and by which user. You need to select your server name and then either
go to the reports tab of the Summary page (pre SP2) or right click the
server and go to standard reports (SP2).
Markus