Basic package is causing an error

I'm getting the following error message on a basic copy from a datareader (using an ODBC datasource) to a sqlnativeclient. There are no transformations or anything. Don't know what is going on. Any insights are appreciated.

[SQL Server Destination [361]] Error: An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Could not bulk load because SSIS file mapping object 'Global\DTSQLIMPORT ' could not be opened. Operating system error code 2(The system cannot find the file specified.). Make sure you are accessing a local server via Windows security.".

SQL Server Destination only works if the server you are inserting to is the same server that you are running SSIS on. Otherise you get the message that you are seeing.

-Jamie

|||

Jamie Thomson wrote:

SQL Server Destination only works if the server you are inserting to is the same server that you are running SSIS on. Otherise you get the message that you are seeing.

-Jamie

jamie is correct. you can use the ole db destination instead.

btw, in her ssis webcast, joy mundy said that the ole db destination outperforms the sql server destination (in most cases).

|||

Duane Douglas wrote:

Jamie Thomson wrote:

SQL Server Destination only works if the server you are inserting to is the same server that you are running SSIS on. Otherise you get the message that you are seeing.

-Jamie

jamie is correct. you can use the ole db destination instead.

btw, in her ssis webcast, joy mundy said that the ole db destination outperforms the sql server destination (in most cases).

Really? Then Joy Mundy is wrong. Please could you send me a link to the webcast, I need to check this out?

Regards

Jamie

|||Thank you Jamie and Duane. Makes sense, but I didn't realize you had to use OLE DB for non-local connections. I'll go that route.|||

OLE DB Destination is the "default" destination for any relational database table. The SQL Server Destination is an optional extra that can be used in very specific circumstances.

Personally I think the name "SQL Server Destination" confuses people. They see it and automatically think it should be used when inserting into SQL Server and that is not the case. In Microsoft's defence it does say this very very clearly in the documentation.

-Jamie

|||I'm sure it is documented, but as often happens in life I have to fly by the seat of my pants learning as I go for a quick solution to a problem. No time to actually learn the product till later. Again, the help is greatly appreciated.|||

Jamie Thomson wrote:

Duane Douglas wrote:

Jamie Thomson wrote:

SQL Server Destination only works if the server you are inserting to is the same server that you are running SSIS on. Otherise you get the message that you are seeing.

-Jamie

jamie is correct. you can use the ole db destination instead.

btw, in her ssis webcast, joy mundy said that the ole db destination outperforms the sql server destination (in most cases).

Really? Then Joy Mundy is wrong. Please could you send me a link to the webcast, I need to check this out?

Regards

Jamie

jamie,

here's the link to joy's webcast: http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032297072&EventCategory=5&culture=en-US&CountryCode=US

|||

Jamie Thomson wrote:

Personally I think the name "SQL Server Destination" confuses people. They see it and automatically think it should be used when inserting into SQL Server and that is not the case. In Microsoft's defence it does say this very very clearly in the documentation.

-Jamie

i agree. "local sql server destination" might be a more appropriate title.sql

Basic Mirroring Setup Help

After going through the Enterprise Manage mirroring setup, I get the error message ...

The server network address "TCP://MYMACH.mynet.net:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)

I have three instances of SQL Server 2005 Enterprise Edtion
MSSQLSERVER (primary) endpoint 5022
MSSQLSERVER (partner) endpoint 5023
MSSQLSERVER (witness) endpoint 5024

I have enabled TCP\IP and named pipes on all three protocols.
In surface configuration I have enabled everything.
Each instance has the -T1400 flag set.
Each instance is running under mixed security.
Each sql Server and sql agent instance runs exactly in the same domain account.
The machine has been rebooted.
The following tests all pass

telnet MYMACH.mynet.net 5022
telnet MYMACH.mynet.net 5023
telnet MYMACH.mynet.net 5024

This problem happens both with Enterprise Edition and Developer Edition.

Any ideas?

AIM

Hi,

Thank you for providing informtaion into the problem that occurred. It is very difficult to diagnose some of these problems with so little information.

My first guess is security, but lets start from the top.

I assume that you have all three instances on the same machine, correct? That should work just fine. And you have setup the endpoints to listen on the different ports, which is correct. Now you said that you can telnet to the different ports, I'm assuming that you did it from the same machine. If you can try the telnet test again from a different machine that would be good, but not neccessary. Should be fine.

If this is the recent SP1 CTP build, http://www.microsoft.com/sql/ctp_sp1.mspx, then you do not need the 1400 trace flag (it is just a noop now). Should be fine.

Now the account that the instances are running under? What type of account is it? Can we make it a Sys Admin account on all three instances? Look in the errorlog for the instances. If you see anything along the lines of "denied access" in there?

Also, one last thing; you state that the error message is:

"The server network address "TCP://MYMACH.mynet.net:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)"

If you want the principal to listen on the 5022 port, then you should have gotten an error saying "... MYMACH.mynet.net:5023..." Can you go back and check your setup?

Thanks,

Mark

|||

O.K.

FIRST

All three instances are running under a Windows Account that is an Adminstrator on the machine. This has always been this way.

SECOND

I said:

"The server network address "TCP://MYMACH.mynet.net:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)"

I meant to say:

"The server network address "TCP://MYMACH.mynet.net:5023" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)"

O.K. WHAT NEXT SHOULD I TRY?

THANKS.

AIMDBA

|||

Can you verify that the Windows account that the instances are running as are "SQL Server System Administrators?" Thanks.

If you could attach the error logs during the time that you tried to setup database mirroring, that would help a lot. Grab the error logs from both the principal and mirror instance. By default these are located at:

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG

Get the "errorlog" that contains the time at which you issued the start mirroring command.

At this point, I see two approaches.

1. posting the errorlogs so that I can look at them.

2. trying to setup mirroring just using t-sql. There are some examples in BOL.

Let me know how things are going.

Thanks,

Mark

|||

I'm getting the same error here. Below is my sql server error (machines are on different IP's) and below this is my error log.

An error occurred while starting mirroring.

ADDITIONAL INFORMATION:

Alter failed for Database 'UOP_GSO'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2040.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

The server network address "TCP://BOGEYWRKSTATION.svc.nt.edu:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. (Microsoft SQL Server, Error: 1418)

2006-04-12 16:48:01.75 spid51 Using 'xpstar90.dll' version '2005.90.2040' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2006-04-12 16:48:02.55 spid12s The Service Broker protocol transport is disabled or not configured.
2006-04-12 16:48:02.57 spid12s Server is listening on [ 'any' <ipv4> 5022].
2006-04-12 16:48:02.57 spid12s The Database Mirroring protocol transport is now listening for connections.
2006-04-12 16:48:02.77 spid12s Service Broker manager has started.
2006-04-12 16:48:04.49 spid5s Recovery is complete. This is an informational message only. No user action is required.

|||

First thing to do is to go to the "Troubleshooting Database Mirroring Setup" topic in BOL. It was designed to solve this first basic question of "why do I get error 1418?"

The snippette of the errorlog that you posted indicates that the database mirroring endpoint was started at one point, but that doesn't tell me much.

If you could post the part of the errorlog around the time you got the 1418 error, that would tell me much more. It is generally one of two things.

1. Network error where we tried to open the port and for some reason the network said we failed.

2. Security problem where we connected to the port but for some reason, our security credentials were not correct.

Thanks,

Mark

|||

Got it up and running. Had nothing to do with the specific error that I was receiving but I had not restored the failover correctly.

thanks

|||

Bogey1,

What did method did you use, (what did you do) to do the correct failover restore?

AIMDBA

|||Two seperate machines on the network, but still in the same domain. Running domain accounts for sql server. I did a backup of my primary and applied that to my mirror, but I kept getting the error my mirror is not in sync. So I just restored my backup to my primary and started the mirroring. Works quite well.|||

So, to initialize the mirror, you must do a full backup of the database on the princpal, restore the full backup to the mirror with NO_RECOVERY, and then usually (there are some cases where you do not have to do another backup or restore, but they are not normal operating scenarios) take a log backup and restore it to the mirror with NO_RECOVERY. You must also restore any other log backups that are taken on the principal to the mirror.

Thanks,

Mark

|||Rather that starting an entirely new thread, I figured I would post my question here since my issues are stemming from the next point of the mirror creation process.

Basically I take my full principal backup and then run the restore with no recovery to the mirror, once the restore is underway and then complete, according to my sql logs, I have the DBname (Restoring) indicator in management studio. Low and behold this message can be there for countless hours and in this scenario the database is unalvailable for use. Any ideas on what could be causing this?

Thanks
|||

This is correct behavior. Doing any type of restore with NO_RECOVERY leaves the database in an unrecovered state.

Continue with setting up database mirroring.

Thanks,

Mark

|||

I'm facing the same issue with error 1418. I have 3 VM servers ( hosted in the same host machine) that host each an instance of SQL server. I'm using a domain account with admin right on each server to run SQL server and my database mirroring. I have granted System admin right to that account and full right on all sql folder. Telnet test is successfull. after the mirroring failed, there is no failure audit in the security audit log. Everything seems to be setup properly. I have added the service account in all group created by SQL Server during the installation. But I'm still receiving this error.

In another network, where the servers are not VM Ware server but real physical machine I do not have any problem The mirroring is working fine. But with the VMWare server , I have the problem. Is this problem linked to the virtual machine architecture? Why I don't have the problem with physical machine?

Basic Mirroring Setup Help

After going through the Enterprise Manage mirroring setup, I get the error message ...

The server network address "TCP://MYMACH.mynet.net:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)

I have three instances of SQL Server 2005 Enterprise Edtion
MSSQLSERVER (primary) endpoint 5022
MSSQLSERVER (partner) endpoint 5023
MSSQLSERVER (witness) endpoint 5024

I have enabled TCP\IP and named pipes on all three protocols.
In surface configuration I have enabled everything.
Each instance has the -T1400 flag set.
Each instance is running under mixed security.
Each sql Server and sql agent instance runs exactly in the same domain account.
The machine has been rebooted.
The following tests all pass

telnet MYMACH.mynet.net 5022
telnet MYMACH.mynet.net 5023
telnet MYMACH.mynet.net 5024

This problem happens both with Enterprise Edition and Developer Edition.

Any ideas?

AIM

Hi,

Thank you for providing informtaion into the problem that occurred. It is very difficult to diagnose some of these problems with so little information.

My first guess is security, but lets start from the top.

I assume that you have all three instances on the same machine, correct? That should work just fine. And you have setup the endpoints to listen on the different ports, which is correct. Now you said that you can telnet to the different ports, I'm assuming that you did it from the same machine. If you can try the telnet test again from a different machine that would be good, but not neccessary. Should be fine.

If this is the recent SP1 CTP build, http://www.microsoft.com/sql/ctp_sp1.mspx, then you do not need the 1400 trace flag (it is just a noop now). Should be fine.

Now the account that the instances are running under? What type of account is it? Can we make it a Sys Admin account on all three instances? Look in the errorlog for the instances. If you see anything along the lines of "denied access" in there?

Also, one last thing; you state that the error message is:

"The server network address "TCP://MYMACH.mynet.net:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)"

If you want the principal to listen on the 5022 port, then you should have gotten an error saying "... MYMACH.mynet.net:5023..." Can you go back and check your setup?

Thanks,

Mark

|||

O.K.

FIRST

All three instances are running under a Windows Account that is an Adminstrator on the machine. This has always been this way.

SECOND

I said:

"The server network address "TCP://MYMACH.mynet.net:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)"

I meant to say:

"The server network address "TCP://MYMACH.mynet.net:5023" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)"

O.K. WHAT NEXT SHOULD I TRY?

THANKS.

AIMDBA

|||

Can you verify that the Windows account that the instances are running as are "SQL Server System Administrators?" Thanks.

If you could attach the error logs during the time that you tried to setup database mirroring, that would help a lot. Grab the error logs from both the principal and mirror instance. By default these are located at:

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG

Get the "errorlog" that contains the time at which you issued the start mirroring command.

At this point, I see two approaches.

1. posting the errorlogs so that I can look at them.

2. trying to setup mirroring just using t-sql. There are some examples in BOL.

Let me know how things are going.

Thanks,

Mark

|||

I'm getting the same error here. Below is my sql server error (machines are on different IP's) and below this is my error log.

An error occurred while starting mirroring.

ADDITIONAL INFORMATION:

Alter failed for Database 'UOP_GSO'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2040.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

The server network address "TCP://BOGEYWRKSTATION.svc.nt.edu:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. (Microsoft SQL Server, Error: 1418)

2006-04-12 16:48:01.75 spid51 Using 'xpstar90.dll' version '2005.90.2040' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2006-04-12 16:48:02.55 spid12s The Service Broker protocol transport is disabled or not configured.
2006-04-12 16:48:02.57 spid12s Server is listening on [ 'any' <ipv4> 5022].
2006-04-12 16:48:02.57 spid12s The Database Mirroring protocol transport is now listening for connections.
2006-04-12 16:48:02.77 spid12s Service Broker manager has started.
2006-04-12 16:48:04.49 spid5s Recovery is complete. This is an informational message only. No user action is required.

|||

First thing to do is to go to the "Troubleshooting Database Mirroring Setup" topic in BOL. It was designed to solve this first basic question of "why do I get error 1418?"

The snippette of the errorlog that you posted indicates that the database mirroring endpoint was started at one point, but that doesn't tell me much.

If you could post the part of the errorlog around the time you got the 1418 error, that would tell me much more. It is generally one of two things.

1. Network error where we tried to open the port and for some reason the network said we failed.

2. Security problem where we connected to the port but for some reason, our security credentials were not correct.

Thanks,

Mark

|||

Got it up and running. Had nothing to do with the specific error that I was receiving but I had not restored the failover correctly.

thanks

|||

Bogey1,

What did method did you use, (what did you do) to do the correct failover restore?

AIMDBA

|||Two seperate machines on the network, but still in the same domain. Running domain accounts for sql server. I did a backup of my primary and applied that to my mirror, but I kept getting the error my mirror is not in sync. So I just restored my backup to my primary and started the mirroring. Works quite well.|||

So, to initialize the mirror, you must do a full backup of the database on the princpal, restore the full backup to the mirror with NO_RECOVERY, and then usually (there are some cases where you do not have to do another backup or restore, but they are not normal operating scenarios) take a log backup and restore it to the mirror with NO_RECOVERY. You must also restore any other log backups that are taken on the principal to the mirror.

Thanks,

Mark

|||Rather that starting an entirely new thread, I figured I would post my question here since my issues are stemming from the next point of the mirror creation process.

Basically I take my full principal backup and then run the restore with no recovery to the mirror, once the restore is underway and then complete, according to my sql logs, I have the DBname (Restoring) indicator in management studio. Low and behold this message can be there for countless hours and in this scenario the database is unalvailable for use. Any ideas on what could be causing this?

Thanks
|||

This is correct behavior. Doing any type of restore with NO_RECOVERY leaves the database in an unrecovered state.

Continue with setting up database mirroring.

Thanks,

Mark

|||

I'm facing the same issue with error 1418. I have 3 VM servers ( hosted in the same host machine) that host each an instance of SQL server. I'm using a domain account with admin right on each server to run SQL server and my database mirroring. I have granted System admin right to that account and full right on all sql folder. Telnet test is successfull. after the mirroring failed, there is no failure audit in the security audit log. Everything seems to be setup properly. I have added the service account in all group created by SQL Server during the installation. But I'm still receiving this error.

In another network, where the servers are not VM Ware server but real physical machine I do not have any problem The mirroring is working fine. But with the VMWare server , I have the problem. Is this problem linked to the virtual machine architecture? Why I don't have the problem with physical machine?

Bad Page error

I am getting an error in my DTS logs about a bad page. Here is the exact
message.
Step Error Description:I/O error (bad page ID) detected during read at
offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
We are getting this error on 2 different servers. The process has been
running like a champ for years and now we are getting this message. All that
is running when it errors out is an update statement that is joining 2
tables. I have read some about tempdb running into these issues and it
suggests that there may be hardware issues. That is not the case as we have
looked into that and we have many other processes that run on these servers.
I have also read that service pack 4 needs to be installed. Well we moved
our process to another server with exactly the same configuration and it ran
fine on there. Had anybody else ran into this? Any suggestions? All help
is appreciated.
Thankshave you run DBCC CHECKDB to see if there are any errors?
--
Jack Vamvas
__________________________________________________________________
Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
New article by Jack Vamvas - SQL and Markov Chains -
www.ciquery.com/articles/art_04.asp
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> I am getting an error in my DTS logs about a bad page. Here is the exact
> message.
> Step Error Description:I/O error (bad page ID) detected during read at
> offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> We are getting this error on 2 different servers. The process has been
> running like a champ for years and now we are getting this message. All
that
> is running when it errors out is an update statement that is joining 2
> tables. I have read some about tempdb running into these issues and it
> suggests that there may be hardware issues. That is not the case as we
have
> looked into that and we have many other processes that run on these
servers.
> I have also read that service pack 4 needs to be installed. Well we moved
> our process to another server with exactly the same configuration and it
ran
> fine on there. Had anybody else ran into this? Any suggestions? All
help
> is appreciated.
> Thanks|||Yes, we ran that and no errors were returned. We also ran it with Allow data
loss and no errors were returned. Like I mentioned below, this is happening
on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
"Jack Vamvas" wrote:
> have you run DBCC CHECKDB to see if there are any errors?
> --
> Jack Vamvas
> __________________________________________________________________
> Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> New article by Jack Vamvas - SQL and Markov Chains -
> www.ciquery.com/articles/art_04.asp
> "Andy" <Andy@.discussions.microsoft.com> wrote in message
> news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > I am getting an error in my DTS logs about a bad page. Here is the exact
> > message.
> >
> > Step Error Description:I/O error (bad page ID) detected during read at
> > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> >
> > We are getting this error on 2 different servers. The process has been
> > running like a champ for years and now we are getting this message. All
> that
> > is running when it errors out is an update statement that is joining 2
> > tables. I have read some about tempdb running into these issues and it
> > suggests that there may be hardware issues. That is not the case as we
> have
> > looked into that and we have many other processes that run on these
> servers.
> > I have also read that service pack 4 needs to be installed. Well we moved
> > our process to another server with exactly the same configuration and it
> ran
> > fine on there. Had anybody else ran into this? Any suggestions? All
> help
> > is appreciated.
> >
> > Thanks
>
>|||Hi Andy,
This is usually caused by the hardware, but if it is happening on two
different hardware systems, it seems like a logical problem in the database.
You probably restored a backup of the database from server to another.
Here is the logical meaning of this error:
http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
HTH
DeeJay Puar
MCDBA
(bad page ID): This message means that the pageID on the page header is not
the expected page that was read from the disk. For example, if SQL Server
2000 provides a file offset for database file 1 that is for logical page 100,
the pageID on the page header for that 8 KB page should be 1:100. If not, the
bad page ID is included in the logical I/O check failure message.
You can read more about it here:
"Andy" wrote:
> Yes, we ran that and no errors were returned. We also ran it with Allow data
> loss and no errors were returned. Like I mentioned below, this is happening
> on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
>
> "Jack Vamvas" wrote:
> > have you run DBCC CHECKDB to see if there are any errors?
> >
> > --
> > Jack Vamvas
> > __________________________________________________________________
> > Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> > SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> > New article by Jack Vamvas - SQL and Markov Chains -
> > www.ciquery.com/articles/art_04.asp
> > "Andy" <Andy@.discussions.microsoft.com> wrote in message
> > news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > > I am getting an error in my DTS logs about a bad page. Here is the exact
> > > message.
> > >
> > > Step Error Description:I/O error (bad page ID) detected during read at
> > > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> > >
> > > We are getting this error on 2 different servers. The process has been
> > > running like a champ for years and now we are getting this message. All
> > that
> > > is running when it errors out is an update statement that is joining 2
> > > tables. I have read some about tempdb running into these issues and it
> > > suggests that there may be hardware issues. That is not the case as we
> > have
> > > looked into that and we have many other processes that run on these
> > servers.
> > > I have also read that service pack 4 needs to be installed. Well we moved
> > > our process to another server with exactly the same configuration and it
> > ran
> > > fine on there. Had anybody else ran into this? Any suggestions? All
> > help
> > > is appreciated.
> > >
> > > Thanks
> >
> >
> >|||I looked into that as well, as I thought I did take a backup. The 2nd server
that it is happening on I created brand new databases before I kicked off the
process and we received the same error, at the same point in the process.
"DeeJay Puar" wrote:
> Hi Andy,
> This is usually caused by the hardware, but if it is happening on two
> different hardware systems, it seems like a logical problem in the database.
> You probably restored a backup of the database from server to another.
> Here is the logical meaning of this error:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
> HTH
> DeeJay Puar
> MCDBA
> (bad page ID): This message means that the pageID on the page header is not
> the expected page that was read from the disk. For example, if SQL Server
> 2000 provides a file offset for database file 1 that is for logical page 100,
> the pageID on the page header for that 8 KB page should be 1:100. If not, the
> bad page ID is included in the logical I/O check failure message.
> You can read more about it here:
>
> "Andy" wrote:
> > Yes, we ran that and no errors were returned. We also ran it with Allow data
> > loss and no errors were returned. Like I mentioned below, this is happening
> > on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
> >
> >
> > "Jack Vamvas" wrote:
> >
> > > have you run DBCC CHECKDB to see if there are any errors?
> > >
> > > --
> > > Jack Vamvas
> > > __________________________________________________________________
> > > Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> > > SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> > > New article by Jack Vamvas - SQL and Markov Chains -
> > > www.ciquery.com/articles/art_04.asp
> > > "Andy" <Andy@.discussions.microsoft.com> wrote in message
> > > news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > > > I am getting an error in my DTS logs about a bad page. Here is the exact
> > > > message.
> > > >
> > > > Step Error Description:I/O error (bad page ID) detected during read at
> > > > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> > > >
> > > > We are getting this error on 2 different servers. The process has been
> > > > running like a champ for years and now we are getting this message. All
> > > that
> > > > is running when it errors out is an update statement that is joining 2
> > > > tables. I have read some about tempdb running into these issues and it
> > > > suggests that there may be hardware issues. That is not the case as we
> > > have
> > > > looked into that and we have many other processes that run on these
> > > servers.
> > > > I have also read that service pack 4 needs to be installed. Well we moved
> > > > our process to another server with exactly the same configuration and it
> > > ran
> > > > fine on there. Had anybody else ran into this? Any suggestions? All
> > > help
> > > > is appreciated.
> > > >
> > > > Thanks
> > >
> > >
> > >|||No too sure as to what is happening. I can not really duplicate it here.
On the server, did you take a backup from the old server and restore the
database on the new server? Or did you just create a shell and then ran your
dts package to load the data? Have you looked at the source tables in the DTS
package?
Have you looked into torn-page?
"Andy" wrote:
> I looked into that as well, as I thought I did take a backup. The 2nd server
> that it is happening on I created brand new databases before I kicked off the
> process and we received the same error, at the same point in the process.
> "DeeJay Puar" wrote:
> > Hi Andy,
> >
> > This is usually caused by the hardware, but if it is happening on two
> > different hardware systems, it seems like a logical problem in the database.
> > You probably restored a backup of the database from server to another.
> >
> > Here is the logical meaning of this error:
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
> >
> > HTH
> >
> > DeeJay Puar
> > MCDBA
> >
> > (bad page ID): This message means that the pageID on the page header is not
> > the expected page that was read from the disk. For example, if SQL Server
> > 2000 provides a file offset for database file 1 that is for logical page 100,
> > the pageID on the page header for that 8 KB page should be 1:100. If not, the
> > bad page ID is included in the logical I/O check failure message.
> >
> > You can read more about it here:
> >
> >
> >
> > "Andy" wrote:
> >
> > > Yes, we ran that and no errors were returned. We also ran it with Allow data
> > > loss and no errors were returned. Like I mentioned below, this is happening
> > > on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
> > >
> > >
> > > "Jack Vamvas" wrote:
> > >
> > > > have you run DBCC CHECKDB to see if there are any errors?
> > > >
> > > > --
> > > > Jack Vamvas
> > > > __________________________________________________________________
> > > > Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> > > > SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> > > > New article by Jack Vamvas - SQL and Markov Chains -
> > > > www.ciquery.com/articles/art_04.asp
> > > > "Andy" <Andy@.discussions.microsoft.com> wrote in message
> > > > news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > > > > I am getting an error in my DTS logs about a bad page. Here is the exact
> > > > > message.
> > > > >
> > > > > Step Error Description:I/O error (bad page ID) detected during read at
> > > > > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> > > > >
> > > > > We are getting this error on 2 different servers. The process has been
> > > > > running like a champ for years and now we are getting this message. All
> > > > that
> > > > > is running when it errors out is an update statement that is joining 2
> > > > > tables. I have read some about tempdb running into these issues and it
> > > > > suggests that there may be hardware issues. That is not the case as we
> > > > have
> > > > > looked into that and we have many other processes that run on these
> > > > servers.
> > > > > I have also read that service pack 4 needs to be installed. Well we moved
> > > > > our process to another server with exactly the same configuration and it
> > > > ran
> > > > > fine on there. Had anybody else ran into this? Any suggestions? All
> > > > help
> > > > > is appreciated.
> > > > >
> > > > > Thanks
> > > >
> > > >
> > > >

Bad error message

I just spent 4 hours of frustration, trying to debug a problem with SQL
2000. It was self-inflicted, as it turned out, but I could have fixed
the problem in 5 minutes instead of 4 hours if the @.#%@.#$% error
message:
"String or binary data would be truncated"
would give some CLUES! How about a field name, or even the data that
it's trying to put into the mystery field in some mystery table? And
why not tell me whether it's actually a string or binary data, not
lumping them both together. (I envision a mythical error message that
says "You have caused a numeric overflow, or underflow, or divide by
zero, or there's a key violation, or a trigger is not defined, or the
statement syntax is wrong." Which might be a perfectly correct but not-
helpful error message.)
I was convinced that I was trying to put a single character 'C' into a
field defined as Char(2), and I was tearing my hair out. Aaargh.
The actual Update statement was buried in the guts of a DTS transform,
but this isn't a DTS complaint, it's a SQL error message complaint.
When you try to put a null into a field that can't accept nulls, at
least the error message gives you the name of the field that you're
trying to update. That is infinitely more helpful than this stupid
truncation message. (And I don't want to turn warnings off; in this
case, I was trying to put the wrong value into a different field, so the
error was important -- but I wasn't being pointed to the right place.)
A little help from the error message would be nice.
Hmmm. I wonder if the new upcoming SQL does a better job. I'll have to
ask someone over there.
David Walker
YOu sure have to give us some mistery SQL Query or magic DDL to understand
whats going on, seems that one column is truncated.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"DWalker" <none@.none.com> schrieb im Newsbeitrag
news:OUBF6SnSFHA.3356@.TK2MSFTNGP12.phx.gbl...
>I just spent 4 hours of frustration, trying to debug a problem with SQL
> 2000. It was self-inflicted, as it turned out, but I could have fixed
> the problem in 5 minutes instead of 4 hours if the @.#%@.#$% error
> message:
> "String or binary data would be truncated"
> would give some CLUES! How about a field name, or even the data that
> it's trying to put into the mystery field in some mystery table? And
> why not tell me whether it's actually a string or binary data, not
> lumping them both together. (I envision a mythical error message that
> says "You have caused a numeric overflow, or underflow, or divide by
> zero, or there's a key violation, or a trigger is not defined, or the
> statement syntax is wrong." Which might be a perfectly correct but not-
> helpful error message.)
> I was convinced that I was trying to put a single character 'C' into a
> field defined as Char(2), and I was tearing my hair out. Aaargh.
> The actual Update statement was buried in the guts of a DTS transform,
> but this isn't a DTS complaint, it's a SQL error message complaint.
> When you try to put a null into a field that can't accept nulls, at
> least the error message gives you the name of the field that you're
> trying to update. That is infinitely more helpful than this stupid
> truncation message. (And I don't want to turn warnings off; in this
> case, I was trying to put the wrong value into a different field, so the
> error was important -- but I wasn't being pointed to the right place.)
> A little help from the error message would be nice.
> Hmmm. I wonder if the new upcoming SQL does a better job. I'll have to
> ask someone over there.
>
> David Walker
|||David,
I agree that error less-informative messages as a pain to work with. Did you consider posting to
sqlwish@.microsoft.com on this case?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
|||I figured out my problem, the complaint is that the error message is not
very helpful. I was not looking for more assistance, I was just
complaining about the error message... But thanks!
David
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
in news:#QWpPWnSFHA.1312@.TK2MSFTNGP14.phx.gbl:

> YOu sure have to give us some mistery SQL Query or magic DDL to
> understand whats going on, seems that one column is truncated.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "DWalker" <none@.none.com> schrieb im Newsbeitrag
> news:OUBF6SnSFHA.3356@.TK2MSFTNGP12.phx.gbl...
>
|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in news:uzUDsVnSFHA.3712@.TK2MSFTNGP10.phx.gbl:

> David,
> I agree that error less-informative messages as a pain to work with.
> Did you consider posting to sqlwish@.microsoft.com on this case?
>
I will do that, thanks.
David
|||ok. Gotit. :-)
"DWalker" <none@.none.com> schrieb im Newsbeitrag
news:O763lynSFHA.3176@.TK2MSFTNGP09.phx.gbl...
>I figured out my problem, the complaint is that the error message is not
> very helpful. I was not looking for more assistance, I was just
> complaining about the error message... But thanks!
> David
>
> "Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
> in news:#QWpPWnSFHA.1312@.TK2MSFTNGP14.phx.gbl:
>

Bad error message

I just spent 4 hours of frustration, trying to debug a problem with SQL
2000. It was self-inflicted, as it turned out, but I could have fixed
the problem in 5 minutes instead of 4 hours if the @.#%@.#$% error
message:
"String or binary data would be truncated"
would give some CLUES! How about a field name, or even the data that
it's trying to put into the mystery field in some mystery table? And
why not tell me whether it's actually a string or binary data, not
lumping them both together. (I envision a mythical error message that
says "You have caused a numeric overflow, or underflow, or divide by
zero, or there's a key violation, or a trigger is not defined, or the
statement syntax is wrong." Which might be a perfectly correct but not-
helpful error message.)
I was convinced that I was trying to put a single character 'C' into a
field defined as Char(2), and I was tearing my hair out. Aaargh.
The actual Update statement was buried in the guts of a DTS transform,
but this isn't a DTS complaint, it's a SQL error message complaint.
When you try to put a null into a field that can't accept nulls, at
least the error message gives you the name of the field that you're
trying to update. That is infinitely more helpful than this stupid
truncation message. (And I don't want to turn warnings off; in this
case, I was trying to put the wrong value into a different field, so the
error was important -- but I wasn't being pointed to the right place.)
A little help from the error message would be nice.
Hmmm. I wonder if the new upcoming SQL does a better job. I'll have to
ask someone over there.
David WalkerYOu sure have to give us some mistery SQL Query or magic DDL to understand
whats going on, seems that one column is truncated.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"DWalker" <none@.none.com> schrieb im Newsbeitrag
news:OUBF6SnSFHA.3356@.TK2MSFTNGP12.phx.gbl...
>I just spent 4 hours of frustration, trying to debug a problem with SQL
> 2000. It was self-inflicted, as it turned out, but I could have fixed
> the problem in 5 minutes instead of 4 hours if the @.#%@.#$% error
> message:
> "String or binary data would be truncated"
> would give some CLUES! How about a field name, or even the data that
> it's trying to put into the mystery field in some mystery table? And
> why not tell me whether it's actually a string or binary data, not
> lumping them both together. (I envision a mythical error message that
> says "You have caused a numeric overflow, or underflow, or divide by
> zero, or there's a key violation, or a trigger is not defined, or the
> statement syntax is wrong." Which might be a perfectly correct but not-
> helpful error message.)
> I was convinced that I was trying to put a single character 'C' into a
> field defined as Char(2), and I was tearing my hair out. Aaargh.
> The actual Update statement was buried in the guts of a DTS transform,
> but this isn't a DTS complaint, it's a SQL error message complaint.
> When you try to put a null into a field that can't accept nulls, at
> least the error message gives you the name of the field that you're
> trying to update. That is infinitely more helpful than this stupid
> truncation message. (And I don't want to turn warnings off; in this
> case, I was trying to put the wrong value into a different field, so the
> error was important -- but I wasn't being pointed to the right place.)
> A little help from the error message would be nice.
> Hmmm. I wonder if the new upcoming SQL does a better job. I'll have to
> ask someone over there.
>
> David Walker|||David,
I agree that error less-informative messages as a pain to work with. Did you consider posting to
sqlwish@.microsoft.com on this case?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/|||I figured out my problem, the complaint is that the error message is not
very helpful. I was not looking for more assistance, I was just
complaining about the error message... But thanks!
David
"Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
in news:#QWpPWnSFHA.1312@.TK2MSFTNGP14.phx.gbl:
> YOu sure have to give us some mistery SQL Query or magic DDL to
> understand whats going on, seems that one column is truncated.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "DWalker" <none@.none.com> schrieb im Newsbeitrag
> news:OUBF6SnSFHA.3356@.TK2MSFTNGP12.phx.gbl...
>>I just spent 4 hours of frustration, trying to debug a problem with
>>SQL
>> 2000. It was self-inflicted, as it turned out, but I could have
>> fixed the problem in 5 minutes instead of 4 hours if the @.#%@.#$%
>> error message:
>> "String or binary data would be truncated"
>> would give some CLUES! How about a field name, or even the data that
>> it's trying to put into the mystery field in some mystery table? And
>> why not tell me whether it's actually a string or binary data, not
>> lumping them both together. (I envision a mythical error message
>> that says "You have caused a numeric overflow, or underflow, or
>> divide by zero, or there's a key violation, or a trigger is not
>> defined, or the statement syntax is wrong." Which might be a
>> perfectly correct but not- helpful error message.)
>> I was convinced that I was trying to put a single character 'C' into
>> a field defined as Char(2), and I was tearing my hair out. Aaargh.
>> The actual Update statement was buried in the guts of a DTS
>> transform, but this isn't a DTS complaint, it's a SQL error message
>> complaint.
>> When you try to put a null into a field that can't accept nulls, at
>> least the error message gives you the name of the field that you're
>> trying to update. That is infinitely more helpful than this stupid
>> truncation message. (And I don't want to turn warnings off; in this
>> case, I was trying to put the wrong value into a different field, so
>> the error was important -- but I wasn't being pointed to the right
>> place.)
>> A little help from the error message would be nice.
>> Hmmm. I wonder if the new upcoming SQL does a better job. I'll have
>> to ask someone over there.
>>
>> David Walker
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in news:uzUDsVnSFHA.3712@.TK2MSFTNGP10.phx.gbl:
> David,
> I agree that error less-informative messages as a pain to work with.
> Did you consider posting to sqlwish@.microsoft.com on this case?
>
I will do that, thanks.
David|||ok. Gotit. :-)
"DWalker" <none@.none.com> schrieb im Newsbeitrag
news:O763lynSFHA.3176@.TK2MSFTNGP09.phx.gbl...
>I figured out my problem, the complaint is that the error message is not
> very helpful. I was not looking for more assistance, I was just
> complaining about the error message... But thanks!
> David
>
> "Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
> in news:#QWpPWnSFHA.1312@.TK2MSFTNGP14.phx.gbl:
>> YOu sure have to give us some mistery SQL Query or magic DDL to
>> understand whats going on, seems that one column is truncated.
>> HTH, Jens Suessmeyer.
>> --
>> http://www.sqlserver2005.de
>> --
>> "DWalker" <none@.none.com> schrieb im Newsbeitrag
>> news:OUBF6SnSFHA.3356@.TK2MSFTNGP12.phx.gbl...
>>I just spent 4 hours of frustration, trying to debug a problem with
>>SQL
>> 2000. It was self-inflicted, as it turned out, but I could have
>> fixed the problem in 5 minutes instead of 4 hours if the @.#%@.#$%
>> error message:
>> "String or binary data would be truncated"
>> would give some CLUES! How about a field name, or even the data that
>> it's trying to put into the mystery field in some mystery table? And
>> why not tell me whether it's actually a string or binary data, not
>> lumping them both together. (I envision a mythical error message
>> that says "You have caused a numeric overflow, or underflow, or
>> divide by zero, or there's a key violation, or a trigger is not
>> defined, or the statement syntax is wrong." Which might be a
>> perfectly correct but not- helpful error message.)
>> I was convinced that I was trying to put a single character 'C' into
>> a field defined as Char(2), and I was tearing my hair out. Aaargh.
>> The actual Update statement was buried in the guts of a DTS
>> transform, but this isn't a DTS complaint, it's a SQL error message
>> complaint.
>> When you try to put a null into a field that can't accept nulls, at
>> least the error message gives you the name of the field that you're
>> trying to update. That is infinitely more helpful than this stupid
>> truncation message. (And I don't want to turn warnings off; in this
>> case, I was trying to put the wrong value into a different field, so
>> the error was important -- but I wasn't being pointed to the right
>> place.)
>> A little help from the error message would be nice.
>> Hmmm. I wonder if the new upcoming SQL does a better job. I'll have
>> to ask someone over there.
>>
>> David Walker
>>
>

Bad error message

I just spent 4 hours of frustration, trying to debug a problem with SQL
2000. It was self-inflicted, as it turned out, but I could have fixed
the problem in 5 minutes instead of 4 hours if the @.#%@.#$% error
message:
"String or binary data would be truncated"
would give some CLUES! How about a field name, or even the data that
it's trying to put into the mystery field in some mystery table? And
why not tell me whether it's actually a string or binary data, not
lumping them both together. (I envision a mythical error message that
says "You have caused a numeric overflow, or underflow, or divide by
zero, or there's a key violation, or a trigger is not defined, or the
statement syntax is wrong." Which might be a perfectly correct but not-
helpful error message.)
I was convinced that I was trying to put a single character 'C' into a
field defined as Char(2), and I was tearing my hair out. Aaargh.
The actual Update statement was buried in the guts of a DTS transform,
but this isn't a DTS complaint, it's a SQL error message complaint.
When you try to put a null into a field that can't accept nulls, at
least the error message gives you the name of the field that you're
trying to update. That is infinitely more helpful than this stupid
truncation message. (And I don't want to turn warnings off; in this
case, I was trying to put the wrong value into a different field, so the
error was important -- but I wasn't being pointed to the right place.)
A little help from the error message would be nice.
Hmmm. I wonder if the new upcoming SQL does a better job. I'll have to
ask someone over there.
David WalkerYOu sure have to give us some mistery SQL Query or magic DDL to understand
whats going on, seems that one column is truncated.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"DWalker" <none@.none.com> schrieb im Newsbeitrag
news:OUBF6SnSFHA.3356@.TK2MSFTNGP12.phx.gbl...
>I just spent 4 hours of frustration, trying to debug a problem with SQL
> 2000. It was self-inflicted, as it turned out, but I could have fixed
> the problem in 5 minutes instead of 4 hours if the @.#%@.#$% error
> message:
> "String or binary data would be truncated"
> would give some CLUES! How about a field name, or even the data that
> it's trying to put into the mystery field in some mystery table? And
> why not tell me whether it's actually a string or binary data, not
> lumping them both together. (I envision a mythical error message that
> says "You have caused a numeric overflow, or underflow, or divide by
> zero, or there's a key violation, or a trigger is not defined, or the
> statement syntax is wrong." Which might be a perfectly correct but not-
> helpful error message.)
> I was convinced that I was trying to put a single character 'C' into a
> field defined as Char(2), and I was tearing my hair out. Aaargh.
> The actual Update statement was buried in the guts of a DTS transform,
> but this isn't a DTS complaint, it's a SQL error message complaint.
> When you try to put a null into a field that can't accept nulls, at
> least the error message gives you the name of the field that you're
> trying to update. That is infinitely more helpful than this stupid
> truncation message. (And I don't want to turn warnings off; in this
> case, I was trying to put the wrong value into a different field, so the
> error was important -- but I wasn't being pointed to the right place.)
> A little help from the error message would be nice.
> Hmmm. I wonder if the new upcoming SQL does a better job. I'll have to
> ask someone over there.
>
> David Walker|||David,
I agree that error less-informative messages as a pain to work with. Did you
consider posting to
sqlwish@.microsoft.com on this case?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/|||I figured out my problem, the complaint is that the error message is not
very helpful. I was not looking for more assistance, I was just
complaining about the error message... But thanks!
David
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
in news:#QWpPWnSFHA.1312@.TK2MSFTNGP14.phx.gbl:

> YOu sure have to give us some mistery SQL Query or magic DDL to
> understand whats going on, seems that one column is truncated.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "DWalker" <none@.none.com> schrieb im Newsbeitrag
> news:OUBF6SnSFHA.3356@.TK2MSFTNGP12.phx.gbl...
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in news:uzUDsVnSFHA.3712@.TK2MSFTNGP10.phx.gbl:

> David,
> I agree that error less-informative messages as a pain to work with.
> Did you consider posting to sqlwish@.microsoft.com on this case?
>
I will do that, thanks.
David|||ok. Gotit. :-)
"DWalker" <none@.none.com> schrieb im Newsbeitrag
news:O763lynSFHA.3176@.TK2MSFTNGP09.phx.gbl...
>I figured out my problem, the complaint is that the error message is not
> very helpful. I was not looking for more assistance, I was just
> complaining about the error message... But thanks!
> David
>
> "Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
> in news:#QWpPWnSFHA.1312@.TK2MSFTNGP14.phx.gbl:
>
>

BackupDiskFile::CreateMedia: Backup device failed to create.

Hi there,
I am getting this error message:
BackupDiskFile::CreateMedia: Backup device failed to create. Operating
system error = 1130(Not enough server storage is available to process this
command.).
Someone has already posted this question below.
http://groups.google.com/group/microsoft.public.sqlserver.dts/browse_thread/thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreateMedia%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not+enough+server+storage+is+available+to+process+this+command.).&rnum=1&hl=en#d438e8317739acd8
I checked our security and it is alright. Also, I won't get this error if I
run manually and I am little bit confused.
Could you help?
Thanks.
Abel ChanHello Abel,
First, please make sure you have the latest OS/SQL server service pack.
Also, I found similar issue is resolved by incresae size of IRPStacksize.
Please refer to the following article to test
285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: BackupDiskFile::CreateMedia: Backup device failed to create.
>thread-index: AcYzStfdEVNmKflURjaV99MKSuljqQ==>X-WBNR-Posting-Host: 206.253.218.194
>From: =?Utf-8?B?QWJlbCBDaGFu?= <awong@.newsgroup.nospam>
>Subject: BackupDiskFile::CreateMedia: Backup device failed to create.
>Date: Thu, 16 Feb 2006 14:46:36 -0800
>Lines: 19
>Message-ID: <6155BC54-E793-4FA0-9FF0-B8C03E93F9FF@.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.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:421397
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi there,
>I am getting this error message:
>BackupDiskFile::CreateMedia: Backup device failed to create. Operating
>system error = 1130(Not enough server storage is available to process this
>command.).
>Someone has already posted this question below.
http://groups.google.com/group/microsoft.public.sqlserver.dts/browse_thread/
thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreate
Media%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not
+enough+server+storage+is+available+to+process+this+command.).&rnum=1&hl=en#
d438e8317739acd8
>I checked our security and it is alright. Also, I won't get this error if
I
>run manually and I am little bit confused.
>Could you help?
>Thanks.
>Abel Chan
>

Backup/Restore History Question

This is a multi-part message in MIME format.
--=_NextPart_000_0009_01C4E35E.2D639B30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear to = be orphaned records in the RestoreHistory table. (eg. The = RestoreHistory has a record of the restore as well as a BackupSetID = value, however these values cannot be found in the BackupSet and = BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0009_01C4E35E.2D639B30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi all,

Occasionally, when I perform a RESTORE = on a database,
The msdb tables are not updated = properly.

The RESTORE functions normally, however = when I run a query against the
BackupSet, BackupMediaFamily and = RestoreHistory tables, there appear to be orphaned records in the RestoreHistory = table. (eg. The RestoreHistory has a record of the restore as well as a = BackupSetID value, however these values cannot be found in the BackupSet and BackupMediaFamily tables.


This is a recurring problem, however it = does not happen all of the time.

Do you have any ideas?

TIA


Rick Sawtell
MCT, MCSD, MCDBA


--=_NextPart_000_0009_01C4E35E.2D639B30--This is a multi-part message in MIME format.
--=_NextPart_000_0048_01C4E370.FDF3EB80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Too many drinks I think Rick<g>. Seriously though I have not noticed =this before. Is there any chance there is a job that tries to clean out =the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP

"Rick Sawtell" <quickening@.msn.com> wrote in message =news:e7q53A54EHA.1260@.TK2MSFTNGP12.phx.gbl...
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear =to be orphaned records in the RestoreHistory table. (eg. The =RestoreHistory has a record of the restore as well as a BackupSetID =value, however these values cannot be found in the BackupSet and =BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the =time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0048_01C4E370.FDF3EB80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Too many drinks I think Rick. =Seriously though I have not noticed this before. Is there any chance there is a job =that tries to clean out the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP
"Rick Sawtell" wrote in =message news:e7q53A54EHA.1260=@.TK2MSFTNGP12.phx.gbl...
Hi all,

Occasionally, when I perform a =RESTORE on a database,
The msdb tables are not updated =properly.

The RESTORE functions normally, =however when I run a query against the
BackupSet, BackupMediaFamily and =RestoreHistory tables, there appear to be orphaned records in the RestoreHistory =table. (eg. The RestoreHistory has a record of the restore as well as a =BackupSetID value, however these values cannot be found in the BackupSet and BackupMediaFamily tables.


This is a recurring problem, however =it does not happen all of the time.

Do you have any ideas?

TIA


Rick Sawtell
MCT, MCSD, MCDBA

---

--=_NextPart_000_0048_01C4E370.FDF3EB80--|||This is a multi-part message in MIME format.
--=_NextPart_000_0034_01C4E36D.A1FD50D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
There is that possibility,
I'm still researching it however. This only happens occasionally, so =it is a bit baffling.
I've got 50 or so servers in the hosted environment and only a few of =them are experiencing this problem.
All the servers are the same H/W and S/W, service packs etc.
Win 2k Server, SP4, SQL 2k SP3a etc.
I'll keep you posted, meanwhile if anyone else can think of =anything...
I've got jobs that run after a restore takes place which ensures that =everything in these logs match up (just in case we run into problems =like this. ;-))
Rick
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:uT3Lwr54EHA.4008@.TK2MSFTNGP15.phx.gbl...
Too many drinks I think Rick<g>. Seriously though I have not noticed =this before. Is there any chance there is a job that tries to clean out =the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP

"Rick Sawtell" <quickening@.msn.com> wrote in message =news:e7q53A54EHA.1260@.TK2MSFTNGP12.phx.gbl...
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against =the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear =to be orphaned records in the RestoreHistory table. (eg. The =RestoreHistory has a record of the restore as well as a BackupSetID =value, however these values cannot be found in the BackupSet and =BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the =time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0034_01C4E36D.A1FD50D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

There is that possibility, =
I'm still researching it =however. This only happens occasionally, so it is a bit baffling.
I've got 50 or so servers in the hosted =environment and only a few of them are experiencing this problem.
All the servers are the same H/W and =S/W, service packs etc.
Win 2k Server, SP4, SQL 2k =SP3a etc.
I'll keep you posted, meanwhile =if anyone else can think of anything...
I've got jobs that run after a restore =takes place which ensures that everything in these logs match up (just in case we =run into problems like this. ;-))
Rick
"Andrew J. Kelly" wrote in message news:uT3Lwr54EHA.4008=@.TK2MSFTNGP15.phx.gbl...
Too many drinks I think Rick. =Seriously though I have not noticed this before. Is there any chance there =is a job that tries to clean out the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP
"Rick Sawtell" wrote =in message news:e7q53A54EHA.1260=@.TK2MSFTNGP12.phx.gbl...
Hi all,

Occasionally, when I perform a =RESTORE on a database,
The msdb tables are not updated =properly.

The RESTORE functions normally, =however when I run a query against the
BackupSet, BackupMediaFamily and =RestoreHistory tables, there appear to be orphaned records in the RestoreHistory table. (eg. The RestoreHistory has a record of the restore as =well as a BackupSetID value, however these values cannot be found in the =BackupSet and BackupMediaFamily tables.


This is a recurring problem, =however it does not happen all of the time.

Do you have any ideas?

TIA


Rick Sawtell
MCT, MCSD, MCDBA

---

--=_NextPart_000_0034_01C4E36D.A1FD50D0--

backup/restore from SQL 2000 to SQL 2005: diagram ownership

> This produces an error: 15151
Can you show us the error message and not only the error number?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"david" <david@.discussions.microsoft.com> wrote in message
news:5494E0D2-1097-476A-8C00-45FCE60DA67A@.microsoft.com...
> I have trouble with it. I have tried several ways and talked to some people
> in the forum, but it is not working. The following is waht I did.
> (1) Backup: use Enterprise Manager with COMPLETE backup setup, owners: dbo
> and machine name\my login name.
> (2) Copy backup file to another machine with SQL Server 2005.
> (3) Start SQL Server Management Studio of SQL Server 2005.
> (4) Use Restore to restore the backup to a database.
> (5) Tables, Viewers, and SPs are OK. But Database Diagrams need to further
> work.
> the error massage. I can not either display the diagram or create new
> diagram on the database. The error message:
> "Database diagram support objects cannot be installed because this database
> does not have valid owner.
> To continue, first use the Files page of the Database Properties dialog box
> ot the Alter Authorization statement
> to set the database owner to a valid login, then add the datatbase diagram
> support objects."
> I do not know the detail steps for doing it. In the MSDN, it suggests that
> For compatiable, run
> exec sp_dbcmptlevel 'database_name', '90';
> It is OK for exec.
> For alter authorization, run
> ALTER AUTHORIZATION ON DATABASE::databasename to valid_login
> This produces an error: 15151
> Are there any tricks in backup and restore process?
> Thank you for any help.
> David
>
>
> Should 'valid_login' be a user name?
No, it should be a login name. If you don't know the difference between a login and a user, I
strongly suggest you read up on the subject. Here's a good start:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/5d43fefc-5aa4-43d7-aedb-7808659449c5.htm
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"david" <david@.discussions.microsoft.com> wrote in message
news:6FFF5FBA-3E01-46AC-982C-B60CE88DD66F@.microsoft.com...[vbcol=seagreen]
> Can not find the principal 'valid_login', because it does not exist.
> Should 'valid_login' be a user name?
> How to create a correct user name?
> I created one, and use the username instead of 'valid_login' and got same
> error.
> David
> "Tibor Karaszi" wrote:
|||No, under the server node (the root node), in the security folder.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"david" <david@.discussions.microsoft.com> wrote in message
news:65951F87-DC9D-4CC9-8819-896924752E32@.microsoft.com...[vbcol=seagreen]
> Is a lohin name displayed under security under databases tree node?
> David
> "Tibor Karaszi" wrote:

backup to tape failed

I was trying to do a backup to tape but it failed with the following message:

Msg 3229, Level 16, State 2, Line 2

Request for device '\\.\Tape0' timed out.

Msg 3013, Level 16, State 1, Line 2

BACKUP DATABASE is terminating abnormally.

Any clues why this happened?

Any help is appreciated.

Take a look at the system event log and sql errorlogs.

You may have a hardware issue with the tape drive (or the connection to it...).

If the OS returned an error code to sql server, it will have been logged in the errorlog.

That 3229 is also raised if a tape mount was pending but a new tape was not loaded prior to the timeout. However, that instance should have "state = 1" and not 2 as you report.

|||

Thanks for the help. The problem was with the MEDIANAME. i was specifying a new Medianame.

If MEDIANAME is specified, it must match the previously specified media name already existing on the backup volume.

Thanks Anyways