Monday, March 19, 2012
[SQL Server 2000 Driver for JDBC]Must declare the variable '@P7where'
2) When I try to update the database in my DAO by using:
ps.executeUpdate();
3) Server throws the exception:
java.sql.SQLException: [Microsoft][SQL Server 2000 Driver for
JDBC][SQL Server]Must declare the variable '@.P7where'.
Anything is wrong with the MS JDBC driver with IBM WSAD? shall I set
something somewhere?
Experts, please help!
Show the JDBC code that creates the statement, sets the parameters, and calls the execute().
nauna wrote:
> 1) I'm using MS Sql Server 2000 JDBC driver at WSAD5.1.1.
> 2) When I try to update the database in my DAO by using:
> ps.executeUpdate();
> 3) Server throws the exception:
> java.sql.SQLException: [Microsoft][SQL Server 2000 Driver for
> JDBC][SQL Server]Must declare the variable '@.P7where'.
> Anything is wrong with the MS JDBC driver with IBM WSAD? shall I set
> something somewhere?
> Experts, please help!
Thursday, March 8, 2012
[ODBC SQL Server Driver] Timeout Expired - How to fix
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
Tuesday, March 6, 2012
[Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is either invalid or not
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][SQLServer 2000 Driver for JDBC]Row update failed
failed" while updating an int value on result set. Below is the code snippet
that i use in java. The error is occurring occasionally. Not able to
replicate.
strSQL = "SELECT intCol FROM Table1 WHERE intCol = 1";
PreparedStatement objPS = null;
...get the connection object, prepare object...using msjdbc driver with SQL
server 2000
ResultSet objRS = objPS.executeQuery();
objRS.updateInt("intCol", 2);
objRS.updateRow();
any help is appreciated.
Thanks in advance.
| Thread-Topic: [Microsoft][SQLServer 2000 Driver for JDBC]Row update failed
| thread-index: AcUbT0uzY+NiEZNfSCeDqAYi6cibWQ==
| X-WBNR-Posting-Host: 152.160.15.58
| From: "=?Utf-8?B?U2FyYW4=?=" <Saran@.discussions.microsoft.com>
| Subject: [Microsoft][SQLServer 2000 Driver for JDBC]Row update failed
| Date: Fri, 25 Feb 2005 07:33:03 -0800
| Lines: 15
| Message-ID: <05BEC007-4670-4D11-9C3F-E46F19A60BDC@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: TK2MSFTNGXA02.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFT NGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.jdbcdriver:6702
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I am getting an error "[Microsoft][SQLServer 2000 Driver for JDBC]Row
update
| failed" while updating an int value on result set. Below is the code
snippet
| that i use in java. The error is occurring occasionally. Not able to
| replicate.
|
| strSQL = "SELECT intCol FROM Table1 WHERE intCol = 1";
| PreparedStatement objPS = null;
| ...get the connection object, prepare object...using msjdbc driver with
SQL
| server 2000
| ResultSet objRS = objPS.executeQuery();
| objRS.updateInt("intCol", 2);
| objRS.updateRow();
|
| any help is appreciated.
| Thanks in advance.
|
What is the frequency of this problem? Did the problem occur while other
activity the same database was occurring? Do you have a primary key
defined on the table? Which options did you use when preparing the
statement? Are you using the most recent build of the JDBC driver?
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.
|||Hi Carb, thanks for your reply, here is my answers for your questions. Hope
that will help us to resolve the issue.
1. What is the frequency of this problem? - not able to determine,
occurring occasinoaly.
2. Did the problem occur while other activity the same database was
occurring? - I couldn't make sure it 100% though, i am possitive that there
could be some other activity on the database.
3. Do you have a primary key defined on the table? - Yes e.g. table script
tbl1(col1 varchar(100) NOT NULL, col2 int NULL)
here: col1 is primary key - but i am trying to update col2
4. Which options did you use when preparing the statement? - here is e.g.
objCon.prepareStatement(strSQL, ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY)
5. Are you using the most recent build of the JDBC driver? MS-JDBC SP2
thanks
-Saran
""Carb Simien [MSFT]"" wrote:
> --
> | Thread-Topic: [Microsoft][SQLServer 2000 Driver for JDBC]Row update failed
> | thread-index: AcUbT0uzY+NiEZNfSCeDqAYi6cibWQ==
> | X-WBNR-Posting-Host: 152.160.15.58
> | From: "=?Utf-8?B?U2FyYW4=?=" <Saran@.discussions.microsoft.com>
> | Subject: [Microsoft][SQLServer 2000 Driver for JDBC]Row update failed
> | Date: Fri, 25 Feb 2005 07:33:03 -0800
> | Lines: 15
> | Message-ID: <05BEC007-4670-4D11-9C3F-E46F19A60BDC@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.jdbcdriver
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> | Path: TK2MSFTNGXA02.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFT NGXA03.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.jdbcdriver:6702
> | X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
> |
> | I am getting an error "[Microsoft][SQLServer 2000 Driver for JDBC]Row
> update
> | failed" while updating an int value on result set. Below is the code
> snippet
> | that i use in java. The error is occurring occasionally. Not able to
> | replicate.
> |
> | strSQL = "SELECT intCol FROM Table1 WHERE intCol = 1";
> | PreparedStatement objPS = null;
> | ...get the connection object, prepare object...using msjdbc driver with
> SQL
> | server 2000
> | ResultSet objRS = objPS.executeQuery();
> | objRS.updateInt("intCol", 2);
> | objRS.updateRow();
> |
> | any help is appreciated.
> | Thanks in advance.
> |
> What is the frequency of this problem? Did the problem occur while other
> activity the same database was occurring? Do you have a primary key
> defined on the table? Which options did you use when preparing the
> statement? Are you using the most recent build of the JDBC driver?
> 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.
>
|||saran wrote:
> 4. Which options did you use when preparing the statement? - here is
e.g.
> objCon.prepareStatement(strSQL, ResultSet.TYPE_SCROLL_INSENSITIVE,
> ResultSet.CONCUR_READ_ONLY)
And if the ResultSet was created as read only how do you expect
updateRow() to work? Speaking of which, if the error message would have
been "General error" or simply "Error", it would have been just as easy
to track down the cause.
Alin,
The jTDS Project.
|||| Thread-Topic: [Microsoft][SQLServer 2000 Driver for JDBC]Row update failed
| thread-index: AcUpfTtxzBvD5vNlRPaQXIKezzsWHg==
| X-WBNR-Posting-Host: 152.160.15.58
| From: "=?Utf-8?B?c2FyYW4=?=" <saran@.discussions.microsoft.com>
| References: <05BEC007-4670-4D11-9C3F-E46F19A60BDC@.microsoft.com>
<zQR4wCMKFHA.1136@.TK2MSFTNGXA02.phx.gbl>
| Subject: RE: [Microsoft][SQLServer 2000 Driver for JDBC]Row update failed
| Date: Tue, 15 Mar 2005 08:37:09 -0800
| Lines: 86
| Message-ID: <4F9F2476-D4EE-4EA1-8288-B9C2EB8D5A30@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSF TNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.jdbcdriver:6756
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| Hi Carb, thanks for your reply, here is my answers for your questions.
Hope
| that will help us to resolve the issue.
|
| 1. What is the frequency of this problem? - not able to determine,
| occurring occasinoaly.
|
| 2. Did the problem occur while other activity the same database was
| occurring? - I couldn't make sure it 100% though, i am possitive that
there
| could be some other activity on the database.
|
| 3. Do you have a primary key defined on the table? - Yes e.g. table script
| tbl1(col1 varchar(100) NOT NULL, col2 int NULL)
| here: col1 is primary key - but i am trying to update col2
|
| 4. Which options did you use when preparing the statement? - here is e.g.
| objCon.prepareStatement(strSQL, ResultSet.TYPE_SCROLL_INSENSITIVE,
| ResultSet.CONCUR_READ_ONLY)
|
| 5. Are you using the most recent build of the JDBC driver? MS-JDBC SP2
|
| thanks
| -Saran
|
| ""Carb Simien [MSFT]"" wrote:
|
| >
| > --
| > | Thread-Topic: [Microsoft][SQLServer 2000 Driver for JDBC]Row update
failed
| > | thread-index: AcUbT0uzY+NiEZNfSCeDqAYi6cibWQ==
| > | X-WBNR-Posting-Host: 152.160.15.58
| > | From: "=?Utf-8?B?U2FyYW4=?=" <Saran@.discussions.microsoft.com>
| > | Subject: [Microsoft][SQLServer 2000 Driver for JDBC]Row update failed
| > | Date: Fri, 25 Feb 2005 07:33:03 -0800
| > | Lines: 15
| > | Message-ID: <05BEC007-4670-4D11-9C3F-E46F19A60BDC@.microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.sqlserver.jdbcdriver
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| > | Path: TK2MSFTNGXA02.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFT NGXA03.phx.gbl
| > | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.jdbcdriver:6702
| > | X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
| > |
| > | I am getting an error "[Microsoft][SQLServer 2000 Driver for JDBC]Row
| > update
| > | failed" while updating an int value on result set. Below is the code
| > snippet
| > | that i use in java. The error is occurring occasionally. Not able to
| > | replicate.
| > |
| > | strSQL = "SELECT intCol FROM Table1 WHERE intCol = 1";
| > | PreparedStatement objPS = null;
| > | ...get the connection object, prepare object...using msjdbc driver
with
| > SQL
| > | server 2000
| > | ResultSet objRS = objPS.executeQuery();
| > | objRS.updateInt("intCol", 2);
| > | objRS.updateRow();
| > |
| > | any help is appreciated.
| > | Thanks in advance.
| > |
| >
| > What is the frequency of this problem? Did the problem occur while
other
| > activity the same database was occurring? Do you have a primary key
| > defined on the table? Which options did you use when preparing the
| > statement? Are you using the most recent build of the JDBC driver?
| >
| > 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.
| >
| >
|
Yes, you will need to use Resultset.CONCUR_UPDATABLE to allow the updates..
Also, the most recent build of the Microsoft JDBC driver is JDBC SP3
(build 2.2.0040):
SQL Server 2000 Driver for JDBC Service Pack 3
http://www.microsoft.com/downloads/d...B11-0502-461A-
B138-2AA54BFDC03A&displaylang=en
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][SQLServer 2000 Driver for JDBC]net dll not initi
MSDE, and some of our users are getting the following SQLException
when attempting to query the database. The exception occurs
sporadically, and it only seems to happen after the application is
used for an extended duraton of time. Also, once the exception
occurs, it seems like the only way to obtain a good connection again
is to restart the JVM. Successive calls to get a connection from the
drivermanager fail otherwise.
Our calling application uses JNI to call a java function which is
responsible for creating the database connection and querying the
database.
Any help would be appreciated!
Here's the exception:
[Microsoft][SQLServer 2000 Driver for JDBC]net dll not initialized
(WSAStartup): socket write error
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]net
dll not initialized (WSAStartup): socket write error
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.sub mitRequest(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest. openCursor(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.execute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.executeQuery Internal(Unknown
Source)
at com.microsoft.jdbc.base.BasePreparedStatement.exec uteQuery(Unknown
Source)
Hello,
WSAStartup is a Windows API that is called (typically once) during an
application's startup to start using Winsock calls. Since you have been
using sockets up until the failure, it had to be called prior to that. It
looks like somehow the Winsock got uninitialized or unloaded but the JVM is
unaware of that.
Can you try opening a socket directly when this happens to confirm? You
could try something like:
java.net.Socket conn = new java.net.Socket("localhost", 1433);
and if you get the same failure, I would say this is an issue in the JVM.
Thanks,
Kamil
Kamil Sykora
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/securXity.
| NNTP-Posting-Date: Wed, 13 Jul 2005 00:58:48 -0500
| Subject: [Microsoft][SQLServer 2000 Driver for JDBC]net dll not initi
| From: akraai@.hotmail-dot-com.no-spam.invalid (akraai)
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| Mime-Version: 1.0
| Content-Type: text/plain; charset=ISO-8859-15
| Content-Transfer-Encoding: 8bit
| User-Agent: newsSync (SQL Server) 112669
| Message-ID: <foWdneohifEFMEnfRVn_vg@.giganews.com>
| Date: Wed, 13 Jul 2005 00:58:48 -0500
|
| We are currently in the middle of piloting a new application using
MSDE, and some of our users are getting the following SQLException
when attempting to query the database. The exception occurs
sporadically, and it only seems to happen after the application is
used for an extended duraton of time. Also, once the exception
occurs, it seems like the only way to obtain a good connection again
is to restart the JVM. Successive calls to get a connection from the
drivermanager fail otherwise.
Our calling application uses JNI to call a java function which is
responsible for creating the database connection and querying the
database.
Any help would be appreciated!
Here's the exception:
[Microsoft][SQLServer 2000 Driver for JDBC]net dll not initialized
(WSAStartup): socket write error
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]net
dll not initialized (WSAStartup): socket write error
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.sub mitRequest(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest. openCursor(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.execute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.executeQuery Internal(Unknown
Source)
at com.microsoft.jdbc.base.BasePreparedStatement.exec uteQuery(Unknown
Source)
|
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
database
SQL Server 2000 with JDBC driver.
when i have Windows Xp Pro with service Pack 1
i don't have a problem
all works
now with Windows Xp Pro and service Pack 2 i have this problem
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
See com.borland.dx.dataset.DataSetException error code: BASE+66
com.borland.dx.dataset.DataSetException: [Microsoft][SQLServer 2000 Driver
for JDBC]Error establishing socket.
at com.borland.dx.dataset.DataSetException.a(Unknown Source)
at com.borland.dx.dataset.DataSetException.throwExcep tion(Unknown Source)
at com.borland.dx.dataset.DataSetException.SQLExcepti on(Unknown Source)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
Chained exception:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error
establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<in it>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnecti on.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplC onnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknow n Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:517)
at java.sql.DriverManager.getConnection(DriverManager .java:177)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
ava.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error
establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<in it>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnecti on.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplC onnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknow n Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:517)
at java.sql.DriverManager.getConnection(DriverManager .java:177)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
Thanks very much!
Take a look at the firewall configuration. XP SP2 comes with a firewall
that blocks all ports by default.
Alin,
The jTDS Project.
|||thanks .
the firewall want's one exeption for sql server
[Microsoft][ODBC Text Driver] In the file specification '...', the Col1 option is invalid.
I'm trying to connect to a tab-delimited text file using the ODBC data access. I set it up using Administrative Tools - Data Sources (ODBC) from the start menu, and clicked the 'Guess' button under Define Format.
The schema it created looks like this:
[cims_output_data.txt]
ColNameHeader=True
Format=TabDelimited
MaxScanRows=0
CharacterSet=OEM
Col1=SIMNAME
Col2=TIMESTAMP
Col3=SIMTYPE
Col4=REGION
Col5=SECTOR
....etc.
It looks OK, but if I go back to Define in Administrative Tools and try to review it, I get a similar error message:
Ini File (or Registry) C:\Program Files\CIMS\schema.ini is corrupt.
Section: cims_output_data.txt, Key: Col1.
Has anyone seen this before? There is nothing on MSDN as far as I could find. I read on another forum that if you replace the label 'Col1' with 'Col' the problem is solved but it still reports that the schema is corrupt when I try to open it in Administrative Tools.
Bill.
Hi Bill,
Could you try specifying the types of your columns in the schema (i.e. Col1=SIMNAME string...)?
I hope this helps,
John Gordon (MSFT)
|||John
thanks, I tried that. The funny thing is switching the "Col1" label to "Col" really does solve the problem so I am just going with this solution and ignoring the fact that the ODBC configuration editor says the schema is corrupt.
Bill.
[Microsoft][ODBC Text Driver] In the file specification '...', the Col1 option is invalid.
I'm trying to connect to a tab-delimited text file using the ODBC data access. I set it up using Administrative Tools - Data Sources (ODBC) from the start menu, and clicked the 'Guess' button under Define Format.
The schema it created looks like this:
[cims_output_data.txt]
ColNameHeader=True
Format=TabDelimited
MaxScanRows=0
CharacterSet=OEM
Col1=SIMNAME
Col2=TIMESTAMP
Col3=SIMTYPE
Col4=REGION
Col5=SECTOR
....etc.
It looks OK, but if I go back to Define in Administrative Tools and try to review it, I get a similar error message:
Ini File (or Registry) C:\Program Files\CIMS\schema.ini is corrupt.
Section: cims_output_data.txt, Key: Col1.
Has anyone seen this before? There is nothing on MSDN as far as I could find. I read on another forum that if you replace the label 'Col1' with 'Col' the problem is solved but it still reports that the schema is corrupt when I try to open it in Administrative Tools.
Bill.
Hi Bill,
Could you try specifying the types of your columns in the schema (i.e. Col1=SIMNAME string...)?
I hope this helps,
John Gordon (MSFT)
|||John
thanks, I tried that. The funny thing is switching the "Col1" label to "Col" really does solve the problem so I am just going with this solution and ignoring the fact that the ODBC configuration editor says the schema is corrupt.
Bill.
[Microsoft][ODBC Text Driver] error
I am trying to import test file into a SQL Server 2000 database. If I
run the dts package manually I do not receive any errors. However when
I try and attempt to run the same package with dtsrun I receive the
following error.
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled
correctly and that you are connected to the server on which the file
resides
The path of the file is set correctly in the ODBC connection. Any
insight or assistance would be imprecated.
ThanksOn Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> Hello,
> I am trying to import test file into a SQL Server 2000 database. If I
> run the dts package manually I do not receive any errors. However when
> I try and attempt to run the same package with dtsrun I receive the
> following error.
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled
> correctly and that you are connected to the server on which the file
> resides
> The path of the file is set correctly in the ODBC connection. Any
> insight or assistance would be imprecated.
> Thanks
Hi
Are you running DTSRun from a command prompt?
Why are you using a DSN?
Have you tried creating the package using the Import Wizard?
John|||On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
> > Hello,
> > I am trying to import test file into a SQL Server 2000 database. If I
> > run the dts package manually I do not receive any errors. However when
> > I try and attempt to run the same package with dtsrun I receive the
> > following error.
> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > valid path. Make sure that the path name is spelled
> > correctly and that you are connected to the server on which the file
> > resides
> > The path of the file is set correctly in the ODBC connection. Any
> > insight or assistance would be imprecated.
> > Thanks
> Hi
> Are you running DTSRun from a command prompt?
> Why are you using a DSN?
> Have you tried creating the package using the Import Wizard?
> John
I am trying to run the schedule the package from using .xp_cmdshell
and DTSRun , The package will run if execute it from Enterprise Manager|||On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > Hello,
> > > I am trying to import test file into a SQL Server 2000 database. If I
> > > run the dts package manually I do not receive any errors. However when
> > > I try and attempt to run the same package with dtsrun I receive the
> > > following error.
> > > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > valid path. Make sure that the path name is spelled
> > > correctly and that you are connected to the server on which the file
> > > resides
> > > The path of the file is set correctly in the ODBC connection. Any
> > > insight or assistance would be imprecated.
> > > Thanks
> > Hi
> > Are you running DTSRun from a command prompt?
> > Why are you using a DSN?
> > Have you tried creating the package using the Import Wizard?
> > John
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> - Show quoted text -
Hi
If you manually run the command from a command prompt does it work?
If xp_cmdshell is running from a job, then make sure service accounts
have access to the directory/file.
John|||On Jun 11, 1:30 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
> > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > > Hello,
> > > > I am trying to import test file into a SQL Server 2000 database. If I
> > > > run the dts package manually I do not receive any errors. However when
> > > > I try and attempt to run the same package with dtsrun I receive the
> > > > following error.
> > > > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > > valid path. Make sure that the path name is spelled
> > > > correctly and that you are connected to the server on which the file
> > > > resides
> > > > The path of the file is set correctly in the ODBC connection. Any
> > > > insight or assistance would be imprecated.
> > > > Thanks
> > > Hi
> > > Are you running DTSRun from a command prompt?
> > > Why are you using a DSN?
> > > Have you tried creating the package using the Import Wizard?
> > > John
> > I am trying to run the schedule the package from using .xp_cmdshell
> > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> > - Show quoted text -
> Hi
> If you manually run the command from a command prompt does it work?
> If xp_cmdshell is running from a job, then make sure service accounts
> have access to the directory/file.
> John
Thanks, If I manually run the command from the command prompt it does
work, however if I try and run using xp_cmdshell I receive the error.
Both SQLAgent and MSSQL services have access to the directory/file|||When you are running it from EM, the package will use your logon to
determine the right and security to access a file but this will not be the
case when running it from a service (xp_cmdshell, DTS_Run or any other
service like SQL-Agent).
Also, if you are not using a UNC pathway but a drive letter (such as C:\);
many of these drive letters will be unknown to system accounts and other
accounts other than your own login. If you have used a driver letter, you
should replace with its full UNC name.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
<mtatlow@.gmail.com> wrote in message
news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>>
>> > Hello,
>> > I am trying to import test file into a SQL Server 2000 database. If I
>> > run the dts package manually I do not receive any errors. However when
>> > I try and attempt to run the same package with dtsrun I receive the
>> > following error.
>> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
>> > valid path. Make sure that the path name is spelled
>> > correctly and that you are connected to the server on which the file
>> > resides
>> > The path of the file is set correctly in the ODBC connection. Any
>> > insight or assistance would be imprecated.
>> > Thanks
>> Hi
>> Are you running DTSRun from a command prompt?
>> Why are you using a DSN?
>> Have you tried creating the package using the Import Wizard?
>> John
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager
>|||On Jun 11, 9:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:30 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > > On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > > > Hello,
> > > > > I am trying to import test file into a SQL Server 2000 database. If I
> > > > > run the dts package manually I do not receive any errors. However when
> > > > > I try and attempt to run the same package with dtsrun I receive the
> > > > > following error.
> > > > > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > > > valid path. Make sure that the path name is spelled
> > > > > correctly and that you are connected to the server on which the file
> > > > > resides
> > > > > The path of the file is set correctly in the ODBC connection. Any
> > > > > insight or assistance would be imprecated.
> > > > > Thanks
> > > > Hi
> > > > Are you running DTSRun from a command prompt?
> > > > Why are you using a DSN?
> > > > Have you tried creating the package using the Import Wizard?
> > > > John
> > > I am trying to run the schedule the package from using .xp_cmdshell
> > > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> > > - Show quoted text -
> > Hi
> > If you manually run the command from a command prompt does it work?
> > If xp_cmdshell is running from a job, then make sure service accounts
> > have access to the directory/file.
> > John
> Thanks, If I manually run the command from the command prompt it does
> work, however if I try and run using xp_cmdshell I receive the error.
> Both SQLAgent and MSSQL services have access to the directory/file- Hide quoted text -
> - Show quoted text -
Hi
You don't say what the service accounts are. The LOCALSYSTEM will not
have access to network resources, so it would have to be a domain
account. Try logging in as this account and run the package from the
command prompt.
John|||I am using a domain account that has access to the file. I am using
the [ODBC Text Driver] which does not allow you to use a UNC in the
pathway.
On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
blanks, no spam please)> wrote:
> When you are running it from EM, the package will use your logon to
> determine the right and security to access a file but this will not be the
> case when running it from a service (xp_cmdshell, DTS_Run or any other
> service like SQL-Agent).
> Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> many of these drive letters will be unknown to system accounts and other
> accounts other than your own login. If you have used a driver letter, you
> should replace with its full UNC name.
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
> <mtat...@.gmail.com> wrote in message
> news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> >> > Hello,
> >> > I am trying to import test file into a SQL Server 2000 database. If I
> >> > run the dts package manually I do not receive any errors. However when
> >> > I try and attempt to run the same package with dtsrun I receive the
> >> > following error.
> >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> >> > valid path. Make sure that the path name is spelled
> >> > correctly and that you are connected to the server on which the file
> >> > resides
> >> > The path of the file is set correctly in the ODBC connection. Any
> >> > insight or assistance would be imprecated.
> >> > Thanks
> >> Hi
> >> Are you running DTSRun from a command prompt?
> >> Why are you using a DSN?
> >> Have you tried creating the package using the Import Wizard?
> >> John
> > I am trying to run the schedule the package from using .xp_cmdshell
> > and DTSRun , The package will run if execute it from Enterprise Manager|||On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> I am using a domain account that has access to the file. I am using
> the [ODBC Text Driver] which does not allow you to use a UNC in the
> pathway.
> On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> blanks, no spam please)> wrote:
>
> > When you are running it from EM, the package will use your logon to
> > determine the right and security to access a file but this will not be the
> > case when running it from a service (xp_cmdshell, DTS_Run or any other
> > service like SQL-Agent).
> > Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> > many of these drive letters will be unknown to system accounts and other
> > accounts other than your own login. If you have used a driver letter, you
> > should replace with its full UNC name.
> > --
> > Sylvain Lafontaine, ing.
> > MVP - Technologies Virtual-PC
> > E-mail: sylvain aei ca (fill the blanks, no spam please)
> > <mtat...@.gmail.com> wrote in message
> >news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > >> > Hello,
> > >> > I am trying to import test file into a SQL Server 2000 database. If I
> > >> > run the dts package manually I do not receive any errors. However when
> > >> > I try and attempt to run the same package with dtsrun I receive the
> > >> > following error.
> > >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > >> > valid path. Make sure that the path name is spelled
> > >> > correctly and that you are connected to the server on which the file
> > >> > resides
> > >> > The path of the file is set correctly in the ODBC connection. Any
> > >> > insight or assistance would be imprecated.
> > >> > Thanks
> > >> Hi
> > >> Are you running DTSRun from a command prompt?
> > >> Why are you using a DSN?
> > >> Have you tried creating the package using the Import Wizard?
> > >> John
> > > I am trying to run the schedule the package from using .xp_cmdshell
> > > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> - Show quoted text -
Hi
So logging in as this account, you can run the job/package
sucessfully? Have you used the /L command to log output to a file?
John|||On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
> > I am using a domain account that has access to the file. I am using
> > the [ODBC Text Driver] which does not allow you to use a UNC in the
> > pathway.
> > On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> > blanks, no spam please)> wrote:
> > > When you are running it from EM, the package will use your logon to
> > > determine the right and security to access a file but this will not be the
> > > case when running it from a service (xp_cmdshell, DTS_Run or any other
> > > service like SQL-Agent).
> > > Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> > > many of these drive letters will be unknown to system accounts and other
> > > accounts other than your own login. If you have used a driver letter, you
> > > should replace with its full UNC name.
> > > --
> > > Sylvain Lafontaine, ing.
> > > MVP - Technologies Virtual-PC
> > > E-mail: sylvain aei ca (fill the blanks, no spam please)
> > > <mtat...@.gmail.com> wrote in message
> > >news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > >> > Hello,
> > > >> > I am trying to import test file into a SQL Server 2000 database. If I
> > > >> > run the dts package manually I do not receive any errors. However when
> > > >> > I try and attempt to run the same package with dtsrun I receive the
> > > >> > following error.
> > > >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > >> > valid path. Make sure that the path name is spelled
> > > >> > correctly and that you are connected to the server on which the file
> > > >> > resides
> > > >> > The path of the file is set correctly in the ODBC connection. Any
> > > >> > insight or assistance would be imprecated.
> > > >> > Thanks
> > > >> Hi
> > > >> Are you running DTSRun from a command prompt?
> > > >> Why are you using a DSN?
> > > >> Have you tried creating the package using the Import Wizard?
> > > >> John
> > > > I am trying to run the schedule the package from using .xp_cmdshell
> > > > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> > - Show quoted text -
> Hi
> So logging in as this account, you can run the job/package
> sucessfully? Have you used the /L command to log output to a file?
> John
This is the output that I get when I use xp_cmdshell
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSDataPumpTask_1
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259
(80004005)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
Error Detail Records:
Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
DTSRun: Package execution complete.
NULL
this is the output when I run from the cmd prompt
The execution of the following DTS Package succeeded:
Package Name: test
Package Description: (null)
Package ID: {28220C92-CA63-4664-B356-2155FC002749}
Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
Executed On: SERVERNAME
Executed By: username
Execution Started: 6/12/2007 9:31:01 AM
Execution Completed: 6/12/2007 9:31:01 AM
Total Execution Time: 0.64 seconds
Package Steps execution information:
Step 'DTSStep_DTSDataPumpTask_1' succeeded
Step Execution Started: 6/12/2007 9:31:01 AM
Step Execution Completed: 6/12/2007 9:31:01 AM
Total Step Execution Time: 0.593 seconds
Progress count in Step: 1672
****************************************************************************************************|||On Jun 12, 2:37 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > I am using a domain account that has access to the file. I am using
> > > the [ODBC Text Driver] which does not allow you to use a UNC in the
> > > pathway.
> > > On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> > > blanks, no spam please)> wrote:
> > > > When you are running it from EM, the package will use your logon to
> > > > determine the right and security to access a file but this will not= be the
> > > > case when running it from a service (xp_cmdshell, DTS_Run or any ot=her
> > > > service like SQL-Agent).
> > > > Also, if you are not using a UNC pathway but a drive letter (such a=s C:\);
> > > > many of these drive letters will be unknown to system accounts and =other
> > > > accounts other than your own login. If you have used a driver lett=er, you
> > > > should replace with its full UNC name.
> > > > --
> > > > Sylvain Lafontaine, ing.
> > > > MVP - Technologies Virtual-PC
> > > > E-mail: sylvain aei ca (fill the blanks, no spam please)
> > > > <mtat...@.gmail.com> wrote in message
> > > >news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > > > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > > >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrot=e:
> > > > >> > Hello,
> > > > >> > I am trying to import test file into a SQL Server 2000 databas=e=2E If I
> > > > >> > run the dts package manually I do not receive any errors. Howe=ver when
> > > > >> > I try and attempt to run the same package with dtsrun I receiv=e the
> > > > >> > following error.
> > > > >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is no=t a
> > > > >> > valid path. Make sure that the path name is spelled
> > > > >> > correctly and that you are connected to the server on which th=e file
> > > > >> > resides
> > > > >> > The path of the file is set correctly in the ODBC connection. =Any
> > > > >> > insight or assistance would be imprecated.
> > > > >> > Thanks
> > > > >> Hi
> > > > >> Are you running DTSRun from a command prompt?
> > > > >> Why are you using a DSN?
> > > > >> Have you tried creating the package using the Import Wizard?
> > > > >> John
> > > > > I am trying to run the schedule the package from using .xp_cmdsh=ell
> > > > > and DTSRun , The package will run if execute it from Enterprise M=anager- Hide quoted text -
> > > - Show quoted text -
> > Hi
> > So logging in as this account, you can run the job/package
> > sucessfully? Have you used the /L command to log output to a file?
> > John
> This is the output that I get when I use xp_cmdshell
> DTSRun: Loading...
> DTSRun: Executing...
> DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error =3D -2147467259
> (80004005)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> Error Detail Records:
> Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
> DTSRun: Package execution complete.
> NULL
> this is the output when I run from the cmd prompt
> The execution of the following DTS Package succeeded:
> Package Name: test
> Package Description: (null)
> Package ID: {28220C92-CA63-4664-B356-2155FC002749}
> Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
> Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
> Executed On: SERVERNAME
> Executed By: username
> Execution Started: 6/12/2007 9:31:01 AM
> Execution Completed: 6/12/2007 9:31:01 AM
> Total Execution Time: 0.64 seconds
> Package Steps execution information:
> Step 'DTSStep_DTSDataPumpTask_1' succeeded
> Step Execution Started: 6/12/2007 9:31:01 AM
> Step Execution Completed: 6/12/2007 9:31:01 AM
> Total Step Execution Time: 0.593 seconds
> Progress count in Step: 1672
> *************************************************************************=**=AD*************************- Hide quoted text -
> - Show quoted text -
Although you are not using ASP this article gives reasons for this
error number http://support.microsoft.com/kb/306518 especially
http://support.microsoft.com/kb/306269
John
[Microsoft][ODBC Text Driver] error
I am trying to import test file into a SQL Server 2000 database. If I
run the dts package manually I do not receive any errors. However when
I try and attempt to run the same package with dtsrun I receive the
following error.
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled
correctly and that you are connected to the server on which the file
resides
The path of the file is set correctly in the ODBC connection. Any
insight or assistance would be imprecated.
Thanks
On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> Hello,
> I am trying to import test file into a SQL Server 2000 database. If I
> run the dts package manually I do not receive any errors. However when
> I try and attempt to run the same package with dtsrun I receive the
> following error.
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled
> correctly and that you are connected to the server on which the file
> resides
> The path of the file is set correctly in the ODBC connection. Any
> insight or assistance would be imprecated.
> Thanks
Hi
Are you running DTSRun from a command prompt?
Why are you using a DSN?
Have you tried creating the package using the Import Wizard?
John
|||On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
>
>
>
> Hi
> Are you running DTSRun from a command prompt?
> Why are you using a DSN?
> Have you tried creating the package using the Import Wizard?
> John
I am trying to run the schedule the package from using .xp_cmdshell
and DTSRun , The package will run if execute it from Enterprise Manager
|||On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> - Show quoted text -
Hi
If you manually run the command from a command prompt does it work?
If xp_cmdshell is running from a job, then make sure service accounts
have access to the directory/file.
John
|||When you are running it from EM, the package will use your logon to
determine the right and security to access a file but this will not be the
case when running it from a service (xp_cmdshell, DTS_Run or any other
service like SQL-Agent).
Also, if you are not using a UNC pathway but a drive letter (such as C:\);
many of these drive letters will be unknown to system accounts and other
accounts other than your own login. If you have used a driver letter, you
should replace with its full UNC name.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
<mtatlow@.gmail.com> wrote in message
news:1181582401.465253.261890@.w5g2000hsg.googlegro ups.com...
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager
>
|||I am using a domain account that has access to the file. I am using
the [ODBC Text Driver] which does not allow you to use a UNC in the
pathway.
On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
blanks, no spam please)> wrote:[vbcol=seagreen]
> When you are running it from EM, the package will use your logon to
> determine the right and security to access a file but this will not be the
> case when running it from a service (xp_cmdshell, DTS_Run or any other
> service like SQL-Agent).
> Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> many of these drive letters will be unknown to system accounts and other
> accounts other than your own login. If you have used a driver letter, you
> should replace with its full UNC name.
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
> <mtat...@.gmail.com> wrote in message
> news:1181582401.465253.261890@.w5g2000hsg.googlegro ups.com...
>
>
>
>
>
>
|||On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> I am using a domain account that has access to the file. I am using
> the [ODBC Text Driver] which does not allow you to use a UNC in the
> pathway.
> On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> blanks, no spam please)> wrote:
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
Hi
So logging in as this account, you can run the job/package
sucessfully? Have you used the /L command to log output to a file?
John
|||On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
> Hi
> So logging in as this account, you can run the job/package
> sucessfully? Have you used the /L command to log output to a file?
> John
This is the output that I get when I use xp_cmdshell
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSDataPumpTask_1
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259
(80004005)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
Error Detail Records:
Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
DTSRun: Package execution complete.
NULL
this is the output when I run from the cmd prompt
The execution of the following DTS Package succeeded:
Package Name: test
Package Description: (null)
Package ID: {28220C92-CA63-4664-B356-2155FC002749}
Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
Executed On: SERVERNAME
Executed By: username
Execution Started: 6/12/2007 9:31:01 AM
Execution Completed: 6/12/2007 9:31:01 AM
Total Execution Time: 0.64 seconds
Package Steps execution information:
Step 'DTSStep_DTSDataPumpTask_1' succeeded
Step Execution Started: 6/12/2007 9:31:01 AM
Step Execution Completed: 6/12/2007 9:31:01 AM
Total Step Execution Time: 0.593 seconds
Progress count in Step: 1672
************************************************** **************************************************
|||On Jun 12, 2:37 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> This is the output that I get when I use xp_cmdshell
> DTSRun: Loading...
> DTSRun: Executing...
> DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259
> (80004005)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> Error Detail Records:
> Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
> DTSRun: Package execution complete.
> NULL
> this is the output when I run from the cmd prompt
> The execution of the following DTS Package succeeded:
> Package Name: test
> Package Description: (null)
> Package ID: {28220C92-CA63-4664-B356-2155FC002749}
> Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
> Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
> Executed On: SERVERNAME
> Executed By: username
> Execution Started: 6/12/2007 9:31:01 AM
> Execution Completed: 6/12/2007 9:31:01 AM
> Total Execution Time: 0.64 seconds
> Package Steps execution information:
> Step 'DTSStep_DTSDataPumpTask_1' succeeded
> Step Execution Started: 6/12/2007 9:31:01 AM
> Step Execution Completed: 6/12/2007 9:31:01 AM
> Total Step Execution Time: 0.593 seconds
> Progress count in Step: 1672
> ************************************************** *************************X************************ *- Hide quoted text -
> - Show quoted text -
Although you are not using ASP this article gives reasons for this
error number http://support.microsoft.com/kb/306518 especially
http://support.microsoft.com/kb/306269
John
Saturday, February 25, 2012
[Microsoft][ODBC SQL Server Driver] Timeout Expired
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
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.
What is the exact error number and message? There are several types of
timeouts. If you are not specifying the correct parameter, it will continue
to timeout on that type.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
I am getting this error when I try and look at the Top 1000 records of a
view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.
|||Unfortunately, there is no error number, and the error message is the subject
line of this post. Also, I am not specifying any parameters at all, as this
is happening in Enterrpise Manager, Views, right-click on view, Open View,
Return Top.
"AnthonyThomas" wrote:
> What is the exact error number and message? There are several types of
> timeouts. If you are not specifying the correct parameter, it will continue
> to timeout on that type.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> I am getting this error when I try and look at the Top 1000 records of a
> view
> that I have created, in Enterprise Manager. If I copy the SQL for the View
> into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> Enterprise Manager Properties Advanced window, I have set Query timeout to
> both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> suggestions would be greatly appreciated.
>
>
|||If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
value to 0 and you are still getting the message, then you are probably being
blocked by current processes and are getting a LOCK TIMEOUT (which is really
a Lock Wait timeout). You do not have the ability to modify the Lock Timout
setting through EM; however, you can through Query Analyzer.
The Properties, Advanced Window does not exist for SQLEM. There is a
Properties, Connections, Remote Connections area for the currently selected
database, but that property is a timeout setting for RPC queries, not SQLEM
DMO.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" wrote:
[vbcol=seagreen]
> Unfortunately, there is no error number, and the error message is the subject
> line of this post. Also, I am not specifying any parameters at all, as this
> is happening in Enterrpise Manager, Views, right-click on view, Open View,
> Return Top.
> "AnthonyThomas" wrote:
|||Thanks for all your assisstance Anthony. This has cleared things up for me
as far as SQLEM is concerned (ie: I won't use it to display views, I'll use
QA instead).
I had initially thought that if I could resolve the timeout issue in SQLEM,
then the same issues in getting data into MapPoint, Excel, etc. through an
ODBC connection could be resolved as well.
Now at least, I can focus my efforts on getting the View data into
MapPoint/Excel etc.
Thanks again Anthony.
Sincerely,
Gary W. Hinkel
"AnthonyThomas" wrote:
[vbcol=seagreen]
> If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
> value to 0 and you are still getting the message, then you are probably being
> blocked by current processes and are getting a LOCK TIMEOUT (which is really
> a Lock Wait timeout). You do not have the ability to modify the Lock Timout
> setting through EM; however, you can through Query Analyzer.
> The Properties, Advanced Window does not exist for SQLEM. There is a
> Properties, Connections, Remote Connections area for the currently selected
> database, but that property is a timeout setting for RPC queries, not SQLEM
> DMO.
> Sincerely,
>
> Anthony Thomas
>
> "Gary W. Hinkel" wrote:
[Microsoft][ODBC SQL Server Driver] Timeout Expired
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
w
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.What is the exact error number and message? There are several types of
timeouts. If you are not specifying the correct parameter, it will continue
to timeout on that type.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
I am getting this error when I try and look at the Top 1000 records of a
view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.|||Unfortunately, there is no error number, and the error message is the subjec
t
line of this post. Also, I am not specifying any parameters at all, as this
is happening in Enterrpise Manager, Views, right-click on view, Open View,
Return Top.
"AnthonyThomas" wrote:
> What is the exact error number and message? There are several types of
> timeouts. If you are not specifying the correct parameter, it will contin
ue
> to timeout on that type.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> I am getting this error when I try and look at the Top 1000 records of a
> view
> that I have created, in Enterprise Manager. If I copy the SQL for the Vie
w
> into Query Analyzer, it returns results fine (in approx. 2 minutes). In t
he
> Enterprise Manager Properties Advanced window, I have set Query timeout to
> both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> suggestions would be greatly appreciated.
>
>|||If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
value to 0 and you are still getting the message, then you are probably bein
g
blocked by current processes and are getting a LOCK TIMEOUT (which is really
a Lock Wait timeout). You do not have the ability to modify the Lock Timout
setting through EM; however, you can through Query Analyzer.
The Properties, Advanced Window does not exist for SQLEM. There is a
Properties, Connections, Remote Connections area for the currently selected
database, but that property is a timeout setting for RPC queries, not SQLEM
DMO.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" wrote:
[vbcol=seagreen]
> Unfortunately, there is no error number, and the error message is the subj
ect
> line of this post. Also, I am not specifying any parameters at all, as th
is
> is happening in Enterrpise Manager, Views, right-click on view, Open View,
> Return Top.
> "AnthonyThomas" wrote:
>|||Thanks for all your assisstance Anthony. This has cleared things up for me
as far as SQLEM is concerned (ie: I won't use it to display views, I'll use
QA instead).
I had initially thought that if I could resolve the timeout issue in SQLEM,
then the same issues in getting data into MapPoint, Excel, etc. through an
ODBC connection could be resolved as well.
Now at least, I can focus my efforts on getting the View data into
MapPoint/Excel etc.
Thanks again Anthony.
Sincerely,
Gary W. Hinkel
"AnthonyThomas" wrote:
[vbcol=seagreen]
> If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
> value to 0 and you are still getting the message, then you are probably be
ing
> blocked by current processes and are getting a LOCK TIMEOUT (which is real
ly
> a Lock Wait timeout). You do not have the ability to modify the Lock Timo
ut
> setting through EM; however, you can through Query Analyzer.
> The Properties, Advanced Window does not exist for SQLEM. There is a
> Properties, Connections, Remote Connections area for the currently selecte
d
> database, but that property is a timeout setting for RPC queries, not SQLE
M
> DMO.
> Sincerely,
>
> Anthony Thomas
>
> "Gary W. Hinkel" wrote:
>
[Microsoft][ODBC SQL Server Driver] Timeout expired
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.What is the exact error number and message? There are several types of
timeouts. If you are not specifying the correct parameter, it will continue
to timeout on that type.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
I am getting this error when I try and look at the Top 1000 records of a
view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.|||Unfortunately, there is no error number, and the error message is the subject
line of this post. Also, I am not specifying any parameters at all, as this
is happening in Enterrpise Manager, Views, right-click on view, Open View,
Return Top.
"AnthonyThomas" wrote:
> What is the exact error number and message? There are several types of
> timeouts. If you are not specifying the correct parameter, it will continue
> to timeout on that type.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> I am getting this error when I try and look at the Top 1000 records of a
> view
> that I have created, in Enterprise Manager. If I copy the SQL for the View
> into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> Enterprise Manager Properties Advanced window, I have set Query timeout to
> both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> suggestions would be greatly appreciated.
>
>|||If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
value to 0 and you are still getting the message, then you are probably being
blocked by current processes and are getting a LOCK TIMEOUT (which is really
a Lock Wait timeout). You do not have the ability to modify the Lock Timout
setting through EM; however, you can through Query Analyzer.
The Properties, Advanced Window does not exist for SQLEM. There is a
Properties, Connections, Remote Connections area for the currently selected
database, but that property is a timeout setting for RPC queries, not SQLEM
DMO.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" wrote:
> Unfortunately, there is no error number, and the error message is the subject
> line of this post. Also, I am not specifying any parameters at all, as this
> is happening in Enterrpise Manager, Views, right-click on view, Open View,
> Return Top.
> "AnthonyThomas" wrote:
> > What is the exact error number and message? There are several types of
> > timeouts. If you are not specifying the correct parameter, it will continue
> > to timeout on that type.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > --
> >
> > "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> > news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> > I am getting this error when I try and look at the Top 1000 records of a
> > view
> > that I have created, in Enterprise Manager. If I copy the SQL for the View
> > into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> > Enterprise Manager Properties Advanced window, I have set Query timeout to
> > both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> > suggestions would be greatly appreciated.
> >
> >
> >|||Thanks for all your assisstance Anthony. This has cleared things up for me
as far as SQLEM is concerned (ie: I won't use it to display views, I'll use
QA instead).
I had initially thought that if I could resolve the timeout issue in SQLEM,
then the same issues in getting data into MapPoint, Excel, etc. through an
ODBC connection could be resolved as well.
Now at least, I can focus my efforts on getting the View data into
MapPoint/Excel etc.
Thanks again Anthony.
Sincerely,
Gary W. Hinkel
"AnthonyThomas" wrote:
> If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
> value to 0 and you are still getting the message, then you are probably being
> blocked by current processes and are getting a LOCK TIMEOUT (which is really
> a Lock Wait timeout). You do not have the ability to modify the Lock Timout
> setting through EM; however, you can through Query Analyzer.
> The Properties, Advanced Window does not exist for SQLEM. There is a
> Properties, Connections, Remote Connections area for the currently selected
> database, but that property is a timeout setting for RPC queries, not SQLEM
> DMO.
> Sincerely,
>
> Anthony Thomas
>
> "Gary W. Hinkel" wrote:
> > Unfortunately, there is no error number, and the error message is the subject
> > line of this post. Also, I am not specifying any parameters at all, as this
> > is happening in Enterrpise Manager, Views, right-click on view, Open View,
> > Return Top.
> >
> > "AnthonyThomas" wrote:
> >
> > > What is the exact error number and message? There are several types of
> > > timeouts. If you are not specifying the correct parameter, it will continue
> > > to timeout on that type.
> > >
> > > Sincerely,
> > >
> > >
> > > Anthony Thomas
> > >
> > >
> > > --
> > >
> > > "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> > > news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> > > I am getting this error when I try and look at the Top 1000 records of a
> > > view
> > > that I have created, in Enterprise Manager. If I copy the SQL for the View
> > > into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> > > Enterprise Manager Properties Advanced window, I have set Query timeout to
> > > both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> > > suggestions would be greatly appreciated.
> > >
> > >
> > >
[Microsoft][ODBC SQL Server Driver] Timeout Expired
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 Driver] Invalid Descriptor Index
I am using MFC ODBC classes in my VC++ application for database accesss (on
a SQL Server/Access Database).
Some times after opening a Recordset (containing bound columns generated
using the ClassWizard) I have to use the
CRecordset::GetFieldValue( LPCTSTR lpszName, CDBVariant& varValue, short
nFieldType = DEFAULT_FIELD_TYPE )
method of the CRecordset object to obtain field values. The above method
works fine with ODBC drivers for Jet but when I use ODBC for SQL Server it
throws the following exception
State:S1002,Native:0,Origin:[Microsoft][
ODBC SQL Server Driver] Invalid
Descriptor Index
I don't understand why the Microsoft SQL Server ODBC Driver is throwing this
exception.
Please help me!
SameerHi Sameer,
Thanks for posting in the community.
From your description, I understand that when you use the CRecordset::GetFie
ldValue
method t oobtain the field values after opening a binding columns recordset,
you will
receive the exception of Invalid Descriptor Index for ODBC SQL Server Driver
. However, the
problem doesn't occur with ODBC drivers for Jet.
Before we start, please notice that the issue is related to MFC programming
which is
gracefully handling in this queue. However, it's my pleasure to let me see i
f I can address
your problem and give some solutions. For quickly and efficiently solve your
problem, it's
better to post this issue in the corresponding queues such as ADO/VC/VC++ ne
wsgroup.
I'm not 100% sure why the exception was genereted when using ODBC SQL Server
Drivers.
Based on my research, per the ODBC docs SQLGetData throws that error if it's
called and
all the columns are already bound when it is generated using the ClassWizard
.
So the bottom line is that if you're using a CRecordset that was created wit
h
the AppWizard, don't use GetFieldValue. Instead, go to the record that you
want and then look at the data member of the recordset to get the field valu
e.
Please apply my suggestions above and let me know if this helps resolve your
problem. If
there is anything more I can do to assist you, please feel free to post it i
n the group.
If the problem still persists and you'd like to get the most qualified pool
of respondents,
please repost this issue to the corresponding queues I mentioned above. Addi
tionally,
other partners who read the newsgroups regularly can either share their know
ledge or learn
from your interaction with us. I hope the problem can be resolved quickly.
Best regards,
Billy Yao
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
[Microsoft][ODBC SQL Server Driver] Invalid cursor stateevery time I save in enterprise ma
every time I save after a change in any table through enterprise nmanager
I receive this error:
[Microsoft][ODBC SQL Server Driver] Invalid cursor state
If I generate a script instead-of saving directly
and if I execute this script through the query analyzer all works fine!
My windows 2003 is english
my SQL Server is french
my default language is french
I've found the same error on another server which is in the same config.
any idea?
thanks.
Jerome.
> every time I save after a change in any table through enterprise nmanager
> I receive this error:
> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
So why not use scripts in Query Analyzer? IMHO, there are only a few cases
where Enterprise Manager should be used...
http://www.aspfaq.com/2515
http://www.aspfaq.com/2455
http://www.aspfaq.com/
(Reverse address to reply.)
|||enterprise manager is easy to use.
When I update or add a column, I can do this very quickly in enterprise
manager
using query analyzer is an overhead for me :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
> So why not use scripts in Query Analyzer? IMHO, there are only a few
> cases
> where Enterprise Manager should be used...
> http://www.aspfaq.com/2515
> http://www.aspfaq.com/2455
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
|||This is over your head?
ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
http://www.aspfaq.com/
(Reverse address to reply.)
"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> enterprise manager is easy to use.
> When I update or add a column, I can do this very quickly in enterprise
> manager
> using query analyzer is an overhead for me :-)
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
nmanager
>
|||yep
specially when you have a lot of columns to change/add/remove :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
> This is over your head?
> ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Jj" <willgart_A_@.hotmail_A_.com> wrote in message
> news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
> nmanager
>
|||> yep
> specially when you have a lot of columns to change/add/remove :-)
Okay, so is there something especially painful about learning them? It
certainly can't HURT you to have this knowledge; surely someday you will
have to connect to SQL Server without using a GUI as a crutch...
|||There are different combinations of service packs that lend
themselves to having this error more often - e.g between
8.00.0859 and 8.00.0875 you can get the error more often,
version 8.00.0927 or no SP3 version 8.00.0194 you don't,
etc.
The bottom line is what Aaron keeps telling you - you should
be using Query Analyzer for this type of thing. It was
designed more for this type of activity.
-Sue
On Mon, 15 Nov 2004 11:17:34 -0500, "Jj"
<willgart_A_@.hotmail_A_.com> wrote:
>yep
>specially when you have a lot of columns to change/add/remove :-)
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
>
|||I've the version 859
what is the 927 version? SP4? intermediate release?
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.4ax.com...
> There are different combinations of service packs that lend
> themselves to having this error more often - e.g between
> 8.00.0859 and 8.00.0875 you can get the error more often,
> version 8.00.0927 or no SP3 version 8.00.0194 you don't,
> etc.
> The bottom line is what Aaron keeps telling you - you should
> be using Query Analyzer for this type of thing. It was
> designed more for this type of activity.
> -Sue
> On Mon, 15 Nov 2004 11:17:34 -0500, "Jj"
> <willgart_A_@.hotmail_A_.com> wrote:
>
|||> what is the 927 version? SP4? intermediate release?
Hotfix. Only certain ones are available without contacting PSS directly.
http://www.aspfaq.com/2160
http://www.aspfaq.com/
(Reverse address to reply.)
|||Hot fix for the following:
http://support.microsoft.com/?kbid=839688
But then you will be managing hot fixes based upon not
wanting to use Query Analyzer for writing T-SQL to maintain
your databases. Doesn't seem like a good path to go down.
So if another slammer comes out, would your company want you
to patch it and use T-SQL for table changes or would they
want you to leave the box vulnerable so you could use
Enterprise Manager to make all your table changes?
-Sue
On Mon, 15 Nov 2004 13:40:43 -0500, "Jj"
<willgart_A_@.hotmail_A_.com> wrote:
>I've the version 859
>what is the 927 version? SP4? intermediate release?
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.4ax.com.. .
>