Cannot acces files on database

M

Mille

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel Email Client: pop Ive had a memory collapse on my laptop. And now im having trouble accessing my last database. I can open an older database (security backup) But it refuses to open the newer one. Ive tried rebuilding and verifying and EVERYTHING. It rebuilds - and says the database is fine - and then when i reboot and start entourage - it says Cannot access files on database. Is there anything else i can do??? Im kind of desperate at the moment.

Hope someone can help me!
 
W

William Smith [MVP]

Ive had a memory collapse on my laptop. And now im having trouble
accessing my last database. I can open an older database (security
backup) But it refuses to open the newer one. Ive tried rebuilding
and verifying and EVERYTHING. It rebuilds - and says the database is
fine - and then when i reboot and start entourage - it says Cannot
access files on database. Is there anything else i can do???
Click to expand...

What is a "memory collapse"? What did this do to your machine and what
did you have to do to recover?

What happens when you try to open the Database? Do you receive any error
messages?

Did you have to re-install Office? Is it fully patched up to the version
where your Entourage Database was last saved?

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>
 
M

Mille

One of the memory card failed. I had to &quot;target mode&quot; backup from my harddrive. It had a kernel Panic problem. And start all over again. So YES i had to reinstall ofiice. And I have the databases in the same place as before - user/documents/microsoft user data/office 2008 identities. As i said before i can open an earlier version of the database - without problems. The error i get is: &quot;Cannot access files on database&quot; - when i try with the one i want to open (the latest). Ive even tried with a MUD and then moving the datafrom one folder to the other. Still the same error. It seems like the database is sick. And yet when i rebuild it finds no errors!

HELPPPP!!!!
 
M

Mille

Does it have anything to do with my office identity? I typed another email when i registrered than the old identity?
 
W

William Smith [MVP]

So YES i had to reinstall ofiice. And I have the databases in the
same place as before - user/documents/microsoft user data/office 2008
identities. As i said before i can open an earlier version of the
database - without problems. The error i get is: "Cannot access files
on database" - when i try with the one i want to open (the latest).
Ive even tried with a MUD and then moving the datafrom one folder to
the other. Still the same error. It seems like the database is sick.
And yet when i rebuild it finds no errors!
Click to expand...

Do you really receive a message that says, "Cannot access files on
database"? I've never heard of this message before. The exact message
would be helpful.

Also, you didn't answer one of my other questions: Is Entourage fully
patched up to the version where your Entourage Database was last saved?
Did you completely update Office with all the latest patches?

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>
 
M

Mille

Its exactly what it says. Cannot acces files on database- and try rebuilding the database (which ive done 8 times now) Successfully i might ad. Except for the fact that it doesnt work.....

I updated office... I did the combo update on MAC OS X and i think ive tried everything...

I can find lots of strings on google with same error! But none of the things work...

Is it not possible to &quot;extract&quot; the messages from the file - in any way? Dont you have any TOOLS for this??? As the file doesnt seem &quot;corrupted&quot;?
 
M

Mille

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-12-07 15:56:33 +0100
Application Name: Microsoft Entourage
Application Bundle ID: com.microsoft.Entourage
Application Signature: OPIM
Application Version: 12.2.3.091001
Crashed Module Name: EntourageCore
Crashed Module Version: unknown
Crashed Module Offset: 0x00015ef4
Blame Module Name: EntourageCore
Blame Module Version: unknown
Blame Module Offset: 0x00015ef4
Application LCID: 1030
Extra app info: Reg=en Loc=0x0406

Thread 0 crashed:

# 1 0x0146cef4 in UContactUtils::GetMeContactID() + 0x00000014 (EntourageCore + 0x00015ef4)
# 2 0x00028ac1 in __mh_execute_header + 0x00027AC1 (Microsoft Entourage + 0x00027ac1)
# 3 0x00029df4 in __mh_execute_header + 0x00028DF4 (Microsoft Entourage + 0x00028df4)
# 4 0x0002a439 in __mh_execute_header + 0x00029439 (Microsoft Entourage + 0x00029439)
# 5 0x000152d5 in __mh_execute_header + 0x000142D5 (Microsoft Entourage + 0x000142d5)
# 6 0x0001b110 in __mh_execute_header + 0x0001A110 (Microsoft Entourage + 0x0001a110)
# 7 0x012b770e in LApplication::Run() + 0x0000002C (PowerPlant + 0x0006f70e)
# 8 0x00019ac1 in __mh_execute_header + 0x00018AC1 (Microsoft Entourage + 0x00018ac1)
# 9 0x0000264e in __mh_execute_header + 0x0000164E (Microsoft Entourage + 0x0000164e)
# 10 0x00002575 in __mh_execute_header + 0x00001575 (Microsoft Entourage + 0x00001575)

X86 Thread State:
&nbsp;eax: 0x00000000 ebx: 0x0146ceec ecx: 0x00000002 edx:0xbffff1dc
&nbsp;edi: 0x1c7c8a90 esi: 0x023c1728 ebp: 0xbffff108 esp:0xbffff0f0
&nbsp;&nbsp;ss: 0x0000001f eip: 0x0146cef4 cs: 0x00000017 ds:0x0000001f
&nbsp;&nbsp;es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010286

Thread 1:

# 1 0x905610ea in __dispatch_hw_config + 0x903A4162 (libSystem.B.dylib + 0x000270ea)
# 2 0x90560cc3 in __dispatch_hw_config + 0x903A3D3B (libSystem.B.dylib + 0x00026cc3)
# 3 0x90560a68 in __dispatch_hw_config + 0x903A3AE0 (libSystem.B.dylib + 0x00026a68)
# 4 0x905604f1 in __dispatch_hw_config + 0x903A3569 (libSystem.B.dylib + 0x000264f1)
# 5 0x90560336 in __dispatch_hw_config + 0x903A33AE (libSystem.B.dylib + 0x00026336)

X86 Thread State:
&nbsp;eax: 0x0000016b ebx: 0x9056173e ecx: 0xb0080d5c edx:0x905610ea
&nbsp;edi: 0xa00b01ac esi: 0xb0080ed8 ebp: 0xb0080ef8 esp:0xb0080d5c
&nbsp;&nbsp;ss: 0x0000001f eip: 0x905610ea cs: 0x00000007 ds:0x0000001f
&nbsp;&nbsp;es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000246

Thread 2:

# 1 0x9053a9ee in __dispatch_hw_config + 0x9037DA66 (libSystem.B.dylib + 0x000009ee)
# 2 0x905db12c in __dispatch_hw_config + 0x9041E1A4 (libSystem.B.dylib + 0x000a112c)
# 3 0x021bbd7d in _MerpCreateSession + 0x00000B07 (merp + 0x00002d7d)
# 4 0x021bb3e5 in _MerpCreateSession + 0x0000016F (merp + 0x000023e5)
# 5 0x021bb46c in _MerpCreateSession + 0x000001F6 (merp + 0x0000246c)
# 6 0x021bbf25 in _MerpCreateSession + 0x00000CAF (merp + 0x00002f25)
# 7 0x90567fbd in __dispatch_hw_config + 0x903AB035 (libSystem.B.dylib + 0x0002dfbd)
# 8 0x90567e42 in __dispatch_hw_config + 0x903AAEBA (libSystem.B.dylib + 0x0002de42)

X86 Thread State:
&nbsp;eax: 0xffffffa6 ebx: 0x905c28a0 ecx: 0xb0184a6c edx:0x9053a9ee
&nbsp;edi: 0x00000dfd esi: 0x2130dc6b ebp: 0xb0184ad8 esp:0xb0184a6c
&nbsp;&nbsp;ss: 0x0000001f eip: 0x9053a9ee cs: 0x00000007 ds:0x0000001f
&nbsp;&nbsp;es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000202

Thread 3:

# 1 0x9060255a in __dispatch_hw_config + 0x904455D2 (libSystem.B.dylib + 0x000c855a)
# 2 0x010e3b76 in _FWaitForConnection + 0x0000002A (MicrosoftComponentPlugin + 0x00174b76)
# 3 0x00fefb50 in _McpFInitNetworkPIDChecking + 0x0000111C (MicrosoftComponentPlugin + 0x00080b50)
# 4 0x98b467ae in __gTECMasterGlobals + 0x9881A84A (CarbonCore + 0x000267ae)
# 5 0x90567fbd in __dispatch_hw_config + 0x903AB035 (libSystem.B.dylib + 0x0002dfbd)
# 6 0x90567e42 in __dispatch_hw_config + 0x903AAEBA (libSystem.B.dyl
 
K

Kerry

I've come into this thread a little late but I suspect what's happened
is the memory chip failure may have damaged the Entourage DB and
possibly badly. I see you've scanned the threads and the unfortunately
the Entourage DB is very vulnerable to damage. Thus, back ups are
essential. Rebuilds frequently do not work. It sounds, if I recall
correctly from the thread that you can't even open the DB as the only
thing you can do if it can't be rebuilt is to export your entire DB as
an RGE file and then import that RGE file into a brand new identity.

So am I correct in that you can't open the DB at all. If that's the
case, are you doing regular backups. If so, go to a backup before the
time the chip failed. Restore that and you should be fine.

If you don't have a backup and cannot open the file I think its toast.
I know of no way of getting around this as its a monolithic database
that is also quite complex and that's why Entourage does so much.

Again, to get your DB working and since rebuild doesn't work you need
to be able to open, export it as an RGE file and import it to a new
identity making that your new active identity. Otherwise, you need to
restore prior to the chip failure from a back up.

If you don't back up, now is the time to put into place a good backup
routine. If you don't have one there's lots of suggestions here on
different approaches that can be taken.
 
D

Diane Ross

K

Kerry

[email protected] said:
No i dont think i have.... Any other ideas?
Click to expand...

Can you open another identity. Just choose Entourage switch identities
and see if you can open another - but a good one. If you have no other
identities in the dialogue create a new identity. Does this open. If
it opens its your current active identity that's the problem and its
just severely damaged. If you can't open the new identity then there
is some problem in the Entourage install which is always a possibility.

If uninstalling and re-installing though keeps leading to problems
with Entourage create a test user account and install it there and see
if it works alright. If it does there's a problem in your user account.

My guess is the problem though is this is a corrupted DB and it may
have happened as a result of the memory chip failure which is not
surprising and since you said this is when it all started it adds up.

I'm guessing from your post though you have no backup as you didn't
mention anything about that.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Frequent corruption of large database 1
How to recover mail from damaged database? 1
Database Daemon Fatal Error 5
Backup Database Queries 2
cannot open entourage 1
Entourage database failure after 10.6.3 update 4
winmail.dat files attached 1
Import Entourage X database into 2008 1

Top