Difference between revisions of "Error Codes"

From PalOMoney
Jump to navigation Jump to search
Line 9: Line 9:
 
=== Opening a Money File ===
 
=== Opening a Money File ===
  
* 80040154 -- newly reported error from MoneyPal launched from PalOMoney ''Update Now'' and perhaps Money open, a normal use case scenario. Log file and console message is "Error 80040154 opening [FullPathToMoneyFile]"
+
* 80040154 -- Money DB engine is not registered on your computer. Earlier MoneyPal versions required a registered Money DB engine. Upgrade to 1.0.3-c or later, where this is optional and not required.
 +
** newly reported error from MoneyPal launched from PalOMoney ''Update Now'' and perhaps Money open, a normal use case scenario. Log file and console message is "Error 80040154 opening [FullPathToMoneyFile]"
 
** Could this be related to Microsoft product 80040154 Class not registered REGDB_E_CLASSNOTREG? However, PalOMoney had the db open, and they share the same db code, so what could this be?
 
** Could this be related to Microsoft product 80040154 Class not registered REGDB_E_CLASSNOTREG? However, PalOMoney had the db open, and they share the same db code, so what could this be?
    [USER additional info: file was not open in Money and password was deactivated.
+
*** USER's additional info: file was not open in Money and password was deactivated. Money file opens normally by double-clicking it.
    Money file opens normally by double-clicking it.)]
+
 
  
 
* 800a1406 -- Missing or incorrect Microsoft Money (Jet) file password. Supply the correct password.
 
* 800a1406 -- Missing or incorrect Microsoft Money (Jet) file password. Supply the correct password.

Revision as of 16:57, 19 February 2013

Error codes appear from time to time in dialogs or log files. We don't have the documentation for the Microsoft Money error codes. Do any of you? If so, please edit this topic (register first) and add a link to an online source, or edit the topic to include the codes, or email support or dev with a list of error codes, whatever you can do. Thank you.

Codes are given in Wikipedia::hexadecimal form. Most of the Money error codes are Microsoft Wikipedia::Component Object Model codes, which translate to hard-to-read large negative decimal numbers.

It is nearly impossible to read MoneyPal messages, including errors, when launched from PalOMoney. See Troubleshooting MoneyPal.

Microsoft Money Error Codes

Opening a Money File

  • 80040154 -- Money DB engine is not registered on your computer. Earlier MoneyPal versions required a registered Money DB engine. Upgrade to 1.0.3-c or later, where this is optional and not required.
    • newly reported error from MoneyPal launched from PalOMoney Update Now and perhaps Money open, a normal use case scenario. Log file and console message is "Error 80040154 opening [FullPathToMoneyFile]"
    • Could this be related to Microsoft product 80040154 Class not registered REGDB_E_CLASSNOTREG? However, PalOMoney had the db open, and they share the same db code, so what could this be?
      • USER's additional info: file was not open in Money and password was deactivated. Money file opens normally by double-clicking it.


  • 800a1406 -- Missing or incorrect Microsoft Money (Jet) file password. Supply the correct password.
  • 800a140b -- opening (Money file) -- file is read only, or access is denied (incorrect permissions)
    • Probably not: possibly associated with file locking, or DB inconsistency.
  • 800a1466 -- Money file not found (wrong name).


Updating Quotes

  • Error 800a148c updating (ticker) (price) (date)
  • Error 800a13ea updating (ticker) (price) (date)


PalOMoney Error Codes

Opening Money Jet Engine

  • Error x locating Money installation -- if Money 2008 or Sunset is not installed, or damaged.
  • Error x locating Money install folder -- if Money 2008 or Sunset is not installed, or damaged.
  • Error d loading Jet 3.5 Engine -- could not load the Money database engine.
  • Error x creating Money Database Engine

Updating

  • Http Error 404 opening URL -- (decimal) the server was contacted, but could not find the URL.