BusinessObjects Board

Cannot open the file due to an unknown error. (FRM0007)

building semantic layer
#1

The universe was imported, worked on locally, and suffered a power failure. After rebooting, I tried re-opening the universe, however Designer does not allow me to open it and gives me a dialog box with error “Cannot open the file due to an unknown error. (FRM0007)”.
I logged in as General supervisor and received the same error.
The unfortunate thing is that I had been saving through out all of the necessary changes and now would like to know if there is a way to recover what I got.
I attempted to re-open the same Unv file in different machines and received the same error.
:confused:

I can still import what is on the repository, but would like to avoid making all of the modifications that I had done previously.

Thanks.

Webi2002 (BOB member since 2002-09-13)

The File is corrupted and cannot be opened. (FRM0003)
FAQ: Reporter
Universe Corrupted
Universe import Error
Unknown Error FRM0007
#2

This happened to me once and another Bobber (then a lister from the listserv) told me to search for temp files created at the time of the crash. I found one. This was a report but same should apply to a universe. The filename wasn’t anything like the name before the crash. I think it ended in tmp though. The time was what helped me locate it. HTH!

Cindy Clayton :us: (BOB member since 2002-06-11)

#3

just had a power outage resulting in this error. did a search for files of approximately the same size of the corrupt Universe file, found one in the temp files with a funky name like 07a654, renamed, and it opened up fine. Saved it as the original Universe name and went on my merry way.

just wanted to provide a success story - thanks.

jswoboda :us: (BOB member since 2002-06-20)

#4

The process worked great!!!

Thanks. :smiley:

Webi2002 (BOB member since 2002-09-13)

#5

Felt good didn’t it? Nice to have one of those saves every now and then…a near disaster averted by tip from BOB :mrgreen: .

Cindy Clayton :us: (BOB member since 2002-06-11)

#6

You’d think BOB would have told us not to get involved with databases in the first place… :lol:

#7

Having same problem, only I didn’t have a crash and I thought that I close Designer down gracefully. Can’t find file in temp directory. When I try to reimport universe, I get a message which says that I must close the universe first. But of course I can’t because I can’t open it.
Any ideas?

rodk (BOB member since 2004-05-28)

#8

Have you searched for all local copies of the problem .unv file?

jswoboda :us: (BOB member since 2002-06-20)

#9

I am having the same issue, my virtual machine crashed and am getting told my universe file is corrupt but am getting (FRM0003), when trying to open the tmp files created at the time of the crash they don’t open via designer or give an error they just start processing and then never come back.

James Head :uk: (BOB member since 2005-02-14)

#10

Hi,
i have had the same problem.
BO 6.5.1
windows 2000

all my attemp were mistakes (delete temporary files, local univers, etc …)

the only one thing i manage to resolve definitely the pb of the FRM00007 message is to delete the local user NT profile and reboot the computer.

after rebooting and open a NT session, all the Bo params are re-initialised and my pb fixed :lol:

have a nice day .

nlebeau :fr: (BOB member since 2005-06-20)

#11

Hi all Just look for same file size in your documents and settings <Windows user>\Local settings folder\XXXXXXXX.tmp a hidden file created while last saved time copy it and rename it with your universe name .UNV . (Do a search for the created date and file size with hidden archived in Local settings ).
Regards,
Vajravelu Annamalai

vajra (BOB member since 2005-11-19)

#12

What do we do if the report uses multiple Data providers with Linked Universe? What Universename.unv must the file be saved as then?

at&t (BOB member since 2007-04-05)

#13

this even worked on a report which got corrupted when BO crashed.
thanks a lot

puru (BOB member since 2010-01-06)

#14

encountered this problem today using BO XI R2: problem was due to limited free disk space on file server, from which the user tried to open the file …

copying the file(s) to a location with sufficient free disk space solved the problem.

mirko (BOB member since 2002-08-21)