This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Knowledge Base
- :
- Runtime Error 2330. Error getting file attributes: GetLastError: 4350
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Runtime Error 2330. Error getting file attributes: GetLastError: 4350
Runtime Error 2330. Error getting file attributes: GetLastError: 4350
Summary
Windows Installer runtime error 2330Symptoms
The error code 2330 is returned by the Windows Installer is an internal errors and does not have authored strings. The problem can occur if the installation package has been incorrectly authored.During runtime a Windows Installer error panel displays:
Error getting file attributes: [3]. GetLastError: [2].
Cause
Based on findings this is a non-exhaustive list of possible causes:- Files are installed to PersonalFolder and the user?s document folder is setup as an UNC path. The situation is known to occur in the event files cannot be found when the standard Operating System directories are changed.
- Another example changing the location of the Program Files folder by modifying the ProgramFilesDir registry value. Reference: Microsoft does not support changing the location of the Program Files folder by modifying the ProgramFilesDir registry value
- Deleting Recognized Environment Variables can exhibit this problem. For example, if the CSIDL_MYPICTURES (The file-system directory that serves as a common repository for image files) is deleted or becomes corrupt or redirected to network share.
Resolution
1) Use Recognized Environment Variables that are not mapped to a UNC path. There are a host of variables the Operating System expects. In the event these are changed, become corrupt and/or deleted you may run into the unexpected situation.Reference Microsoft article: Recognized Environment Variables
2) Provide Administrative privileges. Under certain circumstances elevating the install using a setup.exe wrapper with token to run-as Admin is enough to overcome the problem.
Additional Information
Reference Microsoft Document: Windows Installer Error Messages
No ratings