Hi
When I run the reports in my .NET application, I get an error message when I attempt to use .NET remoting while processing a report :
"The type CrystalDecisions.CrystalReports.Engine.FormatEngine in Assembly CrystalDecisions.CrystalReports.Engine, Version=11.2.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304 is not marked as serializable."
I checked the net for solution, and the work around for this error message, use Report Web Services, or the Crystal Enterprise Report Application Server (CE RAS) or Crystal Enterprise (CE) .NET SDK in your application.
But this will be a major change in the application.
Has anybody else got the same error and found a simpler solution ?
Thanking in advanceSee if you find answer here
http://support.businessobjects.com/
Showing posts with label attempt. Show all posts
Showing posts with label attempt. Show all posts
Thursday, March 22, 2012
Wednesday, March 21, 2012
error creating publication
When I am in my publications folder and I attempt to add
a new publication, I get... 'Error 5: [SQL-DMO]Code
Execution exception: EXCEPTION_ACCESS_VIOLATION' after I
click next for the first time. If I click OK in the
error box, there are no publication databases listed.
HELP!!!!
Some times EM gets confused with all the caching it does.
Can you try to create the publication using the stored procedures?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:0af901c48b82$7daf3420$a501280a@.phx.gbl...
> When I am in my publications folder and I attempt to add
> a new publication, I get... 'Error 5: [SQL-DMO]Code
> Execution exception: EXCEPTION_ACCESS_VIOLATION' after I
> click next for the first time. If I click OK in the
> error box, there are no publication databases listed.
> HELP!!!!
>
sql
a new publication, I get... 'Error 5: [SQL-DMO]Code
Execution exception: EXCEPTION_ACCESS_VIOLATION' after I
click next for the first time. If I click OK in the
error box, there are no publication databases listed.
HELP!!!!
Some times EM gets confused with all the caching it does.
Can you try to create the publication using the stored procedures?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:0af901c48b82$7daf3420$a501280a@.phx.gbl...
> When I am in my publications folder and I attempt to add
> a new publication, I get... 'Error 5: [SQL-DMO]Code
> Execution exception: EXCEPTION_ACCESS_VIOLATION' after I
> click next for the first time. If I click OK in the
> error box, there are no publication databases listed.
> HELP!!!!
>
sql
Monday, March 19, 2012
Error Copying from 2000 to 2005
Hello. I'm getting a frustrating error trying to copy a database from SQL
2000 to SQL 2005 using the copy wizard. The attempt fails with two errors in
the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition o
n
Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the error
even after an upgrade to SP1:
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
&&
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
From this link:
http://www.dbtalk.net/microsoft-pub...
-a-165165.html
It would seem that others are also having this issue - but nothing from
Microsoft on it. I'm not sure how to move forward. And yes, I do realize tha
t
Its probably simplier to offline the database and copy the files, but that i
s
not what I want to do. I want to use a feature of the product we purchased.
Has anyone run into and FIXED this issue before.
Thanks!
Errol NealHi
Try RESTORE command
"Errol Neal" <ErrolNeal@.discussions.microsoft.com> wrote in message
news:5F4BA321-C5BB-4427-A6C8-014E1F22995D@.microsoft.com...
> Hello. I'm getting a frustrating error trying to copy a database from SQL
> 2000 to SQL 2005 using the copy wizard. The attempt fails with two errors
> in
> the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition
> on
> Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the
> error
> even after an upgrade to SP1:
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> &&
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> From this link:
> http://www.dbtalk.net/microsoft-pub...0-a-165165.html
> It would seem that others are also having this issue - but nothing from
> Microsoft on it. I'm not sure how to move forward. And yes, I do realize
> that
> Its probably simplier to offline the database and copy the files, but that
> is
> not what I want to do. I want to use a feature of the product we
> purchased.
> Has anyone run into and FIXED this issue before.
> Thanks!
> Errol Neal|||Just an update, if someone is looking for solution:
Make sure SQLServer domain user you are running SQL SERVER on new
server has access to old SQL server. Usually you need to add SQL User
domain account to Local Administrator group on the old server.
2000 to SQL 2005 using the copy wizard. The attempt fails with two errors in
the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition o
n
Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the error
even after an upgrade to SP1:
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
&&
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
From this link:
http://www.dbtalk.net/microsoft-pub...
-a-165165.html
It would seem that others are also having this issue - but nothing from
Microsoft on it. I'm not sure how to move forward. And yes, I do realize tha
t
Its probably simplier to offline the database and copy the files, but that i
s
not what I want to do. I want to use a feature of the product we purchased.
Has anyone run into and FIXED this issue before.
Thanks!
Errol NealHi
Try RESTORE command
"Errol Neal" <ErrolNeal@.discussions.microsoft.com> wrote in message
news:5F4BA321-C5BB-4427-A6C8-014E1F22995D@.microsoft.com...
> Hello. I'm getting a frustrating error trying to copy a database from SQL
> 2000 to SQL 2005 using the copy wizard. The attempt fails with two errors
> in
> the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition
> on
> Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the
> error
> even after an upgrade to SP1:
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> &&
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> From this link:
> http://www.dbtalk.net/microsoft-pub...0-a-165165.html
> It would seem that others are also having this issue - but nothing from
> Microsoft on it. I'm not sure how to move forward. And yes, I do realize
> that
> Its probably simplier to offline the database and copy the files, but that
> is
> not what I want to do. I want to use a feature of the product we
> purchased.
> Has anyone run into and FIXED this issue before.
> Thanks!
> Errol Neal|||Just an update, if someone is looking for solution:
Make sure SQLServer domain user you are running SQL SERVER on new
server has access to old SQL server. Usually you need to add SQL User
domain account to Local Administrator group on the old server.
Error Copying from 2000 to 2005
Hello. I'm getting a frustrating error trying to copy a database from SQL
2000 to SQL 2005 using the copy wizard. The attempt fails with two errors in
the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition on
Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the error
even after an upgrade to SP1:
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
&&
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
From this link:
http://www.dbtalk.net/microsoft-public-sqlserver-dts/error-copying-sql-server-2000-a-165165.html
It would seem that others are also having this issue - but nothing from
Microsoft on it. I'm not sure how to move forward. And yes, I do realize that
Its probably simplier to offline the database and copy the files, but that is
not what I want to do. I want to use a feature of the product we purchased.
Has anyone run into and FIXED this issue before.
Thanks!
Errol NealHi
Try RESTORE command
"Errol Neal" <ErrolNeal@.discussions.microsoft.com> wrote in message
news:5F4BA321-C5BB-4427-A6C8-014E1F22995D@.microsoft.com...
> Hello. I'm getting a frustrating error trying to copy a database from SQL
> 2000 to SQL 2005 using the copy wizard. The attempt fails with two errors
> in
> the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition
> on
> Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the
> error
> even after an upgrade to SP1:
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> &&
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> From this link:
> http://www.dbtalk.net/microsoft-public-sqlserver-dts/error-copying-sql-server-2000-a-165165.html
> It would seem that others are also having this issue - but nothing from
> Microsoft on it. I'm not sure how to move forward. And yes, I do realize
> that
> Its probably simplier to offline the database and copy the files, but that
> is
> not what I want to do. I want to use a feature of the product we
> purchased.
> Has anyone run into and FIXED this issue before.
> Thanks!
> Errol Neal|||Just an update, if someone is looking for solution:
Make sure SQLServer domain user you are running SQL SERVER on new
server has access to old SQL server. Usually you need to add SQL User
domain account to Local Administrator group on the old server.
2000 to SQL 2005 using the copy wizard. The attempt fails with two errors in
the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition on
Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the error
even after an upgrade to SP1:
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
&&
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
From this link:
http://www.dbtalk.net/microsoft-public-sqlserver-dts/error-copying-sql-server-2000-a-165165.html
It would seem that others are also having this issue - but nothing from
Microsoft on it. I'm not sure how to move forward. And yes, I do realize that
Its probably simplier to offline the database and copy the files, but that is
not what I want to do. I want to use a feature of the product we purchased.
Has anyone run into and FIXED this issue before.
Thanks!
Errol NealHi
Try RESTORE command
"Errol Neal" <ErrolNeal@.discussions.microsoft.com> wrote in message
news:5F4BA321-C5BB-4427-A6C8-014E1F22995D@.microsoft.com...
> Hello. I'm getting a frustrating error trying to copy a database from SQL
> 2000 to SQL 2005 using the copy wizard. The attempt fails with two errors
> in
> the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition
> on
> Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the
> error
> even after an upgrade to SP1:
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> &&
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> From this link:
> http://www.dbtalk.net/microsoft-public-sqlserver-dts/error-copying-sql-server-2000-a-165165.html
> It would seem that others are also having this issue - but nothing from
> Microsoft on it. I'm not sure how to move forward. And yes, I do realize
> that
> Its probably simplier to offline the database and copy the files, but that
> is
> not what I want to do. I want to use a feature of the product we
> purchased.
> Has anyone run into and FIXED this issue before.
> Thanks!
> Errol Neal|||Just an update, if someone is looking for solution:
Make sure SQLServer domain user you are running SQL SERVER on new
server has access to old SQL server. Usually you need to add SQL User
domain account to Local Administrator group on the old server.
Sunday, February 19, 2012
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
[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?
>.
>
[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 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?
>.
>
[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?
>.
>
Error attempting restore of full/differential backup
I am running the following script to attempt a restore of a differential backup:
RESTORE DATABASE AdventureWorks
FROM DISK='C:\SQL2005_Backups\AutoBackups\AdventureWorks.bak'
WITH
NORECOVERY
GO
RESTORE DATABASE AdventureWorks
FROM DISK='C:\SQL2005_Backups\AutoBackups\AdventureWorksDiff.bak'
WITH RECOVERY
GO
I thought this was the way to do it. It does restore the full backup, but on the attempt to restore the differential backup, I get the following error:
Msg 3136, Level 16, State 1, Line 1
This differential backup cannot be restored because the database has not been restored to the correct earlier state.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Does anyone know what this means? Do I have to use "with recovery" on the first restore? (The sample I took this from used "with norecovery")
The original backups were done with SQL Agent scheduled jobs. The script for the full backup is:
BACKUP DATABASE AdventureWorks
TO DISK='C:\SQL2005_Backups\AutoBackups\AdventureWorks.bak'
The script for the differential backup is:
BACKUP DATABASE AdventureWorks
TO DISK='C:\SQL2005_Backups\AutoBackups\AdventureWorksDiff.bak'
WITH DIFFERENTIAL, INIT
All I can say is, it's a good thing I am testing this out with non-critical data, because I obviously don't know what I am doing. (Sorry, I'm primarily a programmer, not a DBA) Can anyone help?
Thanks
Are you running SQL 2000 or 2005, because you can't restore AdventureWorks on SQL 2000?|||I am running SQL 2005 -- sorry, forgot to mention.|||I discovered the problem. In my differential backupBACKUP DATABASE AdventureWorks
TO DISK='C:\SQL2005_Backups\AutoBackups\AdventureWorksDiff.bak'
WITH DIFFERENTIAL, INIT
I should not be using "INIT".
I thought that since you just use the last differential backup file, it would make sense to overwrite it every time, so I put in the INIT. However, it doesn't work. You have to have all the differential files saved, even though you only use the last one.
It doesn't make sense to me, but it appears to be the answer, because when I do it that way the restore works.
Subscribe to:
Posts (Atom)