MSACCESS 2003 Fails After SP2 Update

J

Jon Abbott

I have the fix from Microsoft, although you will need to create or modify your
own MST to resolve the issue. MS have no date for a fix to the MSI package
itself.

You need to all the following entries to the MST:

RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32
Type: STRING
Value: C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll


RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32old
Type: STRING
Value: C:\Windows\System32\msexcl40.dll



I implemented I slightly more elegant solution by doing an AppSearch for win32
and using this for the win32old value. I also made both keys part of the
component that msaexp30.dll resides in. If you're happy modifiying MSI/MST
tables through Orca etc, here's the changes:


AppSearch table (1 entry):

Property: JET4EXCEL
Signature: JetWin32Reg



RegLocator table (1 entry):

Signature: JetWin32Reg
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Type: 2



Registry table (2 entries):

Registry: Access.SP2Fix1
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32old
Value: [JET4EXCEL]
Component: Global_Access_Core

Registry: Access.SP2Fix2
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Value: [#MSAEXP30.DLL]
Component: Global_Access_Core



Regards
Jon Abbott
Clarksons Plc
 
J

Jon Abbott

I have the fix from Microsoft, although you will need to create or modify your
own MST to resolve the issue. MS have no date for a fix to the MSI package
itself.

You need to all the following entries to the MST:

RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32
Type: STRING
Value: C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll


RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32old
Type: STRING
Value: C:\Windows\System32\msexcl40.dll



I implemented I slightly more elegant solution by doing an AppSearch for win32
and using this for the win32old value. I also made both keys part of the
component that msaexp30.dll resides in. If you're happy modifiying MSI/MST
tables through Orca etc, here's the changes:


AppSearch table (1 entry):

Property: JET4EXCEL
Signature: JetWin32Reg



RegLocator table (1 entry):

Signature: JetWin32Reg
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Type: 2



Registry table (2 entries):

Registry: Access.SP2Fix1
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32old
Value: [JET4EXCEL]
Component: Global_Access_Core

Registry: Access.SP2Fix2
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Value: [#MSAEXP30.DLL]
Component: Global_Access_Core



Regards
Jon Abbott
Clarksons Plc
 
J

Jon Abbott

I have the fix from Microsoft, although you will need to create or modify your
own MST to resolve the issue. MS have no date for a fix to the MSI package
itself.

You need to all the following entries to the MST:

RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32
Type: STRING
Value: C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll


RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32old
Type: STRING
Value: C:\Windows\System32\msexcl40.dll



I implemented I slightly more elegant solution by doing an AppSearch for win32
and using this for the win32old value. I also made both keys part of the
component that msaexp30.dll resides in. If you're happy modifiying MSI/MST
tables through Orca etc, here's the changes:


AppSearch table (1 entry):

Property: JET4EXCEL
Signature: JetWin32Reg



RegLocator table (1 entry):

Signature: JetWin32Reg
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Type: 2



Registry table (2 entries):

Registry: Access.SP2Fix1
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32old
Value: [JET4EXCEL]
Component: Global_Access_Core

Registry: Access.SP2Fix2
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Value: [#MSAEXP30.DLL]
Component: Global_Access_Core



Regards
Jon Abbott
Clarksons Plc
 
J

Jon Abbott

I have the fix from Microsoft, although you will need to create or modify your
own MST to resolve the issue. MS have no date for a fix to the MSI package
itself.

You need to all the following entries to the MST:

RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32
Type: STRING
Value: C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll


RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32old
Type: STRING
Value: C:\Windows\System32\msexcl40.dll



I implemented I slightly more elegant solution by doing an AppSearch for win32
and using this for the win32old value. I also made both keys part of the
component that msaexp30.dll resides in. If you're happy modifiying MSI/MST
tables through Orca etc, here's the changes:


AppSearch table (1 entry):

Property: JET4EXCEL
Signature: JetWin32Reg



RegLocator table (1 entry):

Signature: JetWin32Reg
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Type: 2



Registry table (2 entries):

Registry: Access.SP2Fix1
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32old
Value: [JET4EXCEL]
Component: Global_Access_Core

Registry: Access.SP2Fix2
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Value: [#MSAEXP30.DLL]
Component: Global_Access_Core



Regards
Jon Abbott
Clarksons Plc
 
J

Jon Abbott

I have the fix from Microsoft, although you will need to create or modify your
own MST to resolve the issue. MS have no date for a fix to the MSI package
itself.

You need to all the following entries to the MST:

RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32
Type: STRING
Value: C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll


RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32old
Type: STRING
Value: C:\Windows\System32\msexcl40.dll



I implemented I slightly more elegant solution by doing an AppSearch for win32
and using this for the win32old value. I also made both keys part of the
component that msaexp30.dll resides in. If you're happy modifiying MSI/MST
tables through Orca etc, here's the changes:


AppSearch table (1 entry):

Property: JET4EXCEL
Signature: JetWin32Reg



RegLocator table (1 entry):

Signature: JetWin32Reg
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Type: 2



Registry table (2 entries):

Registry: Access.SP2Fix1
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32old
Value: [JET4EXCEL]
Component: Global_Access_Core

Registry: Access.SP2Fix2
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Value: [#MSAEXP30.DLL]
Component: Global_Access_Core



Regards
Jon Abbott
Clarksons Plc
 
J

Jon Abbott

I have the fix from Microsoft, although you will need to create or modify your
own MST to resolve the issue. MS have no date for a fix to the MSI package
itself.

You need to all the following entries to the MST:

RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32
Type: STRING
Value: C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll


RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32old
Type: STRING
Value: C:\Windows\System32\msexcl40.dll



I implemented I slightly more elegant solution by doing an AppSearch for win32
and using this for the win32old value. I also made both keys part of the
component that msaexp30.dll resides in. If you're happy modifiying MSI/MST
tables through Orca etc, here's the changes:


AppSearch table (1 entry):

Property: JET4EXCEL
Signature: JetWin32Reg



RegLocator table (1 entry):

Signature: JetWin32Reg
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Type: 2



Registry table (2 entries):

Registry: Access.SP2Fix1
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32old
Value: [JET4EXCEL]
Component: Global_Access_Core

Registry: Access.SP2Fix2
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Value: [#MSAEXP30.DLL]
Component: Global_Access_Core



Regards
Jon Abbott
Clarksons Plc
 
M

Michael

Still waiting for a hotfix to be issued. I think Microsoft believes that
since I submitted the problem, I'm the only person in the world who has
experienced it.

I've tried to convince them that there are going to by many organizations
affected.

Michael
 
M

Michael

Still waiting for a hotfix to be issued. I think Microsoft believes that
since I submitted the problem, I'm the only person in the world who has
experienced it.

I've tried to convince them that there are going to by many organizations
affected.

Michael
 
M

Michael

Still waiting for a hotfix to be issued. I think Microsoft believes that
since I submitted the problem, I'm the only person in the world who has
experienced it.

I've tried to convince them that there are going to by many organizations
affected.

Michael
 
M

Michael

Still waiting for a hotfix to be issued. I think Microsoft believes that
since I submitted the problem, I'm the only person in the world who has
experienced it.

I've tried to convince them that there are going to by many organizations
affected.

Michael
 
M

Michael

Still waiting for a hotfix to be issued. I think Microsoft believes that
since I submitted the problem, I'm the only person in the world who has
experienced it.

I've tried to convince them that there are going to by many organizations
affected.

Michael
 
M

Michael

Still waiting for a hotfix to be issued. I think Microsoft believes that
since I submitted the problem, I'm the only person in the world who has
experienced it.

I've tried to convince them that there are going to by many organizations
affected.

Michael
 
M

Michael

Still waiting for a hotfix to be issued. I think Microsoft believes that
since I submitted the problem, I'm the only person in the world who has
experienced it.

I've tried to convince them that there are going to by many organizations
affected.

Michael
 
M

Michael

Still waiting for a hotfix to be issued. I think Microsoft believes that
since I submitted the problem, I'm the only person in the world who has
experienced it.

I've tried to convince them that there are going to by many organizations
affected.

Michael
 
M

Michael

Still waiting for a hotfix to be issued. I think Microsoft believes that
since I submitted the problem, I'm the only person in the world who has
experienced it.

I've tried to convince them that there are going to by many organizations
affected.

Michael
 
S

Sharpie

To revive an old thread.

Since Microsoft is now sending letters out saying that we have to upgrade to
SP2 for "legal reasons", are there any updates to this issue, hotfixes,
anything?

The problem still exists.

We are unable to perform this upgrade, well we could hack it, but a machine
that has more working parts, or program that has more lines of code is prone
to more problems.

So if we have to upgrade for "legal reasons" it would be nice for a hotfix
to appear, or anything to make this upgrade work like it should.


Jon,
Are these entries applied to the patched PRO11.msi file? If so after adding
these entries can I then perform the upgrade on the client computers without
the upgrade asking me to locate the pro11.msi file (and not letting me pick
the pro11.msi file on the network)?
 
S

Sharpie

To revive an old thread.

Since Microsoft is now sending letters out saying that we have to upgrade to
SP2 for "legal reasons", are there any updates to this issue, hotfixes,
anything?

The problem still exists.

We are unable to perform this upgrade, well we could hack it, but a machine
that has more working parts, or program that has more lines of code is prone
to more problems.

So if we have to upgrade for "legal reasons" it would be nice for a hotfix
to appear, or anything to make this upgrade work like it should.


Jon,
Are these entries applied to the patched PRO11.msi file? If so after adding
these entries can I then perform the upgrade on the client computers without
the upgrade asking me to locate the pro11.msi file (and not letting me pick
the pro11.msi file on the network)?
 
S

Sharpie

To revive an old thread.

Since Microsoft is now sending letters out saying that we have to upgrade to
SP2 for "legal reasons", are there any updates to this issue, hotfixes,
anything?

The problem still exists.

We are unable to perform this upgrade, well we could hack it, but a machine
that has more working parts, or program that has more lines of code is prone
to more problems.

So if we have to upgrade for "legal reasons" it would be nice for a hotfix
to appear, or anything to make this upgrade work like it should.


Jon,
Are these entries applied to the patched PRO11.msi file? If so after adding
these entries can I then perform the upgrade on the client computers without
the upgrade asking me to locate the pro11.msi file (and not letting me pick
the pro11.msi file on the network)?
 
S

Sharpie

To revive an old thread.

Since Microsoft is now sending letters out saying that we have to upgrade to
SP2 for "legal reasons", are there any updates to this issue, hotfixes,
anything?

The problem still exists.

We are unable to perform this upgrade, well we could hack it, but a machine
that has more working parts, or program that has more lines of code is prone
to more problems.

So if we have to upgrade for "legal reasons" it would be nice for a hotfix
to appear, or anything to make this upgrade work like it should.


Jon,
Are these entries applied to the patched PRO11.msi file? If so after adding
these entries can I then perform the upgrade on the client computers without
the upgrade asking me to locate the pro11.msi file (and not letting me pick
the pro11.msi file on the network)?
 
S

Sharpie

To revive an old thread.

Since Microsoft is now sending letters out saying that we have to upgrade to
SP2 for "legal reasons", are there any updates to this issue, hotfixes,
anything?

The problem still exists.

We are unable to perform this upgrade, well we could hack it, but a machine
that has more working parts, or program that has more lines of code is prone
to more problems.

So if we have to upgrade for "legal reasons" it would be nice for a hotfix
to appear, or anything to make this upgrade work like it should.


Jon,
Are these entries applied to the patched PRO11.msi file? If so after adding
these entries can I then perform the upgrade on the client computers without
the upgrade asking me to locate the pro11.msi file (and not letting me pick
the pro11.msi file on the network)?
 

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

Installing Office-97 pro after uninstalled Office-2000 premium 5
Access 2003 and excel 0
When you start MSACCESS, Windows Installer starts 9
VSTO C# add in Outlook.Appointment error 0
Running Access97 And AccessXP on Windows Server 2003 terminal services 3
Vista and MSAccess Runtime 1
Office 2007 SP2 installation 0
Access 2003 fails to open from mdb file 2

Top