Problems regarding MS Project 2000 SR1
Hello Everyone!
We're deploying MS Office 2000 Prof. SR1 throughout a company and also MS Project 2000 SR1 on some clients. Normally repacking MS Apps is unmatch in ease but the problem I have with MS Project is that the MSI-self healing always comes up and asks for the Project sources when I try to open it under another useraccount. We tried the following but nothing worked:
We also don't use an .ops to migrate user settings.
The .mst's we used we're created using the Office 2000 Resource Kit, the problem still consists when running a normal setup with setup.exe. The eventviewer says that msiexec could'nt find the keypaths of some component of the officeusrdata feature.
Has anyone already had this problem? My solution would be to delete the regkeypath of the components so selfhealing wouldn't come up anymore, because when you abort the selfhealing project works just fine. Has anyone a better idea?
We're deploying MS Office 2000 Prof. SR1 throughout a company and also MS Project 2000 SR1 on some clients. Normally repacking MS Apps is unmatch in ease but the problem I have with MS Project is that the MSI-self healing always comes up and asks for the Project sources when I try to open it under another useraccount. We tried the following but nothing worked:
- set ALLUSERS public Property to 1 to perform a per machine install
- perform a full install with all features on local drive
- perform a full office install with all features on local drive
We also don't use an .ops to migrate user settings.
The .mst's we used we're created using the Office 2000 Resource Kit, the problem still consists when running a normal setup with setup.exe. The eventviewer says that msiexec could'nt find the keypaths of some component of the officeusrdata feature.
Has anyone already had this problem? My solution would be to delete the regkeypath of the components so selfhealing wouldn't come up anymore, because when you abort the selfhealing project works just fine. Has anyone a better idea?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
aogilmor
19 years ago
Very common problem.
Mostly it comes from the user not having access to the original source. ALLUSERS=1 just means a per machine installation. It's supposed to self heal still by design, i.e. the proper defaults are populated to HKCU and user profile directories.
If you click OK on the prompt does it go ahead and install and run correctly, or is there some other error?
See if you still get the prompt when you run the install from a local drive to which the user has access. IF it does, then it's not a user access problem, but has to do with the way the Media are set up. Look in WFWI.CHM for media and make sure all of the features and components are in the CAB file(s).
Mostly it comes from the user not having access to the original source. ALLUSERS=1 just means a per machine installation. It's supposed to self heal still by design, i.e. the proper defaults are populated to HKCU and user profile directories.
If you click OK on the prompt does it go ahead and install and run correctly, or is there some other error?
See if you still get the prompt when you run the install from a local drive to which the user has access. IF it does, then it's not a user access problem, but has to do with the way the Media are set up. Look in WFWI.CHM for media and make sure all of the features and components are in the CAB file(s).
ORIGINAL: sini
Hello Everyone!
We're deploying MS Office 2000 Prof. SR1 throughout a company and also MS Project 2000 SR1 on some clients. Normally repacking MS Apps is unmatch in ease but the problem I have with MS Project is that the MSI-self healing always comes up and asks for the Project sources when I try to open it under another useraccount. We tried the following but nothing worked:
- set ALLUSERS public Property to 1 to perform a per machine install
- perform a full install with all features on local drive
- perform a full office install with all features on local drive
We also don't use an .ops to migrate user settings.
The .mst's we used we're created using the Office 2000 Resource Kit, the problem still consists when running a normal setup with setup.exe. The eventviewer says that msiexec could'nt find the keypaths of some component of the officeusrdata feature.
Has anyone already had this problem? My solution would be to delete the regkeypath of the components so selfhealing wouldn't come up anymore, because when you abort the selfhealing project works just fine. Has anyone a better idea?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
