1316 Network Error Occurred
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 29 Sep 2016 23:55:27 GMT by s_bd40 (squid/3.5.20)
installation Modified on: Fri, 15 May, 2015 at 11:41 AM PROBLEM The following error is encountered either during the installation, in the Agent's Installation Log file, or in Window's error 1316 a network error occurred java Event Logs: "Error 1316: A Network Error has Occurred" Note: The Agent-MSI.csv
Error 1316 A Network Error While Attempting
file can be found in the Agent's Volatile Data folder: C:\ProgramData\VIPRE Business Agent\logs\ (Other OS/Version Locations) ENVIRONMENT VIPRE Business
Network Error Occurred Galaxy S5
VIPRE Business Premium All Supported Environments SOLUTION First make sure the policy has the correct IP address or machine name for the policy and/or update servers under the Communication tab http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/error-1316-a-network-error-occurred-while/cf65ec6f-139c-4eb3-b718-e0c631b0cbe8 of the Policy Properties.If the Microinstaller is still installed, remove it from Add/Remove Programs (Windows XP, 2003) or Programs and Features (Windows Vista+) and run the new installer now that the correct IP address or machine name is in the policy. Note: If you had to change the IP address or machine name, you will need to recreate any MSI installer https://support.threattracksecurity.com/support/solutions/articles/1000071022-msi-error-1316-a-network-error-has-occurred-during-vipre-business-agent-installation packages that you previously created.If that doesn't fix the issue follow, these directions: Open regedit (Start > Run > type regedit and then press Enter) Delete the key HKEY_CLASSES_ROOT\Installer\Products\116445D9734F351419E319EC305638CC Run the installer again CAUSE The IP address or machine name for the policy and/or update server is incorrect. OR The agent sees the software already installed due to the registry key being left behind from a previous installation and will try to run a repair with a cached MSI installer the registry key is pointing to. Did you find it helpful? Yes No Can you please tell us how we can improve this article? Related Articles MSI Error 1317: 'An error occurred while attempting to create the directory' during installation MSI Error 1606: 'Could Not Access Network Location' during installation MSI Error 1402: 'Could not open key' during Vipre product installation/upgrade MSI Error 1721: 'A program required for this install to complete could not be run.' during installation/uninstallation MSI Error 1303: 'The installer has insufficient privileges to access this directory' during installation/upgrade MSI Error 1321: 'The installer has insufficient p
Windows Installer (MSI) Windows Installer (MSI) Error Messages Help with MSI (Microsoft Installer) error 1316: A network error occurred while attempting to read from the file: [2] 0 Comments [ + ] Show Comments http://www.itninja.com/question/help-with-msi-1316 Comments This content is currently hidden from public view. Reason: Member has been banned http://stackoverflow.com/questions/21982496/windows-installer-error-1316-installer-looks-for-wrong-filename from the site For more information, visit our FAQ's. This content is currently hidden from public view. Reason: Member has been banned from the site For more information, visit our FAQ's. Please log in to comment Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable. Answers 1 This network error has been reported to occur if you rename the installation MSI file after installation, and then attempt to execute it a second time. Stuck? Try removing the software with the Windows Installer CleanUp Utility Also see: OFFXP: Error 1316. Setup Cannot Read from .Msi File OFF2000: Error Message: Error 1316 Running Setup for Administrative Installation Answered 01/29/2004 by: AppDeploy.com Please log in to comment Please log in to comment 1 I've been network error occurred struggling with this error for days with no success, the MSI was perfect, no errors, minimal ICE errors but just would not install.It turned out that the fix was to delete ALL of the entries from the WiseSourcePath table and then recompile!I don't know if this is a limitation within Wise (using PS v5.6) as there are 1500+ files in the package or something else.Hopefully this might save someone else a few days in the future. Answered 05/09/2006 by: Nailmonkey Please log in to comment Please log in to comment 1 Initially I had "Don't Update or Recompress Files while Saving(MSI Only)" option UNCHECKED in my MSI. After I modified registry, cleaned up some files, I "CHECKED" the above option in WISE-->Product Details. After saving the MSI with above option checked, when I tried to install on a clean box, I got the "Error 1316 Network Error". So I went back to my MSI, and resaved it with the above option UNCHECKED. This time, I could install the MSI successfully on a clean box. Hope this helps. Answered 10/27/2006 by: YRKUMAR Please log in to comment Please log in to comment 1 Error can occur when the package being run is already installed, and the filename stored in the value PackageName under the here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Windows Installer Error 1316. Installer looks for wrong filename up vote 1 down vote favorite I'm trying to implement the following self-update mechanism for my application: If an update is available, my application downloads the (WiX generated) MSI package and writes it to its AppData folder with an arbitrary name. The application then initiates the update process by calling msiexec /fvomus "