nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Portfolio X-Ray not working

lashleyfamily

I have reported this and asked for help 2 times using the help feature and it sends log and screenshots but no responce.

This use to work and was a great help in looking at my portfolio. I dont think it has worked since the moved to quicken basic.

Anyone have any suggestions?

Find more posts tagged with

Comments

NotACPA

If by "Quicken Basic", you actually mean "Starter Edition" … that function doesn't exist in Starter.

lashleyfamily

It is called Quicken Classic Premier.

Jim_Harman

You will not get any response to the "Report a Problem" link.

Apparently this message sometimes appears if one of the securities you have selected has an invalid Ticker Symbol.

Try selecting just publicly traded securities with valid Tickers and let us know what happens.

q_lurker

In a now-archived post, I offered the information below:

I was able to track this down to inclusion or exclusion of one specific security - a bond. It's ticker is not an exchange traded ticker, but neither are another 19 bonds that do not create the problem. The symbol I am passing through is also not specifically unique or different than the other 19. I am at a loss at this stage as to why this one security causes the SAMLERROR error. Still investigating.

Assuming it is ticker based (inside quotes)
"KS Law 5% 090123" causes the error
"KS Lea 5% 090124" does not cause the error.
I suspect there is something else involved. Both bonds carry the Quicken type = Bond, Asset Class = Domestic Bond.

(This all applies on a copied/validated file using QW-Subscription R25.10.)

On another note, FWIW, these 'bonds' (or any other security) with non-exchange tickers or with CUSIP as tickers do not get factored into the Morningstar X-Ray summaries. That is understandable and not unexpected by me, but I don't know that it is documented anywhere.

bajohnson_47

Jim Harman's suggestion works for me. i.e. only select securities in x-ray that have a public ticker symbol. Thus things like iBonds, cds, etc. will not be included in the x-ray analysis.

[Deleted User]

My Portfolio X-Ray is working just fine. I have several securities without valid or published tickers. I have CDs and other closely held securities with made up tickers. They are all included in the Portfolio X-Ray. At one point I was getting the "SAMLERROR:Redirect failed" error message, but how I fixed it is to make sure every security has an "Asset Class". In other words, no security has an asset class of "Unclassified". Ever since I updated all of the Asset Classes, I haven't had an issue.

q_lurker

Update: My prior comment which I quoted above from an archived post was written in March 2020. I have since sold that problematic bond and bought two others (among several) that are now problematic. For those two (and others) I have used the CUSIP as the ticker symbol. So the problematic tickers are: 46625HJY7 (Type = Bond; Asset Class = Domestic Bond) and 55903VAY9 (Type = Bond; Asset Class = Domestic Bond).

As before, numerous other bonds with similar ticker symbol patters do not create this problem.

Clearly, I am not a frequent user of the X-Ray feature, or I might have picked up on this change when the prior bond matured (sold) or when I bought the other two bonds.

bajohnson_47

q_lurker. Tks for the suggestion. I will try with my bonds tomorrow.

bajohnson_47

q-lurker. Unfortunately only bonds that have a market on exchanges have a CUSIP. Thus Treasury iBonds, savings bonds, etc. that I own do not have a CUSIP.

q_lurker

@bajohnson_47 My point really had nothing to do with the CUSIP as a specific ticker characteristic. My observation has been that I have always been able to track down (by trial and error) one or two securities (in my case bonds) with non-standard tickers that generate the SAMLERROR response. The ticker being non-standard seems to me to be one critical criterion but there is something else going on. Where I have several bonds with CUSIPs as tickers (a nine character alphanumeric mix), only two of those cause the SAMLERROR. Similarly earlier I had similar longer multi-character tickers for different bonds, but only one led to the SAMLERROR.

My trial and error process — I find the one account that leads to the SAMLERROR, then somewhat systematically select and unselect securities to include in the X-Ray until I identify the problem security.

lashleyfamily

Thank you for all of the help.

When I went in and removed the bonds and calls then it worked correctly.

Thanks again.