Error 1606 Could Not Access Network Location Microsoft Word Startup
Contents |
360 games PC games error 1606 when installing Windows games Windows phone games Entertainment All Entertainment error 1606 could not access network location autodesk Movies & TV Music Business & Education Business Students & educators could not access network location windows 7 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet error 1606 in windows 10 Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
Error 1606 Could Not Access Network Location Appdata
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
location [location] Explanation The installer checks the Windows registry to identify the startup path for Microsoft Word templates. If a valid path is found in the Registry, the SDL Trados Word
Error 1606 Could Not Access Network Location 0 Windows 10
template (Trados7.dot, Trados8.dot or Trados8.dotm) is copied to this location. If the path is error 1606 could not access network location vmware vcenter site recovery manager invalid or the installer is unable to write into the registry the error 1606 occurs and the installation stops. Resolution error 1606 fix There are two possible solutions. Solution 1 For each version of Microsoft Word (Word XP, Word 2003, and so on), the startup path is written to different keys in the registry. The [location] in https://support.microsoft.com/en-us/kb/886549 the error message is the Word's startup folder. It could be either: Office-wide: %ProgramFiles%\MicrosoftOffice\OfficeXX\Startupfolder Or User-specific: Windows XP: %USERPROFILE%\ApplicationData\Microsoft\Word\Startupfolder Windows Vista/7: %USERPROFILE%\AppData\Roaming\Microsoft\Word\STARTUP Ensure that the correct Word Startup path is specified in both Microsoft Word and the Windows Registry: Open your Microsoft Word Make sure that the Startup field contains a valid path to the Word Startup folder. If necessary, click the Modify... button and point to http://producthelp.sdl.com/kb/Articles/3185.html the valid path. Microsoft Word 2003 and before: Go to Tools > Options > File Locations Microsoft Word 2007 and later: Go to Microsoft Office Button > Word Options > Advanced > General > File Locations Write down the path and close Word again. Go to Start > Run... Type regedit and click OK. The Registry Editor opens. Navigate to the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\X.0\Word\Option\STARTUP-PATH where X.0 depends on your version of Microsoft Word: Office 2002 (XP) - 10.0 Office 2003 - 11.0 Office 2007 - 12.0 Make sure that the X.0 value in the Registry matches the Office version you have installed. Remove all other X.0 folders as they may confuse the installer. The value of the STARTUP-PATH key must contain a valid path. If it does not, enter a valid path and repeat the installation process. Solution 2 Read the following Microsoft Support article: http://support.microsoft.com/?scid=kb%3Ben-us%3B886549&x=7&y=15 Note Internal Comment Reference Category Reference Attribute This translation is not an official version and has been provided for convenience only, using SDL Language Cloud. It has been provided on a pure “As Is” basis. The official version of this article is its English version. Any discrepancies or differences created in this translation
0 20180 views 07/19/2006 Software Deployment Windows Installer (MSI) Windows Installer (MSI) Error Messages Google Google Desktop Enterprise 5 When installing Autodesk products via SMS as the system account we run into sporadic errors where the package runs fine as a user, but when run from sms fails with an error 1606 - can't access network location. All the 1606 errors I have run into relate to the Windows installer trying to read / use a variable that is not populated. Different Autodesk products want to place files in different places. For example, Architectural Desktop wants to place some files in the My Documents folder, while the DWG viewer does not. The installer reads the variables from the system's registry. If running as a user it reads the variable from HKCU if running as the system account (such as via a GPO or SMS) it should read from the system registry HKEY-USERS\S-1-5-18\Software\Microsoft\Windows\Currentversion\Explorer\Shell Folders... but it appears that it is instead reading from HKEY-USERS\.DEFAULT. I tried the fix suggest in Autodesk support article TS100633 but found the system registry was correctly populated and I was still getting the error. You can turn on verbose logging and compare a failed log to a successful log and see where it incorrectly sets a variable when the registry setting is not configured, then when it tries to read/write to that path it fails with the 1606 error that it cannot access the location because it does not exist. The script below will populate all the default user values in the registry with the "default" values, except for the personal (my docs), app data, and local settings folder which are populated with the paths to the system account's profile. After making the changes on my test machines I did logon as a user without a profile to ensure new profile creation is not effected and indeed a new user's registry is normal (points to its own my docs folder, not the system's). I'm sending this script as a silent mandatory to all the systems to prevent further 1606 errors due to this cause. My guess is there is an error with the Windows installer technology, Autodesk's use of the installer is reading from the wrong key, or possibly the system account is being regenerated each time it runs for some reason and each time pulls its values from the default user registry... in any case, this script has been resolving the 1606 errors.' The "de