Error 1316 Network Error Occurred While Reading
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 11:44:56 GMT by s_ac15 (squid/3.5.20)
'A Network Error has Occurred' during VIPRE Business Agent installation Modified on: Fri, 15 May, 2015 at 11:41 AM PROBLEM The following error is encountered either during the installation, in
Cod4 An Error Occurred While Reading
the Agent's Installation Log file, or in Window's Event Logs: "Error 1316:
An Error Occurred While Reading The Berksfile
A Network Error has Occurred" Note: The Agent-MSI.csv file can be found in the Agent's Volatile Data folder: an error occured while reading from the device ipad C:\ProgramData\VIPRE Business Agent\logs\ (Other OS/Version Locations) ENVIRONMENT VIPRE Business VIPRE Business Premium All Supported Environments SOLUTION First make sure the policy has the correct IP address or machine name for the http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/error-1316-a-network-error-occurred-while/cf65ec6f-139c-4eb3-b718-e0c631b0cbe8 policy and/or update servers under the Communication tab 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, https://support.threattracksecurity.com/support/solutions/articles/1000071022-msi-error-1316-a-network-error-has-occurred-during-vipre-business-agent-installation you will need to recreate any MSI installer 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
Early Adopter Program ArcGIS Ideas Esri Support Services ArcGIS Blogs ArcGIS Code Sharing Product Life Cycles Manage Cases Request Case Start Chat Back to results Print Share Is This http://support.esri.com/technical-article/000005054 Content Helpful? Search on GeoNet Submit to ArcGIS Ideas Error: Error http://support.submain.com/kb/a38/troubleshooting-microsoft-error-1316-a-network-error-occurred-while-attempting-to-read-the-file___.aspx 1316: A network error occurred while attempting to read from the file :\ArcGIS\ArcGIS.msi Error Message Attempting the installation of ArcGIS Desktop, Concurrent or Single Use, returns the following error message:Error 1316: A network error occurred while attempting to read from the file
network error occurred while attempting to read the file... This error is related to the MSI technology we use for GhostDoc setup. NOTE: This article also applies to most any issue related to GhostDoc setup failing to uninstall the product - see the When uninstalling section at the bottom. When installing GhostDoc Most likely Do you have an older version of GhostDoc installed or have had it installed before? Sometimes setup fails to uninstall an older version, causing the error 1316. Removing the old copy through Control Panel usually resolves the issue. If you are not able to uninstall the older version of GhostDoc, use the Microsoft Fix It Utility at http://support.microsoft.com/mats/Program_Install_and_Uninstall Other Are you running setup from a network location? Try to copy GhostDoc setup to local drive and run from there. Do you have roaming profile? There are MSI technology issues related to roaming profiles - contact SubMain customer service for help with this. Do you have enough permissions to install software on the computer? Have you tried installing GhostDoc when logged as local Admin? Are there any IT policies that might restrict executing the setup? Some corporate policies create problems when installing GhostDoc. Do you have real-time anti-virus monitoring software enabled? These occasionally can trigger false positives with GhostDoc setup. Would the setup error go away after rebooting your computer? When uninstalling GhostDoc If you are not able to uninstall the older version of GhostDoc, use the Microsoft Fix It Utility at http://support.microsoft.com/mats/Program_Install_and_Uninstall Article ID: 38, Created: January 21, 2014 at 2:43 PM, Modified: April 8, 2015 at 11:28 AM Add Feedback Was this article helpful? Yes No Thanks for your feedback... Share this articleFacebookGoogle+TwitterOther Social Networks × Share With OthersBlinkListBlogmarksdel.icio.usDiggDiigoFacebookFriendFeedGoogle+LinkedInNetvouzNewsVineRedditStumbleUponTumblrTwitterYahoo BookmarksCancelPrint Help Desk Software powered by SmarterTrack 12.0 © 2003-2016 SmarterTools Inc. By using this site, you are accepting cookies to store user state and login information. × Forgot Login Trouble logging in? Simply enter your email address OR username in order to reset your password. For faster and more reliable delivery, add customer-service@submain.com to your trusted senders list in your email software.
Email Address OR Username Cancel Reset Email × Please log in below Username Password Remember Me Forgot your password? Close Register Login × Not Logged In You must be logged in to perform this action. Ok