Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Error 1720 Windows installer error 1
- Thread starter irlcon
- Start date
-
1
- #2
FROM THE CITRIX SITE!!
MSI-based installations of MetaFrame or NFuse Classic may fail reporting Error 1720. There are a few known possible causes of this error:
1. MSI file is hosted on a network share
While the installer user interface runs under the identity of the current user, the actual MSI installation script runs under the identity of the local computer system account. Therefore the installer can not access network shares unless they are available to both the user running the installer and to the local system account. On most systems, this means that network shares in the same domain will work, but network shares in other domains will not.
Should you encounter error 1720 when attempting to install an MSI package from a network share, copy the MSI file to your local hard drive and perform the installation.
2. Distributed Transaction Coordinator Service is disabled or can not be started
Check to ensure that the Microsoft Distributed Transaction Coordinator (MS DTC) service is not disabled or configured to log in with an invalid account. The COM+ Hotfix Rollup Package 18.1 or later from Microsoft (article 313582) may resolve problems with the MS DTC service.
3. COM catalog corruption on MetaFrame servers with remapped drives
If you attempt to install NFuse Classic 1.7 on a MetaFrame server where the server drives have been remapped, you will receive the 1720 error if the MetaFrame server COM catalog was not updated properly during drive remapping. In this case, you will also find COM+ errors in the event viewer with error ID 4097. See Error: "Event: 4097, Source: COM+" in the Event Viewer for more information about this error and Microsoft (article 286365).
4. FR2 Installation failed Error 1720On line 373 of the MSI log file.
During the installation of NFuse Classic 1.7, a new COM+ application is created. Although the application will impersonate a new account, CTX_NFUSE_ADMIN, the application is initially created with a default owner of IWAM_ServerName and then switched to impersonate CTX_NFUSE_ADMIN. If the IWAM account is disabled or its password is not synchronized with settings in the IIS metabase, NFuse fails to install. This Account may have been disabled for security concerns. Enable the account. Once the installation has completed, the IWAM account may be disabled without affecting the NFuseAdmin tool. See Microsoft article 297989 for information about dealing with unsynchronized metabase passwords.
5. FR2 Installation failed Error 1720 CTX_NFUSE_ADMIN account does not have access...on line 314 of the MSI log file.
The IWAM account or newly created CTX_NFUSE_ADMIN account does not have Access this computer from the network rights (line 314). If neither of the NETWORK or AUTHENTICATED USERS built-in groups has the Access this computer from the network user right assigned to them, then the NFuse installer is not able to assign the CTX_NFUSE_ADMIN account as the owner of the NFuseAdmin COM application. If the CTX_NFUSE_ADMIN account already exists, assign it to the policy. Otherwise, assign at least the NETWORK built-in group.
Select Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment and then double-click Access this computer from the network. Both the IWAM_ServerName account and the CTX_NFUSE_ADMIN account, created during installation, need this right.
Note: Attempting to install NFuse 1.7 when the CTX_NFUSE_ADMIN already exists may require the deletion of the account or require the assignment of administrative rights before reinstalling.
Mike Brown
MSI-based installations of MetaFrame or NFuse Classic may fail reporting Error 1720. There are a few known possible causes of this error:
1. MSI file is hosted on a network share
While the installer user interface runs under the identity of the current user, the actual MSI installation script runs under the identity of the local computer system account. Therefore the installer can not access network shares unless they are available to both the user running the installer and to the local system account. On most systems, this means that network shares in the same domain will work, but network shares in other domains will not.
Should you encounter error 1720 when attempting to install an MSI package from a network share, copy the MSI file to your local hard drive and perform the installation.
2. Distributed Transaction Coordinator Service is disabled or can not be started
Check to ensure that the Microsoft Distributed Transaction Coordinator (MS DTC) service is not disabled or configured to log in with an invalid account. The COM+ Hotfix Rollup Package 18.1 or later from Microsoft (article 313582) may resolve problems with the MS DTC service.
3. COM catalog corruption on MetaFrame servers with remapped drives
If you attempt to install NFuse Classic 1.7 on a MetaFrame server where the server drives have been remapped, you will receive the 1720 error if the MetaFrame server COM catalog was not updated properly during drive remapping. In this case, you will also find COM+ errors in the event viewer with error ID 4097. See Error: "Event: 4097, Source: COM+" in the Event Viewer for more information about this error and Microsoft (article 286365).
4. FR2 Installation failed Error 1720On line 373 of the MSI log file.
During the installation of NFuse Classic 1.7, a new COM+ application is created. Although the application will impersonate a new account, CTX_NFUSE_ADMIN, the application is initially created with a default owner of IWAM_ServerName and then switched to impersonate CTX_NFUSE_ADMIN. If the IWAM account is disabled or its password is not synchronized with settings in the IIS metabase, NFuse fails to install. This Account may have been disabled for security concerns. Enable the account. Once the installation has completed, the IWAM account may be disabled without affecting the NFuseAdmin tool. See Microsoft article 297989 for information about dealing with unsynchronized metabase passwords.
5. FR2 Installation failed Error 1720 CTX_NFUSE_ADMIN account does not have access...on line 314 of the MSI log file.
The IWAM account or newly created CTX_NFUSE_ADMIN account does not have Access this computer from the network rights (line 314). If neither of the NETWORK or AUTHENTICATED USERS built-in groups has the Access this computer from the network user right assigned to them, then the NFuse installer is not able to assign the CTX_NFUSE_ADMIN account as the owner of the NFuseAdmin COM application. If the CTX_NFUSE_ADMIN account already exists, assign it to the policy. Otherwise, assign at least the NETWORK built-in group.
Select Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment and then double-click Access this computer from the network. Both the IWAM_ServerName account and the CTX_NFUSE_ADMIN account, created during installation, need this right.
Note: Attempting to install NFuse 1.7 when the CTX_NFUSE_ADMIN already exists may require the deletion of the account or require the assignment of administrative rights before reinstalling.
Mike Brown
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question