App: 1.x Incident: Run-time error when I minimized the REX Administrator. Cause: Release issue Solution: Fixed in the next release App: 1.x Incident: c:\progra~1\mpsi\rex\temp\studyname.m_0 isn't a valid path Make sure you are connected to the server on which the file resides. [Error Number: 3044] Cause: Study configured to be read from the CD Resolution: Put CD in machine. Changed message in next release. App: 1.x Incident: "Couldn't copy temporary database. Unrecognized database format." OR "Can't find database:D:\SetupStudy\studyname\BaseCase\StudyDatabase.M_0" Cause: REX options were set to load one of the modules automatically (i.e. MAP, Reports, ...) The last market used was not loaded (i.e. Set to run from the CD and the CD was not in the machine.) Resolution: 1) Put the appropriate market CD in the machine. 2) Change the "options to not load module(s) automatically. App: 1.x Incident: Error extracting support files. Setup failed to run installation: The argument string passed to DosExecPgm is not correct. Cause: Previous attempt at install failed or canceled improperly Resolution: 1) Delete all unnecessary temp folders in the Windows temp directory. Such as: _inst... {234520943857230..} 2) Run check disk 3) Restart install. App: 1.x Incident: FATAL ERROR MARKET LIST DATABASE NOT OPENED. Cause: Can't find markets.mdb If path is application path, can't get registry entry for MarketsMDBPath a) Need ARRegistry.ocx registered or b) Problem in code at one time with NT users w/o administrative privilege can't read registry Solution: Should be fixed in the latest release of REX 1 or Have someone sign on as "administrator" and reinstall software. App: 1.x Incident: Run-time error "91" Object variable or with block variable not set. Cause: MPSI modules not registered Resolution: a) Register modules manually (copy MPSI DLLs & OCXs from app path to "new" folder) or b) Rerun the software install (may require administrator privileges if NT or W2K) App: 1.x Incident: ikernel fails Cause1: REX won’t install on win95 from network if using a long path Solution1: Make sure the network path names are under 8 characters long Cause2: Installation files left in Windows temp folder Solution2: Cleanup Windows temp folder Resolution: 1) Delete all unnecessary temp folders in the Windows’ temp directory. Such as: _inst... {234520943857230..} 2) Run check disk 3) Restart install. App: 1.x Incident: No current record Cause: bad case file Resolution: Through Windows Explorer - Delete bad case file App: 1.x Incident: Microsoft jet data base engine can not find the input table or query properties Make sure it exists and that its name is spelled correctly. Cause: Bad case file Resolution: Through Windows Explorer - Delete bad case file App: 1.x Incident: Blank RO screen Cause: Used . in street names? Solution: Don’t do it. Should be fixed in release 1.02.000 and above. App: 1.x Incident: (Error 1011 unexpected error in tmdl) Cause: Missing or can't find mapx.dct file Resolution: Verify Mapx registry entries HKEY_LOCAL_MACHINE\SOFTWARE\MapInfo\MapX\3.0\GeoDictionary\[value] The following commands from a DOS prompt will get you the information: regedit /e c:\mapx.txt HKEY_LOCAL_MACHINE\SOFTWARE\MapInfo\MapX\3.0 type c:\mapx.txt ReInstall selecting the appropriate location for MapX App: 1.x Incident: Bad looking icons on map Cause: Display settings set to 256 colors Resolution: Set display settings greater than 256 colors. Note: Photos will not work if display settings are set to TRUE 32 bit colors. Incident: Photos do not display Cause: Display settings set to TRUE 32 bit colors Resolution: Set display settings greater than 256 colors but less than TRUE 32 bit colors. App: 1.x Incident: From MPSI_GNAENG100a_Map.dll: Error 1059 Unable to create new layer Layer file name already exists Cause: Unknown Resolution: Clean out "windows" temp folder using REXExam utility from MPSI’s web site App: 1.x Incident: User reported that the REXUpdate (download) runs everytime he wants to run REX. Cause: User downloaded update, named it "mpsi_rex.exe" and put it in the application folder. Solution: Rename "mpsi_rex.exe to "update.exe. Run update.exe - runs the download update again, which puts a new mpsi_rex.exe back in the application path. App: 1.x Incident: User reported REX install corrupted Japanese CAPS install. Cause: REX was actually uninstalled. Removing Richtx32.ocx from the windows system folder and unregistering the file. Japanese CAPS places Richtx32.ocx in the app path. Richtx32.ocx is self registering. So when REX was removed, Richtx32.ocx was no longer registered on the machine. Solution: a) (Short term) register Richtx32.ocx in the Japanese app path. b) (long term) Since Richtx32.ocx is a Microsoft OCX, change the Japanese install to place the file in the Windows system folder. App: 1.x Incident: Older software installs when trying to load older market(s). Cause: Install version 1.02.000 - 1.02.005 removed previous registry entries for previous versions of REX. This causes older CDs to think they need to install since their old registry entries do not exist any longer. Solution: a) ReInstall 1.02.xxx after loading old market or b) Replace the old CD with a new CD containing newer software (preferred method) or c) Run the latest update (REX1UPDT.EXE). App: 1.x Incident: User uninstalls REX and it breaks their Microsoft Access. Cause: Some versions of the REX install (somewhere around 1.01.007 & 1.01.008) install a Microsoft Access runtime file set. There is a bug in the InstallShield object for runtime Access. When it is uninstalled, it removes system.mdw from the windows system (or system32 on NT) folder. Which breaks MS Access on the user’s machine. There should be a copy of system.mdw in the root directory of the CD. Solution: Copy system.mdw from the CD to the windows system (or system32 on NT) folder. App: 1.x Incident: Slow running tactics Cause: Case file needs to be compressed Solution: Run MS Access 97 and compress case file (m_0) App: 1.x Incident: Can’t see brand symbols or demand symbols (orange triangles) Cause: 1) Viewing out of the MPSI boundary 2) Viewing to far out Solution: 1) Move within the MPSI boundary 2) Zoom in App: 1.x Incident: Path not found / Run-time error 76 Cause: User does not have administrative rights and old code could not read registry entry Solution: 1) Update to latest version of REX or 2) Change user’s privileges to "Power User at least. App: 1.x Incident: Just before case impact window: Run Time Error = 35613, Image List must be initialized before it can be used. Cause: Incorrect path set in markets.mdb for MKT_MI_LOGOS_PATH. Solution: Depends. 1) a) Change the incorrect markets.mdb path values. b) Correct the registry setting so new markets won't have the same problem Or 2) Make a copy of the custsymb folder and it's contents create a folder matching the path value in markets.mdb. Other: 1) MapX BMP files are too big or 2) An old error - meaning they may have an old MPSI_GNAENG100a_Map.dll Search drives for MPSI_GNAENG100a_Map.dll and make sure there is only one Check date on MPSI_GNAENG100a_Map.dll App: 2.0.x Incident: a) Funny or Funky colors in reports AND/OR b) Bad looking icons on map Cause: Display settings set to 256 colors Resolution: Set display settings greater than 256 colors. App: 2.0.x Incident: msvbvm60.dll missing Cause: Bug in InstallShield Resolution: Run the latest REX 2 install App: 2.0.x (MPSI_GREX_ENG_Map) 2.01.03 (Rex2Mgr) Incident: MPSI_GREX_ENG_Map or Rex2mgr Run-time error ‘3706’ Provider cannot be found. It may not be properly installed. Cause: unknown Resolution: Resolved by user's IT support - resolution unreported App: 2.0.x Incident: Map does not come up on the right LAT/LON Cause: The Language setting is not currently supported. Resolution: Change the Language setting in CONTROL PANEL, Regional Settings to English and make the "numbers tab uses English settings also App: 1.02.015 Incident: MPSI_GNAENG100_Manager Run-time error ‘70’: Permission denied. Cause: MPSI_Rex.exe running (in the background) while trying to start from REX icon on desktop. Misc. Info: User ran REXExam.exe after downloading from our web site. Guess: User did not end REX appropriately after running trace and probably did not reboot machine. Resolution: Reboot and/or If NT: run taksmanager and ‘end process’ from both the ‘Application’ tab and ‘Processes’ tabs. App: 1.02.015 Incident: MPSI_GNAENG100_Map Run-time error ‘-2147417848{80010100}’: Automation Error The object invoked has disconnected from it’s clients. Cause: Dashes in the case name. Misc. Info: User was attempting to print a map (and had a case selected). LAT file in temp folder was could not be deleted. MPSIRex.exe still running in the background. Printer set at ‘0’ seconds job timeout Kill MPSIRex.exe through Task Manager or Reboot Delete files in Windows temp folder Change printer timeout setting Resolution: Rename case without dashes. Not an issue in later releases. App: 2.01.003 Incident: GensysMain Run-time error ‘3704’: Operation is not allowed when the object is closed. Cause: unknown Resolution: Resolved by user's IT support - resolution unreported App: 2.01.003 Incident: GensysMain Unable to find or load Helper Dialog.dll Cause: Msvcp50.dll is missing. Resolution: Reinstall App: 2.00.??? Incident: Error Retrieving Market ID Error 91: Object variable or with block variable not set Misc. Info: User sent case file(s) to be used on Client Services’ machine. Cause: The date in the "Properties" table of the case was in a different format. Example: Date in case = 05:05:01 Expected format = 05/05/01 WorkAround: Edit date in "Properties" table of case to comply. App: 1.00.??? and 2.00.??? Incident: Logos show up as Independents instead of Brand Logo Cause: 1) Too many logos, or a bad logo, or a missing logo, or old logos (too large). 2) OR A property value in markets.mdb has been corrupted or set to something the software cannot handle. Misc. Info: Could be caused by map settings such as logo options and/or colors in map themes. Fix(s): 1) Update all logos with web update GNSSSYMB for REX 2.X software and REX1SYMB for 1.X software. 2) Close REX. Delete all entries for all tables in markets.mdb. App: 2.00.??? Incident: When trying to run REX map: CIO Automation error Cause: User double clicked on EXE in MapX folder (tried to run Mapx standalone). Resolution: Reboot machine. App: 1.x Incident: Load Photo Error Internal Error Cause: Display settings set to TRUE 32 bit colors Resolution: Set display settings greater than 256 colors but less than TRUE 32 bit colors. App: 2.1.022 Incident: Rex21 Map Run-time error ‘429’: ActiveX component can’t create object INFO: This is a module registration problem. NOT a data problem. Cause: Unknown - Usually caused by a component not being registered Resolution: Resolved by user's IT support- resolution unreported. Has been fixed by a reinstall in the past. App: ???? Incident: Microsoft C++ Run-time error Error occurred while launching the setup A remote procedure call failed INFO: This is a module registration problem. NOT a data problem. Cause: On one machine - Norton Utilities or Norton Anti-virus Resolution: Uninstall Norton Utilities App: ???? Incident: Can’t export Cause: Wrong version or bad msvbvm60.dll Resolution: Need version 6.00.8877 of msvbvm60.dll or newer. App: 2 Incident: Can’t read photos Error: REX Photos: Load Error Error 32503 Error Reading from File 2nd dialog box: REX Photos: Load Error Error 32503 Error Reading from File 3rd dialog box: Error Load Photo Error Cause: Bad ImagMan files from some 3rd party install. In the Windows system folder the following files were found (using the GNSSIFNO trace) and caused the Incident: IM31BSB.DIL IM31ADRG.DIL Resolution: Delete the files. Rerun the install. App: 2.x Incident: Missing logos on some outlets. Stars instead. Cause: Bad BITMAP (BMP) LG.BMP. 24 bit instead of 256 colors. Resolution: Replace bitmap (lg.bmp). App: 2.3 Incident: Install problem. Can’t register Atl.dll, MapXADODS.dll and/or MapXRDODS.dll. Cause: Wrong version of ATL.DLL previously installed. Resolution: Delete ATL.DLL from Window’s system folder. Rerun the install. App: 2.x Incident: CDO. OpenCDO File not foundError Number: 53 Cause: A piece of Market data either wasn’t copied during the install or became corrupted. Resolution: Remove market and reinstall. App: 2.x Incident: MPSINI.dll Error: 70 Permission denied. Cause: User did not have enough permission to start REX for the first time. Just exactly what permission or write access needed is unknown (unknown security policy environment). Resolution1: Sign on to NT (NT4, W2K, XP) belonging to Administrative group. Start REX. Open a market. Reset permissions back to where they were. Resolution2: Give write permission to MPSIGNSS folder. App: 2.xx.xxx MachineInfo: W2K Incident: CIO Load Component CIO Automation Error Class Factory could not supply requested class # -2147221231 INFO: Possibly related to bad market data (map data) Cause: Unknown - Possible install media corruption. Resolution: Created a new CD, reinstalled the market, everything is fine. App: 2.04.008 MachineInfo: NT4 SP6 Incident: CIO.LoadComponent Component 'MSCOMCT2.OCX' or one of it's dependencies not correctly registered: a file is missing or an invalidError Number: 339 Cause: On NT4, ImageMan causes a problem using .NET/Crystal Reports Resolution: Later release of Photo DLL does not use ImageMan on NT4 machines App: 2..xx.xxx MachineInfo: unreported Incident: CIO Load Component Error 372 Failed to load control common dialog from COMDLG32.OCX Your version of COMDLG32.OCX may be outdated. Make sure you’re using a version of the control that was provided with your application. INFO: Cause: Unknown Resolution: Resolved by user's IT support - resolution unreported App: x.xx.xxx Environment: Unknown MachineInfo: Incident: Error 429: ActiveX component can’t create object INFO: Cause: Unknown Resolution: Resolved by user's IT support - resolution unreported APP: x.xx.xxx Environment: Unknown MachineInfo: Incident: Microsoft Visual C++ Runtime Library Runtime error! Program: ...\Common Files\InstallShield\engine\6\INTEL 32\Ikernel.exe Abnormal program termination INFO: Cause: Unknown Resolution: Resolved by user's IT support - resolution unreported Incident: 007 APP: REX Std - 2.04.016 MachineInfo: OS=2000 ADMIN=YES CPU=586 LANGUAGE=English COLORS=65536 Incident: RMX Error Error 1935.An error occured during the installation of assembly component. {B40AB920-76E3-47AF-AA97-D0775D8C1143}. HRESULT: -2147319761. INFO: Cause: Unknown - MY guess is: An error or installation of a preexisting assembly component wanted to kick off a rollback and couldn’t (due to registry settings disallowing rollback). Resolution: See Incident 008 Incident: 008 APP: REX Std - 2.04.016 MachineInfo: OS=2000 ADMIN=YES CPU=586 LANGUAGE=English COLORS=65536 Incident: Program Error dotnetfx.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created. INFO: Happened after incident 007 Cause: Unknown - MY guess is: The previous error wanted to kick off a rollback and couldn’t (due to registry settings disallowing rollback). Resolution: Ran dotnetfx.exe from the CD (rather than going through setup.exe) which produced the following error: Microsoft .NET Framework (English) Setup You must enable rollback to continue with setup. For more info, see http://support.microsoft.com/support/kb/articles/q312/4/99.asp" There are two places in the registry where the DisableRollback policy value can be set. To resolve this problem, you must find out where the DisableRollback policy was set and remove or disable the setting. To find out whether this property exists in your registry, run C:\Regedit.exe and check the following locations: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer\DisableRollback HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer\DisableRollback If the DisableRollback key exists and has a value of "1", delete the key or set the value of the key to "0". (You can also set DisableRollback through command-line instructions.) Microsoft recommends that administrators and developers not set this property if they use command line instructions to run Setup, or Setup will not work. Incident: 009 APP: REX Std - 2.04.016 MachineInfo: XP Incident: Installation appears to be hung up (stopped) during MapX installation or during font installation. INFO: Cause: Unknown - MY guess is: An active application will not allow the install to install fonts. Resolution: 1) Cancel Install. 2) Reboot 3) CLOSE ALL APPLICATIONS before running the install It may be necessary to stop any virus protection programs also, to allow the install to complete. Incident: 010 APP: REX Std - 2.xx.xxx MachineInfo: NT (unconfirmed) Incident: Retail Explorer (??) An installation support file could not be installed. Interface not registered. INFO: none provided Cause: This issue can occur if the following corrupted registry value exists: Registry key: HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer32 Value: InprocServer32 Data: Dmi?y'%,g(V$DC!{,`WjOLE_Automation_Support>M5KDYSUnf(HA*L[xeX)y[~]qsL+$_..... (or something similar) Resolution: Go to Start > Run and type in regedit to open the registry. Expand under the HKEY_CLASSES_ROOT hive to: CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer32. Delete the corrupted registry value InprocServer32 Incident: 011 APP: REX Std - 2.xx.xxx MachineInfo: OS=XP Incident: Application (REX) freezes during the validation process (RO). INFO: Bring up Map Bring up RO for an outlet Save tactic (that has errors in it... ex: no primary traffic) When Validation window is called, interface 'freezes' and has to be killed thru Task Manager. No freezing occurs if Validation window never displays (i.e., data is 'clean') Probable Info: Problem happens AFTER XP SP1. Cause: Flaw in Windows WM_TIMER Message Handling Could Enable Privilege Elevation (328310). Resolution: Microsoft Security Bulletin MS02-071 Download & Install MS hotfix 328310 End User Bulletin: An end user version of this bulletin is available at: . Incident: 012 APP: REX Std - 2.xx.xxx & 2.04.016 MachineInfo: OS=XP, SP=1, ADMIN=YES, COLORS=16777216 Incident: Error Retrieving Market ID Error '430' Class does not support Automation or does not support expected interface. INFO: lastgo1mu99279.G_0=2001\07\23 Supposedly with English regional settings on date and numerics Cause: unknown Resolution: Resolved by user's IT support - resolution unreported Incident: 013 APP: REX Std - 2.xx.xxx & 2.04.016 MachineInfo: OS=? Incident: Client has to run reports manually. INFO: Feature Cause: Training Issue Resolution: In the RexReports menu, under Options, there is a setting called Show report when... The client's interface has turned on the option: "I click the Run Button" He needs to change his options to: "I change settings" Then the reports will run automatically. Incident: 014 APP: REX Std - 2.05.006 MachineInfo: OS=2000 Incident: Rex21Reports Run-Time error ‘75’: Path/File access error INFO: All Std Reports receive RunTime error while closing. This particular case, there is only one market installed. The problem is more than likely a market by market issue. Cause: The REX application was unable to update or remove *.QDA files in the ..\market_name\cases folder. Resolution: Manually delete all QDA files in the ..\market_name\cases folder. Incident: 015 APP: REX Std - 2.04.016 MachineInfo: OS=NT4 Incident: AddMkt() Error Error -2147023897 Method ‘~’ of object ‘~’ failed. INFO: User trying to add Houston market to hard drive through the REX Administrator. Option "Add Market. Cause: While trying to replicate problem - 3 different error message occurred. One on Win98, W2K and NT4. Resolution: Manually copied all market files from CD to ..\markets\market_name folder. Configured files through the REX Administrator after all files existed on the hard drive. Incident: 016 APP: REX Std - 2.04.016 MachineInfo: OS=NT4 Incident: UpdateCaseImpactsLst() Error 91: Object variable or With block variable not set. INFO: User trying to display case impact on REX Map. A regular map works. Cause: Unknown. Resolution: Resolved by user's IT support - resolution unreported Incident: 017 APP: REX Plus - 2.05.112 MachineInfo: OS=NT5.1 (XP SP1), UserPrivilege=Administrator Incident: Mapxxxxxxxxxx() Error 91: Object variable or With block variable not set. INFO: User trying to run REX Map. Retail Explorer module works. Cannot close REX app after error. Never ending OK buttons to error. GNSSINFO / Trace won’t finish after ending REX task through task manager. Cause: Unknown. Resolution: User installed Custom Reports and problem went away. Incident: 018 APP: REX Plus - 2.05.??? MachineInfo: OS=NT5.0.???? (W2K), UserPrivilege=Administrator Incident: CreateBasicLayers() Error Error 91: Object variable or With block variable not set. INFO: User trying to run REX+ Map against Perth. All other modules work. Other markets work. Adding Custom Reports did not help as above. Cause: Unknown. Resolution: Resolved by user's IT support - resolution unreported Incident: 019 APP: REX Standard - 2.04.016 MachineInfo: OS= NT5.0.2195 (W2K) SP4, UserPrivilege=Administrator Incident: CIO.Launch Error 91: Object variable or With block variable not set. INFO: ReInstallation of REX using previous MPSIGNSS folder. User was instructed to run the latest update (2.06.005). Trace indicates update was not run. Cause: Unknown. Resolution: Resolved by user's IT support - resolution unreported Incident:  020 APP: REX Std - 2.06.008 MachineInfo: OS=XP SP1, Admin Privilege Incident:  UpdateCaseImpactsLst() Error 91: Object variable or With block variable not set. INFO: User trying to display case impact on REX Map. A regular map works. All cases were removed from machine. ‘No change’ tactic will not display case impact. Cause: Too many BMP files in the MapX custsymb folder. Resolution:  Run RepairLOGOs.exe Incident:  021 APP: REX Std - 2.06.008 MachineInfo: OS=XP SP2, Admin Privilege Incident:  UpdateCaseImpactsLst() Error 91: Object variable or With block variable not set. INFO: User trying to display case impact on REX Map. A regular map works. A ‘No change’ tactic worked in one market. Some cases work, some don’t. Cause: Too many BMP files in the MapX custsymb folder. Resolution:  Run RepairLOGOs.exe Incident:  022 APP: REX Std - 2.04.016 MachineInfo: OS=NT4 SP6, NO Admin Privilege Incident:  Error Error 3706: Provider cannot be found. It may not be properly installed. INFO: User selected market, then Case Explorer. Dialog title=Error User opened Map. Same error except title=Rex21Map New Templates created on the date of the error. <-- Probable cause? Cause: Unknown Resolution:  Resolved by user's IT support - resolution unreported Incident:  023 APP: REX 1 - 1.02.015 MachineInfo: OS=NT4 SP6, NO Admin Privilege Incident:  Unknown INFO: Incident reported as: Problems mapping in my Austin 2001 Refit Cause: Unknown. Resolution:  Resolved by user's IT support - resolution unreported Incident:  024 APP: REX 2 - 2.0?.0?? MachineInfo: OS=???, NO Admin Privilege Incident:  License File Error Error 9: CANNOT CREATE FILE INFO: Incident reported as: Problem running map in Fort Lauderdale Palm Beach 2003 ActionTaken: Suggested logging on as Admin. Possible cause: User can’t write to ...\system32 folder. Cause: Unknown Resolution:  Resolved by user's IT support - resolution unreported Incident:  025 APP: REX Plus 2.06.107 MachineInfo: OS=XP 5.01.2600 Service Pack 2, NO Admin Privilege Incident:  StateSafeReader_GetXMLDocument() Error Error -2147024770: Automation error The specified module could not be found. INFO: Incident reported as: Problem running map using/creating MapX workspace ActionTaken: Requested GNSSInfo Trace files from working machine and machine with error. Looks like MSXML4.DLL is missing. Created XML4.exe (Installs MSXML4). Available in MPSI download area under: REX Plus\English Install failed on client machine. Looking for P drive. Supposition: Security won’t allow install. Cause: Repackaging process of install at client site is missing MS XML DLLs. Resolution:  Unknown. XML4 install would not run on client machine. Resolved by user's IT support - resolution unreported Incident:  026 DATE: 11/02/2005 APP: REX Standard 2.04.016 MachineInfo: OS=XP INFO: Incident reported as: Trying to print from internet and getting error message about needing Disk 1 of RMX.msi ActionTaken: Copied RMX install to MPSI download area. User's IT support person ran uninstall and reinstall Custom Reports. Cause: Unknown Resolution:  Reinstalling RMX worked Incident:  027 DATE: 11/02/2005 APP: REX ?.??.??? MachineInfo: OS=??? INFO: Incident reported as: When map component is selected, getting the error message "The library MITMIN30.DDL could not be found". ActionTaken: Requested GNSSInfo file (no trace) from user. Cause: Resolution:  Resolved by user's IT support - resolution unreported Incident:  028 DATE: 11/08/2005 APP: REX Standard 2.06.010 MachineInfo: OS=XP Incident:  Error while running custom reports. INFO: ShowRMXReport () Error Error -2146233088: SQL Error in: SELECT O.OUTL_ID, ... Plus many lines listed from the query statement ActionTaken: Cause: Needed newer Custom Report Templates Resolution:  Update templates with CRPop.exe Incident:  029 DATE: 12/06/2005 APP: REX Standard 2.06.009 MachineInfo: OS=2000 SP4 Incident:  Received the following error on any function selected (Explorer, Map, Report, ...) INFO: Title not reported Error 91: ~ object or variable not set (may not be complete message text) ActionTaken: Cause: Read Only cases were copied to the machine. Resolution:  Change Properties on cases and remove Read Only setting. Incident:  030 DATE: 12/07/2005 2:18 PM APP: REX Plus 2.06.109? MachineInfo: OS=XP? Incident:  Received the following error when a REX map is selected... ErrorMsg: UpdateLayerShortcuts() Error Error 91: Object variable or With block variable not set INFO: User trying to run REX Plus Map. Retail Explorer and other modules work. Cannot close REX app after error. GNSSINFO / Trace won’t finish after ending REX task through task manager. ActionTaken: Cases and Templates checked out ok. Checked for any read only mapping files - checked out ok. Ran CRPOP utility - no help. Uninstalled/ReInstalled - no help. ReInstalled Custom Reports manually - no help. Ran RepairLogos utility - no help. Copied all mapping files manually to make sure none were corrupted - no help. Reinstalled with REX Standard. All functions reported to run fine. Cause: unknown Resolution:  Resolved by user's IT support - resolution unreported Incident:  031 DATE: 01/03/2006 0:00 PM Happened a while back - just documenting... APP: GENESYS ? MachineInfo: OS=?? Incident:  Installation error... ErrorMsg: GENESYS Internal Error 25001.1615 : RegistrationCosting::CostAllISSelfRegEntries::MsiDatabaseOpenView(hDatabase, from ISSelfReg),&hView INFO: ActionTaken: Cause: unknown Resolution:  Resolved by user's IT support - resolution unreported Incident:  032 DATE: 01/03/2006 0:00 PM Happened a while back - just documenting... APP: REX/Custom Reports/REX Bundle 5 MachineInfo: OS=?? Incident:  Installation error... ErrorMsg: Custom Reports (Title) The installed product does not match the installation Sources(s). Until a matching Source is provided or the installed product & source are synchromized, this action can not be performed. Custom Reports (Title) The file "G:\common\transfer\...RMX\CustomReportsMS.msi is not a valid installation package for the product Custom Reports. Try to find the installation package "CustomReportsMSI.msi in a folder from which you can install CustomReports. INFO: Error 1731. The source installation package for the product CustomReports is out of sync with the client package. Try the installation again using a valid copy of the installation package "CustomReports.msi ActionTaken: 1) You can uninstall CustomReportsMSI and CustomReports. Then rerun the install. 2) Or Find the original "CustomReportsMSI.msi" file that was used to install MPSI’s Custom Reports in the first place (just as the message indicates). Cause: unknown Resolution:  Resolved by user's IT support - resolution unreported Incident:  033 DATE: 04/21/2006 APP: REX Standard/Custom Reports/2.06.010 MachineInfo: OS=XP, SP1 Incident:  Custom Reports Failure ErrorMsg: Error Opening Data Error in File C:\mpsignss\markets\market_name\ClientData\Reports\ReportName.tmp: The Request could not be submitted for background processing. INFO: Appears to be linked to .NET 2.0 being installed. ActionTaken: Install rex21.exe.config file. Cause: .NET 2.0 Resolution:  Install rex21.exe.config file. Incident:  034 DATE: 05/02/2006 APP: REX Plus/2.0?.??? MachineInfo: OS=??, ADMIN=Yes (unverified) Incident:  Invalid Code received (activation code) ErrorMsg: Invalid Code received INFO: ActionTaken: Suggested issuing REX Standard activation code Cause: Uninstalled REX Plus, ReInstalled with REX Standard Resolution:  Verified: REX Standard activation code worked. Incident:       035 DATE:           07/18/2007 APP:            REX Plus/2.0?.??? MachineInfo:    OS= XP, ADMIN=unknown Incident:       Adding a demand tactic to a case causes an error when the case tries to load to the REX Plus map.  ErrorMsg:       457 - This key is already associated with element of this collection  INFO:               ActionTaken:   Remove Read Only From Geoset folder (apply to all files under it)  Cause:              Resolution:     Remove the Read Only attribute of file Properties on all mapping files   Incident:       036 DATE:           10/22/07 APP:            REX ??? MachineInfo:    OS=Vista, ADMIN Group=YES, Actual Administrator User=NO Incident:       Errors after install. Application will not run. ErrorMsg:       DialogName=Unknown/Not reported ErrorMsg        Runtime error 91 Object Variable or Width Block Variable not set INFO:        Vista issue: You have to log on as Administrator to install Belonging to the Administrator group does not give enough authority to install, register and write registry entries. On Vista you have to enter the Activation codes as Administrator also. ActionTaken:   User is reinstalling as Administrator Cause:          Vista security Resolution:     Use RunAs option to install and enter activation codes on Vista.