본문 바로가기
카테고리 없음

A Problem Occurred During Install Nmm

denbovifivomau 2020. 8. 30. 10:56



@squid-box Yes.

  1. A Problem Occurred During Install Nexus Mods
  2. Nmm A Problem Occurred During Install 7zip

'A problem occurred during install: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. I have downloaded two nexus mods called helgen reborn and falskaar through nexus mod manger. Every time i try to install them, i get this failure message: 'a problem occured durning install: exception of type 'system.outofmemoryexception'was thrown.

Tracing an Unhandled Exception:
Exception:
Message:
Object reference not set to an instance of an object.
Full Trace:
System.NullReferenceException: Object reference not set to an instance of an object.
at Nexus.Client.BackgroundTasks.UI.ProgressDialog..ctor(IBackgroundTask p_bgtTask, Boolean p_booAllowCancel)
at Nexus.Client.ModManagement.UI.ModManagerControl.ViewModel_ActivatingMod(Object sender, EventArgs1 e) at System.EventHandler1.Invoke(Object sender, TEventArgs e)
at Nexus.Client.ModManagement.UI.ModManagerVM.DisableMods(List1 p_modMods) at Nexus.Client.Commands.Generic.Command1.Execute(T p_tArgument)
at Nexus.Client.Commands.Generic.CommandBinding`1.Execute()
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Tracing an Unhandled Exception:
Exception:
Message:
Object reference not set to an instance of an object.
Full Trace:
System.NullReferenceException: Object reference not set to an instance of an object.
at Nexus.Client.BackgroundTasks.UI.ProgressDialog.DoDispose()
at Nexus.Client.BackgroundTasks.UI.ProgressDialog.Dispose(Boolean disposing)
at System.ComponentModel.Component.Finalize()

I have attached the full tracelog. This time it happened during the install of the XPMSSE 4.33.
TraceLog20180721190945.txt

When you install Adobe Creative Suite 3 or individual Creative Suite 3 applications, you get one of the following error messages:

  • 'Some problems occurred during installation.'
  • 'Component install failed.'
  • 'Shared components failed to install.'

The Adobe CS5 Cleaner Tool helps resolve installation problems for Adobe Creative Suite 5, Adobe Creative Suite 4, and Adobe Creative Suite 3 software. For instructions on how to download and run the CS5 Cleaner Tool, see Resolve installation problems with CS5 Cleaner Tool (cpsid_82947).

Solution 2: Check the Event Viewer for error numbers.

Check the Windows Event Viewer for msilnstaller errors. For additional information on checking the event viewer, see the Windows Event Viewer in the Additional Information section of this document.

See the table below for common MSI error numbers and solutions. Although some of the referenced documentation points to a specific product, it can be applied to the resource referenced in the event viewer.

Error number Application Solution
1406 or 1402 Acrobat TechNote 329137
1603 Entire Suite Solution 6
1309, 1321 Entire Suite Solution 9
1704 or 1500 Entire Suite TechNote 332507

Solution 3: Disable virus-protection software and all firewall applications before you install Creative Suite 3 or any of its point products.

Virus-protection software exists to stop errant applications from installing on your system. If your virus-protection software believes that your Adobe application is a virus, the product isn't installed correctly. Furthermore, if the virus scan software is scanning a file or registry entry to update, it denies access. Remove your Adobe Creative Suite 3 product if you did not turn off your virus-protection software before you installed. Also, disable your virus-protection software and firewall. After both are disabled, reinstall the software.

The Adobe Creative Suite 3 includes a program called Version Cue. It installs a service called Bonjour that searches the network for other Bonjour-enabled machines. The installation of Version Cue can fail if your firewall is unaware of this protocol and blocks it. Turn off your firewall while installing to prevent this error from occurring.

Solution 4: Verify that you have sufficient disk space. If not, clear disk space on the target drive or install to a drive with sufficient disk space.

See the System Requirements information for the Adobe Creative Suite 3 product you are installing. Make sure that you are installing to a volume that meets the minimum requirements. System requirement information is listed on the Adobe.com product pages http://www.adobe.com/products.

See Remove CS3 prereleases (kb401574) to remove any Adobe pre-release or beta software from your computer.

Google Desktop can prevent the installation of the Adobe Creative Suite 3 products. See the system documentation to remove Google Desktop before installing the Adobe Creative Suite 3 product.

Creative Suite 3 installer can fail if the Creative Suite 3 disk is bad or damaged or if the computer hard drive is defective.

Perform the following steps to determine if the installation media is damaged:

  • Check the DVD for dust or damage. Clean the DVD with a soft, lint-free cloth. Check the back of the DVD for warping, smudges, scratches, or discoloration.

  • Attempt to install the Adobe Creative Suite 3 on a different computer. If the attempt is successful, the issue could be with the file system or hard disk drive on your original computer. For additional information, see the Hard Disk Check Utilities in the Additional Information section.

  • Attempt a desktop installation. For additional information on creating desktop installations, see one of the following documents:
  • Install Adobe Creative Suite 3 from the desktop (Windows XP and Windows Vista) (kb400609)
  • Install Adobe Creative Suite 3 from the desktop (Mac OS X)' (kb400613) for additional information on creating desktop installations.
  • If the purchased software was an electronic software download (ESD), download the software again. A file damaged during the download process causes errors during installation.

Solution 8: Remove previous versions of Flash Player.

If your error in the installer log includes the following, remove previous versions of Flash Player:

1: 0 2: Install Flash Player 8 Plugin.msi 3: {91057632-CA70-413C-B628-2D3CDBBB906B} 4: {91057632-CA70-413C-B628-2D3CDBBB906B}; 5: 0 6: 1 7: 1 8: 0 Error 1714.The older version of Adobe Flash Player 9 Plugin cannot be removed. Contact your technical support group.

To remove Flash Player:

  • Remove any log files in the Program FilesCommon FilesAdobeInstallers folder. These files contain or end in 'log' or 'gz.' Delete the files unless you are currently using them to locate error messages. If you are currently using them, move them out of this folder and in to a new folder on the desktop where they are accessible.

Solution 9: Update the user privileges to files.

Problem

If you received the error, 'Windows Installer Error 1321 'The Installer has insufficient privileges to modify the file C:Windowssystem32MacromedFlashFlashPlayerTrustAcrobatConnect.cfg,' then update the user privileges to the specific folders. (The error appears in the Event Viewer or Adobe Creative Suite installation log.)

The following is a sample from the Adobe Creative Suite installation log or Event Viewer:

Action 11:21:48: InstallValidate. Validating install Action start 11:21:48: InstallValidate. Error 1321.The Installer has insufficient privileges to modify the file C:Windowssystem32MacromedFlashFlashPlayerTrustAcrobatConnect.cfg. Action ended 11:21:48: InstallValidate. Return value 3.

See the installation log to determine which folder or file requires user privilege modification. The steps below reference the folder that has commonly been encountered. See Adobe Creative Suite Installation log for information on locating and reading the installation log.

  • Deselect the Use Simple File Sharing option at the bottom of the Advanced Settings section.
  • Right-click the Macromed folder and select Properties.
  • Make certain that Administrators and SYSTEM are listed and permissions for security is set to full control.
  • Select the Replace Owner On Subcontainers and Objects option and click Apply.
  • Select the Replace Permission Entries On All Child Objects With Entries Shown Here That Apply To Child Objects option.
  • Click OK, and then click Yes in the Security dialog box.
  • Right-click the Macromed folder and choose Delete.
  • Press F8 before Windows starts (when you see a message such as For Advanced Startup Options).
  • Select Safe Mode from the list of startup options.
  • When Windows is in Safe Mode, the words 'Safe Mode' appear in each corner of the desktop.
    • If Safe Mode doesn't appear in each corner of the desktop, then repeat steps a through c.
    • If Safe Mode does appear in each corner of the desktop, then log in as administrator of the local machine.
  • If a dialog box indicates that Windows is running in Safe Mode, then click OK.
  • Deselect the Use Simple File Sharing option at the bottom of the Advanced Settings section.
  • Right-click the Macromed folder and select Properties.
  • Make certain that Administrators and SYSTEM are listed and permissions for security is set to full control.
  • Select the Replace Owner On Subcontainers and Objects option and click Apply.
  • Select the Replace Permission Entries On All Child Objects With Entries Shown Here That Apply To Child Objects option.
  • Click OK, and then click Yes in the Security dialog box.
  • Right-click the Macromed folder and choose Delete.
  • Right-click the Macromed folder and select Properties.
  • Make certain that Administrators and SYSTEM are listed and permissions for security is set to full control.
  • If Administrators and SYSTEM are not set to full control:
  • Follow the onscreen navigation through the UAC elevation prompt.
  • Click Edit and click through the UAC elevation prompt.
  • Select the Replace Owner On Subcontainers and Objects option and click Apply.
  • Select the Replace Permission Entries On All Child Objects With Entries Shown Here That Apply To Child Objects option.
  • Click OK, and then click Yes in the Security dialog box.
  • Right-click the Macromed folder and choose Delete.
  • Click Continue and follow the onscreen navigation through the UAC elevation prompt.

You can use method on all versions of Windows, but it requires use of the command prompt utility.

  • Choose Start > Run, and then type cmd in the Open box. Click OK.
    Note:     Elevate the level of permissions for Windows Vista with UAC enabled.
  • Right-click Command Line and select Run As Administrator.
  • Use the following commands, including quotation marks, and press Return at the end of each line. Also make sure to enter spaces between /T, /E, /C, and /G in the third line:

    c: cd '%SYSTEMROOT%system32' cacls 'Macromed' /T /E /C /G Administrators:F cacls 'Macromed' /T /E /C /G SYSTEM:F exit

Solution 10: Update the registry keys noted in the error log.

A Problem Occurred During Install Nexus Mods

If you receive the Windows Installer error message, '1402 Could not read value to key' or '1406 Could not write value to key,' then update the permissions to the registry keys. (The error appears in the Event Viewer or Adobe Creative Suite installation log.)

See the installation log to determine which registry key requires user privilege modification. See Adobe Creative Suite Installation log for information on locating and reading the installation log.

The following is a sample from the Adobe Creative Suite Installation log or Event Viewer:

[6240] Fri Apr 27 18:02:12 2007 INFO Error 1406.Could not write value to key SoftwareClassesCLSID{1171A62F-05D2-11D1-83FC-00A0C9089C5A}. Verify that you have sufficient access to that key, or contact your support personnel. [6240] Fri Apr 27 18:02:12 2007 INFO Action ended 18:02:12: InstallFinalize. Return value 3.

[6321] Mon May 01 13:04:06 2007 INFO Error 1402.Could not read value to key SoftwareClassesCLSID{1171A62F-05D2-11D1-83FC-00A0C9089C5A}. Verify that you have sufficient access to that key, or contact your support personnel. [6321] Fri May 01 13:04:06 2007 INFO Action ended 18:02:12: InstallFinalize. Return value 3.

Note: Perform the steps in this solution after you complete the Adobe Creative Suite 3 installation.

The Administrators group listed below is the default local administrative group for Windows XP and Vista.

Disclaimer: This procedure involves editing the Windows registry. Adobe doesn't provide support for editing the registry, which contains critical system and application information. Make sure to back up the registry before editing it. For more information about the registry, see the Windows documentation or contact Microsoft.

There are two tasks you can perform before you do these steps to back up your current system and registry:

  • Create a restore point on your computer by choosing Start > Programs > Accessories > System Tools > System Restore.
  • Back up your registry immediately after you enter the Registry Editor by choosing File > Export. Export a backup copy of your registry with a name you can remember to a location you can remember.
  • Write down the path to the key referenced in the error message and leave the installation running. Multiple registry keys can be referenced in the log file. Write down all of the paths listed in the file. For example: SoftwareClassesCLSID{1171A62F-05D2-11D1-83FC-00A0C9089C5A}.
  • Choose Start > Run, type regedit in the Open text field of the Run dialog box, and then click OK.
  • In the Registry Editor dialog box, choose File > Export.
  • Navigate to the parent of the key referenced in the error message. For example, for the key SoftwareClassesCLSID{1171A62F-05D2-11D1-83FC-00A0C9089C5A}, open (double-click) HKEY_LOCAL_MACHINE >SOFTWARE > Software > Classes > CLSID.
    Note: These steps can vary slightly depending on the path in the error message. All registry keys listed begin in the HKEY_LOCAL_MACHINE folder.
  • Right-click on the parent key and select Permissions (HKEY_LOCAL_MACHINESOFTWARESoftwareClassesCLSID).
  • Verify that the Administrators and SYSTEM are present and that Full Control is selected under the Allow column.
  • Select the Administrators group (1), check 'Replace owner on subcontainers and objects' (2), click Apply (3), and select the Permissions tab (4).
    Note: Select the current administrator account if the Administrators group is unavailable.
  • Select 'Reset permissions on all child objects and enable propagation of inheritable permissions' (1) and click OK (2).
  • Click OK in the 'Advanced Security Settings' dialog box. Windows resets the permissions for each child object to correspond with its parent.

  • Repeat steps 1-10 on any additional registry keys.

  • Write down the path to the key referenced in the error message. Multiple registry keys can be referenced in the log file. Write down all of the paths listed in the file. For example: SoftwareClassesCLSID{1171A62F-05D2-11D1-83FC-00A0C9089C5A}.
  • Choose Start, type regedit in the Search text field, and then press Enter.
  • In the Registry Editor dialog box, choose File > Export.
  • Navigate to the parent of the key referenced in the error message. For example, for the key SoftwareClassesCLSID{1171A62F-05D2-11D1-83FC-00A0C9089C5A}, open (double-click) HKEY_LOCAL_MACHINE >SOFTWARE > Software > Classes > CLSID.
    Note: These steps can vary slightly depending on the path in the error message. All registry keys listed begin in the HKEY_LOCAL_MACHINE folder.
  • Right-click on the parent key and select Permissions (HKEY_LOCAL_MACHINESOFTWAREClassesCLSID).
  • Verify that the Administrators and SYSTEM are present and that Full Control is selected under the Allow column.
  • Select the Administrators group and 'Replace owner on subcontainers and objects' on the Owner tab.
    Note: Select the current administrator account if the Administrators group is unavailable.
  • Select 'Allow inheritable permissions from parent to propagate to this object' on the Permissions tab. Also select 'Reset permissions on all child objects and enable propagation of inheritable permissions.'
  • Click OK in the 'Advanced Security Settings' dialog box. Windows resets the permissions for each child object to correspond with its parent.

  • Repeat steps 1-10 on any additional registry keys.

If Adobe Creative Suite 3 still displays an error message, then investigate permissions on the particular registry key causing the error. Occasionally, renaming the key allows the installer to re-create the key and reset the permissions if the key is corrupted. If you can't change permissions or rename that key, then contact Microsoft or your hardware vendor for assistance.

Solution 11: Remove current Adobe color profiles and update registry settings.

If you receive the Windows Installer error message, 'Updating component registration Message type: 2, Argument: 1 Message type: 2, Argument: 1,' then remove current Adobe color profiles and update the permissions to the registry keys. (The error appears in the Event Viewer or Adobe Creative Suite installation log.)

To verify the error, search the installation log for return value 3 and verify the error captured in the log file. See the Adobe Creative Suite Installation log for information on locating and reading the installation log.

The following is a sample from the Adobe Creative Suite Installation log or Event Viewer:

UninstallColorProfilesRollback.E35C3ECB_5FDA_49E1_AB1F_D472B7CB9017 (Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- BEGIN - Adobe_UninstallColorProfiles -*-*-*-*-*-*-*-*-*-*-*-*- (Adobe) UninstallColorProfiles - MSIRUNMODE_ROLLBACK (Adobe) Requesting property: CustomActionData (Adobe) Property cannot be retrieved (Adobe) No Color Profiles to manipulate (Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- END - Adobe_UninstallColorProfiles -*-*-*-*-*-*-*-*-*-*-*-*- Removing ODBC components Updating component registration Message type: 2, Argument: 1 Message type: 2, Argument: 1 Action ended 13:52:26: INSTALL. Return value 3.

The Administrators group listed below is the default local administrative group for Windows XP and Vista.

Disclaimer: This procedure involves editing the Windows registry. Adobe doesn't provide support for editing the registry, which contains critical system and application information. Make sure to back up the registry before editing it. For more information about the registry, see the Windows documentation or contact Microsoft.

There are two tasks you can perform before you do these steps to back up your current system and registry:

  • Create a restore point on your computer by choosing Start > Programs > Accessories > System Tools > System Restore.
  • Back up your registry immediately after you enter the Registry Editor by choosing File > Export.Exporting a backup copy of your registry with a name you can remember to a location you can remember.

Remove the old ICC profiles

  • Navigate to WINDOWSsystem32spooldriverscolor using Windows Explorer.
  • Delete the following ICC profiles:
    • AdobeRGB1998.icc
    • AppleRGB.icc
    • ColorMatchRGB.icc
    • EuropeISOCoatedFOGRA27.icc
    • EuroscaleUncoated.icc
    • JapanColor2001Coated.icc
    • JapanColor2001Uncoated.icc
    • JapanColor2002Newspaper.icc
    • JapanWebCoated.icc
    • USSheetfedCoated.icc
    • USSheetfedUncoated.icc
    • USWebCoatedSWOP.icc
    • USWebUncoated.icc
      Note: It's possible that not of the files listed are located in the directories. Remove as many of the files that are present. If you are unable to remove an ICC profile, try correcting permissions to the folder. Use the steps in Solution 9: Update the user privileges to files as a guide.
  • Repeat Steps 1-2 using Program FilesCommon FilesAdobeColorProfiles as the folder location.
  • Choose Start > Run, type regedit in the Open text field of the Run dialog box, and then click OK.
  • In the Registry Editor dialog box, choose File > Export.
  • Right-click PDF Admin Settings and select Permissions.
  • Verify that the Administrators and SYSTEM are present and that Full Control is selected under the Allow column.
  • Select the Administrators group (1), check 'Replace owner on subcontainers and objects' (2), click Apply (3), and select the Permissions tab (4).
    Note: Select the current administrator account if the Administrators group is unavailable.
  • Select 'Reset permissions on all child objects and enable propagation of inheritable permissions' (1) and click OK (2).
  • Click OK (3) in the 'Advanced Security Settings' dialog box. Windows resets the permissions for each child object to correspond with its parent.
  • Choose Start, type regedit in the Search text field, and then press Enter.
  • In the Registry Editor dialog box, choose File > Export.
  • Verify that the Administrators and SYSTEM are present and that Full Control is selected under the Allow column.
  • Select the Administrators group and 'Replace owner on subcontainers and objects' on the Owner tab.
    Note: Select the current administrator account if the Administrators group is unavailable.
  • Select 'Allow inheritable permissions from parent to propagate to this object' on the Permissions tab. Also select 'Reset permissions on all child objects and enable propagation of inheritable permissions.'
  • Click OK in the 'Advanced Security Settings' dialog box. Windows resets the permissions for each child object to correspond with its parent.

If you can't change permissions or rename that key, then contact Microsoft or your hardware vendor for assistance.

If none of the solutions allow you to install Creative Suite 3, contact Adobe Technical Support. Have your installer log file and event viewer information ready in case you're asked to send it to support. See Adobe Creative Suite Installation log or Windows Event Viewer for additional information to obtain this information.

The Windows Event Viewer and the Adobe Creative Suite installer log are two tools that can assist you in determining the cause of the problem.

Event Viewer is a Microsoft utility that collects data about errors that occur as you run Windows. The Adobe Creative Suite 3 installer uses a number of Windows installers during the installation of any products. You can use the Windows Event Viewer to diagnose issues with the Windows installer.

  • Launch the Event Viewer.
    • On Windows XP
      1. Choose Start > Run and type in eventvwr
      2. Click OK.
    • On Windows Vista
      1. Click Start.
      2. Type eventvwr into the search window and press Enter.
  • Look for yellow warnings and red errors in the Type column that also contain MSI Installer in the Source column.
    Note: Sometimes, this data points you to an application or service that is conflicting with the installer and causing installer failure. Adobe Support sometimes requires this information if you contact Adobe Technical Support.

The Adobe Creative Suite 3 installer log contains detailed messages on why the install failed (or succeeded). The log file can assist you in diagnosing the problem faster. Every attempted installation appends information to the previous installation log. Deleting the current installation log and running the installation again can simplify the troubleshooting process. The log file is created on both Windows and Mac OS. The error messages contained differs in format because of Operating System differences.

  • Navigate to the Adobe Creative Suite 3 log file.
    Program FilesCommon FilesAdobeInstallers folder.
  • Decompress the Adobe Creative Suite 3 log file.
    Important: The log file is archived using a compression utility called gzip and requires a decompression tool such as Winzip or WinRAR.
    Note on log names:
    • The log file for the Creative Suite 3 Design Premium, for example, is Adobe Creative Suite 3 Design Premium 1.0.log.gz.

  • Search the log files for the following case sensitive keywords: FATAL, DEBUG, ERROR, and Return Value 3 (Windows only).
    If the log contains one or more of the following error messages, try Solutions 1-5, and then the solution listed next to the error message:

    • Windows Installer Error 1321 'The Installer has insufficient privileges to modify the file C:Windowssystem32MacromedFlashFlashPlayerTrustAcrobatConnect.cfg.': Solution 9 - Update User Privileges.
    • Windows Installer Error 1402, 'Could not write value to key' on Windows: Solution 10 - Update the registry keys.
    • Windows Installer Error or 1406, 'Could not read value to key' on Windows: Solution 10 - Update the registry keys.

You can run disk utilities to verify the integrity of the hard disk drive. Damaged sectors, cross-linked files, or other file corruptions can cause installation failures. Run these utilities to help correct problems with the hard disk or identify issues.

Nmm A Problem Occurred During Install 7zip

Disk Defragmenter for Windows is designed to increase access speed (and sometimes increase the amount of usable space). Disk Defragmenter rearranges files stored on a disk to occupy contiguous storage locations.

To launch Disk Defragmenter:

  • Click Start > All Programs > Accessories > System Tools > Disk Defragmenter.
  • Select the Primary Hard Disk Drive and click Defragment.

Chkdsk is a command line utility that can check your hard drive for errors and bad sectors. The 'f' switch is designed to scan and attempt to fix the errors found.

Launch Chkdsk

  • Windows XP
    1. Choose Start > Run.
    2. Type cmd and click OK.
    3. Type chkdsk /f and press Enter.
    4. When the scan is complete, type exit and press Enter.
  • Windows Vista
    1. Choose Start > Programs > Accessories.
    2. Right-click the Command Prompt and select Run As Administrator.
      Note: Follow the onscreen UAC dialogs, if present, to allow the process. Supply an administrator account and password, if prompted.
    3. Type cmd and click OK.
    4. Type chkdsk /f and press Enter.
    5. When the scan is complete, type exit and press Enter.

More like this

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices | Online Privacy Policy





티스토리툴바