Corrupted SQL Files !!!

Hi:

I try to run VB2005 Sample101, "Using Datagridvies" with SQL Express,

Here is what I got !"

"One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. if this
is an existing database, the file may be corrupted and should be restored from a
back up.

Cannot open use default database. Login failed.
Login failed for use 'XXXXXXXXXXX\Administrator"
Lof File 'C:\Program Files\Microsoft SQL Server\MSSQL.1\Data\AdventureWorks_Data_Log.idl' does not match the primary file. It may be from a different database or the log
may have been rebuilt previously."

Then I re attached the Database again. Still the Same problem.

I try other sample that used Northwin and Pubs (SQL2000 ) and attached to

SQLExpress, Well I suffered the SAME PROBLEM.

WHY, Please Help

Thanks

Simon

Try downloading the sample databases from http://www.microsoft.com/downloads/details.aspx?FamilyID=06616212-0356-46a0-8da2-eebc53a68034&DisplayLang=en

Might as well use something you know is working. From the looks of it, you are trying to attach a database and the path may not be the same as the one defined in the metadata of the database file.

|||

I downloaded this Sample and Try Last Nite. The Same Problem. That What I thought initially, I make a new connection and try to run the Sample Again, Well SAME Problem.

Thanks

|||

Hi,

Have you try attaching your sample database with only .MDF file ... while you doing this it will ask you for creating a new for you. But do this carefully / test it on dev server before doing on production server.

|||

Hi,

Have you tried the option i suggest ?

Hemantgiri S. Goswami

|||Could you please post your connection string here ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

SimonOng wrote:

"One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. if this
is an existing database, the file may be corrupted and should be restored from a
back up.

Cannot open use default database. Login failed.
Login failed for use 'XXXXXXXXXXX\Administrator"
Lof File 'C:\Program Files\Microsoft SQL Server\MSSQL.1\Data\AdventureWorks_Data_Log.idl' does not match the primary file. It may be from a different database or the log
may have been rebuilt previously."

Have experienced very similar error.

Have my application on staging server ( non-stop ) and uploaded other one to execute short S. Q. L. script . It finished without errors and I noticed no problems. From once , this shocked me

First I think about concurrent attach by both applications ( it's SQL express ) , but this doesn't sound very reallistic.

Don't want to believe that the database may be destroyed this way . . .|||This is not clear to me, which steps did you actually take ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Corrupted SQL Files !!!

Hi:

I try to run VB2005 Sample101, "Using Datagridvies" with SQL Express,

Here is what I got !"

"One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. if this
is an existing database, the file may be corrupted and should be restored from a
back up.

Cannot open use default database. Login failed.
Login failed for use 'XXXXXXXXXXX\Administrator"
Lof File 'C:\Program Files\Microsoft SQL Server\MSSQL.1\Data\AdventureWorks_Data_Log.idl' does not match the primary file. It may be from a different database or the log
may have been rebuilt previously."

Then I re attached the Database again. Still the Same problem.

I try other sample that used Northwin and Pubs (SQL2000 ) and attached to

SQLExpress, Well I suffered the SAME PROBLEM.

WHY, Please Help

Thanks

Simon

Try downloading the sample databases from http://www.microsoft.com/downloads/details.aspx?FamilyID=06616212-0356-46a0-8da2-eebc53a68034&DisplayLang=en

Might as well use something you know is working. From the looks of it, you are trying to attach a database and the path may not be the same as the one defined in the metadata of the database file.

|||

I downloaded this Sample and Try Last Nite. The Same Problem. That What I thought initially, I make a new connection and try to run the Sample Again, Well SAME Problem.

Thanks

|||

Hi,

Have you try attaching your sample database with only .MDF file ... while you doing this it will ask you for creating a new for you. But do this carefully / test it on dev server before doing on production server.

|||

Hi,

Have you tried the option i suggest ?

Hemantgiri S. Goswami

|||Could you please post your connection string here ?

HTH, Jens K. Suessmeyer.

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

SimonOng wrote:

"One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. if this
is an existing database, the file may be corrupted and should be restored from a
back up.

Cannot open use default database. Login failed.
Login failed for use 'XXXXXXXXXXX\Administrator"
Lof File 'C:\Program Files\Microsoft SQL Server\MSSQL.1\Data\AdventureWorks_Data_Log.idl' does not match the primary file. It may be from a different database or the log
may have been rebuilt previously."

Have experienced very similar error.

Have my application on staging server ( non-stop ) and uploaded other one to execute short S. Q. L. script . It finished without errors and I noticed no problems. From once , this shocked me

First I think about concurrent attach by both applications ( it's SQL express ) , but this doesn't sound very reallistic.

Don't want to believe that the database may be destroyed this way . . .|||This is not clear to me, which steps did you actually take ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Corrupted SQL Files !!!

Hi:

I try to run VB2005 Sample101, "Using Datagridvies" with SQL Express,

Here is what I got !"

"One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. if this
is an existing database, the file may be corrupted and should be restored from a
back up.

Cannot open use default database. Login failed.
Login failed for use 'XXXXXXXXXXX\Administrator"
Lof File 'C:\Program Files\Microsoft SQL Server\MSSQL.1\Data\AdventureWorks_Data_Log.idl' does not match the primary file. It may be from a different database or the log
may have been rebuilt previously."

Then I re attached the Database again. Still the Same problem.

I try other sample that used Northwin and Pubs (SQL2000 ) and attached to

SQLExpress, Well I suffered the SAME PROBLEM.

WHY, Please Help

Thanks

Simon

Try downloading the sample databases from http://www.microsoft.com/downloads/details.aspx?FamilyID=06616212-0356-46a0-8da2-eebc53a68034&DisplayLang=en

Might as well use something you know is working. From the looks of it, you are trying to attach a database and the path may not be the same as the one defined in the metadata of the database file.

|||

I downloaded this Sample and Try Last Nite. The Same Problem. That What I thought initially, I make a new connection and try to run the Sample Again, Well SAME Problem.

Thanks

|||

Hi,

Have you try attaching your sample database with only .MDF file ... while you doing this it will ask you for creating a new for you. But do this carefully / test it on dev server before doing on production server.

|||

Hi,

Have you tried the option i suggest ?

Hemantgiri S. Goswami

|||Could you please post your connection string here ?

HTH, Jens K. Suessmeyer.

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

SimonOng wrote:

"One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. if this
is an existing database, the file may be corrupted and should be restored from a
back up.

Cannot open use default database. Login failed.
Login failed for use 'XXXXXXXXXXX\Administrator"
Lof File 'C:\Program Files\Microsoft SQL Server\MSSQL.1\Data\AdventureWorks_Data_Log.idl' does not match the primary file. It may be from a different database or the log
may have been rebuilt previously."

Have experienced very similar error.

Have my application on staging server ( non-stop ) and uploaded other one to execute short S. Q. L. script . It finished without errors and I noticed no problems. From once , this shocked me

First I think about concurrent attach by both applications ( it's SQL express ) , but this doesn't sound very reallistic.

Don't want to believe that the database may be destroyed this way . . .|||This is not clear to me, which steps did you actually take ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Corrupted PDF in subscriptions

Hi,
I'm actually in trouble with some of my reports. Those reports are randomly
producing corrupted PDF files in subscriptions.
The only way for me to avoid those errors is to remove report caching.
Here is my original post which explains tests i have made and patches i have
applied
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5e36216a-766a-40db-b230-997cdcba97a0
I'm really stuck right now and desesperatly looking for help.
Thanks in advance.
Grégory.What happens if you use the export feature to export the report? Does tha
produce a corrupted file?
What is the error that the Acrobat reader outputs when reading the file?
What version of the report server are you running - are you at SP1?
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Greg - NEOS" <GregNEOS@.discussions.microsoft.com> wrote in message
news:E14E2070-1887-4F69-955A-B1AD0CE8D3FD@.microsoft.com...
> Hi,
> I'm actually in trouble with some of my reports. Those reports are
> randomly
> producing corrupted PDF files in subscriptions.
> The only way for me to avoid those errors is to remove report caching.
> Here is my original post which explains tests i have made and patches i
> have
> applied:
> http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5e36216a-766a-40db-b230-997cdcba97a0
> I'm really stuck right now and desesperatly looking for help.
> Thanks in advance.
> Grégory.|||Hi Lukasz,
When I use export feature, the file isn't corrupted.
The error produced by Acrobat is: "An error happened when opening documents.
The file is corrupted and can't be repared".
I'm actually using Reporting Services SP1.
Best Regards,
Grégory.
"Lukasz Pawlowski [MSFT]" wrote:
> What happens if you use the export feature to export the report? Does tha
> produce a corrupted file?
> What is the error that the Acrobat reader outputs when reading the file?
> What version of the report server are you running - are you at SP1?
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Greg - NEOS" <GregNEOS@.discussions.microsoft.com> wrote in message
> news:E14E2070-1887-4F69-955A-B1AD0CE8D3FD@.microsoft.com...
> > Hi,
> >
> > I'm actually in trouble with some of my reports. Those reports are
> > randomly
> > producing corrupted PDF files in subscriptions.
> > The only way for me to avoid those errors is to remove report caching.
> >
> > Here is my original post which explains tests i have made and patches i
> > have
> > applied:
> > http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5e36216a-766a-40db-b230-997cdcba97a0
> >
> > I'm really stuck right now and desesperatly looking for help.
> >
> > Thanks in advance.
> > Grégory.
>
>

Corrupted MSDE files encountered

This is just to pass on something that caused me a lot of problems until we
(I used a support call) discovered the root cause. I hope someone finds it
helpful.
I ran into a frustrating problem when installing MSDE as a part of two
different application -- Backup Exec and WSUS. I also ran into it when I
downloaded MSDE200A and tried to install it seperately.
Setup would start, load and start to run an msi file, then report it
couldn't find that msi. This happened the same way in the Backup Exec
install, the WSUS install and the MSDE200A install.
After a fresh download the install ran fine. I thought about this, then
realized, and subsequently proved to my satisfaction, the problem only
happened when I downloaded a self-expanding exe file and used Winzip to
expand it to my setup source directories.
When I do this, MSDE setup fails when running a .msi file. If I just
double-click the exe and let it expand itself to a temp directory, the MSDE
setup runs fine. I did this with all three failed setups.
I was using Winzip 8. I don't know if it happens with other versions or not.
I don't know if the problem lies in Winzip or in the compression of MSDE
files and don't have the resouces to find out. I am copying this to WINZIP
and to the MS MSDE forum..
Axel Larson,
Share What You Know,
Learn What You Don't
Thanks for sharing this.
Frank McCallister SBS MVP
COMPUMAC
"Axel" <Axel@.office.Reliasense.com> wrote in message
news:%239mpCW2fFHA.3940@.TK2MSFTNGP14.phx.gbl...
> This is just to pass on something that caused me a lot of problems until
> we
> (I used a support call) discovered the root cause. I hope someone finds it
> helpful.
> I ran into a frustrating problem when installing MSDE as a part of two
> different application -- Backup Exec and WSUS. I also ran into it when I
> downloaded MSDE200A and tried to install it seperately.
> Setup would start, load and start to run an msi file, then report it
> couldn't find that msi. This happened the same way in the Backup Exec
> install, the WSUS install and the MSDE200A install.
> After a fresh download the install ran fine. I thought about this, then
> realized, and subsequently proved to my satisfaction, the problem only
> happened when I downloaded a self-expanding exe file and used Winzip to
> expand it to my setup source directories.
> When I do this, MSDE setup fails when running a .msi file. If I just
> double-click the exe and let it expand itself to a temp directory, the
> MSDE
> setup runs fine. I did this with all three failed setups.
> I was using Winzip 8. I don't know if it happens with other versions or
> not.
> I don't know if the problem lies in Winzip or in the compression of MSDE
> files and don't have the resouces to find out. I am copying this to WINZIP
> and to the MS MSDE forum..
> --
> Axel Larson,
> Share What You Know,
> Learn What You Don't
>

Corrupted Log Backup

Hi..!

Is it possible to recover data from corrupted log backup ?

Suppose we have 10 log files and 8th is corrupted then how can we recover database.

I am not facing such problem right now, but it's a question raised in my mind.

I would like to have your help, suggestions & comments. :rolleyes:

Thanks...Hi..!

Is it possible to recover data from corrupted log backup ?

Suppose we have 10 log files and 8th is corrupted then how can we recover database.

I am not facing such problem right now, but it's a question raised in my mind.

I would like to have your help, suggestions & comments. :rolleyes:

Thanks...

If the 8th log file is corrupt, then you would only be able to recover to the end of the 7th log file. It's (remotely) possible that you might be able to recover to some mid-point within the 8th log file using point-in-time recovery, but I would not count on it.

Personally, I always try to configure my production environment to do nightly full backups of all the databases and hourly transaction logs. I try to keep two full backups on disk, plus enough transaction log files to recover from the oldest full backup. I am now using a backup compression utility which speeds the process and shrinks the files making storage a non-issue. The only exception is a medium-large database that I have (300+ GB) that I backup weekly (storage capacity being the main factor in limiting backup frequency).

Remember to:
1. Practice various recovery scenarios
2. Periodically check the validity/recoverability of various backup media (disk/tape).
3. Write down your recovery strategy and file it away somewhere.

Regards,

hmscott|||Thanks... :)

CORRUPTED BAK files

Please could you help me to determine why a BAK file can be refused by
sql server when calling a recovery process
I Allready have these ideas
- Other version of sql server making BAK file than the recovery one
(or... not a real BAK file !)
- BAK file altered on file system (disk problem...)
- Backup launched without integrity check before / altered database
has been baked up
Is there other possibilities ?
ThksHaving different builds of SQL Server is another reason. Let's say you
backup was created with a SP3 build and is being restored on an instance
with a SP4 build...
http://bassplayerdoc.blogspot.com/2007/10/when-sql-server-backups-cant-be.html
"mrique" <mriquelyon@.gmail.com> wrote in message
news:1193999517.156781.102050@.y42g2000hsy.googlegroups.com...
> Please could you help me to determine why a BAK file can be refused by
> sql server when calling a recovery process
> I Allready have these ideas
> - Other version of sql server making BAK file than the recovery one
> (or... not a real BAK file !)
> - BAK file altered on file system (disk problem...)
> - Backup launched without integrity check before / altered database
> has been baked up
> Is there other possibilities ?
> Thks
>|||> - Backup launched without integrity check before / altered database
> has been baked up
I don't understand this one.
Linchi
"mrique" wrote:
> Please could you help me to determine why a BAK file can be refused by
> sql server when calling a recovery process
> I Allready have these ideas
> - Other version of sql server making BAK file than the recovery one
> (or... not a real BAK file !)
> - BAK file altered on file system (disk problem...)
> - Backup launched without integrity check before / altered database
> has been baked up
> Is there other possibilities ?
> Thks
>