Problems with config.msi permissions
I have been fighting with write access from many installers to the Config.Msi folder. For installers that let you retry, doing a retry will succeed. However, some installers don't allow that such as the installer for Office 2010 and when it gets an error
it rolls everything back. I'm assuming there is some application that causes this problem? Doing a clean boot and disabling all non-microsoft services seems to solve the problem most of the time. However, almost all of our Windows 7 machines have the same
problem. I have tried running the installers as admin but it doesn't seem to fix the problem.
I saw a previous post that had iDrive causing the problem but we don't use this software.
Thanks!
September 21st, 2011 11:21pm
Hi,
What error message did you meet?
If it works in clean boot, the issue may relate with some services start by third party programs.
Please temporally disable firewall and antivirus program, also remove third party programs. Also disable UAC on Windows 7.
Furthermore, try to Take ownership of this folder
====================
1. Open My Computer and open the C drive.
2. Enter Windows folder, find out and right click on this folder and choose Properties.
3. Choose the "Security" tab and see if "Administrators" is listed in the "Group and User" name list. If not, please click the Add button and type "Administrators"
in the open window and click "OK" to add this group.
4. Highlight "Administrators" and check "Full Control" under "Accept".
5. Click the "Advanced" button and choose the "Owner" tab.
6. Highlight the "Administrators" user group in the list and mark the check box before "Replace owner on subcontainers and objects".
7. Click "OK" to save changes and wait for Windows XP to transfer ownership of all the objects on the partition.
8. Click OK again to save changes and exit the Properties window.
In addition, right click the installer package and choose “Properties”, in General tab, click “Unblock” for test.
Hope that helps.
Regards,
Leo
Huang
TechNet
Subscriber Support in forum. If you have any feedback on our support, please contact
tngfb@microsoft.com
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2011 8:38am
I always get error 1310 writing to config.msi.
September 22nd, 2011 5:28pm
Hi,
This behavior can occur when you install Microsoft Project 2000 or Microsoft Office 2000 by means of a Microsoft Terminal Server session in which the
system account does not have full permissions to all the necessary files and folders on the server. This behavior can also occur when the Windows Installer becomes unregistered during the installation process.
Try these methods below:
Method 1
Install the product by logging on directly to the server that contains the installation files, rather than by using a Terminal Server
session. (Log on locally to the Terminal Server console.) Make sure that the System account has permissions to all the necessary folders on the server.
NOTE: During the installation process, Windows Installer uses the System account to access all the necessary files and folders.
Method 2
Unregister and reregister Windows Installer. To do this, follow these steps:
Click
Start, and then click Run. In the
Open box, type msiexec /unreg, and then press ENTER.
Click
Start, and then click Run. In the
Open box, type msiexec /regserver, and then press ENTER.
Refer:
http://support.microsoft.com/kb/296175
Regards,
Leo
Huang
TechNet
Subscriber Support in forum. If you have any feedback on our support, please contact
tngfb@microsoft.com
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2011 10:01pm
Hi,
This behavior can occur when you install Microsoft Project 2000 or Microsoft Office 2000 by means of a Microsoft Terminal Server session in which the
system account does not have full permissions to all the necessary files and folders on the server. This behavior can also occur when the Windows Installer becomes unregistered during the installation process.
Try these methods below:
Method 1
Install the product by logging on directly to the server that contains the installation files, rather than by using a Terminal Server
session. (Log on locally to the Terminal Server console.) Make sure that the System account has permissions to all the necessary folders on the server.
NOTE: During the installation process, Windows Installer uses the System account to access all the necessary files and folders.
Method 2
Unregister and reregister Windows Installer. To do this, follow these steps:
Click
Start, and then click Run. In the
Open box, type msiexec /unreg, and then press ENTER.
Click
Start, and then click Run. In the
Open box, type msiexec /regserver, and then press ENTER.
Refer:
http://support.microsoft.com/kb/296175
Regards,
Leo
Huang
TechNet
Subscriber Support in forum. If you have any feedback on our support, please contact
tngfb@microsoft.com
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
September 23rd, 2011 5:01am
Hi,
Did your issue solved Please feel free to give me any update.
Thanks.
Regards,
Leo Huang
TechNet
Subscriber Support in forum. If you have any feedback on our support, please contact
tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2011 12:21pm
Hi,
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will
mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the
answer as you wish.
BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help
other community members facing similar problems. Thanks for your understanding and efforts.
Regards,
Leo Huang
TechNet
Subscriber Support in forum. If you have any feedback on our support, please contact
tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
October 5th, 2011 9:28pm
Sorry for not responding earlier but I found out the issue. We use a backup tool called "CrashPlan" and it was getting a lock on that directory and causing the issues. After disabling the service while installing the problems went away.
Thanks!
Free Windows Admin Tool Kit Click here and download it now
March 26th, 2012 3:35pm