QB POS Product
Technical Support procedure to fix Permission Errors NOT Working in many cases. Here is an update to my Article of June 14 on this QB POS R5 error.
About a week ago, I wrote an IA article titled “QB Point of Sale Release 5 may cause Permission Errors” in which I discussed a rather elaborate set of steps that Intuit POS Technical Support had outlined for repairs to both POS-Servers and POS-Client workstations suffering from these update related errors. Intuit had released the repair steps as part of a KBA to resolve the ‘permission errors’ associated with the POS-2013 (v 11) R5 release.
After more than an hour on the phone with QB-POS Technical Support I now find that ‘the fix’ may or may not work in all situations; and it appears that it DOES NOT work in more situations than it does.
Apparently the problems are not just associated with the QB-POS ‘program’, and the lack of a complete ‘install’ of the R5 patch. It appears in some cases the patch actually corrupted the POS Data-file (in terms of user accounts). I am taking an educated guess here, but this could possibly be either corruption of the POS-user data, or in the encryption of that data; there have been similar user password encryption failures reported in some versions/releases of QuickBooks ‘financial’ in recent months.
Intuit is apparently aware of this situation and is working on a resolution; however, it seems that the only ‘operating solution' for the ‘Error -121 Permission denied, you do not have persmissions.....’ probem is to:
- Log-into the POS-server as Sysadmin, then log-out;
- Log-into a POS-client as Sysadmin, then log-out;
- Repeat step 2 for each POS-client workstation, one at a time; and
- Then log-into the POS-server and each POS-client as Sysadmin simultaneously.
In other words, all users must be logged-into QB-POS on each machine as the Sysadmin; you cannot use any other ‘user account’ to log-in. In my most recent attempt to resolve this I was also forced to ‘remove’ the Sysadmin “password”; some workstations simply refused to accept the Sysadmin log-in without throwing the Error until I removed the password associated with the Sysadmin user.
The alternative solution Intuit can offer at present is for users to send their QB-POS Data-file to POS Technical Support (Data services) for ‘file repair’. This is further indication of ‘data corruption’ in the actual file which resulted from the R5 update, and not simply a POS ‘application’ problem. Intuit POS Technical Support recommends this option only if it is essential to have use of individual user log-in accounts until a final resolution is issued for all installations of QB-POS 2013 (V11). The length of time in repairing the file can vary based upon the file, and workload of Data Services.