Error executing sp_change_users_login

Hello -
Hello, i'm trying to run
Exec sp_change_Users_login 'report'
From a few databases on my servers. When I try to execute,=20
i'm receiving the following error message:
=AB Server: Msg 15289, Level 16, State 1, Procedure=20
sp_change_users_login, Line 27
Terminating this procedure. Cannot have an open=20
transaction when this is
run.=BB
Here's the code i'm trying to execute:
=AB=20
if exists (select * from dbo.sysobjects where id =3D=20
object_id(N'[dbo].[OutputOrphanUsers]') and OBJECTPROPERTY
(id, N'IsUserTable') =3D 1)
drop table [dbo].[OutputOrphanUsers]
go
create table OutputOrphanUsers=20
(uname varchar(30),
usid varbinary(85))
go
insert OutputOrphanUsers EXEC=20
sp_change_users_login 'Report'=BB
I hope that you can help me, i cant found any workarround=20
to this situation.
Best regerdsI'm not sure there is a workaround... I tried hiding the query in openrowset
and that didn't work either... ie
insert OutputOrphanUsers select a.* FROM
OPENROWSET('SQLOLEDB','servername';'logi
n';'password',
'exec sp_change_users_login report') AS a
Actually what you could do is get the source... in master sp_helptest
sp_change_users_login and change the code that requires no transaction (but
only if the parameter is report. Then re-add it as a different name. The
common naming convention would be sp__change_users_login (2 underscores
after sp).
That will work.
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:153ed01c4157e$e99d76d0$a101280a@.phx
.gbl...
Hello -
Hello, i'm trying to run
Exec sp_change_Users_login 'report'
From a few databases on my servers. When I try to execute,
i'm receiving the following error message:
Server: Msg 15289, Level 16, State 1, Procedure
sp_change_users_login, Line 27
Terminating this procedure. Cannot have an open
transaction when this is
run.
Here's the code i'm trying to execute:
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[OutputOrphanUsers]') and OBJECTPROPERTY
(id, N'IsUserTable') = 1)
drop table [dbo].[OutputOrphanUsers]
go
create table OutputOrphanUsers
(uname varchar(30),
usid varbinary(85))
go
insert OutputOrphanUsers EXEC
sp_change_users_login 'Report'
I hope that you can help me, i cant found any workarround
to this situation.
Best regerds

Error executing Backup

Hello,
I've configure "HP Omniback" to perform backups on databases servers under the account "omni_acc", when i configured this account i assign this account the "System Administrators" Server Role because i can=B4t did backups if the account wasn=B4t assign to this role.
Now i want to give to the omni_acc account other previleges since we have the "db_backupoperator" database role but... i cant do the backups if the user is only assign to this role. Can anybody explain to me this situation?
Is not supposed that a user assign to the "db_backupoperator" database role perform backups and restores to databases?
How can i give permissions to a user to make backups and restores of databases?
Best regardsFor RESTORE you cannot use db_backup operator if the database doesn't exist, as ... the database doesn't
exist! In this case, dbcreator server role should do.
Your problem is very likely that HP wrote their software so it requires this permissions. The place to start
is the documentation for the software. If there is no, ask the vendor of the software (HP).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message news:1919d01c44c8f$47eb8c30$a501280a@.phx.gbl...
Hello,
I've configure "HP Omniback" to perform backups on
databases servers under the account "omni_acc", when i
configured this account i assign this account the "System
Administrators" Server Role because i can´t did backups if
the account wasn´t assign to this role.
Now i want to give to the omni_acc account other
previleges since we have the "db_backupoperator" database
role but... i cant do the backups if the user is only
assign to this role. Can anybody explain to me this
situation?
Is not supposed that a user assign to
the "db_backupoperator" database role perform backups and
restores to databases?
How can i give permissions to a user to make backups and
restores of databases?
Best regards

Error during Full-text population

I'm using Full-text in various databases on my servers (SQL2005 on W2K3). On a few databases the Full-text population ends with the error:

'Error '0x80030050' occurred during full-text index population for table or indexed view '[database].[dbo].[table]' (table or indexed view ID '1714105147', database ID '9'), full-text key value 0x00015EE1. Failed to index the row.'

The next log-line lets me know the name of the dll that caused the problem:

The component 'offfilt.dll' reported error while indexing. Component path 'C:\WINDOWS\system32\offfilt.dll'.

There's one solution I read about, but that one is not the case here. That sollution states that this problem occurs when de datatype is not the same as the filetype (e.g. datatype is pdf, documenttype is doc).

What can be the problem here?

Thanks.

I'm getting the same error in a multitude of environments (XP Pro (development/test environment), Windows Server 2003). SQL Server 2005 SP1 has been applied. Also getting on XP Pro system with SP2 applied. However, the OFFFILT.DLL appears to be part of the OS and not SQL Server. The version on my XP Pro is 2003.5.28.0 and is dated 2004-08-04.

I think the problem is with Word (.doc) files as I don't appear to have any problems indexing PowerPoint (.ppt) files.

|||

It sounds like the Microsoft Office Indexing filter DLL is choking on an unrecognised file format. Might you have some very old Word documents in the table, or conversely if there are new Word 2007 documents in there might these be too new?

|||In my case (not the original poster) the files that it is choking on are valid Microsoft Word documents. The documents can be opened in Office 2003. We are avoiding Office 2007 for now. Not every document has a problem. So it is something (style, font, property, ?) in the document that is tripping it up.|||

Ok, it took some time, but here it is:

I had some word-documents with embedded object that were unkown to Word. So I deleted them from the documents. All messages with the error in the original post are gone now. There is however a 'known bug' in Full Text Catalogue (I got the information from Microsoft) which will be patched in SP3. If the Full Text Index is being used very frequent (I'm not sure if that is 500 times a second or 5000000 times...) it gets corrupted.

A few tips here:

Make sure the dll's concerning FTC are in place. You can use this query to see which dll's FTE is using:

select * from sys.fulltext_document_types

Make sure there are no unkown objects in your documents. The error produced, if so, contains a HEX-number which represents the id-column value of the table. You can transform it to a more usable number with this query:

select * from [table] where [id-column] in (cast([HEX-number] as int))

If all this is ok, it's getting more likely that you have the 'known-bug' issue at hand.

Error during Full-text population

I'm using Full-text in various databases on my servers (SQL2005 on W2K3). On a few databases the Full-text population ends with the error:

'Error '0x80030050' occurred during full-text index population for table or indexed view '[database].[dbo].[table]' (table or indexed view ID '1714105147', database ID '9'), full-text key value 0x00015EE1. Failed to index the row.'

The next log-line lets me know the name of the dll that caused the problem:

The component 'offfilt.dll' reported error while indexing. Component path 'C:\WINDOWS\system32\offfilt.dll'.

There's one solution I read about, but that one is not the case here. That sollution states that this problem occurs when de datatype is not the same as the filetype (e.g. datatype is pdf, documenttype is doc).

What can be the problem here?

Thanks.

I'm getting the same error in a multitude of environments (XP Pro (development/test environment), Windows Server 2003). SQL Server 2005 SP1 has been applied. Also getting on XP Pro system with SP2 applied. However, the OFFFILT.DLL appears to be part of the OS and not SQL Server. The version on my XP Pro is 2003.5.28.0 and is dated 2004-08-04.

I think the problem is with Word (.doc) files as I don't appear to have any problems indexing PowerPoint (.ppt) files.

|||

It sounds like the Microsoft Office Indexing filter DLL is choking on an unrecognised file format. Might you have some very old Word documents in the table, or conversely if there are new Word 2007 documents in there might these be too new?

|||In my case (not the original poster) the files that it is choking on are valid Microsoft Word documents. The documents can be opened in Office 2003. We are avoiding Office 2007 for now. Not every document has a problem. So it is something (style, font, property, ?) in the document that is tripping it up.|||

Ok, it took some time, but here it is:

I had some word-documents with embedded object that were unkown to Word. So I deleted them from the documents. All messages with the error in the original post are gone now. There is however a 'known bug' in Full Text Catalogue (I got the information from Microsoft) which will be patched in SP3. If the Full Text Index is being used very frequent (I'm not sure if that is 500 times a second or 5000000 times...) it gets corrupted.

A few tips here:

Make sure the dll's concerning FTC are in place. You can use this query to see which dll's FTE is using:

select * from sys.fulltext_document_types

Make sure there are no unkown objects in your documents. The error produced, if so, contains a HEX-number which represents the id-column value of the table. You can transform it to a more usable number with this query:

select * from [table] where [id-column] in (cast([HEX-number] as int))

If all this is ok, it's getting more likely that you have the 'known-bug' issue at hand.

Error during Full-text population

I'm using Full-text in various databases on my servers (SQL2005 on W2K3). On a few databases the Full-text population ends with the error:

'Error '0x80030050' occurred during full-text index population for table or indexed view '[database].[dbo].[table]' (table or indexed view ID '1714105147', database ID '9'), full-text key value 0x00015EE1. Failed to index the row.'

The next log-line lets me know the name of the dll that caused the problem:

The component 'offfilt.dll' reported error while indexing. Component path 'C:\WINDOWS\system32\offfilt.dll'.

There's one solution I read about, but that one is not the case here. That sollution states that this problem occurs when de datatype is not the same as the filetype (e.g. datatype is pdf, documenttype is doc).

What can be the problem here?

Thanks.

I'm getting the same error in a multitude of environments (XP Pro (development/test environment), Windows Server 2003). SQL Server 2005 SP1 has been applied. Also getting on XP Pro system with SP2 applied. However, the OFFFILT.DLL appears to be part of the OS and not SQL Server. The version on my XP Pro is 2003.5.28.0 and is dated 2004-08-04.

I think the problem is with Word (.doc) files as I don't appear to have any problems indexing PowerPoint (.ppt) files.

|||

It sounds like the Microsoft Office Indexing filter DLL is choking on an unrecognised file format. Might you have some very old Word documents in the table, or conversely if there are new Word 2007 documents in there might these be too new?

|||In my case (not the original poster) the files that it is choking on are valid Microsoft Word documents. The documents can be opened in Office 2003. We are avoiding Office 2007 for now. Not every document has a problem. So it is something (style, font, property, ?) in the document that is tripping it up.|||

Ok, it took some time, but here it is:

I had some word-documents with embedded object that were unkown to Word. So I deleted them from the documents. All messages with the error in the original post are gone now. There is however a 'known bug' in Full Text Catalogue (I got the information from Microsoft) which will be patched in SP3. If the Full Text Index is being used very frequent (I'm not sure if that is 500 times a second or 5000000 times...) it gets corrupted.

A few tips here:

Make sure the dll's concerning FTC are in place. You can use this query to see which dll's FTE is using:

select * from sys.fulltext_document_types

Make sure there are no unkown objects in your documents. The error produced, if so, contains a HEX-number which represents the id-column value of the table. You can transform it to a more usable number with this query:

select * from [table] where [id-column] in (cast([HEX-number] as int))

If all this is ok, it's getting more likely that you have the 'known-bug' issue at hand.

Error during Copy Database Wizard operation

Do anyone know why i got "Failed to create the share OMWWIZD" error message when trying to copy databases from SQL Server 7.0 to SQL Server 2000?
Thanks!Probably something to do with security permissions between the two servers. If so, pick an administrative account which is the same on both. Run the wizard as that account. Test access by logging into one server and map a drive to the other.

--jfp|||Thanks for the suggestion! I tried using a domain admin to copy the database over and it works! I was using a local admin account before to establish the connection.

Thanks again.

--Speedster.|||hi

I have the same problem but i'm in workstation ...
i used Administrator account in the source server and the destination server, but it doesn't work :eek:

What can i do ?|||- quoting "hi I have the same problem but i'm in workstation ...
i used Administrator account in the source server and the destination server, but it doesn't work What can i do ?"

asanhaji, are you accessing it from a windows workstation via Enterprise Manger? Is it possible to be at one of the servers locally and try to copy it over? Unless you are a logged into the workstation with a domain admin account OR connect to the server in Enterprise manager with a domain admin account you may not have any luck in copying the stuff over. You may need to connect to both servers using a DBO account (typically sa is the user name for it).

slashman

Error copying databases in SQL Server 2005

How does one copy databases in SQLServer 2005?

I am trying to copy a database from one instance of SQLServer 2005 to another instance of SQLServer 2005 using the SQL Server Management Studio Copy Database Wizard. The source database is a continuously updatable database, while the destination database is used for reporting purposes.

When the wizard tries to create a SSIS package (as part of Copy Database), I get the following error:

While trying to find a folder on SQL an OLE DB error was encountered with error code 0x80004005 ([DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.)

The details have additional message:
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.FolderExistsOnSqlServer(String strFolderName, String strServerName, String strServerUserName, String strServerPassword)
at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.EnsurePackageFolderExist(String folderName, Application app, String serverName, String loginName, String password)
at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()

=============================================

While trying to find a folder on SQL an OLE DB error was encountered with error code 0x80004005 ([DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.)
-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.FolderExistsOnSQLServer(String bstrFolderName, String bstrServerName, String bstrServerUserName, String bstrServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.FolderExistsOnSqlServer(String strFolderName, String strServerName, String strServerUserName, String strServerPassword)

Hi

Copy database wizard is similar to EXPORT/IMPORT wizard of SQL Server 2000. There are new features in SQL Server 2005 for your scenario. You can use Database Mirroring, create a Snapshot on mirrored database for viewing data and can use for reporting services.|||Hi Jason,
This was a known problem in the past that should be working fine with the next CTP release. Right now, your best bet is to detach the database, copy to the destination, and then reattach it. You'll then need to copy recreate your logins at the destination to match with your users.
Thank you,
Bill Ramos

Error ConnectionRead (WrapperRead())

Hi
When I ran the ran the backups of my databases I ahve the next error
ConnectionRead (WrapperRead()). [SQLSTATE 01000]
Msg 11, Sev 16: General network error. Check your network documentation.
[SQLSTATE 08S01]
I’m running windows2000 Server Standard Edition, SQL2000 Server Standard
Edition and MDAC2.6 version.
I found the article 827452 but this article
APPLIES TO
? Microsoft Data Access Components 2.8
? Microsoft SQL Server 2000 Standard Edition, when used with:
Microsoft Windows Server 2003, Standard Edition
Microsoft Windows 2000 Enterprise Edition
I want to know if this article applies for my case
I run the sproc for backup the databases
Thanks very much
See http://support.microsoft.com/default...b;en-us;827452
Adrian
"Valero" <Valero@.discussions.microsoft.com> wrote in message
news:DEE2A24E-F805-4E56-BDD6-265C6A217912@.microsoft.com...
> Hi
> When I ran the ran the backups of my databases I ahve the next error
> ConnectionRead (WrapperRead()). [SQLSTATE 01000]
> Msg 11, Sev 16: General network error. Check your network documentation.
> [SQLSTATE 08S01]
>
> I'm running windows2000 Server Standard Edition, SQL2000 Server Standard
> Edition and MDAC2.6 version.
> I found the article 827452 but this article
> APPLIES TO
> . Microsoft Data Access Components 2.8
> . Microsoft SQL Server 2000 Standard Edition, when used with:
> Microsoft Windows Server 2003, Standard Edition
> Microsoft Windows 2000 Enterprise Edition
> I want to know if this article applies for my case
> I run the sproc for backup the databases
> Thanks very much
>

Error ConnectionRead (WrapperRead())

Hi
When I ran the ran the backups of my databases I ahve the next error
ConnectionRead (WrapperRead()). [SQLSTATE 01000]
Msg 11, Sev 16: General network error. Check your network documentation.
[SQLSTATE 08S01]
Iâ'm running windows2000 Server Standard Edition, SQL2000 Server Standard
Edition and MDAC2.6 version.
I found the article 827452 but this article
APPLIES TO
â?¢ Microsoft Data Access Components 2.8
â?¢ Microsoft SQL Server 2000 Standard Edition, when used with:
Microsoft Windows Server 2003, Standard Edition
Microsoft Windows 2000 Enterprise Edition
I want to know if this article applies for my case
I run the sproc for backup the databases
Thanks very muchSee http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
Adrian
"Valero" <Valero@.discussions.microsoft.com> wrote in message
news:DEE2A24E-F805-4E56-BDD6-265C6A217912@.microsoft.com...
> Hi
> When I ran the ran the backups of my databases I ahve the next error
> ConnectionRead (WrapperRead()). [SQLSTATE 01000]
> Msg 11, Sev 16: General network error. Check your network documentation.
> [SQLSTATE 08S01]
>
> I'm running windows2000 Server Standard Edition, SQL2000 Server Standard
> Edition and MDAC2.6 version.
> I found the article 827452 but this article
> APPLIES TO
> . Microsoft Data Access Components 2.8
> . Microsoft SQL Server 2000 Standard Edition, when used with:
> Microsoft Windows Server 2003, Standard Edition
> Microsoft Windows 2000 Enterprise Edition
> I want to know if this article applies for my case
> I run the sproc for backup the databases
> Thanks very much
>

Error ConnectionRead (WrapperRead())

Hi
When I ran the ran the backups of my databases I ahve the next error
ConnectionRead (WrapperRead()). [SQLSTATE 01000]
Msg 11, Sev 16: General network error. Check your network documentation.
[SQLSTATE 08S01]
I’m running windows2000 Server Standard Edition, SQL2000 Server Standard
Edition and MDAC2.6 version.
I found the article 827452 but this article
APPLIES TO
? Microsoft Data Access Components 2.8
? Microsoft SQL Server 2000 Standard Edition, when used with:
Microsoft Windows Server 2003, Standard Edition
Microsoft Windows 2000 Enterprise Edition
I want to know if this article applies for my case
I run the sproc for backup the databases
Thanks very muchSee http://support.microsoft.com/defaul...kb;en-us;827452
Adrian
"Valero" <Valero@.discussions.microsoft.com> wrote in message
news:DEE2A24E-F805-4E56-BDD6-265C6A217912@.microsoft.com...
> Hi
> When I ran the ran the backups of my databases I ahve the next error
> ConnectionRead (WrapperRead()). [SQLSTATE 01000]
> Msg 11, Sev 16: General network error. Check your network documentation.
> [SQLSTATE 08S01]
>
> I'm running windows2000 Server Standard Edition, SQL2000 Server Standard
> Edition and MDAC2.6 version.
> I found the article 827452 but this article
> APPLIES TO
> . Microsoft Data Access Components 2.8
> . Microsoft SQL Server 2000 Standard Edition, when used with:
> Microsoft Windows Server 2003, Standard Edition
> Microsoft Windows 2000 Enterprise Edition
> I want to know if this article applies for my case
> I run the sproc for backup the databases
> Thanks very much
>

Error backing up Transaction Logs

This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN' is incorrectly formed. SQL Server cannot process this media fami
ly.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a worka
round which involves setting the trace flag to 3111, but that didn't seem to make a difference either.
Ideas?
What is the actual backup command your using?
Andrew J. Kelly SQL MVP
"Garrett Taylor" <gtaylor@.westerntitle.net> wrote in message
news:1049DD05-2DBF-499D-AE0F-C263FAB62C90@.microsoft.com...
> This is the error I get for the database named, "NoteServe4005". I get
this error for all databases whether I attempt to backup manually or
automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination:
[c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC
SQL Server Driver][SQL Server]The media family on device
'c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating
abnormally.
> I searched support for the error pulling up only KB:297104 which says that
this can happen when transaction log files exceed 4GB. However, the T-Log in
this example is only 50MB. It also says the error is fixed by SP1 and I have
SP3a. There's also a workaround which involves setting the trace flag to
3111, but that didn't seem to make a difference either.
> Ideas?
|||I'm running it from Enterprise Manager both as a scheduled
job and manually.

>--Original Message--
>What is the actual backup command your using?
>--
>Andrew J. Kelly SQL MVP
>
>"Garrett Taylor" <gtaylor@.westerntitle.net> wrote in
message[vbcol=seagreen]
>news:1049DD05-2DBF-499D-AE0F-C263FAB62C90@.microsoft.com...
named, "NoteServe4005". I get
>this error for all databases whether I attempt to backup
manually or
>automatically.
>[c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN][vbcol=seagreen]
[Microsoft][ODBC
>SQL Server Driver][SQL Server]The media family on device
>'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly[vbcol=seagreen]
>formed. SQL Server cannot process this media family.
LOG is terminating[vbcol=seagreen]
>abnormally.
KB:297104 which says that
>this can happen when transaction log files exceed 4GB.
However, the T-Log in
>this example is only 50MB. It also says the error is
fixed by SP1 and I have
>SP3a. There's also a workaround which involves setting
the trace flag to
>3111, but that didn't seem to make a difference either.
>
>.
>
|||You might want to give MS PSS a call.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Garrett Taylor" <gtaylor@.westerntitle.net> wrote in message
news:95f101c43380$92fb9c10$a301280a@.phx.gbl...[vbcol=seagreen]
> I'm running it from Enterprise Manager both as a scheduled
> job and manually.
> message
> named, "NoteServe4005". I get
> manually or
> \NoteServe4005_tlog_200405041500.TRN]
> [Microsoft][ODBC
> \NoteServe4005_tlog_200405041500.TRN' is incorrectly
> LOG is terminating
> KB:297104 which says that
> However, the T-Log in
> fixed by SP1 and I have
> the trace flag to

Error backing up Transaction Logs

This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup..
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN' is incorrectly formed. SQL Server cannot process this media family
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a workaround which involves setting the trace flag to 3111, but that didn't seem to make a difference either
IdeasIf this file "c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN" exists, delete it.Make sure that you also have sufficient disk space to store the new backup(s). HTH
-- Garrett Taylor wrote: --
This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup..
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN' is incorrectly formed. SQL Server cannot process this media family
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a workaround which involves setting the trace flag to 3111, but that didn't seem to make a difference either
Ideas|||The file doesn't already exist and I have more than 50GB
free where my transaction file is only 50MB.
>--Original Message--
>If this file "c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN" exists, delete
it.Make sure that you also have sufficient disk space to
store the new backup(s). HTH.
> -- Garrett Taylor wrote: --
> This is the error I get for the database
named, "NoteServe4005". I get this error for all databases
whether I attempt to backup manually or automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination: [c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error
3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The
media family on device 'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]
BACKUP LOG is terminating abnormally.
> I searched support for the error pulling up only
KB:297104 which says that this can happen when transaction
log files exceed 4GB. However, the T-Log in this example
is only 50MB. It also says the error is fixed by SP1 and I
have SP3a. There's also a workaround which involves
setting the trace flag to 3111, but that didn't seem to
make a difference either.
> Ideas?
>.
>

Error backing up Transaction Logs

This is the error I get for the database named, "NoteServe4005". I get this
error for all databases whether I attempt to backup manually or automaticall
y.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: & #91;c:\backup\NoteServe4005\NoteServe400
5_tlog_200405041500.TR
N]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft]&#
91;ODBC SQL Server Driver][SQL Server]The media family on device 'c:\bac
kup\NoteServe4005\NoteServe4005_tlog_200
405041500.TRN' is incorrectly formed
. SQL Server cannot process this media fami
ly.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is ter
minating abnormally.
I searched support for the error pulling up only KB:297104 which says that t
his can happen when transaction log files exceed 4GB. However, the T-Log in
this example is only 50MB. It also says the error is fixed by SP1 and I have
SP3a. There's also a worka
round which involves setting the trace flag to 3111, but that didn't seem to
make a difference either.
Ideas?If this file " c:\backup\NoteServe4005\NoteServe4005_tl
og_200405041500.TRN" e
xists, delete it.Make sure that you also have sufficient disk space to store
the new backup(s). HTH.
-- Garrett Taylor wrote: --
This is the error I get for the database named, "NoteServe4005". I get this
error for all databases whether I attempt to backup manually or automaticall
y.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: & #91;c:\backup\NoteServe4005\NoteServe400
5_tlog_200405041500.TR
N]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft]&#
91;ODBC SQL Server Driver][SQL Server]The media family on device 'c:\bac
kup\NoteServe4005\NoteServe4005_tlog_200
405041500.TRN' is incorrectly formed
. SQL Server cannot process this media
family.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is ter
minating abnormally.
I searched support for the error pulling up only KB:297104 which says that t
his can happen when transaction log files exceed 4GB. However, the T-Log in
this example is only 50MB. It also says the error is fixed by SP1 and I have
SP3a. There's also a
workaround which involves setting the trace flag to 3111, but that didn't se
em to make a difference either.
Ideas?|||The file doesn't already exist and I have more than 50GB
free where my transaction file is only 50MB.

>--Original Message--
>If this file "c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN" exists, delete
it.Make sure that you also have sufficient disk space to
store the new backup(s). HTH.
> -- Garrett Taylor wrote: --
> This is the error I get for the database
named, "NoteServe4005". I get this error for all databases
whether I attempt to backup manually or automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination: [c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error
3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The
media family on device 'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]
BACKUP LOG is terminating abnormally.
> I searched support for the error pulling up only
KB:297104 which says that this can happen when transaction
log files exceed 4GB. However, the T-Log in this example
is only 50MB. It also says the error is fixed by SP1 and I
have SP3a. There's also a workaround which involves
setting the trace flag to 3111, but that didn't seem to
make a difference either.
> Ideas?
>.
>

Error backing up Transaction Logs

This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN' is incorrectly formed. SQL Server cannot process this media fami
ly.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a worka
round which involves setting the trace flag to 3111, but that didn't seem to make a difference either.
Ideas?
If this file "c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN" exists, delete it.Make sure that you also have sufficient disk space to store the new backup(s). HTH.
-- Garrett Taylor wrote: --
This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN' is incorrectly formed. SQL Server cannot process this media
family.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a
workaround which involves setting the trace flag to 3111, but that didn't seem to make a difference either.
Ideas?
|||The file doesn't already exist and I have more than 50GB
free where my transaction file is only 50MB.

>--Original Message--
>If this file "c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN" exists, delete
it.Make sure that you also have sufficient disk space to
store the new backup(s). HTH.
> -- Garrett Taylor wrote: --
> This is the error I get for the database
named, "NoteServe4005". I get this error for all databases
whether I attempt to backup manually or automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination: [c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error
3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The
media family on device 'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]
BACKUP LOG is terminating abnormally.
> I searched support for the error pulling up only
KB:297104 which says that this can happen when transaction
log files exceed 4GB. However, the T-Log in this example
is only 50MB. It also says the error is fixed by SP1 and I
have SP3a. There's also a workaround which involves
setting the trace flag to 3111, but that didn't seem to
make a difference either.
> Ideas?
>.
>