469,927 Members | 1,627 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,927 developers. It's quick & easy.

Can't be started. Was unable to initialize the Windows Registry. Rerun Microsoft Access or Microsoft Office Setup to reinstall

This Access app is in Access 2000 format. It is a mature app that is
running on machines all over the LAN. Today when I tried to put it on
a new PC with a fresh copy of Win XP and Access 2003. XP has all
patches installed and is SP 2. I got this error:

Can't be started.
Was unable to initialize the Windows Registry.
Rerun Microsoft Access or Microsoft Office Setup to reinstall

I ran the app as domain admin and local admin, no change.
I reinstalled Office, no change.
I performed the registry hacks for this problem that I found around
the Internet. No change

I am able to load Access, I just can't launch my app.

This might be a clue: The problem arises when I try to launch my app
through a short-cut on the desktop. If I open Access and then load my
app, it will launch. This is not a work-around, however, because the
app needs a security database and other command line arguments to run
properly. At least I know the mdb is not corrupted.

Thanks,

Bill
Cincinnati, OH USA

Aug 17 '07 #1
4 20709
Hi Bill,

"Bill Nicholson - Cincinnati, OH" <na******************@gmail.comschrieb im
Newsbeitrag news:11**********************@e9g2000prf.googlegro ups.com...
This Access app is in Access 2000 format. It is a mature app that is
running on machines all over the LAN. Today when I tried to put it on
a new PC with a fresh copy of Win XP and Access 2003. XP has all
patches installed and is SP 2. I got this error:

Can't be started.
Was unable to initialize the Windows Registry.
Rerun Microsoft Access or Microsoft Office Setup to reinstall

I ran the app as domain admin and local admin, no change.
I reinstalled Office, no change.
I performed the registry hacks for this problem that I found around
the Internet. No change

I am able to load Access, I just can't launch my app.

This might be a clue: The problem arises when I try to launch my app
through a short-cut on the desktop. If I open Access and then load my
app, it will launch. This is not a work-around, however, because the
app needs a security database and other command line arguments to run
properly. At least I know the mdb is not corrupted.
There might be a problem with the file type relationships on that machine oder
with DDE for the type MDB.
Try the following:
- Explorer Extras Folder options
- File types
- Choose MDB from list
- Click "More options" (sorry, I currently have only a german Window running;
may be this button is named "Extended")
- Choose "Open" from list
- Click "Edit"
- Remove "Use DDE"
- OK, OK, Close

Cia, Sascha
Aug 17 '07 #2
Hi Sascha,

Thank you for the suggestion. I followed your steps and the DDE
option was already checked.

Bill

On Aug 17, 6:10 am, "Sascha Trowitzsch" <n...@moss-soft.dewrote:
Hi Bill,

"Bill Nicholson - Cincinnati, OH" <namewitheldbyrequ...@gmail.comschrieb im
Newsbeitragnews:11**********************@e9g2000pr f.googlegroups.com...
This Access app is in Access 2000 format. It is a mature app that is
running on machines all over the LAN. Today when I tried to put it on
a new PC with a fresh copy of Win XP and Access 2003. XP has all
patches installed and is SP 2. I got this error:
Can't be started.
Was unable to initialize the Windows Registry.
Rerun Microsoft Access or Microsoft Office Setup to reinstall
I ran the app as domain admin and local admin, no change.
I reinstalled Office, no change.
I performed the registry hacks for this problem that I found around
the Internet. No change
I am able to load Access, I just can't launch my app.
This might be a clue: The problem arises when I try to launch my app
through a short-cut on the desktop. If I open Access and then load my
app, it will launch. This is not a work-around, however, because the
app needs a security database and other command line arguments to run
properly. At least I know the mdb is not corrupted.

There might be a problem with the file type relationships on that machine oder
with DDE for the type MDB.
Try the following:
- Explorer Extras Folder options
- File types
- Choose MDB from list
- Click "More options" (sorry, I currently have only a german Window running;
may be this button is named "Extended")
- Choose "Open" from list
- Click "Edit"
- Remove "Use DDE"
- OK, OK, Close

Cia, Sascha

Aug 17 '07 #3
It's fixed. The shortcut pointed to Office10\MSAccess.exe. I changed
it to Office11. Office10 is not installed on the machine and never has
been, so I would have thought that the diagnostic would have been a
little more friendly. Oh well.
On Aug 17, 12:15 am, "Bill Nicholson - Cincinnati, OH"
<namewitheldbyrequ...@gmail.comwrote:
This Access app is in Access 2000 format. It is a mature app that is
running on machines all over the LAN. Today when I tried to put it on
a new PC with a fresh copy of Win XP and Access 2003. XP has all
patches installed and is SP 2. I got this error:

Can't be started.
Was unable to initialize the Windows Registry.
Rerun Microsoft Access or Microsoft Office Setup to reinstall

I ran the app as domain admin and local admin, no change.
I reinstalled Office, no change.
I performed the registry hacks for this problem that I found around
the Internet. No change

I am able to load Access, I just can't launch my app.

This might be a clue: The problem arises when I try to launch my app
through a short-cut on the desktop. If I open Access and then load my
app, it will launch. This is not a work-around, however, because the
app needs a security database and other command line arguments to run
properly. At least I know the mdb is not corrupted.

Thanks,

Bill
Cincinnati, OH USA

Aug 17 '07 #4
Bill Nicholson - Cincinnati, OH wrote:
Hi Sascha,

Thank you for the suggestion. I followed your steps and the DDE
option was already checked.
I think Sascha was saying to Remove the check.
>
Bill

On Aug 17, 6:10 am, "Sascha Trowitzsch" <n...@moss-soft.dewrote:
>>Hi Bill,

"Bill Nicholson - Cincinnati, OH" <namewitheldbyrequ...@gmail.comschrieb im
Newsbeitragnews:11**********************@e9g2000 prf.googlegroups.com...

>>>This Access app is in Access 2000 format. It is a mature app that is
running on machines all over the LAN. Today when I tried to put it on
a new PC with a fresh copy of Win XP and Access 2003. XP has all
patches installed and is SP 2. I got this error:
>>>Can't be started.
Was unable to initialize the Windows Registry.
Rerun Microsoft Access or Microsoft Office Setup to reinstall
>>>I ran the app as domain admin and local admin, no change.
I reinstalled Office, no change.
I performed the registry hacks for this problem that I found around
the Internet. No change
>>>I am able to load Access, I just can't launch my app.
>>>This might be a clue: The problem arises when I try to launch my app
through a short-cut on the desktop. If I open Access and then load my
app, it will launch. This is not a work-around, however, because the
app needs a security database and other command line arguments to run
properly. At least I know the mdb is not corrupted.

There might be a problem with the file type relationships on that machine oder
with DDE for the type MDB.
Try the following:
- Explorer Extras Folder options
- File types
- Choose MDB from list
- Click "More options" (sorry, I currently have only a german Window running;
may be this button is named "Extended")
- Choose "Open" from list
- Click "Edit"
- Remove "Use DDE"
- OK, OK, Close

Cia, Sascha


Aug 17 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Kenny Bullock | last post: by
4 posts views Thread by bbdobuddy | last post: by
6 posts views Thread by Boris | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.