| |
Error Message |
|
Solution |
|
|
1 |
Windows 98 - Power Broker 4.0
16 Bit Video Card skews / blurs the screen . |
|
On one of our test machines,
Power Broker 4.0 on a Windows 98 machine had a video card that could only be
set to 16 bit as the highest level in Start, Control Panel, Display,
Settings, click on the color quality and change it to 32 bit. If your
card does not support 32 bit color, then you will need to please change your
video card to a 32 bit card and test again. |
|
|
2 |
Error Number 1002
Error Message : Input/output operation failure
Program : Pack and ReIndex |
|
Open Utilities, Define Your Company Information, Software Directories, and
ensure that the Power Broker drive and path are correct. Compare to
the target line located in your Power Broker Icon on your desktop by right
clicking, choosing properties, and clicking the shortcut tab. |
|
|
3 |
Error 1327
Invalid Drive Specification
E:\ |
|
A) If drive letters have been
changed on your computer, re-assign the original letter to the CD-ROM,
DVD-ROM, or operating system drive. Follow the steps appropriate to your
operating system:
B) Verify that registry entries do not contain invalid drive letters that
might be causing this error:
Click here
|
|
|
4 |
Error 1904 Module C:\Program
Files\Common Files\Power Broker\viscomsoft\Scanner.ocx failed to register.
HRESULT. Contact you support personnel. |
|
This error occurred when a
customer ran Workstation.exe from a Terminal Server connection and didn't
have enough permissions. Please try sitting right at the server, and
run workstation.exe |
|
|
5 |
Error 1426
OLE Error Code : Class Not Registered
|
|
This error occurred when clicking on the camera icon on the customer screen.
One solution was browse to C:\Program Files\Common Files\Power Broker\viscomsoft
and delete imageviewer2.ocx, scanner.ocx, and viscompdf.dll and run your
\BRO\WORKSTATION.EXE file again. Then try again. |
|
|
6 |
Word Integration
Confirm Data Source
|
|
This means that you have not configured your Word Integration correctly,
please
click here and print/follow these included
instructions. This usually means that you either have dbase located in
your ODBC data sources, or you are missing FoxPro files - Word |
|
|
7 |
Word Integration
Error 1429 |
|
This error usually occurs right after confirm data source when the odbc
drivers are not setup correctly. You either have dbase located in your
ODBC data sources, or you are missing FoxPro files - Word |
|
|
8 |
Word Integration
This operation cannot be completed because of dialog or database engine
failures. Please try again |
|
This seems to happen on one
template at a time.
Open Windows Explorer,
browsed to \bro\word97 folder. If you find a ~$xxx.doc name of the
abbreviated name, delete this document. These documents are
usually created when a word document is having issues saving/retrieving
from the server.
Open the good document directly from clicking on the .doc name, and it
will give you the 'options' 'remove data header sources' error, and then
I close it.
Try running the
form again and it should work fine.
|
|
|
9 |
Opening Power Broker
Fatal Error: Exception Code - Error log file: C:\Program
Files\Common Files\Microsoft Shared\VFP\vfp8err.log
This error occurs after you click on 'Yes' when it asks 'Convert 3.0
resource file to 6.0 Format' |
|
In Windows Explorer, delete
foxuser.dbf and foxuser.fpt. If the system will not allow you to
delete these two files because they are being used someone else, this means
that the files are locked on your server. The way to release these
files is to go to the server, Start, Control Panel, Administrative Tools,
Computer Management, Shared Folders, Open Files, and find/close anyone using
foxuser.dbf and foxuser.fpt. |
|
|
10 |
Vista - Aero - Display Issues |
|
Until Resolved, should you find that you are
having a display issue with Vista, please go to Start, Control Panel,
Personalization, Appearance, and change from Aero, to Vista Basic, or some
other option, and then test. |
|
|
11 |
Variable 'MQPLACE' is not found
Writing Cheques |
|
Contact Technical Support about
restoring this file from a copy that a technical support staff will provide
to you.
(Q:\BRO) |
|
|
12 |
Error 36
Command contains unrecognized phrase/keyword - Clicking on 'Outstanding
Abeyance from the main PB desktop |
|
Check to see if the user I.D. is
numeric. If so, exit all Power Broker users, and go to Tables, User
Security Codes, create a new users matching the same security settings as
the existing user, go to Utilities, Change User Security Codes and run this
from the numeric code to the alpha code. |
|
|
13 |
Vfp8r.dll is corrupt |
|
1) Browse to
C:\ProgramFiles\CommonFiles\MicrosoftShared\VFP and delete vfp8r.dll and
then install \BRO\Workstation.exe again
2) Delete \BRO\Foxuser.dbf and \BRO\Foxuser.fpt file and try logging
in again.
3) Shut down workstation, and log back on, and test again
4) Disconnect mapped drive, and reconnect mapped drive |
|
|
14 |
Error 1102
Cannot Create J:\BRO\GG\FORMNAME.DBF |
|
This error occurs when a user i.d. folder is
not created.
Open Windows Explorer, browse to your \BRO folder and create a folder that
matches the User Code. In this example the users' code is GG. |
|
|
15 |
Error 202
Pack and Re-Index |
|
Usually this means that you are
sitting at a computer that does not have the same drive letter as indicated
in Utilities, Define Your Company Information, Software Directories.
If you are in an office with 20 people and every desktop PB Icon points to
H:\BRO\BROW.EXE but you are sitting at the server and PB is in C:\DATA\BRO\BROW.EXE,
then sitting
at the server, map a drive letter H back to it's own C:\DATA directory and
create a new Icon on the desktop pointing to
H:\BRO\BROW.exe |
|
|
16 |
Error 107 - Operator/Operand type
mismatch when printing applications |
|
In one case, there was a
corrupted .mem file for Define your company information. Restore from
Backup. If you restore from a backup that was from Build 3.32, then
you will also need to go into Software Directories, and add the drive path
to your Mastercom EDI software. |
|
|
17 |
On the log in screen, your cursor
does not default into the password box |
|
config.fpw should have
screen=off, so edit this file in notepad, add the line and then save |
|
|
18 |
Printing 1298 |
|
Test to another printer, change printer driver, re-install driver |
|
|
19 |
Word Conversion - Error 7 |
|
This can happen of two documents
somehow have the same name. Open Power Broker, go to Forms, Delete
Word Documents, find a document that has a duplicate name and delete either
one or both letters. Once deleted, exit Power Broker, go to start,
run, browse to the \bro folder and find a file called msword_update.exe and
launch this file. Once launched, it's going to update the templates
again. |
|
|
20 |
CompuQuote - Must specify
additional parameters |
|
This is as
Citrix/Terminal Server setting.
You will have to setup up the home folders with
a mapped drive letter.
You will have to setup home folder for the
Citrix users instead of running through C:\documents and settings for their
local files. |
|
|
21 |
Broker Management Software -
Broker Management Software has encountered a problem and needs to close.
We are sorry for the inconvenience - This may happen during an upgrade from
Build 32 to Version 4. |
|
The set
compatibility mode on BROW.exe was set to Windows95. Right click over
brow.exe and go to Properties to view these details. Unselected this
setting and now they are able to launch.
|
|
|
22 |
While Running PowerTools
16 bit MS-DOS Subsystem
\BRO\FOXRUN.PIF
c:\windows\system32\autoexec.nt
The system file is not suitable for running MS-DOS and Microsoft Windows
Applications. Choose 'Close' to terminate the application.
Close/Ignore |
|
This error was discovered on a
computer that had a missing c:\windows\system32\autoexec.nt file. The
file was restored from c:\windows\repair and PowerTools ran as it should. |
|
|
23 |
EDI - Send and Receive - Proceed
Error 36 - Command Contains Unrecognized Phrase/Keyword |
|
Utilities, Define your Company
information, Software Directories, Mastercom EDI path had a space between
the G:\ and the word EMAIL. Check for spaces. |
|
|
24 |
Microsoft Word Integration
Forms, Create or Edit Word Template
This operation cannot be completed because of dialog or database engine
failures. Please try again later. OK |
|
If you receive this error, click 'OK', Microsoft Word will launch the letter.
Click on 'Save Document and return to Power Broker'. After a brief
pause, Word will display a 'Recover my work and restart Microsoft Office
Word' message. Uncheck this box and click on Don't Send. Please
try editing your template a second time. It should be reset and ready
for use. |
|
|
25 |
EDI, Reformat Latest CSIO Download
does not reformat |
|
Corrupt or invalid entries in memos.dbf, fpt, cdx files. Someone placed
Question Marks in the Machine Address in CSIO TAbles. Once the
question marks were removed, the reforat worked. |
|
|
26 |
Error Number 4
End of File Encountered |
|
This was due to a user not 'Tagging' the producer code with an X when choosing
a report by a specific producer. This would happen in other menus
where tagging is involved. |
|
|
27 |
Error 1753 Cannot Load 32 Bit DLL
Foxfix5.dll, FixCorruptTables |
|
This error is a result of a
Windows Security setting that can either be disabled, or settings may be
added to by pass this error.
Click here for more details. |
|
|
28 |
During Upgrade to Version 4
Could not find path
218 or 228
Bro81w
Form_p1 |
|
This happened when a local tech skipped the part of the instructions where you
go into Utilities, and run the Update MS Word Document Structures in Build
32 before the upgrade. We went into Forms, Delete Custom Form Letters
and deleted any invalid name that had spaces or symbols. |
|
|
29 |
Error Number 15
Not a table
FORM1.NEXISYS_SAVE |
|
Copy the nexisys.dbf FROM the \BRO\AD folder TO the IMAGE Storage directory
mentioned in Utilities, Define your Company Information, Software
Directories, Image Storage path. |
|
|
30 |
popupf.prg Does Not Exist |
|
Go to Tables, User Preferences, change language from French to English. |
|
|
31 |
Error 1113 during Pack and Re-index |
|
Corrupted .CDX file. Figure out which one and restore. |
|
