Support Topics Documentation Slack YouTube Blog

RestorePassword (error code: '3025')


(Aleks P) #1

Hello, i got issue while restoring password
BackendlessFault{ code: ‘3025’, message: ‘Unable to perform password recovery due to error: null’, detail: ‘Unable to perform password recovery due to error: null’, extendedData: ‘{}’ }
that does not describe issue but when i tried to setup
Email Templates
Communicate with users
saw only empty screen https://www.evernote.com/l/AaDM_MVref1NdZmkCqSzUJmDkcWHuJDcEWcB/image.png


(Sergey Kukurudzyak) #2

Hello, what is your application id?


(Aleks P) #3

[details="here it is "]
z[/details]


(Sergey Kukurudzyak) #4

We have fixed your app. please check if everything ok


(Aleks P) #5

it works properly , thx a lot


(Aleks P) #6

I got the same issue ,pls help
appID 8B290ED5-688B-853A-FFF0-5146BF30ED00


(Mark Piller) #7

is it in the same app as before? I see that the app id was removed from a previous comment


(Aleks P) #8

yes the same, it happend after importing data.zip while migration from 3x version


(Sergey Kukurudzyak) #9

I have fixed your db and will create an internal issue to fix this bug in general


(Sergey Kukurudzyak) #10

internal issue number is BKNDLSS-17746


(Aleks P) #11

ok , Thank you a lot !


(Sergey Chupov) #12

Hey @aleks-p, can you provide a migration log for the migration which resulted in the app causing this error?


(Aleks P) #13

sure,
Backendless finished processing data and files from your 3.x application. There were failures during the migration process.
Please contact Backendless Support for assistance. To do this, make send your application ID of the application you attempted to migrate to 4.0 to support@backendless.com.

Detailed migration report is available at:
https://api.backendless.com/8B290ED5-688B-853A-FFF0-5146BF30ED00/1BB2FFEB-9543-9FBF-FF56-D9610D1B0A00/files/migration/migration_import.log


(Sergey Chupov) #14

Thank you!
The error log is truncated (there should be a “Migration finished” message in the end) so unfortunately we can’t see what was the failure. But the good news is that we have already fixed the truncation problem and after we release the fix soon we’ll be able to see what’s wrong.
Will you be able to repeat the migration import (after we notify you about the release) and let us know if the problem occurs again?


(Aleks P) #15

sure notify me when need