POWER BROKER Quick Fixes Technical Reference
 

This table was created based on re-occurring calls from our clients.

  One moment please...
Although attempts are made to make the information in these bulletins accurate and understandable, they are only a guide. Any time you are making changes to Power Broker or to Windows, there is a chance of things going wrong. If you feel something is beyond your abilities or just not quite clear, contact our technical support department or get someone with computer experience to help you.
  Error Message   Solution  
1 Runtime Error in Word   Restore Office Assistant with Windows Office  
2 OTH6PREMO not found   Problem with ddriver.dbf / Contact Power Broker Technical Department  
3 Error 214 /
Window Has Not Been Defined / Send and Receive
  Press Esc / This error has been reported and should be fixed in future upgrade  
4 Error message "Reading Mail Into PB Format"   Check for EDI installed twice / LAN Setup not being used but installed on workstations  
5 Internal Inconsistency Error   Fonts required for PB:  CG X's, Bernard MT Condensed, Time New Roman, Arial, Arial Bold / Re-install/Repair Windows Operating System  
6 Error NDX file Missing   Novell Issue / See Power Broker  Technical documents about Novell  
7 Wordgen Error 
Word97 Integration Setup
  Create File folder (Using User's initials) in Windows Explorer in the bro dir.  Fox and Pack   
8 Pure virtual function call   Check config.sys
Inserted policy controls
Check the print option of Define your company / EDI/Misc / Allow users to choose printer.
Re-install Printer drivers
 
9 Error # 1405
Err Msg:Run/!Command failed
Program with error: WORDFORM
  Pack and reindex or ensure that your Define your 
Company Information, Software Directory matches the "Start In" line of the Power broker icon, or browse the winword.exe in the Tables, User Preferences menu.  Goto Start, Programs, and look to see if you have Microsoft Excel installed.  Test with another user and a new document.
 
10 Printer not ready 125   Scan disk/Reboot the printer server and shut down computer/deleted old print jobs at workstation.
Ensure you have a
trout directory.
Contact Power Broker Technical Support
Please also review our driver website link. 
Click here
It was reported that when getting this error during EDI, and all else fails, upgrade Mastercom.  Doing upload - missing contract number, or other type of information in the policy info trying to be uploaded.  Ensure the CSIO table for that company has been completed properly.
 
11 Mvariable not found   Memory File Error.
Contact Technical Support as soon as possible.
 
12 1162 Procedure not found   Autoexec.bat / Work station C:\bro folder not updated or duplicated  
13 Memory Variable File is Missing or Invalid -
divide by 0 / ignore/cancel
  Foxw2600 Error / Download from Power Broker Website from the Download Area  - contact techsupport about restoring .mem files  
14 File Trap Error   When creating a 5dsp disk/ Define your company info / Do the  Attrib -r *.* feature in D.O.S. in the bro\ad and the bro\rr directory  
15 Error when uploading
First time Setup
  This customer could not upload because they had their bro and email folder in another folder….\power\bro or \power\email  
16 1111 invalid file descriptor xxconv   Missing fpt files - doing upgrade - Maybe from a file restore from a backup.  In one case, the server was shut down for 10 seconds, and then rebooted.  The next step was that the missing .fpt file was restored, the PBMech steps 2,3, and 4 were run, and then the upgrade was reinstalled.  
17 Operand Type Mismatch / Abeyances  / Error 107   Key file needed to be replaced or you have duplicate win.app or brow.exe files on your network/computer.   
18 Cannot find Foxpro Utilities/Fix corrupted databases   Define your company information / Software directories  
19 xxconv error during upgrade   Go to Forms, Delete forms, find form names with spaces/over 8 characters/bad symbols.  
Reset "All Forms"
 
20 Position is off screen   Restore Fonts  /  The Position is Off screen error could be caused by not having the correct entries in the Config.fpw file, make sure that you have mvcount=5000 and memlimit=90
In Windows Display, use 800x600, click advanced, then use 'small fonts' and reboot.

First change your display settings to 800 by 600, small fonts or in Windows XP, to Normal 96 dpi.  Select Apply and then try running Power Broker again.  Another reason would be that you have older versions of Power Broker on your workstation or server.  One customer had Office 95 and upgraded to Office 2000 which gave them this error.  They uninstalled both Offices', reinstalled just Office 2000 and it was fixed.
 
21 Error 1105
File read/write error
  Doing the attrib -r *.* in the bro directory from DOS.
This error was reported when a servers hard-drive did not have enough disk space.  Another option is to go to Start, Help, choose Index and do a search on the word "Event".  This will display some window environment features that can be viewed after the error 1105 has happened.
 
22
Error 1234
Subscript Out of Bounds
  When you are trying to print your installment from the Print and Post/ Invoice and Commission area, ensure that you only have 12 installments and not more or this will generate the Error 1234.  Fixed in Build 20 Oct 16/2001  
23 ICHAN 2
Error with Word97
Integration
  This error has been reported based on errors with Excel when doing the Word Integration setup.  This may be due to problems with Excel.  Re-install Excel OR Excel is open when you run Word Integration.  Close Excel and try again.  
24 Error 5
Record is out of range
Line Number of Error: 0
Initializ 2 and 3
 
  Open Utilities, Insert Policy Control Records, and increase the number by 10.  Click Trigger.  
25 Error 1691
Library file is invalid
  Restore foxfix.fll, foxtools.fll and foxw2600.esl from a backup to your \bro directory on your server.  Check for duplicate copies of Win.app or Key.app that has maybe been installed in a wrong location from a previous upgrade.  
26 Word Integration Document Printing over and over and over   Close Outlook and / or say "No" to use Word as your email editor  
27 Error 114
Index does not match Table
Recreate Index
QC124
  Tables, User Security Codes, Number 40 - Set from No to Yes  
28 Error 12
Variable CBAL not found
Printing Word Docs
  Create a new Word Template and try again.  This error has been associated with clients jumping from a really old version.  Ensure that you have WINFORMS.DBF in your \bro directory.  Download and re-install most recent upgrade.  
29 Word Integration - Settings.dbf does not exist   \bro\word97\settings is missing, or Utilities, Define Your Company Information, Software Directories has been not defined correctly.  Change the drive letter to reflect the path you have to your \bro directory.  Should you be at the server, you would need to either map with the same drive as the workstation, or use the substitute command.  Contact Tech Support for this procedure.  
30 Error message
Composing Phone Messagescharset="us-ascii"
 
  This error is generated if you use the PowerBar Telephone message icon in a customer screen.  The error does not occur if you are at Home Page adding a telephone message  
31 Thumbs.db in \bro   This file is sometimes generated when viewing your \bro direct in Windows Explorer in a "Thumbnail" View Setting.  
32 Subpgm.ini Error/ EDI Send and Receive   Check Environment Variable to include the drive letter\email then Re-boot.  In some cases you may have to reinstall upgrade, or reinstall from scratch but ensure you have your original software.  
33 Error 11, invalid function/argument, CSIODOWN   The above error is generated when launching PowerQuote® with integration (option 2) when the policy has vehicle and driver but no coverage added  
34 Error 202 - Invalid path or filename   Ensure that Utilities, Define your Company Information, Software Directories drive and directory information reflects the Target line of Right clicking over your Power Broker Icon, Properties, Shortcut.  Setting up Word Integration on the server will need special attention so please contact our office for help (Subst command or mapping server to itself to match workstations.  The filename you used does not fit the "8 Character or less, no spaces, and no symbols" rule when naming a new document.  Create a folder in the \bro that would match a users code or do the pack and re-index which would create the folder automatically.  
35 Logo file has been installed, and I have changed Define your Comp. Info but still shows the wrong name on half of my reports?   Contact our technical support office.  You may need a new key file.  
36 One of our clients reported that using Windows XP and Norton "Email" virus option enabled stopped information from being uploaded during the send and receive procedure.   The customer disabled the "Email" virus scan, tried the send and receive again, and everything went fine.  
37 "Windows cannot read from drive D: , If this is a system drive, make sure the network is working" message when loading Power Broker   Edit config.fpw from the \bro directory to read:
MVCOUNT=5000
MEMLIMIT=90
 
38 Error 12
Variable CCODE not found when running an End of Day
  Ensure that your User I.D. has a 'Y' or 'N' in all of the spaces provided on page 1 and 2 of the Users Security Code Table Menu , or log on with a Power Broker administrator User I.D.  Another option is to delete .tmp files and m0, m1, m2, m3, m4, and m5*.dbf files in the \bro directory.  Please contact tech support for help.  
39 Database is locked   Someone is in Power Broker at another workstation.  User I.D. included a period symbol.  
40 Win.app does not exist   Novell Network and/or long file name and/or check Software directories. Check Power Broker desktop Icon for Path.
Utilities, Define your Company Information, Software Directories may be setup in correctly.  Do a screen capture of your Software Directories and email it to
techsupport@power-broker.com with a description of your problem.
In CQWin integration, look to see if your missing intcall.exe   Run setupi-o.exe which can be downloaded Compu-Quotes website.
 
41 Set CSIO Error - Yellow exclamation mark   This is usually due to too many characters in the fields provided.  Shorten the names to 25 and 10.  
42 Error 36 - Customer to Policy browse feature   Blank or Numeric User I.D. code being used.  Open Power Broker with an Alpha User I.D. code  
43 Error 36 - Upgrade Error
(Your upgrade is fine, but you WILL need to follow these next few steps so you do not get this error again)

OR

Error 12
Variable DTLIC3 not found, WORDFORM
  Hit Escape on this error. Log into PB and go to Forms, Delete Custom Form Letters.  This is a good place to look for any documents that have a name that's longer than 8 characters or contain symbols other than and underscore (_) or that have a space in front of the form name.  Exit the delete screen, duplicate the documents you wish to keep with another name that fits the 8 alphanumeric characteristic attributes and then go back and delete them.  Once deleted, go to Utilities, and then "MS Word Document Structure" option and proceed.  
44 Error Message \bro\message1.ndx does not exist   Are you on Novell? - Click here
One of our customers had this error after signing into Power Broker.  The problem was with a corrupt Notes.dbf and a Notes.fpt file during the pack.  They restored the file that the pack stopped on and did the fox, the pack and launched Power Broker.
 
45 Error Number 2 -
Quoting Integration error - An entry for this Policy is already waiting to be uploaded
  EDI, then Send and Receive
Click on the "Quotes" option and then see in the bottom window if your quote is sitting there.  Click on the line and then delete this policy, then try again.
Note to PB Tech : \bro\ad\outlog.dbf
 
46 Doing a Send and Receive - Could not find Command.com   Check the Environment Variables to ensure that the settings are correct.  Check the Comspec as well MV Variable.  Command.com will be listed there.  Is it in this location when looking in Windows Explorer?  
47 Reports freezing   Contact Power Broker support about possibly having a corrupt file in the \bro\rptw folder   
48 Internal Consistency Error   *The most common causes of this error is either bad indices or low resources (not enough memory and/or hard drive space).
*Run a Foxfix (Fix Corrupted Databases)  and Pack and Re-Index.
Click here for detailed instructions
*Right-mouseclick mycomputer-> properties-> performance or advanced, then performance. If you see a low percentage number, you might have to reduce the number of background applications. Either that or add more RAM to your computer.
*Having either missing or corrupted fonts has also been reported to be a culprit of this error message
*Delete Foxuser.dbf and Foxuser.fpt from your \BRO directory.  Foxpro will recreate these files automatically.
*Having these 2 settings in your CONFIG.FPW located in your \BRO directory.
MVCOUNT=5000
MEMLIMIT=90
In \BRO del *.tmp /s
Error 36 - Delete forms that have wrong names - search error 36 in this page for more details
Re-apply upgrade
 
49 Error 1, file 5***.dbf does not exist, XXCONV   This error indicates that the user has tried running the upgrade conversion on a local workstation before copying the necessary files to their local C:\BRO - as per our Large LAN document.   The user is actually running an old conversion program.  
50 Error 1104 - Error Reading File   Try rebooting the server. 
Try doing an attrib -r /s *.* in the \bro directory of the server.  Should these solutions not resolve this error, consider the steps in this Microsoft document. 
Click here
Check your router and servers DHCP lease time for their I.P. address.  In one case, it was set to ten minutes so the lease was being dropped causing delayed write fail as well ass 1104's.  Change it to 'never expires' to test.
One customer on a workgroup couldn't gain access to permissions so here's what was done.
Click here
 
51 521A.dbf does not exist   During the upgrade, the Power Broker upgrade was launched from the wrong brow.exe.  Power Broker is being launched from the icon that has the (running on a large lan) setup that hasn't had the files updated yet.  Ensure that you open Windows Explorer, go to the \BRO directory of the server (not the workstation) and launch Power Broker by opening BROW.EXE.  If you are on a Novell network, then open Windows Explorer at a workstation, and launch the \BRO\BROW.EXE file on the mapped drive.  
52 Spool 32 Caused a General Protection Fault   Typically, the computer has fax or answering machine software preinstalled that interferes with the printer spooler. However, there does not seem to be any one specific problem that makes Spool 32 errors occur.
Many workarounds have had varying success and are listed
HERE
 
53 Picture to Big or Wrong Format   800 x 600, small fonts, \bro\config.fpw should have MVCOUNT=5000, MEMLIMIT=90, CENTURY=ON  
54 Invoicing and Commission, Enter Cash Receipts Batch, Hitting F2 and then having another brokerage name on the receipt   Go to Utilities, Define your Company Information, Print Options and say "N" to any options in reference to a LOGO scan.   
55 Error 1, mem file does not exist   Config.fpw in the \BRO on the C drive of the problem workstation does not have DEFAULT=F:\BRO.  In this example, we used the F drive.  Supplement the actual drive you use to map to the server.  
56 Error 4 , Bro86
Closing Month end for the first time
without any transactions.
  Enter one Agency Bill zero dollar transaction into Power Broker, and try closing the month again.  
57 Word Integration asks to "Save" the document in a Customer or Policy screen to a specific location and does not automatically do it on it's own.   Ensure that you have a \bro\word97\docs folder.  If not, then please make one and try again.  
58 Upload/download Waiting for 3 Minutes   Ensure that all folders in the EMAIL directory are there.  Call Power Broker Tech Support to do a comparison of your EMAIL folder to theirs.   
59 Error 43 Insufficient Memory     

Delete Foxuser.dbf and .fpt from your \BRO directory.  After you log into PB again, these two files should be recreated.  If they are not, it was reported that foxuser.dbf and .fpt were found in c:\windows\system32.  The files were deleted, PB was opened again, and everything was fine.
In dos, go to your \BRO directory and type:
EDIT CONFIG.FPW found in your \BRO directory and make sure you have:
MVCOUNT=5000
MEMLIMIT=90
Changed colors from True Color 32 Bit to a 256 Setting.
 
60 Error 43 Insufficient Memory   

Line QC1100
 
Using alpha key to pop up insurer table, and then alpha key again to jump to list.  This usually happpens in an application.  The only fix is to 'not' use a letter, but to use a <.> symbol and scrool down to the insurer this way.  Go to Utilities, Insert Policy Control Records and report back to Power Broker Technical Support on what number is in the box of this utility.
 
61 Invalid Function Argument Value Type or Count

Build 24 November 13/2002
  Error occurs when attempting 2 way rating integration with CompuQuote and PowerQuote, as well as policy upload to CSIO on automobile policies where customer has claims recorded.  Download and run upgrade.  
62 Open Database Connectivity Error
Word97 Integration Error
  Usually related to the Header Record error.  Please click on the here to review the download and installation of a possible solution.  
63 Camera Icon - Scanning - Pictures scrolling past - not visible   This has been reported by Terminal Server/Citrix users.  Please visit this website for a possible solution in the near future.   
64 Cannot locate Foxpro Library   This usually means you are trying to execute brow.exe in a location that does not have the supporting Foxpro files.  Do a search for brow.exe on MyComputer to be sure you are choosing the correct brow.exe.  If you have multiple copies, then please contact technical support for details on how to clean them up as well as the directories they may reside.  
65 Microsoft Foxpro - Overwrite invalid foxuser file with a new empty one?  Y or N   Answer Y for yes, and try logging out and coming back in to see if still get the same message.  Your second option is to delete foxuser.dbf and .fpt from the \bro directory.  Try logging in again.  
66 EDI - Reformat 'Y' Error   EDI - Reformat procedure gives you a 'Y' error.  This happened from a win98 workstation to a winxp professional server setup.  The customer then ran the Reformat from another winxp networked machine and it reformated correctly.  Try running this procedure from another computer/operating system/server.  
67 XXConv error Converting 5301.dbf   Create an FSC folder under \bro, delete the 5 Files, and then rerun the setup.exe  
68 Error 94   Search for duplicate copies of other .app files using Start, Find or Search, for Files and Folders on MyComputer.  
69 Error 114
brow_scr
  Delete *.idx and *.cdx  
70 "Opening This Will Run the Following SQL Command" Message When You Open a Word Document Error message Microsoft Office 2003   This problem has occurred on a workstation that has Microsoft Office 2003 installed and has attempted to integrate Microsoft Word with
Power Broker's Microsoft Word Integration.
Click here
www.power-broker.com/wordsqlerror.htm for more details.  Reboot.
 
 
71 Microsoft Word - ODBC Error Visual FoxPro Driver Cannot Open File \bro\word97 Return Code:  SQL_ERROR   Start, Settings, Control Panel, Administrative Tools, Data Sources ODBC, User DSN Tab, click on Foxpro files - Word and then click Configure, and then change to Free Table Directory.  
72

"Reading Mail into Power Broker Format" error during EDI Upload/download

 

  Open Windows Explorer, browse to your \EMAIL folder and then right click and cut the MAILRECV.RML file and then paste it to your 'MyDocuments' folder.  Once pasted, open the MAILRECV.RML file and review it's contents for further information on why it has a problem.  Deleting this file from the \EMAIL folder will solve this problem for the next time you do another EDI, Send and Receive.  
73 No PARAMETER statement if found:
Power Quote Integration
  Power Quotes directory path is not correct.  Go to Windows Explorer and check and see how many PowerQ's you have.  If Power Quote is the 3rd directory down, then your directory path in Utilities, Define your Company Information, Software Directories should have \Powerq~3 or \Powerq~2 or a ~something for however many sub-directories you have.  Remember that if Power Quote is installed in your Programs' folder, then you would have \Progra~1\Powerq~1, or ~2, or ~3 ect. depending.  
74 Error 27
Not a Numeric Expression
Today3
  The customer restored Users.dbf from a backup and was able to log in.  
75 Terminal Server Word Integration Administrative Rights - Permissions   It has been reported by one of customers (March 2004) that should you be in a terminal server environment, and wish to use the Microsoft Word Integration with Power Broker without giving staff members administrative rights, you can give everyone read/write permissions to the c:\winnt\temp(s) directory on the server.  In the past, Word Integration network users needed full administrative permissions for the Word Integration to work.   
76 214
Window Brow has not been defined Build 28
517
EMAIL2BROW
  Problem with grid.app and gridf.app - Re-install new setup.exe - problem with March 25th/2004 setup.exe.  
77 Library file is invalid at workstation but server works fine   Sitting at the workstation, disconnect the mapped drive in which Power Broker is using, shut down the workstation.   Reboot, and then remap the workstation using the same drive mapping.  Was an upgrade done on the server and was not rebooted when ask to be?  
78 Freezing while Printing Invoice -
Policy Transaction screen
or
Invoicing and Commissions - Print and Post Agency Bill Transactions -  Re-Print option
  Most brokerages that have had these symptoms may stem from getting errors during an upgrade.  In the past, error 36 seems to be the red flag error that most brokerages get but then just carry on and never get back to following up on the fix for this error. Follow the instructions for the error 36 fix (number 43 on this page), and then re-apply your upgrade so that it goes from the data conversion, directly into the pack, and then directly into a log in screen without errors and then try printing your invoice again.  
79 TTYCD   Usually happens with Initial Downloads when the \BRO\AD directory's files do not get updated properly.  Please contact technical support  
80 Microsoft Word Integration - Office 2003
Toolbar missing when you run Word Integration
  Verify if you have Adobe Acrobat version 6.0 on the machine.  If so, browse in windows explorer to
C:\Program files\office 11\ and see if you have two folders called Startup and XLStart.  Look and see if you have PDFmaker.dot or PDFmaker.xlt in this directory.  If so, cut and paste this file to a C:\MyDocuments\Backup folder and then try your word integration again.
 
82 This document has not contents to view when logging into Power Broker   PowerMail from the main desktop is stuck.  Delete the PowerMail with the empty contents.  
83 End of File - New Power Broker User   New Power Broker offices can get an End of File Encountered error message when there is no transaction in the system.  Generate a real or zero dollar transaction and then try again.  
84 "Sum of Write Off's do not Equal" doing a Journal Entry   Change/alter the Writeoff/waiver number you used in your Journal Entry from 1 to 2 or visa versa, or if you have blank lines in your journal entry, make the dollar value $0.00 in the blank lines and point it to the policy you are doing the journal for to trick Power Broker in thinking that you have completed the line correctly.  
85 key.app not found   Check network user permissions  
86 Power Quote Integration
LICDT2 Error number 12
  Contact Power Quote for hotfix  
87 Use of Transgressed Handle   Usually has something to do with a workstation or servers hardware such as memory or hard drive space or too many things running at one time.  
88 Outlook Integration does not display .msg as a 'Save as' file type   In Outlook, go to Tools, Mail Format, and change 'Compose in this message format' to HTML and remove the check mark in the 'Use Microsoft Word to edit e-mail messages and also for the 'Use Microsoft Word to read Rich Text e-mail messages' option, close Outlook and try again.  Office 2003 users go to Tools, Options, Mail Format and repeat the same procedure.  
89 Terminal Server - Microsoft Word Integration
Mr. Clipit does not stay open when running Power Broker Microsoft Word Integration
  Open Windows Explorer and navigate to c:\winnt or c:\windows and then right click on the temp directory and under properties and then security, give the users that belong to the group access with full permissions.  Log out of your terminal server user, then log back in and then try your document again  
90 Users3.ndx does not exist   Duplicate copies of Power Broker floating around on the server or an incomplete upgrade.  
91 16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Winnt\System32\Autoexec.nt
,Config.nt,Command.com The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
  November/2004
This issue may occur if one or more of the following files are missing or damaged:
autoexec.nt, config.nt, command.com
Click here for more details

June 8/2006 - One customer reported that they restored dosx.exe to their c:\windows\system32 because the trojan may have removed this file
 
92 Cash Receipt - No Bars have been defined for this pop up   Bank table information is blank or missing - Contact Technical Support  
93 Unable to locate integration file Error
Power Quote Integration
  In Power Quote, changing the location of BMS in PQ DYCI from P:\BRO to P:\BRO\BROW.EXE or whatever your mapped drive is to the server.  
94 Power Broker Microsoft Word Integration
Text Boxes inserted into the word document disrupts Word Integration with locked Fields - Error message on print out is 'Word found locked fields during the update.  Word cannot update locked fields'
  Click here for more information  
95 Error number 12
Variable uprint1 not found
line 0
qc7
  Run step number two of the PBMech, shut down your server and all workstations, reboot, and reapply your Power Broker upgrade.  
96 Corrupted .dat file on upload - information damaged   The customer was using AVG Antivirus.  Once uninstalled, upload completed properly without error or damage.  
97 I/O Operation - General Protection Fault in module
 
  Start, Search, Files and Folders, Name = win.app and Look In = MyComputer and see how many win.app's you have.  Contact Power Broker tech support for further details should you find more than two copies of this file.  Also check the settings in config.fpw.  This would be done with the help of a Power Broker technical staff member.  Check to see if you are using 800 by 600 as your desktop size.  
98 'This document has no contents to view' on the return to the main Power Broker desktop   Check to see if the user had a blank PowerMail sent to them.  PowerMail notifies you that you have mail for users that have this setting set to yes when you return to the main Power Broker desktop.  
99 Auto Application Data from another customer combined   Click here or contact tech support and review autoapp.dbf with them and see what number to reset your system counters too.  
100 NOFID error during Power Quote Integration   Contact Power Soft Technical Support for patch  
101 Foreign node found during compaction   a)  find out what version of windows is this person working with  b)  open and edit/compare config.sys/nt and autoexec.bat/nt to another pc that's got the same operating system that's not having this problem or open either one of the four files and edit copy the contents into an email and send it to us here so we can look at the text inside these files.   c)  check to see where tmp files are being sent too on this pc.   d)  is this office 'or' computer using the Running on a large lan 'or' has this pc ever been setup this way and to look for duplicate power broker files like win.app   e) delete foxuser.dbf and .fpt from the \bro directory on your server.  
102 xmailerd.exe has generated an error and will be closed by Windows   run clear engine of all messages (in the MasterCom software)  
103 Policy Record is in Use Elsewhere.  Cannot Access   Utilities, Define your Company Information, EDI/MISC. Options, Page Two, and bump up the Property/Claim Record Addition Wait Seconds settings by a few seconds.  
104 Integration Errors error #2000 and #12 Variable FAX   Visit PowerQuotes website for hotfix.  
106 Error 12
Variable 'CRCRC' is not found
Program EDI_FUNCTIONS CSIODOWN
  DB policy in PB with a pay schedule added, they are trying to obtain quote in PQ and PQ does not have this field. 
Print off pay schedule, then delete it, do quote, add pay schedule back or to contact PQ to adjust the necessary fields
 
107 No Message Files to delete because delrecd.lst does not exist   Check that the dial-up/VPN connection was successful  
108 Word asks to save back to the hard drive when saving the document and doesn't do it automatically   Check in Forms, Create or Edit Word docs, and look at the Edit screen to see if it says to save to the customer as 'N'.  Change to 'Y'.  
109 EDI
1405 - RUN! Command Failed
Bro 34
  You either have something in your Utilities, Define your Company Information, EDI Options, Lombard path that's not correct for the setup.  Contact Tech Support for further help.

If you don't use this feature please empty this box, exit Power Broker, then log in and try your EDI Upload/Download again.
 
110 Error 12
Variable MREC_TOUSE not found
CSIO24
  This usually means that you have duplicate copies of Mastercom installed.  The other thing to do would be to Winzip a copy of your memos.dbf and memos.fpt and email it to our technical support department, and then mention which insurers you plan on uploading to.  
111 &muidsecurity_file_with_path.dbf does not exist - Power Quote Integration   When a Power Broker user had this error, we created a new user I.D. code called TR and then went to Utilities, Change a User I.D. Code and move RT into TR and everything was fine.  Another RJ user had the same issue so we did the same and the integration was fine after that.  
112 Error 1002
Alberta Auto Application
  A bitmap was pointing to the wrong location when the setup.exe was created.  (I:\bro instead of C:\foxpro25\bro)
Please apply a Power Broker upgrade older than March 7/2006
 
113 File Access Denied
Compu-Quote One Way Integration
 
  Apply the Power Broker upgrade older than March 7/2006.  Should you still experience this error after the upgrade, please contact technical support.  
114 Error 30
Position is off Screen
 
  In Display, from your control panel, click 'settings' and then advanced, and then change from large fonts to small fonts or 120 to 96DPI.  
115 when you click on the scanning button you do not get the three buttons above to get jpg tif pdf.   Ensure that you have a 'P' in the Acquire Scanned Images on your Utilities, Define your Company Information, EDI/MISC options, Page 2  
116 NTVDM error   Click here for more details  
117 After installing Norton Internet Security a problem when sending, each email comes up with an error message, timing out.   Tell Norton Internet Security 2006 to give "xmailer.exe" and "xmailerd.exe" located in the EMAIL\MHS\MAIL\GATES\ICENET\PUBLIC directory rights to ports 25 and 110 and not to scan mail going out on port 25 sent by xmailer.exe" and "xmailerd.exe"  
118 Error 1405
CompuQuote Integration
  This error may happen if you do not have
intcall.exe in your CompuQuote software software directory.  Please contact CompuQuote.
 
119 Alias Driver not found - CompuQuote Integration   Ensure that your Power Broker upgraded successfully, and that if you are using Running on a large Lan setup, that you have copied the 27 new files to the workstation.  Ensure that you are also on the latest version of CompuQuote.  
120 Visual Foxpro Driver ODBC Data source needs to be upgraded first message -
Word Integration
  A few customers have experienced that in the ODBC Data sources, that Windows for some reason does not realize that there already is the updated VFPODBC.MSI installed and keeps asking for it to be upgraded.  When you try and configure, add, or delete foxpro files - word , it gives you this message.  One work-around was to go into Add/Remove Programs, and uninstall the Visual Foxpro ODBC Data source and then it allows you to delete the Foxpro Files - Word from the data sources, and then allows you to add it back again.  
121 EDI - Send and Receive - the program hangs reading line something of something.  Public\Popin folder of the Email sub folder   Deleted VPN connection, and then re-installed from instructions located on the PB Tech Bull website.  
122 CQ One Way Integration - MS FoxPro Support Library Missing   PB tech determined that the setting for the BMS location in CompuQuote configuration file was incorrect, phone CompuQuote Tech Support.  
123 O Big Corrupt or Wrong Format.IVE  
One of the first things I would look at is in your \bro folder, you will have a file called config.fpw .
If you try and double click on this file and then choose the program NOTEPAD and open it up, it should say this:
mvcount=5000
memlimit=90
If it says something else, then please let us know.
If you close out of all of this, and then on the desktop of your computer, right click over your Power Broker icon, and then choose Properties, and then Shortcut, please email me back what it says at the TARGET line.
Close all that and do this:
Start, Search, Files and Folders, All files and folders
Name of the file = Win.app
Location = MyComputer
Click on Search
Once it's completed, please email tech support back how many win.app's are found.
One office reported getting this and they were on a wireless connection.
 
124 Word Integration
'File Save As'
'Cannot write to a read only file'
error message
  A customer reported having fixed this problem by uninstalling 'Bit Defender' which is a third party Trojan/Anti-Virus product.  The customer then re-installed Bit Defender and then un-checked a setting in the program that mentioned something like 'Scan Accessed Files' and was ok after that.  
125 Internet Explorer 7.0  - Microsoft Windows 2003 Server edition
- The publisher could not be verified. Are you sure you want to run this software?
  Click here for more details  
126 EDI Send and Receive
Mastercom XMailer.exe
#623 Error - delrecd.lst does not exist
  Open Power Broker, use the EDI, 'Clear Out Download Databases' option.  Try your EDI Send and Receive again.  
127 User Limit has Exceeded Error   User Limit has Exceeded Error - Click here  
128 Variable MCBATCH not found   Problem with mem file, phone tech support.  
129 Slow or non active page changes/refreshes when clicking next or prior buttons in any PB Screens in a Remote Desktop or Terminal Server Connections   http://support.microsoft.com/default.aspx/kb/811080/en-us
 
 
130 PR_REC2 when printing a Cash Receipt   Disable ' Logoscan ' to print on the cash receipt  
131 Invalid Switch - viewing an Outlook Email from the abeyance screen   This error starts happening once you update Office 2003 Service Pack 3.  This has been fixed in Version 4 of Power Broker.  To fix this in PB3, you will need to roll back your update, or if you can't do that, you will need to backup up your mails .pst file, uninstall Office, reinstall office and upgrade to Service pack 2 but NOT 3.  
132 EDI - Merging in data - FGETS error  

Please delete file (Example would be $I000024.txt ) in the \EMAIL\MHS\MAIL\GATES\ICENET\POPIN directory as it is a corrupted file.  Should this problem persist, contact technical support.

 
133 Customers - opening more than one screen at a time -
Record is Locked, Press 'Y' to Retry
  In Customers, Customer and prospects, when you open more than a few Power Brokers, and you try and access the cus