Error Messages
Access Violation Errors
|
Nancy Administrator Posts: 765
3/28/2012
|
NancyAdministrator Posts: 765
The top three causes of the Access Violation are:
1. Virus scanning software – Exempt the PrintBoss from any virus scanning software. Some extensions may need to be exempt as well.
2. Permissions issue – Verify the User has Full Control of the PrintBoss Home Directory.
3. Corrupted Registry Setting – See below.
Please follow these steps to check the Registry Settings:
1. Verify the location of the PrintBoss Configuration Settings.
a. Open the PrintBoss Master Application (PB32.exe).
b. Click on the Options menu and choose PrintBoss Driver Settings.
c. Verify 'Configuration settings Save Location' is set to 'Local Registry & User Registry (Standard)'. Continue to Step 2 if this is a match.
2. Verify the user has sufficient permissions to the Registry.
a. Return to the PrintBoss Master Application screen.
b. Hold down the Shift+Ctrl+P keys to open the Permission Analyzer.
c. The permissions for the Current User (CU) registry should be all capital letters.
d. The user only needs Read (capital R) permissions to the Local Machine (LM) registry once PrintBoss is installed.
e. 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.
a. Close PrintBoss.
b. Run or open regedit.
c. Navigate to Current User\Software\Wellspring Software and rename the Wellspring Software folder by adding something to the end of the name.
d. 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 to the end of the name.
ii. If this is not a 64-bit computer, select the Wellspring Software folder and rename the Wellspring Software folder by adding something to the end of the name.
4. Open PrintBoss to recreate the registry settings.
5. 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.
|
|
|
0
link
|