Office XP MOD/Access 2002 runtime can't install on Windows XP SP2, Vista, 2003 Server or Windows 7

(Last Updated 2009-11-29)

Error: "The Office System Pack cannot be installed on  this system because it requires Windows NT 4.0 Service Pack 6 or later."

For Windows 7 also remove the AGENTSVR.EXE line from the OSPFILELIST file.  See Error with Access 2002 deployment package on Windows 7 which referenced http://www.access-programmers.co.uk/forums/showthread.php?p=908669   The other files to be removed from that file are Dbmsadsn.dll, Msxml.dll. Dbnmpntw.dll, Sqloledb.dll.

The below is for Windows XP SP2, Windows Vista and Windows 2003 Server and also applies to Windows 7.

The following article now supersedes the rest of this page.   You may receive error messages when you install an Access 2002 runtime deployment package on a computer that is running Windows XP SP2, Windows Server 2003, or Windows Vista


Note:  This is preliminary information.  Thanks to the original posters for making the call to Microsoft Support.

This page only exists to give folks who are encountering this problem something to locate when doing a search.  This page will be deprecated  once a KB article is available at Microsoft.

Someone else contacted MS and posted the following:

We were able to get support from Microsoft regarding this  issue.

It turns out to be a known issue; they found a reference to it in their internal (not public) version of Knowledge Base.

They say the problem is due to a dll that is no longer needed.

Here is their fix: Error: "The Office System Pack cannot be installed on  this system because it requires Windows NT 4.0 Service Pack 6 or later."

Cause:
======
A specific DLL (DBMSADSN.DLL) that is on the OSPFILELIST is no longer included in MDAC. (Effective with MDAC 2.8) As such, since the runtime setup cannot locate the file, the installation fails.

Resolution:
=========

- Navigate to where the runtime files have been installed on your developer machine and then open the Packaging Wizard folder (i.e. C:\Program Files\Microsoft Office Developer\Packaging Wizard)

- Rename the OSPFILELIST.TXT file to OSPFILELISTORIGINAL.TXT to retain a backup for packaging
for other OS's.

- Make a copy of OSPFILELISTORIGINAL.TXT and rename it to OSPFILELIST.TXT
- Open OSPFILELIST.TXT
- Delete the entire line for:
- DBMSADSN.DLL
- Save and close the file

- Re-package the application (This is required so the package will include the modified OSPFILELIST.)

(This message can't be found on msnews.microsoft.com or groups.google.com but can be located by visiting the Microsoft microsoft.public.windows.server.general page and searching on OSPFILELIST.TXT)

==============================================

(Created 2003-06-01

The following is now out of date but is retained for historical purposes.

Error message: "The Office System Pack cannot be installed on this system because it requires Windows NT 4.0 Service Pack 6 or later." The window was titled "Visual Basic 6.0 Setup Toolkit"

Original groups.google.com posting.

The poster states "I just got off the phone with Microsoft. They are able to reproduce the problem.

They were able to track the problem down to c:\windows\system32\psapi.dll on their machine

They renamed the file and a newer version was automatically copied from the cache folder.

I have not tried this yet. They said different machines could have problems with different files. They suggested using filemon utility from sysinternals.com to diagnose the install problem."

[ Access ! Main ]