+54A colleague recently installed Desktop 2018.0 and later on 2018.1. Workspace seems to run correctly but when the inspector pops up it logs the following error:
Failed to create the reader in the worker process for 2D rendering Best answer by nielsgerrits
Work around is to borrow a license from the license server. Not really a fix but it works well enough for now!
The weird part is that not one of the other users with the same installation on the same hardware in the same network connecting to the same license server have this problem.
+54
@nielsgerrits
Hi, yes in the end I contacted Safe Support, and it turns out installing the 32bit version solves the issue. So right now I am not seeing this error anymore, but still the question is what caused it in the first place, and will it happen again ...
+54@nielsgerrits
Hi, yes in the end I contacted Safe Support, and it turns out installing the 32bit version solves the issue. So right now I am not seeing this error anymore, but still the question is what caused it in the first place, and will it happen again ...
+54Work around is to borrow a license from the license server. Not really a fix but it works well enough for now!
The weird part is that not one of the other users with the same installation on the same hardware in the same network connecting to the same license server have this problem.
+7Nathan
+5Work around is to borrow a license from the license server. Not really a fix but it works well enough for now!
The weird part is that not one of the other users with the same installation on the same hardware in the same network connecting to the same license server have this problem.
+5@nielsgerrits
Hi, yes in the end I contacted Safe Support, and it turns out installing the 32bit version solves the issue. So right now I am not seeing this error anymore, but still the question is what caused it in the first place, and will it happen again ...
+5
+54
In our case I think the issue is windows profile related because when the user got new hardware the problem reappeared. When I logged on with my profile on his machine I got no issues...
What we tried, but didn't make any difference:
- 32-bit installer
- Uninstall all FME versions, delete C:\\Users\\<user>\\AppData\\Roaming\\Safe Software, remove HKEY_LOCAL_MACHINE\\SOFTWARE\\Safe Software Inc., reboot, install FME 2018.1.
- Install FME 2018.1 on a new, clean, laptop.
I now suspect it might be an old, node locked license file confusing the Inspector. I'm gonna check out the directories where license files might live when the user is back at the office. (As this is not my hardware/login it's even harder to solve...) Locations can be:
- <fme-install-folder>/licenses
- C:\\ProgramData\\Safe Software\\FME\\Licenses
- C:\\users\\<user>\\Documents\\FME\\Licenses
I expect to find something in the last folder.
+5Work around is to borrow a license from the license server. Not really a fix but it works well enough for now!
The weird part is that not one of the other users with the same installation on the same hardware in the same network connecting to the same license server have this problem.
+54
+7Hi all,
We may have narrowed down this issue and found a potential workaround. Please contact Safe Support if you encounter the error indicated by the OP, and provide a log file from Data Inspector showing the error as well as a screen shot of the "About FME Workbench Dialog" from FME Workbench (this shows us the current license and edition information which is important for troubleshooting the issue).
An initial workaround is to try to borrow a license if you are using a floating license, although this is not applicable in all situations.
Thanks for your continued patience as we work through this issue.
Best,
Nathan
+5Hi all,
We may have narrowed down this issue and found a potential workaround. Please contact Safe Support if you encounter the error indicated by the OP, and provide a log file from Data Inspector showing the error as well as a screen shot of the "About FME Workbench Dialog" from FME Workbench (this shows us the current license and edition information which is important for troubleshooting the issue).
An initial workaround is to try to borrow a license if you are using a floating license, although this is not applicable in all situations.
Thanks for your continued patience as we work through this issue.
Best,
Nathan
Ekki
Hi all,
We may have narrowed down this issue and found a potential workaround. Please contact Safe Support if you encounter the error indicated by the OP, and provide a log file from Data Inspector showing the error as well as a screen shot of the "About FME Workbench Dialog" from FME Workbench (this shows us the current license and edition information which is important for troubleshooting the issue).
An initial workaround is to try to borrow a license if you are using a floating license, although this is not applicable in all situations.
Thanks for your continued patience as we work through this issue.
Best,
Nathan
So, what is the solution? I just ran into this, and borrowing a license does nothing for me.
+18So, what is the solution? I just ran into this, and borrowing a license does nothing for me.
@igatchik We're still not 100% certain of the problem yet. The solution for others might not help you. As @NathanAtSafe said, please contact Safe Support.
+24New computer and I have the same issue :(
Failed to initialize the reader in the temporary rendering process
Failed to create the reader in the worker process for 2D rendering
Will try to install 32-bit now to see if it fixes the issue on the 64-bit.
Tried both latest 2018 and 2019 BETA (64-bit).
+24New computer and I have the same issue :(
Failed to initialize the reader in the temporary rendering process
Failed to create the reader in the worker process for 2D rendering
Will try to install 32-bit now to see if it fixes the issue on the 64-bit.
Tried both latest 2018 and 2019 BETA (64-bit).
Installing 32-bit FME does not help either.
+54New computer and I have the same issue :(
Failed to initialize the reader in the temporary rendering process
Failed to create the reader in the worker process for 2D rendering
Will try to install 32-bit now to see if it fixes the issue on the 64-bit.
Tried both latest 2018 and 2019 BETA (64-bit).
@sigtill please contact Safe Support. They can help you with a functioning workaround.
+24@sigtill please contact Safe Support. They can help you with a functioning workaround.
@nielsgerrits - the workaround from Safe (regedit ++) makes FME start a new FME Data Inspector every time, instead of using the existing one. So it creates a delay of starting FME Data Inspector (20sec) every time i click inspect features. It seems to ignore the already opened FME Data Inspector. I`ll get back to them again.
+54@nielsgerrits - the workaround from Safe (regedit ++) makes FME start a new FME Data Inspector every time, instead of using the existing one. So it creates a delay of starting FME Data Inspector (20sec) every time i click inspect features. It seems to ignore the already opened FME Data Inspector. I`ll get back to them again.
@sigtill excuse me, I was not aware of that as I didn't need to use this solution. The 20 sec drawback sounds not workable for me either.
+7New computer and I have the same issue :(
Failed to initialize the reader in the temporary rendering process
Failed to create the reader in the worker process for 2D rendering
Will try to install 32-bit now to see if it fixes the issue on the 64-bit.
Tried both latest 2018 and 2019 BETA (64-bit).
Hi @sigtill,
Would you consider opening a support ticket so we can investigate the issue more thoroughly? With more information about the problem hopefully we can get closer to a fix rather than a workaround.
Thanks,
Nathan
+5Hi @sigtill,
Would you consider opening a support ticket so we can investigate the issue more thoroughly? With more information about the problem hopefully we can get closer to a fix rather than a workaround.
Thanks,
Nathan
Hi @NathanAtSafe, in case it helps - the workaround that you fixed my inspector with didn't result in this issue. For me, the same instance of FME Data Inspector is being used each time I run, opening new tabs.
For your information: I just encountered the same message too. After closing all instances of FME desktop and inspector and restarting the same workbench, this error no longer appears.
FME(R) 2018.1.0.1 (20180730 - Build 18528 - WIN64)
+7Please let me bump this:
Failed to initialize the reader in the temporary rendering processon version FME(R) 2023.1.0.0 (20230825 - Build 23619 - WIN64)
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
