Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Discussioni su EssentialPIM in italiano
Alex81
Experienced
Posts: 56
Joined: Thu Nov 03, 2016 12:21 pm
Been thanked: 2 times

Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by Alex81 »

salve ho problemi con epim portable pro ultima versione
quando faccio una ricerca sau tabelle o passo dal tab tabelle a giornaliero o settimsanale mi da questo errore di continuo...


There was an error during the execution of this program.
Click "Send" to submit the report to the developer. Please also provide any steps necessary to reproduce the problem.

Access violation at address 01538FFC in module 'EssentialPIM.exe'. Read of address 1305BE9C.

There was an error during the execution of this program.
Click "Send" to submit the report to the developer. Please also provide any steps necessary to reproduce the problem.

''DxÖ'' is not a valid integer value.

------------------------------------------------------------------------------
Exception log with detailed tech info. Generated on 06/01/2024 18:02.
You may send it to the application vendor, helping him to understand what had happened.
Application title: Alex.epim - EssentialPIM Pro Portable
Application file: C:\Essential pim pro portable_old\EssentialPIM.exe
Application: EssentialPIM Pro Portable 11.8 19/12/2023
------------------------------------------------------------------------------
Exception class: EConvertError
Exception message: ''DxÖ'' is not a valid integer value.
Exception address: 0042903A
------------------------------------------------------------------------------
Main thread ID = 3064
Exception thread ID = 3064
------------------------------------------------------------------------------
Object Logs:
18:01:50.872 SetViewMode OK
18:01:50.606 SetViewMode 1
18:01:48.014 DBSave OK
18:01:48.011 DBSave
18:01:37.920 DBOpen OK
18:01:37.721 SetViewMode OK
18:01:37.560 SetViewMode 0
18:01:34.437 DBClose OK
18:01:33.867 DBSave OK
18:01:33.865 DBSave
18:01:33.851 DBClose
18:01:33.851 DBOpen
18:01:16.886 SetViewMode OK
18:01:16.548 SetViewMode 1
18:01:15.426 DBOpen OK
18:01:15.224 SetViewMode OK
18:01:14.981 SetViewMode 0
18:01:03.801 DBOpen
18:00:48.202 DBOpen
------------------------------------------------------------------------------
Active Controls:
18:02:29.519 MainForm FormPan TBXToolbar2 TopPan Top2TB FindCB
18:02:27.112 ExceptionDialog OkBtn
18:02:25.016 MainForm FormPan TBXToolbar2 TopPan Top2TB FindCB
18:02:22.518 ExceptionDialog OkBtn
18:02:20.012 MainForm FormPan TBXToolbar2 TopPan Top2TB FindCB
18:02:16.553 MainForm FormPan FormPan2 TasksForm TablePan TableSubPan TasksPan TasksVT
18:02:05.511 MainForm FormPan FormPan2 TasksForm TablePan SearchBar FromPan FromDateDTP
18:02:05.011 MainForm FormPan FormPan2 TasksForm TablePan SearchBar FilterSelPan FilterSelCB
18:02:03.511 ExceptionDialog OkBtn
18:02:00.704 MainForm FormPan FormPan2 TasksForm TablePan SearchBar FilterSelPan FilterSelCB
------------------------------------------------------------------------------
Memory: 32597; free 22730
Display: 1920x1080 pixels, 32 bpp, 96 PPI
------------------------------------------------------------------------------
PrevExceptions:
18:01:19.036 ''DxÖ'' is not a valid integer value
18:01:23.394 ''DxÖ'' is not a valid integer value
18:01:53.048 ''DxÖ'' is not a valid integer value
18:02:04.599 ''DxÖ'' is not a valid integer value
18:02:13.081 ''DxÖ'' is not a valid integer value
18:02:24.826 ''DxÖ'' is not a valid integer value
18:02:29.506 ''DxÖ'' is not a valid integer value
------------------------------------------------------------------------------
Updates: 1
Last update: 06/01/2024
admin
Site Admin
Posts: 15681
Joined: Thu Nov 25, 2004 3:12 am
Has thanked: 1424 times
Been thanked: 990 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by admin »

Will you be able to reproduce the problem with a new test database?
Android version of EssentialPIM. Keep all your data in sync!
Alex81
Experienced
Posts: 56
Joined: Thu Nov 03, 2016 12:21 pm
Been thanked: 2 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by Alex81 »

con un database vuoto? comunque succede quando vado dentro la voce tabella e poi ritorno su visione calendario giornaliera compare l'errore....il popup di errore...
potrei provare a riprodurlo con db vuoto .... devo trovare il tempo
Alex81
Experienced
Posts: 56
Joined: Thu Nov 03, 2016 12:21 pm
Been thanked: 2 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by Alex81 »

con il db nuovo e vuoto non da problemi

adesso sto cercando di togliere la crittograFIA dal db (sperando sia quello il problema) ma mi riporta questo errore e non me lo decrittografa.
sbaglio qualche cosa?



There was an error during the execution of this program.
Click "Send" to submit the report to the developer. Please also provide any steps necessary to reproduce the problem.

violation of PRIMARY or UNIQUE KEY constraint "PK_PARAMS2" on table "PARAMS2"
Problematic key value is ("IDUSER" = 1, "NAME" = 'SidebarToDosViewMode').

------------------------------------------------------------------------------
Exception log with detailed tech info. Generated on 08/01/2024 17:39.
You may send it to the application vendor, helping him to understand what had happened.
Application title: Alex.epim - EssentialPIM Pro Portable
Application file: C:\Epim\EssentialPIM.exe
Application: EssentialPIM Pro Portable 11.8 19/12/2023
------------------------------------------------------------------------------
Exception class: EIBInterBaseError
Exception message: violation of PRIMARY or UNIQUE KEY constraint "PK_PARAMS2" on table "PARAMS2"
Problematic key value is ("IDUSER" = 1, "NAME" = 'SidebarToDosViewMode').
Exception address: 00779090
------------------------------------------------------------------------------
Main thread ID = 5884
Exception thread ID = 5884
------------------------------------------------------------------------------
Object Logs:
17:34:51.623 DBOpen OK
17:34:51.404 SetViewMode OK
17:34:51.159 SetViewMode 0
17:34:47.920 DBClose OK
17:34:47.741 DBSave OK
17:34:47.739 DBSave
17:34:47.721 DBClose
17:34:46.330 DBOpen
17:34:35.062 SetViewMode OK
17:34:34.980 SetViewMode 1
17:34:33.767 SetViewMode OK
17:34:33.697 SetViewMode 0
17:34:32.243 SetViewMode OK
17:34:32.205 SetViewMode 1
17:34:31.676 SetViewMode OK
17:34:31.630 SetViewMode 5
17:34:30.945 SetViewMode OK
17:34:30.900 SetViewMode 7
17:34:30.257 SetViewMode OK
17:34:30.089 SetViewMode 6
------------------------------------------------------------------------------
Active Controls:
17:39:42.879 MainForm FormPan TBXToolbar2 TopTB NewItemBtn
17:39:12.771 StatusForm
17:39:10.236 NewPassDialog Panel1 PasswordEd
17:39:07.735 NewPassDialog Panel1 ConfirmPassEd
17:38:58.368 NewPassDialog GroupBox1 EncryptCB
17:38:53.237 NewPassDialog Panel1 PasswordEd
17:38:49.733 PasswordDialog PasswordEd
17:38:45.736 MainForm FormPan TBXToolbar2 TopTB NewItemBtn
17:38:42.236 ExceptionDialog OkBtn
17:38:41.957 MainForm FormPan TBXToolbar2 TopTB NewItemBtn
------------------------------------------------------------------------------
Exception stack
Stack list, generated 08/01/2024 17:24
(01137FFC) [01538FFC]
(00F86224) [01387224]
(00F855C5) [013865C5]
(00F857D9) [013867D9]
(00F83CDB) [01384CDB]
(00F89ABA) [0138AABA]
(000D44FC) [004D54FC]
------------------------------------------------------------------------------
Memory: 32597; free 21729
Display: 1920x1080 pixels, 32 bpp, 96 PPI
------------------------------------------------------------------------------
PrevExceptions:
17:23:26.239 Access violation at address 01538FFC in module 'EssentialPIM.exe'. Read of address 145A236C
17:24:09.384 Access violation at address 01538FFC in module 'EssentialPIM.exe'. Read of address 147C010C
17:24:11.748 Access violation at address 01538FFC in module 'EssentialPIM.exe'. Read of address 147C010C
17:38:45.337 violation of PRIMARY or UNIQUE KEY constraint "PK_PARAMS2" on table "PARAMS2"
Problematic key value is ("IDUSER" = 1, "NAME" = 'SidebarToDosViewMode')
------------------------------------------------------------------------------
Updates: 1
Last update: 08/01/2024
Alex81
Experienced
Posts: 56
Joined: Thu Nov 03, 2016 12:21 pm
Been thanked: 2 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by Alex81 »

ho creato nuovo db ed esportato calendario rubrica etc nel nuovo database e sembra non dare errori.
Chissa se il problema è legato alla cifratura dati? Perche pero non me la rimuove la cifratura sul vecchio db?

In caso esportassi tutto dal vecchio database al nuovo non dovrei perdere nulla giusto?
Su calendario--> appuntamenti da esportare per salvare tutto devo selezionare "riepilogo" ?

Mi esporta solamente 10563 appuntamenti, invece da db risultano 17000 circa mon capisco perche....

cosa posso fare? vorrei ricreare nuovo db se voi non avete soluzioni in merito per riparare il vecchio ma non capisco perchè mi esporta meno appuntamenti....
Alex81
Experienced
Posts: 56
Joined: Thu Nov 03, 2016 12:21 pm
Been thanked: 2 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by Alex81 »

ma quindi? mi tengo il problema? nessuna soluzione? perche se esporto il calendario in un altro database mi importa meno appuntamenti?
sto cercando il modo di risolvermi da solo il preoblema dato che non riucevo assistenza!
admin
Site Admin
Posts: 15681
Joined: Thu Nov 25, 2004 3:12 am
Has thanked: 1424 times
Been thanked: 990 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by admin »

Which EPIM version was your database file initially created in? To find that out, please click on File->Database Management and pay attention to the "This database was opened in" string at the bottom of the dialog window. If the total number of versions is greater than 5, we'd recommend you to renew your database by synchronizing it over to a new one using our free tool EPIM Synchronizer (https://www.essentialpim.com/features/f ... nchronizer). Please let us know if it helps. Thanks!
Android version of EssentialPIM. Keep all your data in sync!
Alex81
Experienced
Posts: 56
Joined: Thu Nov 03, 2016 12:21 pm
Been thanked: 2 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by Alex81 »

Admin ho provato a sincronizzare su nuovo db ma il problema persiste.
La versione del mio db cmq è 7.13.
Se provo esportare ad esempio gli appuntamenti su nuovo db non mi copia alcuni. Ho provato anche a esportare un solo appuntamento e quell'unico appuntamento non lo esporta. Magari l'appuntamento al di sotto lo esporta correttamente. Insomma durante esportazione si perde tanti appuntamenti.
Non esiste un modo per fare un controllo di coerenza?
Sta diventanto inutilizzabile il mio epim dato che da sempre errore.....
Come posso risolvere?

Grazie per l'attenzione
admin
Site Admin
Posts: 15681
Joined: Thu Nov 25, 2004 3:12 am
Has thanked: 1424 times
Been thanked: 990 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by admin »

So, after synchronizing your data to the new DB, are you still encountering the same error? Please post a screenshot of the database management window of the newly created DB with data synced from the previous DB into it.
Android version of EssentialPIM. Keep all your data in sync!
Alex81
Experienced
Posts: 56
Joined: Thu Nov 03, 2016 12:21 pm
Been thanked: 2 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by Alex81 »

ecco le schermate con l'errore. Il popup compare quando cambio schede.
Attachments
IMG_20240114_164002.jpg
epim.jpg
admin
Site Admin
Posts: 15681
Joined: Thu Nov 25, 2004 3:12 am
Has thanked: 1424 times
Been thanked: 990 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by admin »

Thank you. When you synchronize your database over to the new one, only the latest version number is mentioned in the "Your database was opened in" field. So please make sure you really moved your data over to the new database using EPIM Synchronizer. Thanks!
Android version of EssentialPIM. Keep all your data in sync!
Alex81
Experienced
Posts: 56
Joined: Thu Nov 03, 2016 12:21 pm
Been thanked: 2 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by Alex81 »

si compare solamente la nuova versione del nuovo database ma non risolve il problema
admin
Site Admin
Posts: 15681
Joined: Thu Nov 25, 2004 3:12 am
Has thanked: 1424 times
Been thanked: 990 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by admin »

We'd appreciate it if you could record a short video showing the point at which the error occurs, as well as the Database Management dialog window. Thank you!
Android version of EssentialPIM. Keep all your data in sync!
Alex81
Experienced
Posts: 56
Joined: Thu Nov 03, 2016 12:21 pm
Been thanked: 2 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by Alex81 »

Il video vorrei mandaro in via privata dato che compaiono dati sensibili. A quale indirizzo posso mandare il video?
admin
Site Admin
Posts: 15681
Joined: Thu Nov 25, 2004 3:12 am
Has thanked: 1424 times
Been thanked: 990 times

Re: Access violation at address 01555841 in module 'EssentialPIM.exe'. Read of address 002C007A.

Post by admin »

Please forward it to me via a private message here in the forum. Thanks!
Android version of EssentialPIM. Keep all your data in sync!
Post Reply