Error in restoring SQL Server 6.5 backup

Hi,
I am receiving an error when I try to do a restore of a backup from a
client. I am getting the following error:
"read on dump dump device 'e:\mssql\backup
\NAMEOFFILE' failed, vsn =1 return=1870835794 status = 2. Please consult
the errro log for more details. When I go to the error log I see the message
"dev_read_extent: Trying to read after end of data"
Can someone please tell me what the error means?
I am running 6.5.416 as my dbserver.
Thanks for your assistance,
KimHi
Google turns up nothing other than the obvious ones of corrupt dump file or
no disc space!
Are you both on the same service pack?
Are your devices the same size (or large enough!)?
John
"kimcmm" <kimcmm@.discussions.microsoft.com> wrote in message
news:2001E620-B617-4221-B921-C74BA0C9AB19@.microsoft.com...
> Hi,
> I am receiving an error when I try to do a restore of a backup from a
> client. I am getting the following error:
> "read on dump dump device 'e:\mssql\backup
> \NAMEOFFILE' failed, vsn =1 return=1870835794 status = 2. Please consult
> the errro log for more details. When I go to the error log I see the
> message
> "dev_read_extent: Trying to read after end of data"
> Can someone please tell me what the error means?
> I am running 6.5.416 as my dbserver.
> Thanks for your assistance,
> Kim|||Yeah, I checked google and I believe that this is a bad backup.My devices
that created the database on are large enough, otherwise I would have gotten
the error when the backup first attempted to run that says I don't have
enough space.
The backup proceeds about half way, then I get the error that I posted. The
database stays in a loading state until I run the DROP DATABASE command.
I will check with the client on the service pack.
"John Bell" wrote:
> Hi
> Google turns up nothing other than the obvious ones of corrupt dump file or
> no disc space!
> Are you both on the same service pack?
> Are your devices the same size (or large enough!)?
> John
> "kimcmm" <kimcmm@.discussions.microsoft.com> wrote in message
> news:2001E620-B617-4221-B921-C74BA0C9AB19@.microsoft.com...
> > Hi,
> > I am receiving an error when I try to do a restore of a backup from a
> > client. I am getting the following error:
> > "read on dump dump device 'e:\mssql\backup
> > \NAMEOFFILE' failed, vsn =1 return=1870835794 status = 2. Please consult
> > the errro log for more details. When I go to the error log I see the
> > message
> > "dev_read_extent: Trying to read after end of data"
> >
> > Can someone please tell me what the error means?
> > I am running 6.5.416 as my dbserver.
> >
> > Thanks for your assistance,
> > Kim
>
>

Error in ODBC Connetion

I had in a customer a ODBC connection to the database sql
in which I modified the client configurations the
connection I took off the option to determine door
dynamicly and placed the 1433 but it gave error and after
this exactly placing again to determine door dynamicly it
gives always error and it does not function i remember
that before this it was to function perfectly. The error
is:
Error in Connection:
SQLState: ' 01000 '
Error in the SQL Server: 10061 [ Microsoft][ODBC SQL
Server Driver][TCP/IP Sockets ] ConnectionOpen(Connect()).
Error in Connection:
SQLState: ' 08001 ' Error in the SQL Sever: 17 [
Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]O SQL
Server does not exist or the access was refused the
computer in cause is with all the right definitions of
net, has access to the server... Please help Me! .J=E1 tentaste fazer um ODBCping? J=E1 verificas-te as permiss=F5es?
>--Original Message--
>I had in a customer a ODBC connection to the database sql >in which I modified the client configurations the >connection I took off the option to determine door >dynamicly and placed the 1433 but it gave error and after >this exactly placing again to determine door dynamicly it >gives always error and it does not function i remember >that before this it was to function perfectly. The error >is: >Error in Connection: >SQLState: ' 01000 ' >Error in the SQL Server: 10061 [ Microsoft][ODBC SQL >Server Driver][TCP/IP Sockets ] ConnectionOpen(Connect()).
>Error in Connection:
>SQLState: ' 08001 ' Error in the SQL Sever: 17 [ >Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]O SQL >Server does not exist or the access was refused the >computer in cause is with all the right definitions of >net, has access to the server... Please help Me! .
>.
>

Error in ODBC Connection HELP

I had in a customer a ODBC connection to the database sql
in which I modified the client configurations the
connection I took off the option to determine door
dynamicly and placed the 1433 but it gave error and after
this exactly placing again to determine door dynamicly it
gives always error and it does not function i remember
that before this it was to function perfectly. The error
is:
Error in Connection:
SQLState: ' 01000 '
Error in the SQL Server: 10061 [ Microsoft][ODBC SQL
Server Driver][TCP/IP Sockets ] ConnectionOpen(Connect()).
Error in Connection:
SQLState: ' 08001 ' Error in the SQL Sever: 17 [
Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]O SQL
Server does not exist or the access was refused the
computer in cause is with all the right definitions of
net, has access to the server... Please help Me! .
Hi Nuno,
first of all be sure that you don't have network generic problems, using for
example the dos PING command or TRACERT.
Then I'd reinstall MDAC on client machine (if you've to connect to SQL
Server 7.00 install MDAC 2.5, for SQL 2000 MDAC 2.6SP2), reboot the client
and try again deleting the old DSN and recreating a newest one.
Very important is checking the TCP port is your server listening on (check
the server network utility on your server machine) and the TCP port is your
server transmetting (check the client network utility on your client
machine): they must be identical.
Finally check the authentication mode on your sql server: it must be the
same of the specified into your DSN configuration.
Hope it helps, regards
Riccardo Piccini
Supporto Software
EDP SERVICE SRL
"Nuno Pereira" <n.pereira@.desis.pt> ha scritto nel messaggio
news:17df301c42221$d6cab310$a001280a@.phx.gbl...
> I had in a customer a ODBC connection to the database sql
> in which I modified the client configurations the
> connection I took off the option to determine door
> dynamicly and placed the 1433 but it gave error and after
> this exactly placing again to determine door dynamicly it
> gives always error and it does not function i remember
> that before this it was to function perfectly. The error
> is:
> Error in Connection:
> SQLState: ' 01000 '
> Error in the SQL Server: 10061 [ Microsoft][ODBC SQL
> Server Driver][TCP/IP Sockets ] ConnectionOpen(Connect()).
> Error in Connection:
> SQLState: ' 08001 ' Error in the SQL Sever: 17 [
> Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]O SQL
> Server does not exist or the access was refused the
> computer in cause is with all the right definitions of
> net, has access to the server... Please help Me! .

Error in ODBC Connection HELP

I had in a customer a ODBC connection to the database sql
in which I modified the client configurations the
connection I took off the option to determine door
dynamicly and placed the 1433 but it gave error and after
this exactly placing again to determine door dynamicly it
gives always error and it does not function i remember
that before this it was to function perfectly. The error
is:
Error in Connection:
SQLState: ' 01000 '
Error in the SQL Server: 10061 [ Microsoft][ODBC SQL
Server Driver][TCP/IP Sockets ] ConnectionOpen(Connect()).
Error in Connection:
SQLState: ' 08001 ' Error in the SQL Sever: 17 [
Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]O SQL
Server does not exist or the access was refused the
computer in cause is with all the right definitions of
net, has access to the server... Please help Me! .Hi Nuno,
first of all be sure that you don't have network generic problems, using for
example the dos PING command or TRACERT.
Then I'd reinstall MDAC on client machine (if you've to connect to SQL
Server 7.00 install MDAC 2.5, for SQL 2000 MDAC 2.6SP2), reboot the client
and try again deleting the old DSN and recreating a newest one.
Very important is checking the TCP port is your server listening on (check
the server network utility on your server machine) and the TCP port is your
server transmetting (check the client network utility on your client
machine): they must be identical.
Finally check the authentication mode on your sql server: it must be the
same of the specified into your DSN configuration.
Hope it helps, regards
Riccardo Piccini
Supporto Software
EDP SERVICE SRL
"Nuno Pereira" <n.pereira@.desis.pt> ha scritto nel messaggio
news:17df301c42221$d6cab310$a001280a@.phx
.gbl...
> I had in a customer a ODBC connection to the database sql
> in which I modified the client configurations the
> connection I took off the option to determine door
> dynamicly and placed the 1433 but it gave error and after
> this exactly placing again to determine door dynamicly it
> gives always error and it does not function i remember
> that before this it was to function perfectly. The error
> is:
> Error in Connection:
> SQLState: ' 01000 '
> Error in the SQL Server: 10061 [ Microsoft][ODBC SQL
> Server Driver][TCP/IP Sockets ] ConnectionOpen(Connect()).
> Error in Connection:
> SQLState: ' 08001 ' Error in the SQL Sever: 17 [
> Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]O SQL
> Server does not exist or the access was refused the
> computer in cause is with all the right definitions of
> net, has access to the server... Please help Me! .

Error in Management Studio

Have installed SQL 2008 db engine and client tools. Each time I attempt to return a resultset, I receive the following error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

This error occurs on any data access, such as:

select * from sys.columns

Does anyone know what might be going on?

And if you switch results to text instead of the grid, does everything work?|||

No, I receive the same error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

|||Nope. Do you have more than one machine to do this on, or could you re-install SSMS?|||

Had same exact error message. Tried uninstalling and reinstalling just the client tools with no affect. Then completely uninstalled SQL 2008 (had both June and July instances) and reinstalled all of July. This "fixed" the problem. This is a frustrating one, I'd already submitted it as a bug earlier today. Perhaps it is related to partial uninstalls of just the client tools, since I had to uninstall the June tools to install the July ones the first time around. But doing a total remove of all of SQL 2008 seemed to do the trick.

Have Fun!

Ron

Error in Management Studio

Have installed SQL 2008 db engine and client tools. Each time I attempt to return a resultset, I receive the following error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

This error occurs on any data access, such as:

select * from sys.columns

Does anyone know what might be going on?

And if you switch results to text instead of the grid, does everything work?|||

No, I receive the same error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

|||Nope. Do you have more than one machine to do this on, or could you re-install SSMS?|||

Had same exact error message. Tried uninstalling and reinstalling just the client tools with no affect. Then completely uninstalled SQL 2008 (had both June and July instances) and reinstalled all of July. This "fixed" the problem. This is a frustrating one, I'd already submitted it as a bug earlier today. Perhaps it is related to partial uninstalls of just the client tools, since I had to uninstall the June tools to install the July ones the first time around. But doing a total remove of all of SQL 2008 seemed to do the trick.

Have Fun!

Ron

Error in Management Studio

Have installed SQL 2008 db engine and client tools. Each time I attempt to return a resultset, I receive the following error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

This error occurs on any data access, such as:

select * from sys.columns

Does anyone know what might be going on?

And if you switch results to text instead of the grid, does everything work?

|||

No, I receive the same error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

|||Nope. Do you have more than one machine to do this on, or could you re-install SSMS?

|||

Had same exact error message. Tried uninstalling and reinstalling just the client tools with no affect. Then completely uninstalled SQL 2008 (had both June and July instances) and reinstalled all of July. This "fixed" the problem. This is a frustrating one, I'd already submitted it as a bug earlier today. Perhaps it is related to partial uninstalls of just the client tools, since I had to uninstall the June tools to install the July ones the first time around. But doing a total remove of all of SQL 2008 seemed to do the trick.

Have Fun!

Ron

Error in Management Studio

Have installed SQL 2008 db engine and client tools. Each time I attempt to return a resultset, I receive the following error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

This error occurs on any data access, such as:

select * from sys.columns

Does anyone know what might be going on?

And if you switch results to text instead of the grid, does everything work?|||

No, I receive the same error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

|||Nope. Do you have more than one machine to do this on, or could you re-install SSMS?|||

Had same exact error message. Tried uninstalling and reinstalling just the client tools with no affect. Then completely uninstalled SQL 2008 (had both June and July instances) and reinstalled all of July. This "fixed" the problem. This is a frustrating one, I'd already submitted it as a bug earlier today. Perhaps it is related to partial uninstalls of just the client tools, since I had to uninstall the June tools to install the July ones the first time around. But doing a total remove of all of SQL 2008 seemed to do the trick.

Have Fun!

Ron

Error in Management Studio

Have installed SQL 2008 db engine and client tools. Each time I attempt to return a resultset, I receive the following error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

This error occurs on any data access, such as:

select * from sys.columns

Does anyone know what might be going on?

And if you switch results to text instead of the grid, does everything work?|||

No, I receive the same error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

|||Nope. Do you have more than one machine to do this on, or could you re-install SSMS?|||

Had same exact error message. Tried uninstalling and reinstalling just the client tools with no affect. Then completely uninstalled SQL 2008 (had both June and July instances) and reinstalled all of July. This "fixed" the problem. This is a frustrating one, I'd already submitted it as a bug earlier today. Perhaps it is related to partial uninstalls of just the client tools, since I had to uninstall the June tools to install the July ones the first time around. But doing a total remove of all of SQL 2008 seemed to do the trick.

Have Fun!

Ron