Please remember this is a user-to-user community that relies on member participation. We encourage you to ask questions AND share your own thoughts, experience and advice.
I'm on windows 7. I recently updated to the new version. I did it twice, just like the instructions said I should. I always get this message when I try to open a file: "Unable to open Database. Unable to write to directory:c:\program Files (x86)\Profile". This is too much! What a mess! Can anybody help? If this is another installation problem with the automatic updates then Profile should advise us not to use it at all! Do I need to uninstall the software again and install from a cold version. That's a lot of work!
Page 1 of 1
updated to new version Database doesn't work
MultiQuote
#2
Tim Parris 
- Top Contributor
-
- Group: Members
- Posts: 1,534
- Joined: 02-December 06
- Gender:Male
- Location:Ottawa, ON
Posted 04 October 2010 - 01:53 AM
I had a similar problem, specifically with the database explorer. (I am on the premier version of the software, while you may be on the basic version.)
The problem is that the more recent releases of Windows (not Profile) applies a security rating on the program files directory. The new release of Profile appears to be storing some settings within the program files directory rather than the user directory (or all users directory.)
To fix this, what I did (which may not be correct) was to go to the directory in question (c:\program Files (x86)\Profile) and upgrade the security settings to allow myself full access to the directory. Locate the directory and right-click it. Select properties and you'll find security as one of the tabs.
I caution that changing the security of a directory may have unanticipated effects. You may wish to investigate before attempting this solution.
The problem is that the more recent releases of Windows (not Profile) applies a security rating on the program files directory. The new release of Profile appears to be storing some settings within the program files directory rather than the user directory (or all users directory.)
To fix this, what I did (which may not be correct) was to go to the directory in question (c:\program Files (x86)\Profile) and upgrade the security settings to allow myself full access to the directory. Locate the directory and right-click it. Select properties and you'll find security as one of the tabs.
I caution that changing the security of a directory may have unanticipated effects. You may wish to investigate before attempting this solution.
#3
Jo@Intuit
- New Member
-
- Group: Intuit Staff
- Posts: 8
- Joined: 25-April 07
Posted 04 October 2010 - 02:49 PM
Mozart, on 03 October 2010 - 11:30 PM, said:
I'm on windows 7. I recently updated to the new version. I did it twice, just like the instructions said I should. I always get this message when I try to open a file: "Unable to open Database. Unable to write to directory:c:\program Files (x86)\Profile". This is too much! What a mess! Can anybody help? If this is another installation problem with the automatic updates then Profile should advise us not to use it at all! Do I need to uninstall the software again and install from a cold version. That's a lot of work!
Hello Mozart,
Thank you for your comment.
To address the issue you are having, please right click on the ProFile icon and choose run as administrator.
If you are still having any issues, please don't hesitate to phone support and we will assist you further.
#4
Jeffrey @ Acclaimed Tax Services - Hamilton
- New Member
-
- Group: Members
- Posts: 3
- Joined: 06-October 10
Posted 06 October 2010 - 09:39 PM
It appears that this problem is not caused by Profile. The issue is that Microsoft, in a recent Windows 7 “security update”, made the folder C:\Program Files\ un-writable (except for the installation and removal of program application files) by all Windows 7 computer users - even those with Administrator status. I suppose Microsoft’s objective is to stop people from accidentally altering program application files, or to prevent malicious programs. Microsoft did this for Windows 7, but not Windows XP, which is why Windows XP users are not experiencing this Profile database problem (I don’t know about Vista).
By default since its beginning, Profile has been locating its database index files in C:\Program Files\Profile\, which is now not allowed by Windows 7. So now Profile must use a different location to store database index files for computers using Windows 7 and likely subsequent Windows versions.
Windows 7 has a new folder C:\ProgramData\, which it appears Microsoft created for any application data (including for Microsoft applications). My solution and suggestion is that Profile users create a new folder C:\ProgramData\Profile\. Then, within Profile, use Options | Database to change the folder location for every database index file for each module and year. Simply repace "Program Files" with "ProgramData". For each, the new file location would be C:\ProgramData\Profile\[filename] where the filename is, for example, 2010T1DB.GDT. Then, use Database | Open (as usual to open a tax file) which will initially show a blank list of client names. Click on "Index" to build the new index file for the first time for each module (T1, T2, T3) and for each year. Enjoy!
Side Note: I learned that the Profile database index files should not be located in “My Documents” or in “Shared Documents” or “Public Documents” as doing this would potentially cause conflicts.
I hope this helps everyone experiencing this problem.
- Jeffrey
By default since its beginning, Profile has been locating its database index files in C:\Program Files\Profile\, which is now not allowed by Windows 7. So now Profile must use a different location to store database index files for computers using Windows 7 and likely subsequent Windows versions.
Windows 7 has a new folder C:\ProgramData\, which it appears Microsoft created for any application data (including for Microsoft applications). My solution and suggestion is that Profile users create a new folder C:\ProgramData\Profile\. Then, within Profile, use Options | Database to change the folder location for every database index file for each module and year. Simply repace "Program Files" with "ProgramData". For each, the new file location would be C:\ProgramData\Profile\[filename] where the filename is, for example, 2010T1DB.GDT. Then, use Database | Open (as usual to open a tax file) which will initially show a blank list of client names. Click on "Index" to build the new index file for the first time for each module (T1, T2, T3) and for each year. Enjoy!
Side Note: I learned that the Profile database index files should not be located in “My Documents” or in “Shared Documents” or “Public Documents” as doing this would potentially cause conflicts.
I hope this helps everyone experiencing this problem.
- Jeffrey
Page 1 of 1