Having trouble initializing QuickBooks POS Application Log?

Having trouble initializing QuickBooks POS Application Log?

Error initializing the QuickBooks POS application log is one of the errors in the QuickBooks software which will not allow the user to continue their work on the QuickBooks application. Usually, these kinds of errors occur because of the compatibility of the two software and the same happens with QuickBooks as well. As the name denotes, the most frequent time of this error popping up is while initializing or launching the QuickBooks application. The errors can be understood better and prevented under the expert guidance of the QuickBooks support team who can be reached out. However, there are some causes below that could help the user understand this.

What are the causes of the error?

The several causes for this error to appear to include:

  1. If user experiences crashes in the application, then the system files might have been corrupted or damaged, thus leading to the error initializing QuickBooks POS application log.
  2. When QuickBooks is trying to build a connection to the company file.
  3. Some technical problems such as network issues, changing the same transactions over a period of time.
  4. Unexpected closing of the QuickBooks software.

What are the effects of the error?

The various effects of this error include:

  1. The damage of the Windows system files which causes this error restricts the user to work on the system.
  2. QuickBooks software application gets corrupted. It is better to know about the effects properly from the experts of QuickBooks application as they have a more extensive approach towards this matter.

How to resolve the error?

You May Also Read: How to Fix QuickBooks Error 15271?

Solution 1: Editing the contents of the QBPOS Shell folder

  1. Press Ctrl+Alt+Delete on your keyboard and select Task Manager.
  2. Navigate to the Processes tab and highlight ‘QBPOS Shell’. Then select ‘End Task’.
  3. Navigate to the Windows Start menu and then choose File Explorer or Open Windows Explorer (for Windows 7).
  4. Go to the View tab and mark the Hidden items checkbox.
    For Windows 7: Select Organize, then choose Folder and Search Options.
  5. Then click on ‘This PC or Computer’ (for Windows 7 operating system) and navigate to the below path:

C:\Users\ {User logged on}\AppData\Local\Intuit\QBPOSShell.exe…\{last modified folder}.

  1. Right-click the user.config file, then click on Rename.
  2. Rename the file to user.configold.
  3. Then close the window, then re-launch QuickBooks Point of Sale for Desktop.

Solution 2: Creating a new Windows admin

For Windows 10, 8.1, and 8:

  1. Use the right click button on the Windows Start menu and select Control Panel.
  2. Select the option that says ‘User accounts and Family Safety’, then select ‘User Accounts’.
  3. Select ‘Manage another account’ and then click on ‘Add a new user in PC Settings’ and then select ‘Add a user’.
  4. Sign in without using a Microsoft account and select Local Account.
  5. Enter a user name, leave the password blank, then select Next >> Finish.
  6. After restarting the computer, sign in with the new account.
  7. Open QuickBooks Point of Sale for Desktop.
    Note: The user might have to open it from the Windows Start menu if they do not see an icon on the Desktop.

For Windows 7:

  1. Navigate to Windows Start menu or press the Windows button, then select Control Panel and then User Accounts.
  2. Then move to the User Accounts window and select ‘Manage another account’.
  3. Select ‘Create a new account’ and then add a name for the account. Choose ‘Administrator’. Then create a new account.
  4. After restarting the computer, sign in with the new account.
  5. Open QuickBooks POS for Desktop.
    Note: The user might have to open it from the Windows Start menu if they do not see an icon on the Desktop.

If the issue still persists after trying the above two solutions, the best way to get this issue fixed would be to contact the highly reliable QuickBooks support team.

, , ,

Comments are closed.
error: Content is protected !!