Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Pocketsense: File invalid or Contains corrupt information RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've been using Pocket Sense and Money (Sunset) since they were available.  Today I received this message for the first time.

    I download a "combined" file with 17 accounts.  By importing the accounts individually, I determined that two of those accounts (AT&T and CITI credit card accounts), had returned the same error as above with the following STATUS in the OFX file itself.

    <STATUS>
<CODE>2000
<SEVERITY>ERROR
<MESSAGE>Unsuccessful
</STATUS>

    The other OFX files imported successfully.

    I am not sure how to tell what version of PocketSense I am using, and wonder if the problem could be that I have an older version where this has been corrected?  Or is it just something I will have to work around on rare occasions?

    Thanks.

    Ron




    Tuesday, August 12, 2014 12:18 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Glad the problem is not present now.

    The setup.py  "7. Test Account" is a handy way to fetch the OFX from a single FI. I think it does not delete other OFX files from the XFR folder.

    • Marked as answer by Ron Rosenfeld Tuesday, August 19, 2014 12:05 PM
    Monday, August 18, 2014 8:07 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I got the same error on CitiCard when I tried just now. I was able to log in to the web interface.
    Tuesday, August 12, 2014 9:02 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Well, I'm sure you've got the latest version of PS, so it's probably a universal problem.  I wouldn't mind it with a "single" account, and that message comes from MSMoney.  I wonder if the script could somehow pre-process those errors so as to prevent MSMoney from choking on the whole file, and at least process the OFX downloads that are OK.

    Ron

    Tuesday, August 12, 2014 9:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Got it! Changed to

    appver     : 2100

    for sites.dat for Citicard, and it worked. 2200 would work.

    I plan to change 
    DefaultAppVer = '2200'

    in control2.py to match the latest released version of PocketSense.



    Tuesday, August 12, 2014 9:22 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hmmm.  Before changing appver, I tried downloading again, and it worked fine!  My default appver is 1900 and my version is Jan 2013.  So its not clear to me that appver is the problem.

    Ron


    Tuesday, August 12, 2014 11:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Well, I'm sure you've got the latest version of PS, so it's probably a universal problem.  I wouldn't mind it with a "single" account, and that message comes from MSMoney.  I wonder if the script could somehow pre-process those errors so as to prevent MSMoney from choking on the whole file, and at least process the OFX downloads that are OK.

    Ron

    I was not using the latest version of PS. I did some mods based on an earlier version. So I was using that earlier version and had not updated. I like to be able to analyze the separate OFX files, and I use PopDown2 rather than create a single OFX.

    Money sent its error message because it saw "<SEVERITY>ERROR" in the OFX file.

    Wednesday, August 13, 2014 3:25 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Money sent its error message because it saw "<SEVERITY>ERROR" in the OFX file.

    There is more to it than that.  My last download had several of those strings (<SEVERITY>ERROR), and the only error message was from PocketSense indicating that some of the files had errors.  Money processed the rest of the files without any difficulty.

    Ron

    Wednesday, August 13, 2014 9:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    For version info, you could do the following command in a command window where you have changed to the PocketSense executables directory:

    find  "*rlc" *.py

    You could go by the latest date.

    In XFR, you can get the non-combined *.ofx files. "Open"  (run) any one to feed it separately to Money. Do those that contain "<SEVERITY>ERROR" load into Money successfully?

    Monday, August 18, 2014 7:06 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    latest date is 28-Aug-2012

    And I'm not getting any error messages from either pocket sense or money at this time.  Since the files in xfr get overwritten each time, I cannot run the test under the original conditions

    I do have some investment accounts that show <STATUS><CODE>2003<SEVERITY>ERROR<MESSAGE>Invalid Account.  The combined.ofx file imports without difficulty and the individual accounts do not show an error message in Money.  Of course, I cannot be certain that this Error message occurs in the same area as the one that was giving a problem.  Also it is a different type of account.  It is possible that the first error message was in the <SIGNONMSGSRSV1>  segment, whereas this error code 2003 is in a later segment.

    Ron

    Monday, August 18, 2014 7:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Glad the problem is not present now.

    The setup.py  "7. Test Account" is a handy way to fetch the OFX from a single FI. I think it does not delete other OFX files from the XFR folder.

    • Marked as answer by Ron Rosenfeld Tuesday, August 19, 2014 12:05 PM
    Monday, August 18, 2014 8:07 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks.  I will keep that in mind should the problem recur.  And also pay more attention to the segment of the OFX file that contains the error message.

    Ron

    Tuesday, August 19, 2014 12:04 PM