Unable to open access database (application hanging) following migration

[NAP50]

Dear all,



I have recently migrated some access tables

From:
32bit Windows server 2003 Enterprise Edition
Service Pack 2
Access 2003
8GB Ram

To:
Access 2010
64bit Windows Server 2008 R2 Standard (Virtual Server)
Service Pack 1
Access 2010
6.GB Ram

Unfortunately recently when I attempt to open them, the MSACCESS window goes white and reads (Access 2000 file format)(Not Responding).

The databases contain numerous liked tables, if I access these is design view I can view the data they contain. I'm Unsure if the problem might therefore be to do
with queries rather than the tables.

I really have no idea where to start trying to resolve this issue, has anyone ever encountered this and if so what did you do? At first they did work ok with the occasional one crashing but as of today I can no longer seem to open any of them at all.

In event viewer I have the following access errors:

Faulting application name: MSACCESS.EXE, version: 14.0.7153.5000, time stamp: 0x5581e7ca
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000417
Fault offset: 0x000320f0
Faulting process id: 0x7e8
Faulting application start time: 0x01d0d13ae1793001
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a 1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR 90.dll

&

The program MSACCESS.EXE version 14.0.7153.5000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check
the problem history in the Action Center control panel.
Process ID: 1600
Start Time: 01d0d3467126f05d
Termination Time: 62
Application Path: C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE

[John_G]

Does this happen with all your databases, or just one?

My first thought is a bad install of MS Access 2010. Do you have another machine running A2010 you can try the migrated databases on?

[NAP50]

It doesn't happen to all the databases, but to the vast majority at the moment.

I am going to try it on a different machine running A2010 to see if this makes a difference anyway. Thank you for your input.

[John_G]

I should have mentioned that if the converted databases still don't run on a different machine, you should try the A2003 - A2010 conversion on a different machine as well; it could be the conversion process has a problem.

[NAP50]

Thanks John, at present I have left them in 2003 format. It was a case of taking them off the 2003 server and running them in A2003 format using A2010 - hope this makes sense.

I did also try creating a new A2010 document importing everything from 2003 document (just to see if it would resolve things) but the problem remained.

[NAP50]

- I attempted to run on another machine with A2010 (Windows 7 machine), setup the ODBC connections accordingly and the same things happens. The databases just crash upon opening. Do you think recent security patching could have impacted on this?

[John_G]

We're getting a bit over my head on the technical stuff here, but why do you need to set up ODBC connections? If you are able to create links to the tables in the external databases, then that should be all you need, because you can see the data as expected when you open them.

You could try to unlink/relink all the external tables.

[ItsMe]

Unfortunately recently when I attempt to open them, the MSACCESS window goes white and reads (Access 2000 file format)(Not Responding).

When I see this I ask myself how you migrated the tables from a previous version of Access to Access 2010. I have heard of some issues with Server 2008 and a particular SP but I would not concern myself with the server. I am guessing there was an upgrade of the DB at the same time the DB files were migrated to the new server.

I suspect that you did an upgrade and the new file format that defaulted was an earlier version of Access. Another thing that may have happened is you imported/upgraded an incompatible feature/macro.

If you upgraded the DB files to A2010, try doing the upgrade again. This time, create a new file using A2010. With that file open and saved, create new links to any tables that you may need. Do a compact and repair. Then, import objects from the original db file(s) using the Wizard. Use the Advanced options in the Import Wizard.

[Micron]

If you also went to a 64 bit version of Office, that could be your problem. AFAIK, any recent version of Access will run in 64 bit Windows, but not in 64 bit Office.

[NAP50]

Dear all, thank you for your valued input, all your suggestions helped narrow things down. After recreating some of the tables in 2010 format (rather than 2003) and moving them over to a 2012 server things seemed to have improved significantly.
Unfortunately I am not able to confirm the root cause of the initial problem – just happy performance has improved now!