I notice this issue occurs when using a relogger. I use Arelog and sometimes i would get the " profile could not be found " error message when DB tries to load up before it logs into the Diablo account.. To fix this "temporarily", i log into Diablo 3 manually first then load up DB, reattach the profile "start here" then Start, stop DB, close out. then rerun Arelog and let it do its thing. It should then work right. BUT i dont know why but sometimes itll randomly happen if i ever get disconnected etc.. sorta puts a damper on my 24/7 run.