MVS
(Saritha MV)
Split this topic
July 27, 2021, 4:41pm
2
Hi @Anna_Hotsa ,
Do you have any insights to share for this issue? Or if you can tag someone who would have some information around this would be really helpful.
This process explains how to extract/recover data within .ssp file but once it is recovered, how can that data be used to recreate a .ssp file which can then be opened/edited via Task capture.
Regards
Sonali
Thanks, @sonaliaggarwal47 . We are working internally on this issue with @imran.shaikh
1 Like
Thank you @rashmi.nc for your response.
Please let us know as well when this issue is resolved
Regards
Sonali
wagner
(wagner alexandre pinto)
August 20, 2021, 6:11am
7
system:
ZIP-fixing tool
Hi
Any solution ?
We are struggling with that in our company.
Hi @rashmi.nc ,
Has resolution been achieved for this issue?
Regards
Sonali
No, I am having the same issue when I try to open an .ssp
Can you give an update @rashmi.nc ?
Hi @Georgy_Rudnev_Deefinity.c ,
Welcome to UiPath forum.
You don’t need to open .ssp directly with task capture in case of this error rather follow the steps outlined below:
system:
ssp file is a ZIP archive. Main files are:
document.json - document info, steps etc.
media/ - folder with the screenshots
Possible issues may be because of data corruption and steps below can be followed to identify the corruption
try if .ssp file could be unzipped.
if not - try to fix it with any ZIP-fixing tool and extract as much data as possible.
if no document.json file in the archive - data can’t be restored
send .ssp file, or at least - document.json (in that case - one could remove sensitive data from json file)
And after extracting, you still can’t see document.json, in that case, please share your .ssp file with UiPath team to recover data.
Regards
Sonali
rashmi.nc
(Rashmi C)
November 23, 2021, 8:32am
12
Came across this issue recently, turns out it was just to do with the Version of Task Capture.
The client was using Task Capture Version 21.10.1 and I was locally using Task Capture Version 21.4.1
I removed Task Capture and upgraded to Version 21.10.2 and was able to open all the files that were having that same error code.
It would appear that Task Capture is not backwards compatible.
Hope this helps!