[Transfer SQL Server Objects Task] Error: Table does not exist at the source.

Hello,

I am running a package that used to transfers data from one SQL2005 to another SQL2005. There are multiple schemas associated with the database. Until recently, this pacakage would work. Now I am getting the following error for all the tables not owned by dbo:

Any help on this would be appreciated.

Thanks, sck10

[Transfer SQL Server Objects Task] Error: Table "tblAudiocast" does not exist at the source.

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600

May be it;s a direct error that in the source "tblAudiocast" table may not be exisiting or renamed!!!

Or check the connection strings if it's pointing to the correct data base!!

Dev

|||

Thanks Dev, but all the tables exist. We copy the schema from the production database to the local database, so they are duplicates. And it works for tables that belong to dbo only, but fails for all other tables.

sck10

|||

This thread describes the same problem - it's a known bug. It may have been fixed in SP2, but I'm not positive.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=207812&SiteID=1

|||

Thanks jwelch,

My SSIS package was working until recently.

sck10

sql

[Transfer SQL Server Objects Task] Error: Table does not exist at the source.

Hello,

I am running a package that used to transfers data from one SQL2005 to another SQL2005. There are multiple schemas associated with the database. Until recently, this pacakage would work. Now I am getting the following error for all the tables not owned by dbo:

Any help on this would be appreciated.

Thanks, sck10

[Transfer SQL Server Objects Task] Error: Table "tblAudiocast" does not exist at the source.

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600

May be it;s a direct error that in the source "tblAudiocast" table may not be exisiting or renamed!!!

Or check the connection strings if it's pointing to the correct data base!!

Dev

|||

Thanks Dev, but all the tables exist. We copy the schema from the production database to the local database, so they are duplicates. And it works for tables that belong to dbo only, but fails for all other tables.

sck10

|||

This thread describes the same problem - it's a known bug. It may have been fixed in SP2, but I'm not positive.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=207812&SiteID=1

|||

Thanks jwelch,

My SSIS package was working until recently.

sck10

[strange] date format issue: 2 servers, one query, 2 different results.

I'm running 2 WIN2K SP4 servers with MSSQL Server (v 7.00.1077). Both NT servers seems to have the same setup. I use the ADODB object to connect to MSSQL via OLE DB and notice that the following query generates an error on one server, not the other:

SELECT DATA FROM TABLE_1 WHERE ((TRANSACTION_DATE >='13/11/2003') AND (TRANSACTIONS_DATE <='20/11/2003')) [dates are DD/MM/YYYY]

Query on server_1:
- using OLE DB: correct
- using ODBC: correct
- using Query Analyzer: error <The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value>

On server_2:
- using OLE DB: error <The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value>
- using ODBC: correct
- using Query Analyzer: error <The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value>

Both servers have MDAC 2.8 RTM installed and a <select @.@.language> returns <us_english> via query analyzer and <franais> via ODBC.

I'd like to setup Server 2 so that queries can be executed the same as on server 1.

Any ideas are welcomed!There's a problem with 20/11/2003 in us_english format. Default is: MDY, so it's reading 20th as month, which is why you're getting that error.

Here's an article I found: http://members.lycos.nl/digispy/C2/P56/C2P56A1806.htm

G'luck!
Meera|||Possible there is something to do with locale settings of windows, check the "Region Options" in Control Panel for both servers.|||I'd say the languages are different...and accordingingly each date format is different

Di SELECT * FROM master..syslanguages

I think English is the only one that mdy|||(D/M/Y is a French date format).

I just had to set <French> to user's default language instead of <US_ENGLISH>. This means ODBC settings override the default SQL Server settings as OLE DB uses the default SQL Server setting.sql

[SQLSTATE 42000] (Error 8198)).

Running SQL 2000 & Win 2000.
My main server was upgraded/replaced today. We stopped
SQL on the ond server and copied the dBs to the new
server, which has the same name as old server. I receive
the following message on all my subscriptions from my
remote locations.
The job failed. Unable to determine if the owner
(domain.COM\user) of job sqlname-StoreMain-
vCost,vItem,PLU-remotesqlSERVER-StoreMain-D80E140D-1D56-
4A0A-96D3-E33335441348 has server access (reason: Could
not obtain information about Windows NT
group/user 'domain.COM\user'. [SQLSTATE 42000] (Error
8198)).
I have done some research and found I need to change the
owner of the job.
How do I do that?
HELP!!!!
Larry...
locate the job in the jobs subfolder of the management folder. Right click
on it, select properties and modify it there.
You can also use sp_update_job to make this change.
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:515a01c42cb9$00956860$a401280a@.phx.gbl...
> Running SQL 2000 & Win 2000.
> My main server was upgraded/replaced today. We stopped
> SQL on the ond server and copied the dBs to the new
> server, which has the same name as old server. I receive
> the following message on all my subscriptions from my
> remote locations.
> The job failed. Unable to determine if the owner
> (domain.COM\user) of job sqlname-StoreMain-
> vCost,vItem,PLU-remotesqlSERVER-StoreMain-D80E140D-1D56-
> 4A0A-96D3-E33335441348 has server access (reason: Could
> not obtain information about Windows NT
> group/user 'domain.COM\user'. [SQLSTATE 42000] (Error
> 8198)).
> I have done some research and found I need to change the
> owner of the job.
> How do I do that?
>
> HELP!!!!
> Larry...
|||Larry,
the job owner is only validated in AD and not actually used as the job runs
as SQL Agent. With that in mind, you can change the job owner to sa to fix
this type of problem.
Regards,
Paul Ibison

[SQL Server]Transaction (Process ID 52) was deadlocked

I am using SQL Server 2000 and running number of query simulatneously. While
running update query it is always giving above error. The error discriptions
are -
1. [SQL Server]Transaction (Process ID 52) was deadlocked on {lock}
resources with another process and has been chosen as the deadlock victim
2. SQL Server]Transaction (Process ID 51) was deadlocked on {lock} reso
urces
with another process and has been chosen as the deadlock victim
3. [SQL Server]Transaction (Process ID 56) was deadlocked on {lock}
resources with another process and has been chosen as the deadlock victim
I have tried cleaning up the database, increased the fixed memory size of
SQL Server to 800 MB, restart the machine. But nothing works.
Plz help out to resolve this problem.get output from
sp_who
sp_who2
sp_lock
when the trans is running
"Sudhanshu" <Sudhanshu@.discussions.microsoft.com> wrote in message
news:EBF56A23-2CBC-4E4F-9220-F53C6B656AB1@.microsoft.com...
>I am using SQL Server 2000 and running number of query simulatneously.
>While
> running update query it is always giving above error. The error
> discriptions
> are -
> 1. [SQL Server]Transaction (Process ID 52) was deadlocked on {loc
k}
> resources with another process and has been chosen as the deadlock victim
> 2. SQL Server]Transaction (Process ID 51) was deadlocked on {lock}
> resources
> with another process and has been chosen as the deadlock victim
> 3. [SQL Server]Transaction (Process ID 56) was deadlocked on {loc
k}
> resources with another process and has been chosen as the deadlock victim
>
> I have tried cleaning up the database, increased the fixed memory size of
> SQL Server to 800 MB, restart the machine. But nothing works.
> Plz help out to resolve this problem.|||Thx. I will check that.
"David J. Cartwright" wrote:

> get output from
> sp_who
> sp_who2
> sp_lock
> when the trans is running
> "Sudhanshu" <Sudhanshu@.discussions.microsoft.com> wrote in message
> news:EBF56A23-2CBC-4E4F-9220-F53C6B656AB1@.microsoft.com...
>
>

[SQL Server]Transaction (Process ID 52) was deadlocked

I am using SQL Server 2000 and running number of query simulatneously. While
running update query it is always giving above error. The error discriptions
are -
1. [SQL Server]Transaction (Process ID 52) was deadlocked on {lock}
resources with another process and has been chosen as the deadlock victim
2. SQL Server]Transaction (Process ID 51) was deadlocked on {lock} resources
with another process and has been chosen as the deadlock victim
3. [SQL Server]Transaction (Process ID 56) was deadlocked on {lock}
resources with another process and has been chosen as the deadlock victim
I have tried cleaning up the database, increased the fixed memory size of
SQL Server to 800 MB, restart the machine. But nothing works.
Plz help out to resolve this problem.
get output from
sp_who
sp_who2
sp_lock
when the trans is running
"Sudhanshu" <Sudhanshu@.discussions.microsoft.com> wrote in message
news:EBF56A23-2CBC-4E4F-9220-F53C6B656AB1@.microsoft.com...
>I am using SQL Server 2000 and running number of query simulatneously.
>While
> running update query it is always giving above error. The error
> discriptions
> are -
> 1. [SQL Server]Transaction (Process ID 52) was deadlocked on {lock}
> resources with another process and has been chosen as the deadlock victim
> 2. SQL Server]Transaction (Process ID 51) was deadlocked on {lock}
> resources
> with another process and has been chosen as the deadlock victim
> 3. [SQL Server]Transaction (Process ID 56) was deadlocked on {lock}
> resources with another process and has been chosen as the deadlock victim
>
> I have tried cleaning up the database, increased the fixed memory size of
> SQL Server to 800 MB, restart the machine. But nothing works.
> Plz help out to resolve this problem.
|||Thx. I will check that.
"David J. Cartwright" wrote:

> get output from
> sp_who
> sp_who2
> sp_lock
> when the trans is running
> "Sudhanshu" <Sudhanshu@.discussions.microsoft.com> wrote in message
> news:EBF56A23-2CBC-4E4F-9220-F53C6B656AB1@.microsoft.com...
>
>

[ODBC SQL Server Driver] Timeout Expired - How to fix

I am running SQL (Selects and Deletes) against a large
table in a database and am getting Timeout Expired. I am
using Enterprise Manager (Right Click on Table and select
Query). Is there a setting that I need to change to allow
a long running query? It works fine in the SQL Query
Analyzer.
SELECT COUNT(*) AS Expr1
FROM CallDetailThe timeout is a property of the connection to the server. Select your
instance in the Enterprise manager, select properties. Then on the
connection tab change the timeout. (Zero means infinite)
Bruce
"Michael Orechoff" <anonymous@.discussions.microsoft.com> wrote in message
news:0ee701c39d6b$f0e86750$a401280a@.phx.gbl...
> I am running SQL (Selects and Deletes) against a large
> table in a database and am getting Timeout Expired. I am
> using Enterprise Manager (Right Click on Table and select
> Query). Is there a setting that I need to change to allow
> a long running query? It works fine in the SQL Query
> Analyzer.
> SELECT COUNT(*) AS Expr1
> FROM CallDetail|||Better indexing / design so that the query doesn't take so long? Use Query
Analyzer rather than Enterprise Manager (see http://www.aspfaq.com/2455)?
You could kludge it up by increasing your timeouts, but this is like
bandaging a fever.
"Michael Orechoff" <anonymous@.discussions.microsoft.com> wrote in message
news:0ee701c39d6b$f0e86750$a401280a@.phx.gbl...
> I am running SQL (Selects and Deletes) against a large
> table in a database and am getting Timeout Expired. I am
> using Enterprise Manager (Right Click on Table and select
> Query). Is there a setting that I need to change to allow
> a long running query? It works fine in the SQL Query
> Analyzer.
> SELECT COUNT(*) AS Expr1
> FROM CallDetail

[Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is either invalid or not

I have this instance running, on a server. I can connect to it using SQL
Query Analyzer as well as SQL Enterprise Manager.
But when I try to connect to it using SQL Server JDBC it gives error,
[Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is either
invalid or not running.
I havent changed anything in Java code it is still the same. It was working
fine earlier. Can any one help?
I had similar problem with SQL Analyzer too but I could fix it using
cliconfg utility provided by MS.
| From: "Developers@.Enzigma" <developers@.enzigma.com>
| Subject: [Microsoft][SQLServer 2000 Driver for JDBC]The requested
instance is either invalid or not running.
| Date: Thu, 20 May 2004 16:29:47 +0530
| Lines: 14
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <eIISfmlPEHA.1340@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: 203.123.162.162
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP12
.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.jdbcdriver:6044
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I have this instance running, on a server. I can connect to it using SQL
| Query Analyzer as well as SQL Enterprise Manager.
|
| But when I try to connect to it using SQL Server JDBC it gives error,
| [Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is
either
| invalid or not running.
|
| I havent changed anything in Java code it is still the same. It was
working
| fine earlier. Can any one help?
|
| I had similar problem with SQL Analyzer too but I could fix it using
| cliconfg utility provided by MS.
|
|
|
With JDBC SP2, I can only reproduce this behavior if I have incorrectly
specified the instance name in my code. What is the name of your instance,
and can you post the code snippet that reproduces the problem? You
mentioned using cliconfg.exe to fix a similar problem with Query Analyzer.
Please run this tool again and verify that there are no aliases that point
to an invalid instance name as well.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

[Microsoft][ODBC SQL Server Driver] Timeout Expired

Hello,
I installed MS SQL Server 2000 Evaluation Edition on
Windows XP Pro PC. I have database on the same PC. When I
am running a query(view) from Query Analyser I
get "[Microsoft][ODBC SQL Server Driver] Timeout Expired"
error message . When I am running the same view on
smaller amount of data it works.
Could you please help me with that?
Thanks
DJ
hi
goto the server properties.then there is a property called connection time.
check it and give the appropiate time on this

[Microsoft][ODBC SQL Server Driver] Timeout Expired

Hello,
I installed MS SQL Server 2000 Evaluation Edition on
Windows XP Pro. I have database on the same PC. When I
am running a query(view) from Query Analyser I
get "[Microsoft][ODBC SQL Server Driver] Timeout Expired"
error message . When I am running the same view on
smaller amount of data it works.

:confused:

Could you please help me with that?
Thanks
DJCheck out this page.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;313661|||The link in the previous post is for a connection timeout using SQL Server 7. It does not apply to running a query on SQL Server 2000.|||SQL Server 2000's default timeout period it 600 seconds (10 minutes). If you change it to zero (0), that's infinite. How long is it taking to timeout?

If you run a long query through the Enterprise Manager, it will timeout after 30 seconds. MS's answer to this is to use the Query Analyzer (which should not timeout). I've run a 14-hour query through SQL Query Analyzer before.

[Microsoft][ODBC SQL Server Driver] Timeout Expired

Hello,
I installed MS SQL Server 2000 Evaluation Edition on
Windows XP Pro PC. I have database on the same PC. When I
am running a query(view) from Query Analyser I
get "[Microsoft][ODBC SQL Server Driver] Timeout Expired"
error message . When I am running the same view on
smaller amount of data it works.
Could you please help me with that?
Thanks
DJhi
goto the server properties.then there is a property called connection time
.
check it and give the appropiate time on this

[Microsoft][ ODBC SQL Server Drive ] Timeout expired

I am running a VB application which makes connection to the SQL server
database using DSN connection using ODBC. This application pulls data using
stored procedure. The application does not insert / delete / update data.
The application was working fine since it has been installed (more than ONE
year). Suddendly it has started generating runtime error '-2147217871
(80040e31)'. I have taken the following actions so far to identify the
problem:
1. Checked user permission set on the database. Its fine. ODBC test
connection is successful.
2. Debugged VB source. It successfully makes connection to the database but
generated error while executing Command object which is using a stored
procedure which pulls the data into the grid.
3. Changed the timeout property of the Command object to 60 seconds. Still
generating error.
4. Copy pasted Query from stored procedure into Query Analyzer. The query
ran within 10 seconds generating desired resultset. Hence, Table index /
fragmentation problem is ruled out.
5. Copy data and Object from Live database into another database on the same
server using DTS wizard. Changed database name in the ODBC configuration
pointing it to the new database having same data & objects (including users &
permissions). The application ran succussefully without generating any
error. Hence database server problem is ruled out.
6. The stored procedure used by the command object in VB code fails to
execute.
Any help on how to fix this problem?
Manish Acharya
Systems Analyst & database developer
Task Transactions Ltd., New Zealand.
Have you considered taking ODBC or SQL Server Profiler traces? These might
give more clues.
"Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>I am running a VB application which makes connection to the SQL server
> database using DSN connection using ODBC. This application pulls data
> using
> stored procedure. The application does not insert / delete / update data.
> The application was working fine since it has been installed (more than
> ONE
> year). Suddendly it has started generating runtime error '-2147217871
> (80040e31)'. I have taken the following actions so far to identify the
> problem:
> 1. Checked user permission set on the database. Its fine. ODBC test
> connection is successful.
> 2. Debugged VB source. It successfully makes connection to the database
> but
> generated error while executing Command object which is using a stored
> procedure which pulls the data into the grid.
> 3. Changed the timeout property of the Command object to 60 seconds.
> Still
> generating error.
> 4. Copy pasted Query from stored procedure into Query Analyzer. The query
> ran within 10 seconds generating desired resultset. Hence, Table index /
> fragmentation problem is ruled out.
> 5. Copy data and Object from Live database into another database on the
> same
> server using DTS wizard. Changed database name in the ODBC configuration
> pointing it to the new database having same data & objects (including
> users &
> permissions). The application ran succussefully without generating any
> error. Hence database server problem is ruled out.
> 6. The stored procedure used by the command object in VB code fails to
> execute.
> Any help on how to fix this problem?
> Manish Acharya
> Systems Analyst & database developer
> Task Transactions Ltd., New Zealand.
|||Thanks Chris for your response. I have been working on SQL server profiler
traces to identify this problem. My experience on using SQL server profiler
is a bit limited and I see this as an opportunity to hone my skills in this
area. Your reply confirms that I am on the right direction. I will post the
solution in this discussion group once I crack it.
Cheers.
Manish Acharya.
"Chris Lee[MS]" wrote:

> Have you considered taking ODBC or SQL Server Profiler traces? These might
> give more clues.
> "Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
> news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>
>
|||Hi Manish Acharya,
Had you find the solution for the problem above? I have the same problem
like you, so hope you can shared the solution with us.
Thank you.

[Microsoft][ ODBC SQL Server Drive ] Timeout expired

I am running a VB application which makes connection to the SQL server
database using DSN connection using ODBC. This application pulls data using
stored procedure. The application does not insert / delete / update data.
The application was working fine since it has been installed (more than ONE
year). Suddendly it has started generating runtime error '-2147217871
(80040e31)'. I have taken the following actions so far to identify the
problem:
1. Checked user permission set on the database. Its fine. ODBC test
connection is successful.
2. Debugged VB source. It successfully makes connection to the database but
generated error while executing Command object which is using a stored
procedure which pulls the data into the grid.
3. Changed the timeout property of the Command object to 60 seconds. Still
generating error.
4. Copy pasted Query from stored procedure into Query Analyzer. The query
ran within 10 seconds generating desired resultset. Hence, Table index /
fragmentation problem is ruled out.
5. Copy data and Object from Live database into another database on the same
server using DTS wizard. Changed database name in the ODBC configuration
pointing it to the new database having same data & objects (including users
&
permissions). The application ran succussefully without generating any
error. Hence database server problem is ruled out.
6. The stored procedure used by the command object in VB code fails to
execute.
Any help on how to fix this problem?
Manish Acharya
Systems Analyst & database developer
Task Transactions Ltd., New Zealand.Have you considered taking ODBC or SQL Server Profiler traces? These might
give more clues.
"Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>I am running a VB application which makes connection to the SQL server
> database using DSN connection using ODBC. This application pulls data
> using
> stored procedure. The application does not insert / delete / update data.
> The application was working fine since it has been installed (more than
> ONE
> year). Suddendly it has started generating runtime error '-2147217871
> (80040e31)'. I have taken the following actions so far to identify the
> problem:
> 1. Checked user permission set on the database. Its fine. ODBC test
> connection is successful.
> 2. Debugged VB source. It successfully makes connection to the database
> but
> generated error while executing Command object which is using a stored
> procedure which pulls the data into the grid.
> 3. Changed the timeout property of the Command object to 60 seconds.
> Still
> generating error.
> 4. Copy pasted Query from stored procedure into Query Analyzer. The query
> ran within 10 seconds generating desired resultset. Hence, Table index /
> fragmentation problem is ruled out.
> 5. Copy data and Object from Live database into another database on the
> same
> server using DTS wizard. Changed database name in the ODBC configuration
> pointing it to the new database having same data & objects (including
> users &
> permissions). The application ran succussefully without generating any
> error. Hence database server problem is ruled out.
> 6. The stored procedure used by the command object in VB code fails to
> execute.
> Any help on how to fix this problem?
> Manish Acharya
> Systems Analyst & database developer
> Task Transactions Ltd., New Zealand.|||Thanks Chris for your response. I have been working on SQL server profiler
traces to identify this problem. My experience on using SQL server profiler
is a bit limited and I see this as an opportunity to hone my skills in this
area. Your reply confirms that I am on the right direction. I will post th
e
solution in this discussion group once I crack it.
Cheers.
Manish Acharya.
"Chris Lee[MS]" wrote:

> Have you considered taking ODBC or SQL Server Profiler traces? These might
> give more clues.
> "Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in messa
ge
> news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>
>|||Hi Manish Acharya,
Had you find the solution for the problem above? I have the same problem
like you, so hope you can shared the solution with us.
Thank you.

[Microsoft] [ODBC SQL Server Driver] Timeout expired

Hi, Everyone,

I have a SQL 2000 cluster with sp4. I used SQL QUERY Analyzer to running DBCC CHECKDB for 2 of user’s databases (one is 110 GB and other 5 GB) and get the following message: [Microsoft] [ODBC SQL Server Driver] Timeout expired.I am running same DBCC CHECKDB against system databases or other small users’ databases are fine.

I can get resulted back from T-SQL (DBCC CHECKDB) against these 2 user databases and I checked sp_configure with other server, I can not find the difference.

Can someone help me out?

KT

Are you executing CHECKDB against 2 of those databases at the same time?

Also check event viewer and SQL error logs for any sort of slow performance with any of the hardware or components on this server.

Have you tried scheduling the same using a SQLagent job?

Have you applied or tested the sp4 hotfix?

|||

I ran dbcc checkdb agaist each database at each time. There has no information logon at even view and SQL log when I got time out message.

I haven't schedule this dbcc checkdb at SQL agent job yet.

I only applied hot fix -KB903086 and brought SQL server level to v8.00 2140.

|||ODBC Sql server drive Timeout expires error message getting when I connect to sql200 server data base with query analyzer

[Microsoft] [ODBC SQL Server Driver] Timeout expired

Hi, Everyone,

I have a SQL 2000 cluster with sp4. I used SQL QUERY Analyzer to running DBCC CHECKDB for 2 of user’s databases (one is 110 GB and other 5 GB) and get the following message: [Microsoft] [ODBC SQL Server Driver] Timeout expired.I am running same DBCC CHECKDB against system databases or other small users’ databases are fine.

I can get resulted back from T-SQL (DBCC CHECKDB) against these 2 user databases and I checked sp_configure with other server, I can not find the difference.

Can someone help me out?

KT

Are you executing CHECKDB against 2 of those databases at the same time?

Also check event viewer and SQL error logs for any sort of slow performance with any of the hardware or components on this server.

Have you tried scheduling the same using a SQLagent job?

Have you applied or tested the sp4 hotfix?

|||

I ran dbcc checkdb agaist each database at each time. There has no information logon at even view and SQL log when I got time out message.

I haven't schedule this dbcc checkdb at SQL agent job yet.

I only applied hot fix -KB903086 and brought SQL server level to v8.00 2140.

|||ODBC Sql server drive Timeout expires error message getting when I connect to sql200 server data base with query analyzer

[DBNETLIB][ConnetionWrite (WrapperWrite()).]General network error. Check your ne

Hi
While running a DTS, many times the error message: "[DBNETLIB][ConnetionWrite (WrapperWrite()).]General network error. Check your network documentation." appears.
Does somebody knows why?

I am running the DTS from a computer (not the server where the DTS is stored) and it is connected without any problem when this happens.

Thanks!!
Regards
Lautaro - Argentina.Do you get your results that your looking for from the dts?|||This looks like a network connectivity issue to me. Check (1) Network Connectivity by pinging, etc. (2) Check O/S security and permissions on any files you are trying to access, and (3) Check SQL Server login issues (i.e. SQL Service logins etc).

Great Detailed Error Messages Brought To Us By Microsoft ! ;)

Michael D.|||Hi

I am getting the same Wrapperwrite error .

The server is windows NT running SQL6.5 with all the latest service packs
The client machines are running all different operating systems.
The ODBC connections on the clients and server use either TCP/IP or named pipes but I get the same error on all clients.
The clients and server connect to a sql 6.5 database and when requesting information about certain clients, not all, the wrapperwrite error comes up and i have to close the progarm down.

I have heard people say on forums the it could be to do with the network but please note that this also happens on the server!

can any one help Please

Cheers|||General Network errors are commonly caused by tcp resets on the network.
You'll want to capture as much data about the clients and the statements they're executing using PROFILER.

Select All Errors and Warnings
RPC: Completed, Starting, sp Recompile
TSQL BatchCompleted, BatchStarting
Stmt:Starting

[DBNETLIB][ConnectionWrite (send()).] errors

We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.

Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.

Does anyone have any ideas ?

Hi Brian,

I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.

The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...

I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp

Both to no avail....

Was wondering if you'd found a resolution yet?

Best regards

Keith
|||

For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.

HTH

|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue

[DBNETLIB][ConnectionWrite (send()).] errors

We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.

Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.

Does anyone have any ideas ?

Hi Brian,

I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.

The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...

I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp

Both to no avail....

Was wondering if you'd found a resolution yet?

Best regards

Keith
|||

For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.

HTH

|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue

[DBNETLIB][ConnectionRead (WrapperRead()).]General network error. Check your network docum

Starting to get really tired of this error message, it's completely random
and happens usually on long running queries, it is not a network failure
since the sql server is on the same machine.
Things I have tried:
o Updating MDAC
o Changing connection string
o Using only TCP/IP
o Using only pipes
o Removing shared memory option
The only articles on MS site I can find talks about doing backups or
running some built in sp which is not what I'm doing.
One of the articles refer to MDAC 2.8 SP1 which does not exist !
Doing some googling reveals that this is not an uncommon problem
but so far no solutions.
This is starting to have serious side effects and needs to be solved,
please help with any ideas !
Thanks.
PL.Talke a look at the following BLOG. This helped fix my "General Networ
Errors"...
'The infamous General Network Error' (http://tinyurl.com/4yc7k)
'SQL Data Provider Patch' (http://support.microsoft.com/?kbid=328476
-
cbuzzett
----
Posted via http://www.mcse.m
----
View this thread: http://www.mcse.ms/message389824.htm|||cbuzzetta wrote:
> *Talke a look at the following BLOG. This helped fix my "General
> Network Errors"...
> 'The infamous General Network Error' (http://tinyurl.com/4yc7k)
> 'SQL Data Provider Patch' (http://support.microsoft.com/?kbid=328476)
> *
Just FYI I was getting this error on archived tables that no longer had
indexes - added indexes for them on the key fields and the error
disappeared. May not be relevant but it was the fix for me : )
X
DocFKNx
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message389824.html

[DBNETLIB][ConnectionRead (WrapperRead()).]General network error. Check your network d

Starting to get really tired of this error message, it's completely random
and happens usually on long running queries, it is not a network failure
since the sql server is on the same machine.
Things I have tried:
o Updating MDAC
o Changing connection string
o Using only TCP/IP
o Using only pipes
o Removing shared memory option
The only articles on MS site I can find talks about doing backups or
running some built in sp which is not what I'm doing.
One of the articles refer to MDAC 2.8 SP1 which does not exist !
Doing some googling reveals that this is not an uncommon problem
but so far no solutions.
This is starting to have serious side effects and needs to be solved,
please help with any ideas !
Thanks.
PL.Talke a look at the following BLOG. This helped fix my "General Network
Errors"...
'The infamous General Network Error' (http://tinyurl.com/4yc7k)
'SQL Data Provider Patch' (http://support.microsoft.com/?kbid=328476)
cbuzzetta
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message389824.html|||cbuzzetta wrote:
> *Talke a look at the following BLOG. This helped fix my "General
> Network Errors"...
> 'The infamous General Network Error' (http://tinyurl.com/4yc7k)
> 'SQL Data Provider Patch' (http://support.microsoft.com/?kbid=328476)
> *
Just FYI I was getting this error on archived tables that no longer had
indexes - added indexes for them on the key fields and the error
disappeared. May not be relevant but it was the fix for me : )
X
DocFKNx
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message389824.html