Error when using rskeymgmt to backup encryption key

When I run the rskeymgmt program to backup the encryption key, I get the
following error:
The Report Server Windows service is not responding to RPC requests. The
service may not be running.
I have checked, and the service is running. We are using SQL Server 2005
sp2. The command I am using is:
rskeymgmt -e -fc:\rskey\rsdbkey.txt -psomepassword
Any ideas why this is failing. I was able to run the program some time ago.
Thanks.On May 2, 11:50 am, "Tim Kelley" <tkel...@.company.com> wrote:
> When I run the rskeymgmt program to backup the encryption key, I get the
> following error:
> The Report Server Windows service is not responding to RPC requests. The
> service may not be running.
> I have checked, and the service is running. We are using SQL Server 2005
> sp2. The command I am using is:
> rskeymgmt -e -fc:\rskey\rsdbkey.txt -psomepassword
> Any ideas why this is failing. I was able to run the program some time ago.
> Thanks.
This link might be helpful:
http://www.technologyone.org/new-6210113-3731.html
Regards,
Enrique Martinez
Sr. Software Consultant

Error when running RedGate SQL Backup Job in SQL Server 2005

I have 4 SQL Server 2005 production servers that I installed RedGate SQL Bac
k
up on. All but one run fine. The one that doesn't I get the below error.
Executed as user : AD-DomainName\UserName. SQL Backup job failed with
exitcode 0 SQL Error code 18456[SQLState 42000] (Error 50000) The step f
ailed.
The back up is backing up to the AD server which is different than the
server the job runs on. It is a shared folder on the AD and the permissions
grant the owner of the job Full Access.
I do not know what else to do with this issue. It mirrors the other 3 that
work fine.
Any and all help is appreciated.
-ChrisChris,
SQL Server caches login information from active directory. The one
troublesome machine has apparently cached out of date AD information. In
David Grey's BLOG he discusses a similar problem (not with Red Gate) that
may help you resolve.
http://www.codefounders.com/communi...entication.aspx
RLF
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:2B7A5543-C258-4BA2-8CF4-BF2A7F4F1434@.microsoft.com...
>I have 4 SQL Server 2005 production servers that I installed RedGate SQL
>Back
> up on. All but one run fine. The one that doesn't I get the below error.
> Executed as user : AD-DomainName\UserName. SQL Backup job failed with
> exitcode 0 SQL Error code 18456[SQLState 42000] (Error 50000) The step
> failed.
> The back up is backing up to the AD server which is different than the
> server the job runs on. It is a shared folder on the AD and the
> permissions
> grant the owner of the job Full Access.
> I do not know what else to do with this issue. It mirrors the other 3 that
> work fine.
> Any and all help is appreciated.
> -Chris
>

Error when running a back up job created n a SQL cluster

Hello,
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
4035). The step failed.
Can anyone help me out on a solution?
may be anything
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/default...b;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:

> Hello,
> I'm haveing a strange problem. When I run a backup off the database without
> making it a schedule job I get a good backup, when I create it as a job and
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
> 4035). The step failed.
> Can anyone help me out on a solution?

Error when running a back up job created n a SQL cluster

Hello,
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQ
LSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for databa
se
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Erro
r
4035). The step failed.
Can anyone help me out on a solution?may be anything
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/defaul...kb;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:

> Hello,
> I'm haveing a strange problem. When I run a backup off the database withou
t
> making it a schedule job I get a good backup, when I create it as a job an
d
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [
;SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for data
base
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Er
ror
> 4035). The step failed.
> Can anyone help me out on a solution?

Error when running a back up job created n a SQL cluster

Hello,
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
4035). The step failed.
Can anyone help me out on a solution?may be anything :)
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:
> Hello,
> I'm haveing a strange problem. When I run a backup off the database without
> making it a schedule job I get a good backup, when I create it as a job and
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
> 4035). The step failed.
> Can anyone help me out on a solution?

Error when Restoring Full Backup with NORECOVERY

I restored a full backup with NORECOVERY because I need to restore the differentials for the week. When I try to restore the differential i receive the following:

System.Data.SqlClient.SqlError: This differential backup cannot be restored because the database has not been restored to the correct earlier state. (Microsoft.SqlServer.Smo)

The database that reads the dbname (Restoring...).

Does anyone know what I need to do?

Thank you in advance.

Julio

I have replied you here.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1896613&SiteID=1

Error when issuing BACKUP LOG mydb with truncate_only

Hi,

Following error appears in the SQL Server error log when I execute BACKUP Log db with truncate_only using a stored procedure. The stored proc I am using is as follows:

CREATE procedure spm_tranlog as

declare @.DBName as Varchar(120)

select @.DBName = DB_name()

dump transaction @.DBName with truncate_only

GO

There are data import processes running in the night, before starting the processes we are executing spm_tranlog procedure to clear the transaction logs. The following error appears in log after executing the spm_tranlog:

“BACKUP failed to complete the command exec spm_tranlog”

This always happens after weekly server maintenance tasks. The scheduled maintenance tasks I am running are:Index rebuild, truncate log and shrinking database. There were no other processes running during that time when the spm_tranlog prodecure fail.

The Database size is 40GB, Log size is 80MB.

The database is in the simple recovery model.The database is in the simple recovery model.

I am running SQL Server 2000 (SP4) on windows server 2003.

Please help me to resolve this issue.

Thanks,

Roshan.

Hello Roshan,

Try this instead:

create procedure spm_tranlog

as

declare @.DBName asvarchar(120), @.sql asvarchar(200)

select @.DBName =DB_name()

select @.sql ='backup log '+ @.DBName +' with truncate_only'

execute(@.sql)
go

Hope this helps.

Jarret

|||

Hi Jarret,

Thanks for your reply. I have changed the DUMP TRANSACTION to BACKUP LOG in my stored proc, but still shows same error message.

Usualy the dump transaction (or Backup Log) fails only when server is backing up databases or shrinking.

My problem is Backup Log satement fails even there are no database backups running. This is really strange.

Thanks,

Roshan.

|||

Can you run the backup log statement directly without getting an error?

backup log DB_Name with truncate_only

Jarret

|||

No. its not allowing me to run the backup log statement directly.

Roshan.

|||

Can you post the error message you are getting and the exact statement you are running?

Are you sure you have permissions to do this? You need to be a sysadmin on the server or in the db_owner role of the database.

Jarret

|||

Hi Jarret,

I am receiving following error in the SQL server log: "BACKUP failed to complete the command exec spm_tranlog"

and I am running following stored proc:

CREATE procedure spm_tranlog as

/* 29/03/2006 RXP: Modified to get the database name using system function
* DB_name(), to avoid hardcoding database name.
*
*/

declare @.DBName as Varchar(120)

select @.DBName = DB_name()
dump transaction @.DBName with truncate_only
GO

This was running perfecctly for a long time, suddenly start creating problems. The user running this proc has sysadmin rights.

Thanks,

Roshan.

|||

How are you running the stored procedure, just 'exec spm_tranlog' from a new query window?

Bypassing the stored procedure, can you try to run this:

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
dump transaction @.DBName with truncate_only

And also...

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
backup log @.DBName with truncate_only

If these still don't work, post the error message(s) you get from each.

Jarret

|||You cant truncate the Log with SIMPLE PLAN in a DB. Because it is doing by itself.

Error when issuing BACKUP LOG mydb with truncate_only

Hi,

Following error appears in the SQL Server error log when I execute BACKUP Log db with truncate_only using a stored procedure. The stored proc I am using is as follows:

CREATE procedure spm_tranlog as

declare @.DBName as Varchar(120)

select @.DBName = DB_name()

dump transaction @.DBName with truncate_only

GO

There are data import processes running in the night, before starting the processes we are executing spm_tranlog procedure to clear the transaction logs. The following error appears in log after executing the spm_tranlog:

“BACKUP failed to complete the command exec spm_tranlog”

This always happens after weekly server maintenance tasks. The scheduled maintenance tasks I am running are:Index rebuild, truncate log and shrinking database. There were no other processes running during that time when the spm_tranlog prodecure fail.

The Database size is 40GB, Log size is 80MB.

The database is in the simple recovery model.The database is in the simple recovery model.

I am running SQL Server 2000 (SP4) on windows server 2003.

Please help me to resolve this issue.

Thanks,

Roshan.

Hello Roshan,

Try this instead:

create procedure spm_tranlog

as

declare @.DBName asvarchar(120), @.sql asvarchar(200)

select @.DBName =DB_name()

select @.sql ='backup log '+ @.DBName +' with truncate_only'

execute(@.sql)
go

Hope this helps.

Jarret

|||

Hi Jarret,

Thanks for your reply. I have changed the DUMP TRANSACTION to BACKUP LOG in my stored proc, but still shows same error message.

Usualy the dump transaction (or Backup Log) fails only when server is backing up databases or shrinking.

My problem is Backup Log satement fails even there are no database backups running. This is really strange.

Thanks,

Roshan.

|||

Can you run the backup log statement directly without getting an error?

backup log DB_Name with truncate_only

Jarret

|||

No. its not allowing me to run the backup log statement directly.

Roshan.

|||

Can you post the error message you are getting and the exact statement you are running?

Are you sure you have permissions to do this? You need to be a sysadmin on the server or in the db_owner role of the database.

Jarret

|||

Hi Jarret,

I am receiving following error in the SQL server log: "BACKUP failed to complete the command exec spm_tranlog"

and I am running following stored proc:

CREATE procedure spm_tranlog as

/* 29/03/2006 RXP: Modified to get the database name using system function
* DB_name(), to avoid hardcoding database name.
*
*/

declare @.DBName as Varchar(120)

select @.DBName = DB_name()
dump transaction @.DBName with truncate_only
GO

This was running perfecctly for a long time, suddenly start creating problems. The user running this proc has sysadmin rights.

Thanks,

Roshan.

|||

How are you running the stored procedure, just 'exec spm_tranlog' from a new query window?

Bypassing the stored procedure, can you try to run this:

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
dump transaction @.DBName with truncate_only

And also...

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
backup log @.DBName with truncate_only

If these still don't work, post the error message(s) you get from each.

Jarret

|||You cant truncate the Log with SIMPLE PLAN in a DB. Because it is doing by itself.

Error when issuing BACKUP LOG mydb with truncate_only

Hi,

Following error appears in the SQL Server error log when I execute BACKUP Log db with truncate_only using a stored procedure. The stored proc I am using is as follows:

CREATE procedure spm_tranlog as

declare @.DBName as Varchar(120)

select @.DBName = DB_name()

dump transaction @.DBName with truncate_only

GO

There are data import processes running in the night, before starting the processes we are executing spm_tranlog procedure to clear the transaction logs. The following error appears in log after executing the spm_tranlog:

“BACKUP failed to complete the command exec spm_tranlog”

This always happens after weekly server maintenance tasks. The scheduled maintenance tasks I am running are:Index rebuild, truncate log and shrinking database. There were no other processes running during that time when the spm_tranlog prodecure fail.

The Database size is 40GB, Log size is 80MB.

The database is in the simple recovery model.The database is in the simple recovery model.

I am running SQL Server 2000 (SP4) on windows server 2003.

Please help me to resolve this issue.

Thanks,

Roshan.

Hello Roshan,

Try this instead:

create procedure spm_tranlog

as

declare @.DBName asvarchar(120), @.sql asvarchar(200)

select @.DBName =DB_name()

select @.sql ='backup log '+ @.DBName +' with truncate_only'

execute(@.sql)
go

Hope this helps.

Jarret

|||

Hi Jarret,

Thanks for your reply. I have changed the DUMP TRANSACTION to BACKUP LOG in my stored proc, but still shows same error message.

Usualy the dump transaction (or Backup Log) fails only when server is backing up databases or shrinking.

My problem is Backup Log satement fails even there are no database backups running. This is really strange.

Thanks,

Roshan.

|||

Can you run the backup log statement directly without getting an error?

backup log DB_Name with truncate_only

Jarret

|||

No. its not allowing me to run the backup log statement directly.

Roshan.

|||

Can you post the error message you are getting and the exact statement you are running?

Are you sure you have permissions to do this? You need to be a sysadmin on the server or in the db_owner role of the database.

Jarret

|||

Hi Jarret,

I am receiving following error in the SQL server log: "BACKUP failed to complete the command exec spm_tranlog"

and I am running following stored proc:

CREATE procedure spm_tranlog as

/* 29/03/2006 RXP: Modified to get the database name using system function
* DB_name(), to avoid hardcoding database name.
*
*/

declare @.DBName as Varchar(120)

select @.DBName = DB_name()
dump transaction @.DBName with truncate_only
GO

This was running perfecctly for a long time, suddenly start creating problems. The user running this proc has sysadmin rights.

Thanks,

Roshan.

|||

How are you running the stored procedure, just 'exec spm_tranlog' from a new query window?

Bypassing the stored procedure, can you try to run this:

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
dump transaction @.DBName with truncate_only

And also...

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
backup log @.DBName with truncate_only

If these still don't work, post the error message(s) you get from each.

Jarret

|||You cant truncate the Log with SIMPLE PLAN in a DB. Because it is doing by itself.sql

Error when issuing BACKUP LOG mydb with truncate_only

Hi,

Following error appears in the SQL Server error log when I execute BACKUP Log db with truncate_only using a stored procedure. The stored proc I am using is as follows:

CREATE procedure spm_tranlog as

declare @.DBName as Varchar(120)

select @.DBName = DB_name()

dump transaction @.DBName with truncate_only

GO

There are data import processes running in the night, before starting the processes we are executing spm_tranlog procedure to clear the transaction logs. The following error appears in log after executing the spm_tranlog:

“BACKUP failed to complete the command exec spm_tranlog”

This always happens after weekly server maintenance tasks. The scheduled maintenance tasks I am running are: Index rebuild, truncate log and shrinking database. There were no other processes running during that time when the spm_tranlog prodecure fail.

The Database size is 40GB, Log size is 80MB.

The database is in the simple recovery model.The database is in the simple recovery model.

I am running SQL Server 2000 (SP4) on windows server 2003.

Please help me to resolve this issue.

Thanks,

Roshan.

Hello Roshan,

Try this instead:

create procedure spm_tranlog

as

declare @.DBName as varchar(120), @.sql as varchar(200)

select @.DBName = DB_name()

select @.sql = 'backup log ' + @.DBName + ' with truncate_only'

execute (@.sql)
go

Hope this helps.

Jarret

|||

Hi Jarret,

Thanks for your reply. I have changed the DUMP TRANSACTION to BACKUP LOG in my stored proc, but still shows same error message.

Usualy the dump transaction (or Backup Log) fails only when server is backing up databases or shrinking.

My problem is Backup Log satement fails even there are no database backups running. This is really strange.

Thanks,

Roshan.

|||

Can you run the backup log statement directly without getting an error?

backup log DB_Name with truncate_only

Jarret

|||

No. its not allowing me to run the backup log statement directly.

Roshan.

|||

Can you post the error message you are getting and the exact statement you are running?

Are you sure you have permissions to do this? You need to be a sysadmin on the server or in the db_owner role of the database.

Jarret

|||

Hi Jarret,

I am receiving following error in the SQL server log: "BACKUP failed to complete the command exec spm_tranlog"

and I am running following stored proc:

CREATE procedure spm_tranlog as

/* 29/03/2006 RXP: Modified to get the database name using system function
* DB_name(), to avoid hardcoding database name.
*
*/

declare @.DBName as Varchar(120)

select @.DBName = DB_name()
dump transaction @.DBName with truncate_only
GO

This was running perfecctly for a long time, suddenly start creating problems. The user running this proc has sysadmin rights.

Thanks,

Roshan.

|||

How are you running the stored procedure, just 'exec spm_tranlog' from a new query window?

Bypassing the stored procedure, can you try to run this:

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
dump transaction @.DBName with truncate_only

And also...

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
backup log @.DBName with truncate_only

If these still don't work, post the error message(s) you get from each.

Jarret

|||You cant truncate the Log with SIMPLE PLAN in a DB. Because it is doing by itself.

Error when executing ALTER DATABASE statement

Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
ALTER DATABASE <Your database name>
SET RECOVERY FULL
but I am getting the following error:
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajesh
It looks like a permission issue. Are you a member of sysadmin, dbcreator
or db_owner?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Rajesh" <Rajesh@.discussions.microsoft.com> wrote in message
news:4EC91AF7-A227-4A52-86F1-C4F0529A8AAD@.microsoft.com...
Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
ALTER DATABASE <Your database name>
SET RECOVERY FULL
but I am getting the following error:
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajesh

Error when executing ALTER DATABASE statement

Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
RajeshIt looks like a permission issue. Are you a member of sysadmin, dbcreator
or db_owner?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Rajesh" <Rajesh@.discussions.microsoft.com> wrote in message
news:4EC91AF7-A227-4A52-86F1-C4F0529A8AAD@.microsoft.com...
Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajesh

Error when executing ALTER DATABASE statement

Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
RajeshIt looks like a permission issue. Are you a member of sysadmin, dbcreator
or db_owner?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Rajesh" <Rajesh@.discussions.microsoft.com> wrote in message
news:4EC91AF7-A227-4A52-86F1-C4F0529A8AAD@.microsoft.com...
Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajeshsql

Error when doing Diff Backup

Hi Everyone,
I'm getting this weird error when doing a differential backup. Does anyone
know what could be the problem or how to fix it? Here is the log text.
================================================== ====================
Job server: WFLEXSQL
Job name: Winflex daily diff.
Job started: Tuesday, May 18, 2004 at 12:05:09 PM
Job type: Backup
Log file: BEX23.txt
================================================== ====================
Consistency checking WINFLEX
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
Consistency checking tables from WINFLEX
Consistency checking PRIMARY
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
Drive and media information from media mount:
Changer Name:
Drive Name: SONY 1
Media Slot: 0
Media Cartridge Label: 4MM000025
Targeted Media Set Name: Media Set 1
================================================== ====================
Job Operation - Backup
Media operation - overwrite.
Hardware compression enabled.
================================================== ====================
Media Name: "Media created 5/18/04 12:09:38 PM"
Backup of "WFLEXSQL "
Backup set #1 on storage media #1
Backup set description: "Winflex daily diff."
Backup Type: DATABASE - Only Back Up Database Changes (Differential)
Backup started on 5/18/04 at 12:09:52 PM.
Backup completed on 5/18/04 at 12:13:44 PM.
Backed up 1 database(s)
Backed up 1 filegroup(s) in 1 database(s)
Processed 1,520,449,536 bytes in 3 minutes and 52 seconds.
Throughput rate: 375.0 MB/min
================================================== ====================
Job Operation - Verify
================================================== ====================
Verify of "WFLEXSQL "
Backup set #1 on storage media #1
Backup set description: "Winflex daily diff."
Verify started on 5/18/04 at 12:14:01 PM.
Verify completed on 5/18/04 at 12:17:15 PM.
Verified 1 database(s)
Processed 1,520,449,536 bytes in 3 minutes and 14 seconds.
Throughput rate: 448.5 MB/min
Consistency checking WINFLEX
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
Consistency checking tables from WINFLEX
Consistency checking PRIMARY
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
================================================== ====================
Job ended: Tuesday, May 18, 2004 at 12:21:39 PM
Job completion status: Failed
================================================== ====================
Thank you in advance! I really appreciate it.
Josh Gerszewski
> Hi Everyone,
> I'm getting this weird error when doing a differential backup. Does anyone
> know what could be the problem or how to fix it? Here is the log text.
> ================================================== ====================
> Job server: WFLEXSQL
> Job name: Winflex daily diff.
> Job started: Tuesday, May 18, 2004 at 12:05:09 PM
> Job type: Backup
> Log file: BEX23.txt
> ================================================== ====================
> Consistency checking WINFLEX
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
> 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
> 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
> Consistency checking tables from WINFLEX
> Consistency checking PRIMARY
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
> 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
> 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
>
> Drive and media information from media mount:
> Changer Name:
> Drive Name: SONY 1
> Media Slot: 0
> Media Cartridge Label: 4MM000025
> Targeted Media Set Name: Media Set 1
> ================================================== ====================
> Job Operation - Backup
> Media operation - overwrite.
> Hardware compression enabled.
> ================================================== ====================
> Media Name: "Media created 5/18/04 12:09:38 PM"
> Backup of "WFLEXSQL "
> Backup set #1 on storage media #1
> Backup set description: "Winflex daily diff."
> Backup Type: DATABASE - Only Back Up Database Changes (Differential)
> Backup started on 5/18/04 at 12:09:52 PM.
> Backup completed on 5/18/04 at 12:13:44 PM.
> Backed up 1 database(s)
> Backed up 1 filegroup(s) in 1 database(s)
> Processed 1,520,449,536 bytes in 3 minutes and 52 seconds.
> Throughput rate: 375.0 MB/min
> ================================================== ====================
> Job Operation - Verify
> ================================================== ====================
> Verify of "WFLEXSQL "
> Backup set #1 on storage media #1
> Backup set description: "Winflex daily diff."
> Verify started on 5/18/04 at 12:14:01 PM.
> Verify completed on 5/18/04 at 12:17:15 PM.
> Verified 1 database(s)
> Processed 1,520,449,536 bytes in 3 minutes and 14 seconds.
> Throughput rate: 448.5 MB/min
> Consistency checking WINFLEX
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
> 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
> 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
> Consistency checking tables from WINFLEX
> Consistency checking PRIMARY
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
> 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
> 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
>
> ================================================== ====================
> Job ended: Tuesday, May 18, 2004 at 12:21:39 PM
> Job completion status: Failed
> ================================================== ====================
> Thank you in advance! I really appreciate it.
> Josh Gerszewski
Hi Josh,
You should run
DBCC CheckDB 'WINFLEX', repair_fast
to fix these errors. For more details, please consult your SQL Server Books
Online.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Error when doing Diff Backup

Hi Everyone,
I'm getting this weird error when doing a differential backup. Does anyone
know what could be the problem or how to fix it? Here is the log text.
====================================================================== Job server: WFLEXSQL
Job name: Winflex daily diff.
Job started: Tuesday, May 18, 2004 at 12:05:09 PM
Job type: Backup
Log file: BEX23.txt
====================================================================== Consistency checking WINFLEX
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode = 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode = 'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
Consistency checking tables from WINFLEX
Consistency checking PRIMARY
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode = 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode = 'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
Drive and media information from media mount:
Changer Name:
Drive Name: SONY 1
Media Slot: 0
Media Cartridge Label: 4MM000025
Targeted Media Set Name: Media Set 1
====================================================================== Job Operation - Backup
Media operation - overwrite.
Hardware compression enabled.
======================================================================
Media Name: "Media created 5/18/04 12:09:38 PM"
Backup of "WFLEXSQL "
Backup set #1 on storage media #1
Backup set description: "Winflex daily diff."
Backup Type: DATABASE - Only Back Up Database Changes (Differential)
Backup started on 5/18/04 at 12:09:52 PM.
Backup completed on 5/18/04 at 12:13:44 PM.
Backed up 1 database(s)
Backed up 1 filegroup(s) in 1 database(s)
Processed 1,520,449,536 bytes in 3 minutes and 52 seconds.
Throughput rate: 375.0 MB/min
---
====================================================================== Job Operation - Verify
======================================================================
Verify of "WFLEXSQL "
Backup set #1 on storage media #1
Backup set description: "Winflex daily diff."
Verify started on 5/18/04 at 12:14:01 PM.
Verify completed on 5/18/04 at 12:17:15 PM.
Verified 1 database(s)
Processed 1,520,449,536 bytes in 3 minutes and 14 seconds.
Throughput rate: 448.5 MB/min
---
Consistency checking WINFLEX
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode = 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode = 'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
Consistency checking tables from WINFLEX
Consistency checking PRIMARY
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode = 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode = 'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
====================================================================== Job ended: Tuesday, May 18, 2004 at 12:21:39 PM
Job completion status: Failed
======================================================================
Thank you in advance! I really appreciate it.
Josh Gerszewski> Hi Everyone,
> I'm getting this weird error when doing a differential backup. Does anyone
> know what could be the problem or how to fix it? Here is the log text.
> ======================================================================> Job server: WFLEXSQL
> Job name: Winflex daily diff.
> Job started: Tuesday, May 18, 2004 at 12:05:09 PM
> Job type: Backup
> Log file: BEX23.txt
> ======================================================================> Consistency checking WINFLEX
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode => 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode => 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
> Consistency checking tables from WINFLEX
> Consistency checking PRIMARY
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode => 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode => 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
>
> Drive and media information from media mount:
> Changer Name:
> Drive Name: SONY 1
> Media Slot: 0
> Media Cartridge Label: 4MM000025
> Targeted Media Set Name: Media Set 1
> ======================================================================> Job Operation - Backup
> Media operation - overwrite.
> Hardware compression enabled.
> ======================================================================> Media Name: "Media created 5/18/04 12:09:38 PM"
> Backup of "WFLEXSQL "
> Backup set #1 on storage media #1
> Backup set description: "Winflex daily diff."
> Backup Type: DATABASE - Only Back Up Database Changes (Differential)
> Backup started on 5/18/04 at 12:09:52 PM.
> Backup completed on 5/18/04 at 12:13:44 PM.
> Backed up 1 database(s)
> Backed up 1 filegroup(s) in 1 database(s)
> Processed 1,520,449,536 bytes in 3 minutes and 52 seconds.
> Throughput rate: 375.0 MB/min
> ---
> ======================================================================> Job Operation - Verify
> ======================================================================> Verify of "WFLEXSQL "
> Backup set #1 on storage media #1
> Backup set description: "Winflex daily diff."
> Verify started on 5/18/04 at 12:14:01 PM.
> Verify completed on 5/18/04 at 12:17:15 PM.
> Verified 1 database(s)
> Processed 1,520,449,536 bytes in 3 minutes and 14 seconds.
> Throughput rate: 448.5 MB/min
> ---
> Consistency checking WINFLEX
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode => 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode => 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
> Consistency checking tables from WINFLEX
> Consistency checking PRIMARY
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode => 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode => 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
>
> ======================================================================> Job ended: Tuesday, May 18, 2004 at 12:21:39 PM
> Job completion status: Failed
> ======================================================================> Thank you in advance! I really appreciate it.
> Josh Gerszewski
--
Hi Josh,
You should run
DBCC CheckDB 'WINFLEX', repair_fast
to fix these errors. For more details, please consult your SQL Server Books
Online.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Error when doing Diff Backup

Hi Everyone,
I'm getting this weird error when doing a differential backup. Does anyone
know what could be the problem or how to fix it? Here is the log text.
========================================
==============================
Job server: WFLEXSQL
Job name: Winflex daily diff.
Job started: Tuesday, May 18, 2004 at 12:05:09 PM
Job type: Backup
Log file: BEX23.txt
========================================
==============================
Consistency checking WINFLEX
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
Consistency checking tables from WINFLEX
Consistency checking PRIMARY
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
Drive and media information from media mount:
Changer Name:
Drive Name: SONY 1
Media Slot: 0
Media Cartridge Label: 4MM000025
Targeted Media Set Name: Media Set 1
========================================
==============================
Job Operation - Backup
Media operation - overwrite.
Hardware compression enabled.
========================================
==============================
Media Name: "Media created 5/18/04 12:09:38 PM"
Backup of "WFLEXSQL "
Backup set #1 on storage media #1
Backup set description: "Winflex daily diff."
Backup Type: DATABASE - Only Back Up Database Changes (Differential)
Backup started on 5/18/04 at 12:09:52 PM.
Backup completed on 5/18/04 at 12:13:44 PM.
Backed up 1 database(s)
Backed up 1 filegroup(s) in 1 database(s)
Processed 1,520,449,536 bytes in 3 minutes and 52 seconds.
Throughput rate: 375.0 MB/min
---
========================================
==============================
Job Operation - Verify
========================================
==============================
Verify of "WFLEXSQL "
Backup set #1 on storage media #1
Backup set description: "Winflex daily diff."
Verify started on 5/18/04 at 12:14:01 PM.
Verify completed on 5/18/04 at 12:17:15 PM.
Verified 1 database(s)
Processed 1,520,449,536 bytes in 3 minutes and 14 seconds.
Throughput rate: 448.5 MB/min
---
Consistency checking WINFLEX
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
Consistency checking tables from WINFLEX
Consistency checking PRIMARY
Consistency Check including Indexes.
There was a problem running the DBCC.
^ ^ ^ ^ ^
SQL Server returned the following error message:
Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
'MEDICAL ') points to the data row identified by ().
^ ^ ^ ^ ^
========================================
==============================
Job ended: Tuesday, May 18, 2004 at 12:21:39 PM
Job completion status: Failed
========================================
==============================
Thank you in advance! I really appreciate it.
Josh Gerszewski> Hi Everyone,
> I'm getting this weird error when doing a differential backup. Does anyone
> know what could be the problem or how to fix it? Here is the log text.
> ========================================
==============================
> Job server: WFLEXSQL
> Job name: Winflex daily diff.
> Job started: Tuesday, May 18, 2004 at 12:05:09 PM
> Job type: Backup
> Log file: BEX23.txt
> ========================================
==============================
> Consistency checking WINFLEX
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
> 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
> 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
> Consistency checking tables from WINFLEX
> Consistency checking PRIMARY
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
> 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
> 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
>
> Drive and media information from media mount:
> Changer Name:
> Drive Name: SONY 1
> Media Slot: 0
> Media Cartridge Label: 4MM000025
> Targeted Media Set Name: Media Set 1
> ========================================
==============================
> Job Operation - Backup
> Media operation - overwrite.
> hardware compression enabled.
> ========================================
==============================
> Media Name: "Media created 5/18/04 12:09:38 PM"
> Backup of "WFLEXSQL "
> Backup set #1 on storage media #1
> Backup set description: "Winflex daily diff."
> Backup Type: DATABASE - Only Back Up Database Changes (Differential)
> Backup started on 5/18/04 at 12:09:52 PM.
> Backup completed on 5/18/04 at 12:13:44 PM.
> Backed up 1 database(s)
> Backed up 1 filegroup(s) in 1 database(s)
> Processed 1,520,449,536 bytes in 3 minutes and 52 seconds.
> Throughput rate: 375.0 MB/min
> ---
> ========================================
==============================
> Job Operation - Verify
> ========================================
==============================
> Verify of "WFLEXSQL "
> Backup set #1 on storage media #1
> Backup set description: "Winflex daily diff."
> Verify started on 5/18/04 at 12:14:01 PM.
> Verify completed on 5/18/04 at 12:17:15 PM.
> Verified 1 database(s)
> Processed 1,520,449,536 bytes in 3 minutes and 14 seconds.
> Throughput rate: 448.5 MB/min
> ---
> Consistency checking WINFLEX
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
> 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
> 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
> Consistency checking tables from WINFLEX
> Consistency checking PRIMARY
> Consistency Check including Indexes.
> There was a problem running the DBCC.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> Index row (1:196847:125) with values (BenefCode = 'MEDICAL ' and CoCode =
> 'GUN ' and EmpNum = '502709265g ' and PlanYear = 2003 and BenefCode =
> 'MEDICAL ') points to the data row identified by ().
>
> ^ ^ ^ ^ ^
>
> ========================================
==============================
> Job ended: Tuesday, May 18, 2004 at 12:21:39 PM
> Job completion status: Failed
> ========================================
==============================
> Thank you in advance! I really appreciate it.
> Josh Gerszewski
--
Hi Josh,
You should run
DBCC CheckDB 'WINFLEX', repair_fast
to fix these errors. For more details, please consult your SQL Server Books
Online.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.sql

Error when creating a backup job

Hello, I'm trying to do a backup of a database by creating a job for it....
I'm entering the command but when I do a Parse to ensure that the syntax is
correct, I'm getting the following error:
"TITLE: Parse Command Text
The following errors were detected in the command text.
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The identifier that starts with 'EXEC sp_addumpdecive 'disk',
'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
backup database WSS_Content to back' is too long. Maximum length is 128.
(Microsoft SQL Server, Error: 103)"
Is that because of the location(
'\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the backup
to?
Please help.....
Thanks
Shelly
Run in the job's step
BACKUP DATABASE dbname TO DISK =
N'\\Server\folder\dbname.BAK'
"Shelley" <Shelley@.discussions.microsoft.com> wrote in message
news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
> Hello, I'm trying to do a backup of a database by creating a job for
> it....
> I'm entering the command but when I do a Parse to ensure that the syntax
> is
> correct, I'm getting the following error:
> "TITLE: Parse Command Text
> --
> The following errors were detected in the command text.
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> The identifier that starts with 'EXEC sp_addumpdecive 'disk',
> 'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
> backup database WSS_Content to back' is too long. Maximum length is 128.
> (Microsoft SQL Server, Error: 103)"
> Is that because of the location(
> '\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the
> backup
> to?
> Please help.....
> Thanks
>
|||HI, ,thank you so much it worked.....
But I would like to know, what is the purose of the "N"?
Also, If i want to overwrite the backup, what do I need to include in the
command?
"Uri Dimant" wrote:

> Shelly
> Run in the job's steps
> BACKUP DATABASE dbname TO DISK =
> N'\\Server\folder\dbname.BAK'
>
> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
>
>
|||Hi, thank you it worked.
However I would like to know what is the purpose of the "N"?
Also, If i want to overwrite the backup, what exactly do I need to include
in the command?
"Uri Dimant" wrote:

> Shelly
> Run in the job's step
> BACKUP DATABASE dbname TO DISK =
> N'\\Server\folder\dbname.BAK'
>
> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
>
>
|||Shelley
1) You do not have to use N.
http://support.microsoft.com/kb/239530
2) Use WITH INIT option of the BACKUP DATABASE command
"Shelley" <Shelley@.discussions.microsoft.com> wrote in message
news:6E0ED4AC-38AA-41C6-916A-E752D62185EF@.microsoft.com...[vbcol=seagreen]
> HI, ,thank you so much it worked.....
> But I would like to know, what is the purose of the "N"?
> Also, If i want to overwrite the backup, what do I need to include in the
> command?
> "Uri Dimant" wrote:
|||Hi, thanks alot..... it worked.
"Uri Dimant" wrote:

> Shelley
> 1) You do not have to use N.
> http://support.microsoft.com/kb/239530
> 2) Use WITH INIT option of the BACKUP DATABASE command
>
> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> news:6E0ED4AC-38AA-41C6-916A-E752D62185EF@.microsoft.com...
>
>
|||N makes the string Unicode.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Shelley" wrote:
[vbcol=seagreen]
> Hi, thank you it worked.
> However I would like to know what is the purpose of the "N"?
> Also, If i want to overwrite the backup, what exactly do I need to include
> in the command?
> "Uri Dimant" wrote:
|||Thank you
"Mohit K. Gupta" wrote:
[vbcol=seagreen]
> N makes the string Unicode.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "Shelley" wrote:

Error when creating a backup job

Hello, I'm trying to do a backup of a database by creating a job for it....
I'm entering the command but when I do a Parse to ensure that the syntax is
correct, I'm getting the following error:
"TITLE: Parse Command Text
--
The following errors were detected in the command text.
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
The identifier that starts with 'EXEC sp_addumpdecive 'disk',
'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
backup database WSS_Content to back' is too long. Maximum length is 128.
(Microsoft SQL Server, Error: 103)"
Is that because of the location(
'\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the backup
to?
Please help.....
ThanksShelly
Run in the job's step
BACKUP DATABASE dbname TO DISK = N'\\Server\folder\dbname.BAK'
"Shelley" <Shelley@.discussions.microsoft.com> wrote in message
news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
> Hello, I'm trying to do a backup of a database by creating a job for
> it....
> I'm entering the command but when I do a Parse to ensure that the syntax
> is
> correct, I'm getting the following error:
> "TITLE: Parse Command Text
> --
> The following errors were detected in the command text.
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> The identifier that starts with 'EXEC sp_addumpdecive 'disk',
> 'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
> backup database WSS_Content to back' is too long. Maximum length is 128.
> (Microsoft SQL Server, Error: 103)"
> Is that because of the location(
> '\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the
> backup
> to?
> Please help.....
> Thanks
>|||HI, ,thank you so much it worked.....
But I would like to know, what is the purose of the "N"?
Also, If i want to overwrite the backup, what do I need to include in the
command?
"Uri Dimant" wrote:
> Shelly
> Run in the job's steps
> BACKUP DATABASE dbname TO DISK => N'\\Server\folder\dbname.BAK'
>
> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
> > Hello, I'm trying to do a backup of a database by creating a job for
> > it....
> >
> > I'm entering the command but when I do a Parse to ensure that the syntax
> > is
> > correct, I'm getting the following error:
> >
> > "TITLE: Parse Command Text
> > --
> >
> > The following errors were detected in the command text.
> >
> > --
> > ADDITIONAL INFORMATION:
> >
> > An exception occurred while executing a Transact-SQL statement or batch.
> > (Microsoft.SqlServer.ConnectionInfo)
> >
> > --
> >
> > The identifier that starts with 'EXEC sp_addumpdecive 'disk',
> > 'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
> > backup database WSS_Content to back' is too long. Maximum length is 128.
> > (Microsoft SQL Server, Error: 103)"
> >
> > Is that because of the location(
> > '\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the
> > backup
> > to?
> >
> > Please help.....
> >
> > Thanks
> >
>
>|||Hi, thank you it worked.
However I would like to know what is the purpose of the "N"?
Also, If i want to overwrite the backup, what exactly do I need to include
in the command?
"Uri Dimant" wrote:
> Shelly
> Run in the job's step
> BACKUP DATABASE dbname TO DISK => N'\\Server\folder\dbname.BAK'
>
> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
> > Hello, I'm trying to do a backup of a database by creating a job for
> > it....
> >
> > I'm entering the command but when I do a Parse to ensure that the syntax
> > is
> > correct, I'm getting the following error:
> >
> > "TITLE: Parse Command Text
> > --
> >
> > The following errors were detected in the command text.
> >
> > --
> > ADDITIONAL INFORMATION:
> >
> > An exception occurred while executing a Transact-SQL statement or batch.
> > (Microsoft.SqlServer.ConnectionInfo)
> >
> > --
> >
> > The identifier that starts with 'EXEC sp_addumpdecive 'disk',
> > 'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
> > backup database WSS_Content to back' is too long. Maximum length is 128.
> > (Microsoft SQL Server, Error: 103)"
> >
> > Is that because of the location(
> > '\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the
> > backup
> > to?
> >
> > Please help.....
> >
> > Thanks
> >
>
>|||Shelley
1) You do not have to use N.
http://support.microsoft.com/kb/239530
2) Use WITH INIT option of the BACKUP DATABASE command
"Shelley" <Shelley@.discussions.microsoft.com> wrote in message
news:6E0ED4AC-38AA-41C6-916A-E752D62185EF@.microsoft.com...
> HI, ,thank you so much it worked.....
> But I would like to know, what is the purose of the "N"?
> Also, If i want to overwrite the backup, what do I need to include in the
> command?
> "Uri Dimant" wrote:
>> Shelly
>> Run in the job's steps
>> BACKUP DATABASE dbname TO DISK =>> N'\\Server\folder\dbname.BAK'
>>
>> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
>> news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
>> > Hello, I'm trying to do a backup of a database by creating a job for
>> > it....
>> >
>> > I'm entering the command but when I do a Parse to ensure that the
>> > syntax
>> > is
>> > correct, I'm getting the following error:
>> >
>> > "TITLE: Parse Command Text
>> > --
>> >
>> > The following errors were detected in the command text.
>> >
>> > --
>> > ADDITIONAL INFORMATION:
>> >
>> > An exception occurred while executing a Transact-SQL statement or
>> > batch.
>> > (Microsoft.SqlServer.ConnectionInfo)
>> >
>> > --
>> >
>> > The identifier that starts with 'EXEC sp_addumpdecive 'disk',
>> > 'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
>> > backup database WSS_Content to back' is too long. Maximum length is
>> > 128.
>> > (Microsoft SQL Server, Error: 103)"
>> >
>> > Is that because of the location(
>> > '\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the
>> > backup
>> > to?
>> >
>> > Please help.....
>> >
>> > Thanks
>> >
>>|||Hi, thanks alot..... it worked.
"Uri Dimant" wrote:
> Shelley
> 1) You do not have to use N.
> http://support.microsoft.com/kb/239530
> 2) Use WITH INIT option of the BACKUP DATABASE command
>
> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> news:6E0ED4AC-38AA-41C6-916A-E752D62185EF@.microsoft.com...
> > HI, ,thank you so much it worked.....
> > But I would like to know, what is the purose of the "N"?
> > Also, If i want to overwrite the backup, what do I need to include in the
> > command?
> >
> > "Uri Dimant" wrote:
> >
> >> Shelly
> >> Run in the job's steps
> >> BACKUP DATABASE dbname TO DISK => >> N'\\Server\folder\dbname.BAK'
> >>
> >>
> >> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> >> news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
> >> > Hello, I'm trying to do a backup of a database by creating a job for
> >> > it....
> >> >
> >> > I'm entering the command but when I do a Parse to ensure that the
> >> > syntax
> >> > is
> >> > correct, I'm getting the following error:
> >> >
> >> > "TITLE: Parse Command Text
> >> > --
> >> >
> >> > The following errors were detected in the command text.
> >> >
> >> > --
> >> > ADDITIONAL INFORMATION:
> >> >
> >> > An exception occurred while executing a Transact-SQL statement or
> >> > batch.
> >> > (Microsoft.SqlServer.ConnectionInfo)
> >> >
> >> > --
> >> >
> >> > The identifier that starts with 'EXEC sp_addumpdecive 'disk',
> >> > 'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
> >> > backup database WSS_Content to back' is too long. Maximum length is
> >> > 128.
> >> > (Microsoft SQL Server, Error: 103)"
> >> >
> >> > Is that because of the location(
> >> > '\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the
> >> > backup
> >> > to?
> >> >
> >> > Please help.....
> >> >
> >> > Thanks
> >> >
> >>
> >>
> >>
>
>|||N makes the string Unicode.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Shelley" wrote:
> Hi, thank you it worked.
> However I would like to know what is the purpose of the "N"?
> Also, If i want to overwrite the backup, what exactly do I need to include
> in the command?
> "Uri Dimant" wrote:
> > Shelly
> > Run in the job's step
> > BACKUP DATABASE dbname TO DISK => > N'\\Server\folder\dbname.BAK'
> >
> >
> > "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> > news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
> > > Hello, I'm trying to do a backup of a database by creating a job for
> > > it....
> > >
> > > I'm entering the command but when I do a Parse to ensure that the syntax
> > > is
> > > correct, I'm getting the following error:
> > >
> > > "TITLE: Parse Command Text
> > > --
> > >
> > > The following errors were detected in the command text.
> > >
> > > --
> > > ADDITIONAL INFORMATION:
> > >
> > > An exception occurred while executing a Transact-SQL statement or batch.
> > > (Microsoft.SqlServer.ConnectionInfo)
> > >
> > > --
> > >
> > > The identifier that starts with 'EXEC sp_addumpdecive 'disk',
> > > 'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
> > > backup database WSS_Content to back' is too long. Maximum length is 128.
> > > (Microsoft SQL Server, Error: 103)"
> > >
> > > Is that because of the location(
> > > '\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the
> > > backup
> > > to?
> > >
> > > Please help.....
> > >
> > > Thanks
> > >
> >
> >
> >|||Thank you
"Mohit K. Gupta" wrote:
> N makes the string Unicode.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "Shelley" wrote:
> > Hi, thank you it worked.
> > However I would like to know what is the purpose of the "N"?
> > Also, If i want to overwrite the backup, what exactly do I need to include
> > in the command?
> >
> > "Uri Dimant" wrote:
> >
> > > Shelly
> > > Run in the job's step
> > > BACKUP DATABASE dbname TO DISK => > > N'\\Server\folder\dbname.BAK'
> > >
> > >
> > > "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> > > news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
> > > > Hello, I'm trying to do a backup of a database by creating a job for
> > > > it....
> > > >
> > > > I'm entering the command but when I do a Parse to ensure that the syntax
> > > > is
> > > > correct, I'm getting the following error:
> > > >
> > > > "TITLE: Parse Command Text
> > > > --
> > > >
> > > > The following errors were detected in the command text.
> > > >
> > > > --
> > > > ADDITIONAL INFORMATION:
> > > >
> > > > An exception occurred while executing a Transact-SQL statement or batch.
> > > > (Microsoft.SqlServer.ConnectionInfo)
> > > >
> > > > --
> > > >
> > > > The identifier that starts with 'EXEC sp_addumpdecive 'disk',
> > > > 'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
> > > > backup database WSS_Content to back' is too long. Maximum length is 128.
> > > > (Microsoft SQL Server, Error: 103)"
> > > >
> > > > Is that because of the location(
> > > > '\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the
> > > > backup
> > > > to?
> > > >
> > > > Please help.....
> > > >
> > > > Thanks
> > > >
> > >
> > >
> > >

Error when creating a backup job

Hello, I'm trying to do a backup of a database by creating a job for it....
I'm entering the command but when I do a Parse to ensure that the syntax is
correct, I'm getting the following error:
"TITLE: Parse Command Text
--
The following errors were detected in the command text.
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The identifier that starts with 'EXEC sp_addumpdecive 'disk',
'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
backup database WSS_Content to back' is too long. Maximum length is 128.
(Microsoft SQL Server, Error: 103)"
Is that because of the location(
'\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the backup
to?
Please help.....
ThanksShelly
Run in the job's step
BACKUP DATABASE dbname TO DISK =
N'\\Server\folder\dbname.BAK'
"Shelley" <Shelley@.discussions.microsoft.com> wrote in message
news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
> Hello, I'm trying to do a backup of a database by creating a job for
> it....
> I'm entering the command but when I do a Parse to ensure that the syntax
> is
> correct, I'm getting the following error:
> "TITLE: Parse Command Text
> --
> The following errors were detected in the command text.
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> The identifier that starts with 'EXEC sp_addumpdecive 'disk',
> 'backup_file1', '\\tcl-fileserver3\backups\moss-weekly\weekly'
> backup database WSS_Content to back' is too long. Maximum length is 128.
> (Microsoft SQL Server, Error: 103)"
> Is that because of the location(
> '\\tcl-fileserver3\backups\moss-weekly\weekly') I am trying to do the
> backup
> to?
> Please help.....
> Thanks
>|||HI, ,thank you so much it worked.....
But I would like to know, what is the purose of the "N"?
Also, If i want to overwrite the backup, what do I need to include in the
command?
"Uri Dimant" wrote:

> Shelly
> Run in the job's steps
> BACKUP DATABASE dbname TO DISK =
> N'\\Server\folder\dbname.BAK'
>
> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
>
>|||Hi, thank you it worked.
However I would like to know what is the purpose of the "N"?
Also, If i want to overwrite the backup, what exactly do I need to include
in the command?
"Uri Dimant" wrote:

> Shelly
> Run in the job's step
> BACKUP DATABASE dbname TO DISK =
> N'\\Server\folder\dbname.BAK'
>
> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> news:17373ED1-5AF5-48BD-9161-0D39F4207BCB@.microsoft.com...
>
>|||Shelley
1) You do not have to use N.
http://support.microsoft.com/kb/239530
2) Use WITH INIT option of the BACKUP DATABASE command
"Shelley" <Shelley@.discussions.microsoft.com> wrote in message
news:6E0ED4AC-38AA-41C6-916A-E752D62185EF@.microsoft.com...[vbcol=seagreen]
> HI, ,thank you so much it worked.....
> But I would like to know, what is the purose of the "N"?
> Also, If i want to overwrite the backup, what do I need to include in the
> command?
> "Uri Dimant" wrote:
>|||Hi, thanks alot..... it worked.
"Uri Dimant" wrote:

> Shelley
> 1) You do not have to use N.
> http://support.microsoft.com/kb/239530
> 2) Use WITH INIT option of the BACKUP DATABASE command
>
> "Shelley" <Shelley@.discussions.microsoft.com> wrote in message
> news:6E0ED4AC-38AA-41C6-916A-E752D62185EF@.microsoft.com...
>
>|||N makes the string Unicode.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Shelley" wrote:
[vbcol=seagreen]
> Hi, thank you it worked.
> However I would like to know what is the purpose of the "N"?
> Also, If i want to overwrite the backup, what exactly do I need to include
> in the command?
> "Uri Dimant" wrote:
>|||Thank you
"Mohit K. Gupta" wrote:
[vbcol=seagreen]
> N makes the string Unicode.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "Shelley" wrote:
>

error when backup transaction log

hi guys,

I'm using sql 2000 and I got this error when I run backup transaction log in maintenence plan.
"The job failed. The Job was invoked by Schedule 38 (Schedule 1). The last step to run was step 1 (Step 1)."

but even it return an error the backup file is created.

please advice.

thanks

There has to be a more detailed error, if you did not choose to log the job execution, try to do this, as this. Otherwiese you will only get this common exception which does not really help very much.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

hi jens,

after I try to backup just 1 database. it went ok.

maybe it because I backup master and msdb also. but I wonder why is my transaction log file is keep on growing ?

should it get truncated everytime the backup is successfull ? either full backup or transaction log backup right

regards,

-dedys