I imagine you are complicated legacy addresses with legacy wallets. They’re distinct and unrelated issues.
- Legacy addresses are pre-segwit addresses (P2PKH mostly), and are contrasted with segwit and taproot addresses.
- Legacy wallets are pockets recordsdata within the BDB file format, created by previous variations of Bitcoin Core (and might nonetheless be opened by new variations, for now). They’re contrasted with descriptor wallets, which use the SQLite file format, that are created by newer variations of Bitcoin Core.
You may create legacy addresses utilizing descriptor wallets, and you may create segwit (however not taproot) addresses utilizing legacy wallets.
What I think is occurring right here is that you just’re attempting to carry out the dumpprivkey on a legacy handle in a descriptor pockets. And that does not work, as a result of dumpprivkey solely works on legacy wallets (no matter handle kind). Exporting non-public key’s harmful, and particularly so for descriptor wallets (the place an attacker can sometimes compute all your non-public keys from only one). In case you should, you’ll be able to export the non-public grasp key utilizing listdescriptors, although I think this won’t be what you need.
That will help you discover an alternate, I encourage you to amend your reply to elucidate precisely what you are attempting to attain (or level out if my interpretation of occasions is inaccurate). Maybe an answer exists that does not contain exporting non-public keys, as that’s typically a foul thought except you actually know what you might be doing.