Showing posts with label write. Show all posts
Showing posts with label write. Show all posts

Thursday, March 22, 2012

error during backup

when a database backup is tried to be taken to the hard disk it gives a
error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.bak'
failed, status =112". The path was changed several times and checked the
same error message was occurring.
Any Clues?
Regards
Sunil Pinto
Hi
Some entry in the ERROR LOG file?
"Sunil Pinto" <SunilPinto@.hotmail.com> wrote in message
news:elnTTAPtEHA.2688@.TK2MSFTNGP14.phx.gbl...
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\****.bak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>
|||Sunil,
You've run out of disk space. Check how much space is available on your
drives by executing
exec master..xp_fixeddrives
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sunil Pinto wrote:
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.bak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>

error during backup

when a database backup is tried to be taken to the hard disk it gives a
error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.bak
'
failed, status =112". The path was changed several times and checked the
same error message was occurring.
Any Clues?
Regards
Sunil PintoHi
Some entry in the ERROR LOG file?
"Sunil Pinto" <SunilPinto@.hotmail.com> wrote in message
news:elnTTAPtEHA.2688@.TK2MSFTNGP14.phx.gbl...
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\****.bak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>|||Sunil,
You've run out of disk space. Check how much space is available on your
drives by executing
exec master..xp_fixeddrives
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sunil Pinto wrote:
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.b
ak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>

error during backup

when a database backup is tried to be taken to the hard disk it gives a
error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.bak'
failed, status =112". The path was changed several times and checked the
same error message was occurring.
Any Clues?
Regards
Sunil PintoHi
Some entry in the ERROR LOG file?
"Sunil Pinto" <SunilPinto@.hotmail.com> wrote in message
news:elnTTAPtEHA.2688@.TK2MSFTNGP14.phx.gbl...
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\****.bak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>|||Sunil,
You've run out of disk space. Check how much space is available on your
drives by executing
exec master..xp_fixeddrives
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sunil Pinto wrote:
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.bak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>

Friday, March 9, 2012

error connecting to sql 2k from an app

Hi,
I rec'd this error.
open dbtables error: General error: Unable to write to file buffer dbtest.
when I connect to a sql 2k db from an test app.
Any ideas?
thanksCan you show the code that is trying to connect? This doesn't look like a
SQL Server error as far as I can tell.
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OMglZPIPGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I rec'd this error.
> open dbtables error: General error: Unable to write to file buffer dbtest.
> when I connect to a sql 2k db from an test app.
> Any ideas?
> thanks
>|||I don't really have the source code.
I think the same as you--windows' problem.
Everytime the app runs it generated a temp file > 2GB.
I have no idea why the temp file gets generated when the app sends a query
statment.
That is the problem
Thanks,
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:uwrjxcIPGHA.344@.TK2MSFTNGP11.phx.gbl...
> Can you show the code that is trying to connect? This doesn't look like a
> SQL Server error as far as I can tell.
>
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OMglZPIPGHA.1676@.TK2MSFTNGP09.phx.gbl...
>

Friday, February 24, 2012

Error catching in SSIS

I have a package that is failing parsing a CSV file. I want to write the failing line to an error file and continue processing. I've added error output to the flat file source, that didn't work. I've added an onerror event handler to the data flow task, that didn't work. I've added an event handler to the package, that didn't work. How can i output the offending line but not have the process fail?

Go to the Error Output page on the Flat File Source editor and set appropriate Error and Truncation values to Redirect. After this connect your error output to a Flat file destination where you can take care of erroneous rows.

Thanks,

Bob

|||Thanks, but that isn't it. I've got it set to redirect. The error is

Error: 0xC0202055 at Data Flow Task, Flat File Source [1]: The column delimiter for column "Column 3" was not found.

It is being caused by an embeded double quote in the source CSV file. It's escaped to "" and the parser blows up. It dosent go to the error output. and i can't seem to catch the error, it kills the process.

|||

The flat file parser cannot handle embedded quotes. You will have to load qualified data and post-process it using script or derived columns.

Thanks,

Bob

Error catching in SSIS

I have a package that is failing parsing a CSV file. I want to write the failing line to an error file and continue processing. I've added error output to the flat file source, that didn't work. I've added an onerror event handler to the data flow task, that didn't work. I've added an event handler to the package, that didn't work. How can i output the offending line but not have the process fail?

Go to the Error Output page on the Flat File Source editor and set appropriate Error and Truncation values to Redirect. After this connect your error output to a Flat file destination where you can take care of erroneous rows.

Thanks,

Bob

|||Thanks, but that isn't it. I've got it set to redirect. The error is

Error: 0xC0202055 at Data Flow Task, Flat File Source [1]: The column delimiter for column "Column 3" was not found.

It is being caused by an embeded double quote in the source CSV file. It's escaped to "" and the parser blows up. It dosent go to the error output. and i can't seem to catch the error, it kills the process.

|||

The flat file parser cannot handle embedded quotes. You will have to load qualified data and post-process it using script or derived columns.

Thanks,

Bob