HomeTechnical Support » Error Messages

Error Messages

access violation message Messages in this topic - RSS

email submissions
Administrator
Posts: 173


6/8/2018
email submissions
Administrator
Posts: 173
From: Wellspring Support
Sent: Friday, June 8, 2018 8:59 AM
Subject: RE: printboss access violation message
– The error you provided is difficult to pinpoint The following are the possibilities:

The top three possible causes for the Access violation that references KERNELBASE32.dlll are:

1. Virus - Run antivirus software.
2. Corrupted File - Remove the file or reinstall OS.
3. Corrupted Registry - Use a DLL Error Repair Tool. (Use Google for recommendations, but we have not tested any DLL error repair tools).

The registry may have a corrupt or incorrect entry. Please try the following:

1. Verify the location of the PrintBoss Configuration Settings:
  • Open the PrintBoss Master Application (PB32.exe).
  • Click on the Options menu and choose PrintBoss Driver Settings.
  • Verify 'Configuration settings Save Location' is set to 'Local Registry & User Registry (Standard)'. Continue to Step 2 is this is a match.
  • 2. Verify the user has sufficient permissions to the Registry.
  • Return to the PrintBoss Master Application screen.
  • Hold down the Shift+Ctrl+P keys to open the Permission Analyzer.
  • The permissions for the Current User (CU) registry should be all capital letters.
  • The user only needs Read (capital R) permissions to the Local Machine (LM) registry once PrintBoss is installed.
  • Continue to Step 3 if 'c' and 'd' above are a match.
  • 3. Rename the Current User and Local Machine registry settings used by PrintBoss and allow new settings to be created the next time PrintBoss is opened.
  • Close PrintBoss.
  • Run or open regedit.
  • Navigate to Current User\Software\Wellspring Software and rename the Wellspring Software folder by adding something on the end.
  • Navigate to Local Machine\Software.
  • i. If this is a 64-bit computer, select Wow6432Node\Wellspring Software and rename the Wellspring Software folder by adding something on the end.
    ii. If this is not a 64-bit computer, select the Wellspring Software folder and rename the Wellspring Software folder by adding something on the end.
  • Reprint to PrintBoss and let us know the results

  • If the error persists, then the corrupted resource used by PrintBoss is elsewhere in the operating system or general registry settings and will more difficult to find. Please keep us apprised of your progress. I do not have any openings today, but you are welcome to enter a case at www.wellspringsoftware.com/help. The next available technician will respond.
    0 link
    email submissions
    Administrator
    Posts: 173


    6/8/2018
    email submissions
    Administrator
    Posts: 173
    Sent: Thursday, June 7, 2018 7:03 PM
    Subject: FW: printboss access violation message



    Print boss can properly see there’s a check file in a given entity folder, but when we click Yes to process it, we received the below error a few times today. The error seems to appear randomly – three times today several hours and many checks processed between the first and second/third errors. This is not the first check for the entity folders.

    Here’s some data about what we saw and tried troubleshooting:
    • The initial error today was from a check file in 01HL1 folder, the second in the 01FUN folder – different check files each time. The user and I both received the first error, which is the only one I tried testing myself.
    • For the first one, the check file could be successfully printed from a different folder. Also, other check files could be printed from in the 01HL1 folder.
    • For the second one, we copied the check file to the 0117N folder and got the same error once again. Then I deleted and repasted the 01FUN check file back into the same 0117N folder and it printed without the error. A subsequent 01FUN check file printed without an error 5 minutes later.

    I tried looking for that error in the PrintBoss Help without any success. Do you have any information about what that error is trying to tell us?
    0 link






    Powered by Jitbit Forum 8.3.8.0 © 2006-2013 Jitbit Software