By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,680 Members | 1,508 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,680 IT Pros & Developers. It's quick & easy.

XP Pro Install Package Wizard

P: n/a
hi guys and girls

I have 2 problems that are driving me crazy!

1/
I have a front end mde, and back end mdb, that I have packaged and
installed successfully in the past on both Win98 and XP Pro PCs.
Since XP Pro PS2 OEM version is installed on a new box, Ive found I get
the following ERROR Message Dialog Box, when I go to install my
application:

Visual Basic 6.0 Setup Toolkit
The Office System Pack cannot be installed on this system because it
requires Windows NT 4.0 Service Pack or Later.

It then cancels the installation.
This has happened on a few PCs with the same OS, XP Pro SP2.
When I package it I include the System Files.

2/
The same App has an ActiveX control "mscal.ocx" in it. Most times when
I have installed it successfully, I sometimes get errors when I access
the form with the Calendar on it. I usually exit the program and using
a dos prompt, I use regsvr32 to unregistered and re-registered
mscal.ocx, and this works ok. But sometimes on XP Pro OSs I get a error
message saying it cant find the file or were it is in the registry.
Mscal.ocx is stored and registered in the local folder of the program.
Ive check the status of the profile and have full access.

Any help would be greatly appreciated!
Thanks for your time and effort.

Chris
Sydney
Australia

Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On 19 Jan 2005 18:50:06 -0800, ch***@krisaracomputers.com.au wrote:

There is a known problem with mscal.ocx and the PDW. Check the MSFT
knowledge base. If memory serves, in setup.lst you need to manually
change $DLLSelfRegister to #DllSelfRegisterEx.

Your first point: no idea what "Office System Pack" is. It doesn't
sound like something you are allowed to redistribute.

-Tom.

hi guys and girls

I have 2 problems that are driving me crazy!

1/
I have a front end mde, and back end mdb, that I have packaged and
installed successfully in the past on both Win98 and XP Pro PCs.
Since XP Pro PS2 OEM version is installed on a new box, Ive found I get
the following ERROR Message Dialog Box, when I go to install my
application:

Visual Basic 6.0 Setup Toolkit
The Office System Pack cannot be installed on this system because it
requires Windows NT 4.0 Service Pack or Later.

It then cancels the installation.
This has happened on a few PCs with the same OS, XP Pro SP2.
When I package it I include the System Files.

2/
The same App has an ActiveX control "mscal.ocx" in it. Most times when
I have installed it successfully, I sometimes get errors when I access
the form with the Calendar on it. I usually exit the program and using
a dos prompt, I use regsvr32 to unregistered and re-registered
mscal.ocx, and this works ok. But sometimes on XP Pro OSs I get a error
message saying it cant find the file or were it is in the registry.
Mscal.ocx is stored and registered in the local folder of the program.
Ive check the status of the profile and have full access.

Any help would be greatly appreciated!
Thanks for your time and effort.

Chris
Sydney
Australia


Nov 13 '05 #2

P: n/a
Thanks Tom
I'll lookup MSKB and see if I can find the solution to fix setup.lst.

With my 1st problem, Ive found what happens with XP SP2.
It removes 2 dlls from the system, and the Packaging Wizard relies on
one of them. "Dbmsadsn.dll".

MS Solution:

1. Locate the Packaging Wizard folder on the computer where the Access
2002 runtime deployment package was created.

By default, the Packaging Wizard folder can be found at the following
location:

<Installation Drive>:\Program Files\Microsoft Office
Developer\Packaging Wizard
2. Start Notepad, and then open the Ospfilelist.txt file.

Note Make a backup copy of the Ospfilelist.txt file.
3. In the Ospfilelist.txt file, locate the line that contains the
Dbmsadsn.dll file. Delete the line that contains the Dbmsadsn.dll file.

4. On the File menu, click Save.
5. On the File menu, click Exit.
6. Create the Access 2002 runtime deployment package again by using the
Packaging Wizard.
7. Install the Access 2002 runtime deployment package on the computer
that is running Windows Server 2003.

Notice that the installation of the Access 2002 runtime deployment
package is successfully completed.

I hope this helps others.

Chris

Nov 13 '05 #3

P: n/a
I have the same problem. Hopefully this will help me too.

ch***@krisaracomputers.com.au wrote:
Thanks Tom
I'll lookup MSKB and see if I can find the solution to fix setup.lst.

With my 1st problem, Ive found what happens with XP SP2.
It removes 2 dlls from the system, and the Packaging Wizard relies on
one of them. "Dbmsadsn.dll".

MS Solution:

1. Locate the Packaging Wizard folder on the computer where the Access 2002 runtime deployment package was created.

By default, the Packaging Wizard folder can be found at the following
location:

<Installation Drive>:\Program Files\Microsoft Office
Developer\Packaging Wizard
2. Start Notepad, and then open the Ospfilelist.txt file.

Note Make a backup copy of the Ospfilelist.txt file.
3. In the Ospfilelist.txt file, locate the line that contains the
Dbmsadsn.dll file. Delete the line that contains the Dbmsadsn.dll file.
4. On the File menu, click Save.
5. On the File menu, click Exit.
6. Create the Access 2002 runtime deployment package again by using the Packaging Wizard.
7. Install the Access 2002 runtime deployment package on the computer
that is running Windows Server 2003.

Notice that the installation of the Access 2002 runtime deployment
package is successfully completed.

I hope this helps others.

Chris


Nov 13 '05 #4

P: n/a
MNF
The same error message "The Office System Pack cannot be installed on
this system because it requires Windows NT 4.0 Service Pack 6 or
later."
is reported if C:\WINDOWS\System32\MSVBVM60.DLL is missing or
corrupted (Unlikely, but it had happened on one of my clients).

Michael Freidgeim
Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.