Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts

Thursday, March 22, 2012

\minint\system32\biosinfo.inf error code 263

I have an HP with Windows XP. I've been gone for a few days and when i came home i tried to start up my PC, but I got:

A disk read error occurred

press ctrl+alt+del to restart

when i do i tap the f10 for system restore, and get the message in the subject line.

When i tap that it send me back to the a disk read error....

I'm not computer literate, but could follow directions or turn it over to my son who is an IT guy.

help, Deuby

Hi,

First of all if you could refer BIOS setting , are you able to see the HDD ? Reset BIOS to default. Check for the Data Cable also.

Hemantgiri S. Goswami

|||

How is this related to SQL Server Security?

Will try to move to a different forum.

Laurentiu

|||

Try the following in order, one at a time - no multi tasking. This was taken from another Forum and has worked at different points on different machines with the same error.

Safest and easiest to try (in order of ease)
-:
*(1) Reset BIOS with "safe" defaults
(2) Yank BIOS battery for about 10 minutes
(3) Disable HD S.M.A.R.T. setting in BIOS
*(4) Disable bus mastering in BIOS
*(5) Disable Ultra DMA (UDMA) moder in BIOS (or at least change the UDMA mode)
(6) Set correct memory settings in BIOS
(7) Test memory to see if it is faulty (MemTest86 from memtest.org is free)
(8) Set HD jumper(s) to Master rather than Cable Select (or even Master w/Slave Present)
(9) Replace HD cable
*(10) Update BIOS
(11) Use FIXBOOT utility on Win XP recovery
*(12) Use chkdsk /r /p
(13) Virus scan (good luck, because that probably isn't the problem)

Medium difficulty and some danger of Data Loss

*(14) Defragment (requires use of second computer or boot to defrag program on CD)
*(15) Use Partition Table Doctor from the Ultimate Boot CD (search on Google)
(16) Use FIXMBR utility on Win XP recovery (DO NOT use if utility indicates non-standard partition if you want to preserve your data!)
(17) Change drive ID from 1 to 0 (if it is 1) or vice versa (personally I don't think this is a good idea); if problem with drive ID, reset ID by powering system on while HD cable is plugged but power unplugged
(18) Resize NTFS Clusters to 4K using partition manager
*(19) Change NTFS to FAT32 using partition manager (and optionally change back to NTFS--although this may cause the problem to recur)

Time-consuming and may not work; definite data loss:

(20) Resize partition below 137 Gb
(21) Perform low-level format on HD (using manufacturer's tools)

Good Luck.

\minint\system32\biosinfo.inf error code 263

I have an HP with Windows XP. I've been gone for a few days and when i came home i tried to start up my PC, but I got:

A disk read error occurred

press ctrl+alt+del to restart

when i do i tap the f10 for system restore, and get the message in the subject line.

When i tap that it send me back to the a disk read error....

I'm not computer literate, but could follow directions or turn it over to my son who is an IT guy.

help, Deuby

Hi,

First of all if you could refer BIOS setting , are you able to see the HDD ? Reset BIOS to default. Check for the Data Cable also.

Hemantgiri S. Goswami

|||

How is this related to SQL Server Security?

Will try to move to a different forum.

Laurentiu

|||

Try the following in order, one at a time - no multi tasking. This was taken from another Forum and has worked at different points on different machines with the same error.

Safest and easiest to try (in order of ease)
-:
*(1) Reset BIOS with "safe" defaults
(2) Yank BIOS battery for about 10 minutes
(3) Disable HD S.M.A.R.T. setting in BIOS
*(4) Disable bus mastering in BIOS
*(5) Disable Ultra DMA (UDMA) moder in BIOS (or at least change the UDMA mode)
(6) Set correct memory settings in BIOS
(7) Test memory to see if it is faulty (MemTest86 from memtest.org is free)
(8) Set HD jumper(s) to Master rather than Cable Select (or even Master w/Slave Present)
(9) Replace HD cable
*(10) Update BIOS
(11) Use FIXBOOT utility on Win XP recovery
*(12) Use chkdsk /r /p
(13) Virus scan (good luck, because that probably isn't the problem)

Medium difficulty and some danger of Data Loss

*(14) Defragment (requires use of second computer or boot to defrag program on CD)
*(15) Use Partition Table Doctor from the Ultimate Boot CD (search on Google)
(16) Use FIXMBR utility on Win XP recovery (DO NOT use if utility indicates non-standard partition if you want to preserve your data!)
(17) Change drive ID from 1 to 0 (if it is 1) or vice versa (personally I don't think this is a good idea); if problem with drive ID, reset ID by powering system on while HD cable is plugged but power unplugged
(18) Resize NTFS Clusters to 4K using partition manager
*(19) Change NTFS to FAT32 using partition manager (and optionally change back to NTFS--although this may cause the problem to recur)

Time-consuming and may not work; definite data loss:

(20) Resize partition below 137 Gb
(21) Perform low-level format on HD (using manufacturer's tools)

Good Luck.

Monday, March 19, 2012

[SQLSTATE 42000] (Error 22029).

We have SQL Server 2000 installed on Windows 2003
machine. Get following error while doing database
maintenance
Executed as user: server\sqladmin. sqlmaint.exe failed.
[SQLSTATE 42000] (Error 22029). The step failed.
SQL Server log doesn't say anything either.
Any idea on what could be wrong? Thanks.
You need to look at the maintenance plan history or the report file for that
job to find the error.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"anonymous" <anonymous@.discussions.microsoft.com> wrote in message
news:885c01c48531$710fd050$a601280a@.phx.gbl...
> We have SQL Server 2000 installed on Windows 2003
> machine. Get following error while doing database
> maintenance
> Executed as user: server\sqladmin. sqlmaint.exe failed.
> [SQLSTATE 42000] (Error 22029). The step failed.
> SQL Server log doesn't say anything either.
> Any idea on what could be wrong? Thanks.

[SQL Server]Login failed for user

I am using Crystal Reports, VB.net, SQL Server 2000sp3, MDAC 8.0, and Windows XP. When I try to make a connection from a Crystal Report to SQL Server via an ODBC connection, I get the following message:

Details: 28000:[Microsoft][SQL Server Driver][SQL Server]Login failed for user domain/username

In the odbc, I specify SQL Server authentication and provide a username and password but these are being ignored. Why is Windows authentication being used in place of the SQL Server authentication that I specify in my odbc?

Thanks in advance,

MattThat's Crystal for you :)|||What version of Crystal Reports are you using?|||Originally posted by awsterling
What version of Crystal Reports are you using?

I am the version that came with Visual Studio .Net 2003. I don't know how to get the version number from it.

Thanks.|||Get ActiveReport from DataDynamics and you won't have to deal with these issues any more :)

Sunday, March 11, 2012

[SQL 2005] backup Diff on MSDB doesnt work

Hello all,

I need help concerning a differential backup on a MSDB database.

I received this message when I tried to backup it

Log from Windows

Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 8/1/2007
Time: 2:03:37 PM
User: N/A
Computer: XXX

Description:
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=9028. Thread=5928. Client. Instance=. VD=Global\Data Protector_(DEFAULT)_msdb_14_00_21.

Log from DataProtector

Normal] From: XXX "(DEFAULT)" Time: XXX
SQL statement:
BACKUP DATABASE [msdb] TO
VIRTUAL_DEVICE = "Data Protector_(DEFAULT)_msdb_06_00_14"
WITH NAME = 'Data Protector: 2007/08/01 0064', DIFFERENTIAL, BLOCKSIZE = 4096, MAXTRANSFERSIZE = 65536;

[Warning] From: XXX "(DEFAULT)" Time: XXX
Error has occurred while executing a SQL statement.
Error message: '<Microsoft SQL-DMO (ODBC SQLState: 42000):bdb>
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot perform a differential backup for database "msdb", because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.'

Ive tried to do a full followed straight after by a diff but doent help.

Thank you for your help

yes you can take differential but for master you can take only full backup ..........whats in the error log ? ? ? you need to take a full backup and then subsequently differential backup

|||

Yes we can, I do it for many servers

|||

The error is pretty explicit about what the problem is.

A differential backup is defined as the set of changes SINCE THE LAST FULL BACKUP.

If you've never done a full backup, there is nothing to base the differential on and it won't work.

Do a full backup of MSDB, and then your differentials should work.

|||

Hi thank you to replay.

That what I do, a full and after a diff, that why I don't understand why I doesnt find any base

Thank you

|||

Is the database recovery set to FULL? Simple won't do it (it actually reset the status field needed).

|||

FULL recovery model applies to log backups, not to differential backups.

In fact, there is no way to clear the differential base once it is set.

What you're attempting to do should work just fine.

Please try it from Management Studio query window and paste the commands and response.

Thanks,

Kevin

|||

Kevin Farlee wrote:

FULL recovery model applies to log backups, not to differential backups.

In fact, there is no way to clear the differential base once it is set.

Thanks for the correction. Somehow, I was thinking the OP wants to backup log for msdb (you can't 'cuz it's simple). Duh!

[SQL 2005] backup Diff on MSDB doesnt work

Hello all,

I need help concerning a differential backup on a MSDB database.

I received this message when I tried to backup it

Log from Windows

Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 8/1/2007
Time: 2:03:37 PM
User: N/A
Computer: XXX

Description:
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=9028. Thread=5928. Client. Instance=. VD=Global\Data Protector_(DEFAULT)_msdb_14_00_21.

Log from DataProtector

Normal] From: XXX "(DEFAULT)" Time: XXX
SQL statement:
BACKUP DATABASE [msdb] TO
VIRTUAL_DEVICE = "Data Protector_(DEFAULT)_msdb_06_00_14"
WITH NAME = 'Data Protector: 2007/08/01 0064', DIFFERENTIAL, BLOCKSIZE = 4096, MAXTRANSFERSIZE = 65536;

[Warning] From: XXX "(DEFAULT)" Time: XXX
Error has occurred while executing a SQL statement.
Error message: '<Microsoft SQL-DMO (ODBC SQLState: 42000):bdb>
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot perform a differential backup for database "msdb", because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.'

Ive tried to do a full followed straight after by a diff but doent help.

Thank you for your help

yes you can take differential but for master you can take only full backup ..........whats in the error log ? ? ? you need to take a full backup and then subsequently differential backup

|||

Yes we can, I do it for many servers

|||

The error is pretty explicit about what the problem is.

A differential backup is defined as the set of changes SINCE THE LAST FULL BACKUP.

If you've never done a full backup, there is nothing to base the differential on and it won't work.

Do a full backup of MSDB, and then your differentials should work.

|||

Hi thank you to replay.

That what I do, a full and after a diff, that why I don't understand why I doesnt find any base

Thank you

|||

Is the database recovery set to FULL? Simple won't do it (it actually reset the status field needed).

|||

FULL recovery model applies to log backups, not to differential backups.

In fact, there is no way to clear the differential base once it is set.

What you're attempting to do should work just fine.

Please try it from Management Studio query window and paste the commands and response.

Thanks,

Kevin

|||

Kevin Farlee wrote:

FULL recovery model applies to log backups, not to differential backups.

In fact, there is no way to clear the differential base once it is set.

Thanks for the correction. Somehow, I was thinking the OP wants to backup log for msdb (you can't 'cuz it's simple). Duh!

Thursday, March 8, 2012

[Performance Discussion] To schedule a time for mssql command, which way would be faster a

1. Use mssql server agent service to take the schedule
2. Use a .NET windows service with timers to call SqlClientConnection

above, which way would be faster and get a better performance?I don't think you'll see any performance difference.

but go with agent.|||ok, but will have a difference when busy

Tuesday, March 6, 2012

[MS Design Tools] - Class not registered."

On a Windows 2000 pro workstation I am using SQL 2000 enterprise
manager I am trying to return all rows, I get the error message "An
unexpected error happened during this operation. [MS Design Tools] -
Class not registered."
I have reinstalled the client tools, reinstalled service pack 3a, but I
am not having any luck. Any ideas how I can resolve this issue?
Thanks
| From: "Ryan" <rstodola@.gmail.com>
| Newsgroups: microsoft.public.sqlserver.clients
| Subject: [MS Design Tools] - Class not registered."
| Date: 22 Feb 2005 11:38:57 -0800
| Organization: http://groups.google.com
| Lines: 12
| Message-ID: <1109101137.832608.183900@.f14g2000cwb.googlegroups .com>
| NNTP-Posting-Host: 129.176.151.126
| Mime-Version: 1.0
| Content-Type: text/plain; charset="iso-8859-1"
| X-Trace: posting.google.com 1109101141 26265 127.0.0.1 (22 Feb 2005
19:39:01 GMT)
| X-Complaints-To: groups-abuse@.google.com
| NNTP-Posting-Date: Tue, 22 Feb 2005 19:39:01 +0000 (UTC)
| User-Agent: G2/0.2
| Complaints-To: groups-abuse@.google.com
| Injection-Info: f14g2000cwb.googlegroups.com;
posting-host=129.176.151.126;
| posting-account=OtO42g0AAAAxhVXq79oLm_y3qUbyubb3
| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSF TNGP08.phx.gbl!newsfeed00.
sul.t-online.de!t-online.de!news.glorb.com!postnews.google.com!f14g2 000cwb.g
ooglegroups.com!not-for-mail
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.clients:29558
| X-Tomcat-NG: microsoft.public.sqlserver.clients
|
| On a Windows 2000 pro workstation I am using SQL 2000 enterprise
| manager I am trying to return all rows, I get the error message "An
| unexpected error happened during this operation. [MS Design Tools] -
| Class not registered."
|
|
| I have reinstalled the client tools, reinstalled service pack 3a, but I
| am not having any luck. Any ideas how I can resolve this issue?
|
|
| Thanks
|
|
<><><><><><><><><><><><><><><><><><><><><><><><><> <><><><><><><>
Hi Ryan,
Try re-installing the current version of MDAC on your system. You can use
the Component Checker
to determine installed version information of MDAC -
http://www.microsoft.com/downloads/d...df6-4a21-4b43-
bf53-14332ef092c9&displaylang=en
HTH,
Yasemin Gunduz
SQL Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.

[MS Design Tools] - Class Not Registered

On a Windows 2000 pro workstation I am using SQL 2000 enterprise
manager I am trying to return all rows, I get the error message "An
unexpected error happened during this operation. [MS Design Tools] -
Class not registered."
I have reinstalled the client tools, reinstalled service pack 3a, but I
am not having any luck. Any ideas how I can resolve this issue?
Thanks
From the command line, or "Run ...", run regsvr32 on the DLLs in %Program
Files%\Common Files\Microsoft Shared\MSDeisgner98 and MSDesigner7 directory.
Seth Sanusi
Test Lead - SQL Server Tools
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ryan" <rstodola@.gmail.com> wrote in message
news:1109100062.665588.142490@.l41g2000cwc.googlegr oups.com...
> On a Windows 2000 pro workstation I am using SQL 2000 enterprise
> manager I am trying to return all rows, I get the error message "An
> unexpected error happened during this operation. [MS Design Tools] -
> Class not registered."
> I have reinstalled the client tools, reinstalled service pack 3a, but I
> am not having any luck. Any ideas how I can resolve this issue?
> Thanks
>

[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.

I'm using JBuilder X, writing a client application and connecting to
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 SQL Server Driver][SQL Server]Transaction (Process ID X) was deadloc

My company recently upgraded from SQL 7 to SQL 2000. We also updated
our application servers from Windows NT to Windows 2003. Now when we
get the error [Microsoft][ODBC SQL Server Driver][SQL
Server]Transaction (Process ID X) was deadlocked, the part that comes
next "on {unprintable" shows up as unprintable characters. The rest of
the error message seems fine. Only the part between the braces is
garbage. Does anyone have any suggestions as to why this is? It
seems to be happening from both C++ and Java apps. We are using ODBC
with the C++ apps and JDBC with the Java apps.
Thanks.
-Jeff-Hi
You may want to run SQL profiler to see what is being sent to the server,
and look at the query plans to see if you are missing indexes or statistics.
You may need to change the order of the SQL in your code/stored procedures
and if you have carried over any hints from the SQL 7 upgrade you may want
to evaluate if they are still necessary.
For ways ways to find blocking check out
http://support.microsoft.com/kb/271509/EN-US/ and general tips on
http://www.sql-server-performance.com/
John
"kludge" <jeff.schuler@.53.com> wrote in message
news:1130515027.782023.128220@.g43g2000cwa.googlegroups.com...
> My company recently upgraded from SQL 7 to SQL 2000. We also updated
> our application servers from Windows NT to Windows 2003. Now when we
> get the error [Microsoft][ODBC SQL Server Driver][SQL
> Server]Transaction (Process ID X) was deadlocked, the part that comes
> next "on {unprintable" shows up as unprintable characters. The rest of
> the error message seems fine. Only the part between the braces is
> garbage. Does anyone have any suggestions as to why this is? It
> seems to be happening from both C++ and Java apps. We are using ODBC
> with the C++ apps and JDBC with the Java apps.
> Thanks.
> -Jeff-
>

Saturday, February 25, 2012

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

I have a ms sqlserver 2000 database installed on my Windows NT4 PC.

I want to access this database from a java program using JDBC - ODBC

Here are the relavent lines of code from my java source code file.

Note : I am attempting to access the sample database "Northwind Traders" that came with the installation.

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
datasource = "NORTHDS";
url = "jdbc:odbc:" + datasource;
con = DriverManager.getConnection(url,username,password) ;
query = "SELECT * from " + datasource + "." + username + "." + tablename;
ResultSet rs = stmt.executeQuery(query);

The connection succeeds but the query fails with :
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid object name 'NORTHDS.username.Customers'.

Using the program "Microsoft Access" I was able to verify that the "Customers" table is intact.

Any ideas ?Take a look at the following:

In your select statement there are a couple of potential problems that you need to verify.

select * from datasource.username.table ... which is returning 'NORTHDS.username.Customers'

should be

select * from Northwind.dbo.Customers ... (unless you renamed the database ...)

In other words, check to make sure your are referencing the correct database/owner/table in your select statement. It appears that the variables you are using are incorrect. tablename appears to be ok, but the username variable is returning username. Also, the datasource variable may not be your database name.

[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 Driver Manager] Data source name not found and no default driver specified

trying to install sql server2005 on a windows 2003 server box.

getting msg below at the sql server . i looked at other posts on trying to uninstall SQL Native Access Client and norton antivirus. i could never find the snac on the add - remove programs and this server does not have a virus protection program yet.

here's the history of the installs on the server:

wanted to test a 2005 upgrade so:

1) installed sql server 2000 then sp4 then restored some databases to it - all OK

2) tried to upgrade to sql 2005 but ran into problems and left it at that.

had a disk drive crash on the d drive so lost the installs but not the operating system

when the drive was replaced, left alone for a while

then wanted to test a straight 2005 install

1) removed the broken 2005 attempt

2) removed the 2000

3) installed 2005 and got the error on the subject line:

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

i've gone through as many of the forums that i can and have tried several things - like uninstalling 2005 and installing pieces and parts but but nothing seems to work.

Thanks!

Dan <><

It sounds like the SNAC version you have might be corrupt or incompatible.

Go to Add or Remove Programs and find the listing for "Microsoft SQL Native Client". Remove this component.

Then try the install again.

Michelle

|||

Thank you so much for replying. last attempt was to install just the sql server commonent - no others like analysis services or integration services.

i looked at the add / remove programs both before, during and after the sql server database services failed attempt and the add/remove has never shown a program called MS sql native access client (SNAC).

when i start the install, the installing prerequisites window shows the two components that will be installed: snac and the sql server 2005 setup support files. the snac goes to a green arrow almost immediately while the 2005 setup files takes a few seconds. i dont know if that helps or not.

the add remove programs just has:

microsoft .net framwork 2.0|||

It definatel looks like the problems is the "Microsoft SQL Server Native Client" layer. At this point your machine thinks that it is already installed but the install is broken.

Follow the directions in the following article to clean up the machine and then try again.

http://support.microsoft.com/kb/909967

Michelle

|||

uninstall manually - did the following (shows issues with some of the directions)

it said to delete the local security groups. but i never could figure out how to do. the article it mensions didnt (at least to me) show how to delete. so i just went on|||

i went out to the website and downloaded the .msi file for snac. it was slightly different from the .msi that came on the DVD (3511k vs 3516k).

the dvd version when i clicked on the msi file just returned me back to windows explorer.

the snac from microsoft's website executed and finally installed the snac.

the install worked perfectly after that.

thanks for your help

|||

Actually that was a good work around as downloading a newer version would have forced the install to run again where as in the previous case it was failing quickly becuase it thought it was laready installed.

Glad you got you machine back.

Michelle

|||

Hi,

I've been handling SQL Server upgrades for many years. The most dangerous path for an upgrade is to directly upgrade 2000 to 2005 (or 7.0 to 2000). That's because you create the risk of destroying the databases on the existing server and causing data loss.

The best approach embraces the fact that we typically upgrade a windows server when the mfg warranty on the hardware has expired. So, you have a new box and windows server. If you don't, the store the backups on another resource (disk, tape, flash drive, etc...) and copy from or restore from that resource. Rebuild the Windows server or uninstall SQL Server 2000. (I would have fresh windows to insure the best chance of success.)

Install SQL 2005 & configure on the new W03 SP1 server. migrate the users. (this worked easily with 2K but MS has hosed that functionality in 2005 from what I can see; you must use a script they provided that is flaky. You will need to manually create the users it fails to migrate.) Backup the dbs on 2K, shut down 2K on the old machine and restore the dbs to 2005. associate the users with the logins.

Now you have a fullly upgraded database server and your databases are unhosed. This may not be elegant but it guarantees the MS upgrade process won't destroy your databases or bring down your business for days.

If you have a completely hosed system, then rebuild the system (and the drives) and follow the steps above to a successful conclusion.

z.

Friday, February 24, 2012

[Help]SQLServer Logon Failure ....

Hi!
I have a SQL server which version is SQL Server 8.0 and I want to change
this server's windows logon password. But, when I did then restart sql
service, I get this error message :"SQL Server Logon Failure". Is there any
way to change this password?
Registration properties : Windows authentication
Authentication mode : SQL Server and Windows
Best Regards,
AresChange the service login info - check
http://www.techgroup21.com/subpage.asp?subnavID=114.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"ares" <aresATasia-minor.info> wrote in message
news:uRCSkJkxEHA.2580@.TK2MSFTNGP10.phx.gbl...
> Hi!
> I have a SQL server which version is SQL Server 8.0 and I want to change
> this server's windows logon password. But, when I did then restart sql
> service, I get this error message :"SQL Server Logon Failure". Is there
any
> way to change this password?
> Registration properties : Windows authentication
> Authentication mode : SQL Server and Windows
> Best Regards,
> Ares
>
>|||Thanks for your help.
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:OiePlJmxEHA.1300@.TK2MSFTNGP14.phx.gbl...
> Change the service login info - check
> http://www.techgroup21.com/subpage.asp?subnavID=114.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "ares" <aresATasia-minor.info> wrote in message
> news:uRCSkJkxEHA.2580@.TK2MSFTNGP10.phx.gbl...
> any
>

[HELP] The right version

Hi Everyone !
I need an advice :
i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
I would like to install the 64-bit version of SQL Server 2000.
Which Windows server do i need ?
Windows 2000 Advanced server is enough ?
or Windows 2003 server ?
I'm confused because the only 64-bit Windows 2003 server available is the
one optimized for Itanium processors... thank you
You have a 32-bit machine. You can only install 32-bit operating systems
and applications on the machine you described.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Danny" <dannyniceOnlyWithWhoWillRespectMe@.hotmail.com> wrote in message
news:2h1lefF84oo0U1@.uni-berlin.de...
> Hi Everyone !
> I need an advice :
> i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
> I would like to install the 64-bit version of SQL Server 2000.
> Which Windows server do i need ?
> Windows 2000 Advanced server is enough ?
> or Windows 2003 server ?
> I'm confused because the only 64-bit Windows 2003 server available is the
> one optimized for Itanium processors... thank you
>
>
|||> i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
> I would like to install the 64-bit version of SQL Server 2000.
Why? You need 64-bit hardware (e.g. Itanium processors!) to run 64-bit
software (!).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

[HELP] The right version

Hi Everyone !
I need an advice :
i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
I would like to install the 64-bit version of SQL Server 2000.
Which Windows server do i need ?
Windows 2000 Advanced server is enough ?
or Windows 2003 server ?
I'm confused because the only 64-bit Windows 2003 server available is the
one optimized for Itanium processors... thank you You have a 32-bit machine. You can only install 32-bit operating systems
and applications on the machine you described.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Danny" < dannyniceOnlyWithWhoWillRespectMe@.hotmai
l.com> wrote in message
news:2h1lefF84oo0U1@.uni-berlin.de...
> Hi Everyone !
> I need an advice :
> i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
> I would like to install the 64-bit version of SQL Server 2000.
> Which Windows server do i need ?
> Windows 2000 Advanced server is enough ?
> or Windows 2003 server ?
> I'm confused because the only 64-bit Windows 2003 server available is the
> one optimized for Itanium processors... thank you
>
>|||> i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
> I would like to install the 64-bit version of SQL Server 2000.
Why? You need 64-bit hardware (e.g. Itanium processors!) to run 64-bit
software (!).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

[help] SQL Error - I/O Error 2 (The system cannot find the file specified)

Windows 2000 Server SP4 + SQL Server 2000 Enterprise Editon SP3,RAID5.

the windows event log give the following error information:

I/O error 2(The system cannot find the file specified) detected during write at offset 0x0000010c6c4000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL\data\GJSZBANK_Data.MDF'.

I have searched microsoft knowledge base and got this article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;828339

but don't understand some contents in the topic:

For example, if you encounter the following error message in the SQL Server Errorlog file, SQL Server encountered operating system error 2 when it uses a Windows API call to write to the tempdb primary database file:

Error: 823, Severity: 24, State: 4
I/O error 2(The system cannot find the file specified.) detected during write at offset 0x00000000284000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'

Because SQL Server has already successfully opened the file and did not receive an Invalid Handle error, the error is likely being raised in a lower-level kernel software component, such as the file system or a device driver. This problem does not indicate a problem in SQL Server, and it must be investigated as an issue with the file system or a device driver that is associated with the file.

Does that mean this is not a SQL Server error?
Does that mean something wrong with my operating system? or something wrong with my hard disk?Are there any errors in the SQL errorlog? Or is it only in the NT Event log?

Sunday, February 19, 2012

[DBNETLIB]ConnectionCheckForData (CheckforData())

Hi...

SQL SERVER 2000 SP3, WINDOWS 2K SERVER...

If i run this command on a remote server

select replicate(' ',190)

i have the following error

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.

Connection Broken

if i run select replicate(' ',60) on the same server it completes
succesfully...

any ideas?...

thanks...Sangines (javier.sangines@.gruposenda.com) writes:
> SQL SERVER 2000 SP3, WINDOWS 2K SERVER...
> If i run this command on a remote server
> select replicate(' ',190)
> i have the following error
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> if i run select replicate(' ',60) on the same server it completes
> succesfully...

Interesting...

Often such events are accompnied by messages in the SQL Server errorlog
with a stack dump, indicating that there was an execution error in
SQL Server. However, given the statement you submit this sounds
unlikely. I assume that you run it from Query Analyzer?

So in this case, I would say that it smells a network problem of
some sort. Do you still get the message if you run the query locally
on the SQL Server machine? Do you get the message if you talk to
other SQL Servers?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||> Interesting...
> Often such events are accompnied by messages in the SQL Server errorlog
> with a stack dump, indicating that there was an execution error in
> SQL Server. However, given the statement you submit this sounds
> unlikely. I assume that you run it from Query Analyzer?
> So in this case, I would say that it smells a network problem of
> some sort. Do you still get the message if you run the query locally
> on the SQL Server machine? Do you get the message if you talk to
> other SQL Servers?

Thanks for quick response Erland...

Yes...it was a network problem, caused by misconfiguration in network device...

problem solved...

thanks again...

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

I'm getting the following error on Windows XP clients only:
[DBNETLIB][ConnectionWrite(WrapperWrite()).]General network error. C
heck
your network documentation.
This error seems to occur at random times of inactivity on my application.
Here is how I am configured:
Windows 2000 Server - Standard
Windows 2000 and Windows XP Pro Clients
SQL Server 2000
MDAC 2.7 or 2.8 on various clients
The error does not occur on Windows 2000 clients, only on Windows XP Pro
clients.
My application first opens a connection to a server database. Every 2
minutes an application watchdog timer triggers and attempts to write an
timestamp value to a data table. After some period of time (seemingly
random) the attempted write fails and I get the above error message,
followed by a "Connection failure." error.
Can anyone point me in the right direction on how to fix this problem?
Thanks,
Al WillisHi Al,
I would try to capture the problem using both SQL Profiler on the
backend, and network traces on the client machines.
General Network errors are commonly caused by tcp resets on the network.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Most probably problem with NIC drivers or network harware on specific
computers.
Also it will much help if you do not expect an open connection to stay
connected forever and make new connection after for each triggering of your
watchdog.
Bojidar Alexandrov
"Al Willis" <alwillisj01@.sbcglobal.net> wrote in message
news:409aa583$1@.newsgroups.borland.com...
> I'm getting the following error on Windows XP clients only:
> [DBNETLIB][ConnectionWrite(WrapperWrite()).]General network error.
Check
> your network documentation.
> This error seems to occur at random times of inactivity on my application.
> Here is how I am configured:
> Windows 2000 Server - Standard
> Windows 2000 and Windows XP Pro Clients
> SQL Server 2000
> MDAC 2.7 or 2.8 on various clients
>
> Development Software
> --
> Delphi 6, update 2
> CoreLabs dbExpress driver for SQL Server
> The error does not occur on Windows 2000 clients, only on Windows XP Pro
> clients.
> My application first opens a connection to a server database. Every 2
> minutes an application watchdog timer triggers and attempts to write an
> timestamp value to a data table. After some period of time (seemingly
> random) the attempted write fails and I get the above error message,
> followed by a "Connection failure." error.
> Can anyone point me in the right direction on how to fix this problem?
> Thanks,
> Al Willis
> Enviroment
> --
> Windows 2000 Server - Standard
> Windows 2000 and Windows XP Pro Clients
> SQL Server 2000
> MDAC 2.7 or 2.8 on various clients
>
>|||Kevin,
Thanks for the reply.
I looked at the SQL Profiler. What categories should I trace to find my
problem?
Al Willis|||Hi Al,
You'll want to capture as much data about the clients and the
statements they're executing.
Select All Errors and Warnings
RPC: Completed, Starting, sp Recompile
TSQL BatchCompleted, BatchStarting
Stmt:Starting
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.