+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.
+7Are you able to provide a snippet of the error from the Data Inspector log and a sample file? I'd be interesting in trying to reproduce this.
Thanks,
Nathan
+54Are you able to provide a snippet of the error from the Data Inspector log and a sample file? I'd be interesting in trying to reproduce this.
Thanks,
Nathan
FME Desktop version is 2018.1.0.1 build 18528 64 bit
Log as attachment. log.txt
+7FME Desktop version is 2018.1.0.1 build 18528 64 bit
Log as attachment. log.txt
Looking into this. Currently unable to reproduce, however.
Nathan
+7Looking into this. Currently unable to reproduce, however.
Nathan
Best,
Nathan
Hi, I have been experiencing the same problem, also using 2018.1. It happens regardless of the input file. Is there anything I can do to fix it? @NathanAtSafe
Thanks,
Dragana
+54Hi, I have been experiencing the same problem, also using 2018.1. It happens regardless of the input file. Is there anything I can do to fix it? @NathanAtSafe
Thanks,
Dragana
Hi, I have been experiencing the same problem, also using 2018.1. It happens regardless of the input file. Is there anything I can do to fix it? @NathanAtSafe
Thanks,
Dragana
+54
+35
+54Looking into this. Currently unable to reproduce, however.
Nathan
+54Looking into this. Currently unable to reproduce, however.
Nathan
Does anyone have any other suggestions to solve this problem? The reinstall does not help unfortunately.
Thanks.
+35Does anyone have any other suggestions to solve this problem? The reinstall does not help unfortunately.
Thanks.
I'd suggest getting in touch with Safe Support (safe.com/support). Include the build number(s) where your seeing the problem, any logs and a sample of the data which causes issues with you. Also provide some details about the environment on which FME is running (32/64 bit, Operating system, VM type, etc)
+7
I'd suggest getting in touch with Safe Support (safe.com/support). Include the build number(s) where your seeing the problem, any logs and a sample of the data which causes issues with you. Also provide some details about the environment on which FME is running (32/64 bit, Operating system, VM type, etc)
Thanks.
Nathan
(PS hey @virtualcitymatt!)
+1I've got the same problem.
In my case, it was caused by a defunct fmedatainspector.exe (a process running on windows - shown in Task Manager, but with no Window - graphic interface).
I just killed that process and the problem was fixed. A simple system reboot would fix it too.
+5Hi, I am having the same issue with 2018.1.0.1 (20180730 - Build 18528 - WIN64). The inspector opens but I can only see the attribute table - geometry not displaying. I've tried with the 32 bit version but to no avail. The 32 bit inspector now seems to hang at the splash screen when opening (initialising user interface...). It does open sometimes but results in the same error. I've tried killing all fme processes, restarting Windows - no change. Weirdly it all worked fine until today - now both 64bit and 32bit installs are not working. FME 2017 still works fine, so I'll have to revert back to that version.
I see there is now build: 18547 available but we only just installed FME Server build 18528. I'm wondering whether this has been fixed in 18547?
+5Hi, I am having the same issue with 2018.1.0.1 (20180730 - Build 18528 - WIN64). The inspector opens but I can only see the attribute table - geometry not displaying. I've tried with the 32 bit version but to no avail. The 32 bit inspector now seems to hang at the splash screen when opening (initialising user interface...). It does open sometimes but results in the same error. I've tried killing all fme processes, restarting Windows - no change. Weirdly it all worked fine until today - now both 64bit and 32bit installs are not working. FME 2017 still works fine, so I'll have to revert back to that version.
I see there is now build: 18547 available but we only just installed FME Server build 18528. I'm wondering whether this has been fixed in 18547?
+54Hi, I am having the same issue with 2018.1.0.1 (20180730 - Build 18528 - WIN64). The inspector opens but I can only see the attribute table - geometry not displaying. I've tried with the 32 bit version but to no avail. The 32 bit inspector now seems to hang at the splash screen when opening (initialising user interface...). It does open sometimes but results in the same error. I've tried killing all fme processes, restarting Windows - no change. Weirdly it all worked fine until today - now both 64bit and 32bit installs are not working. FME 2017 still works fine, so I'll have to revert back to that version.
I see there is now build: 18547 available but we only just installed FME Server build 18528. I'm wondering whether this has been fixed in 18547?
Not sure if its Windows update related. My old Lenovo W540 is working well, but some of my colleagues with the newer P50 have problems. Some of them, not all. All in the same company, updates are managed by IT so the environments should be quite equal.
Might have to do something with AutoDesk Civil 3D. A new P50 is coming our way, we will install FME first, then the other components to check when it starts to fail.
+5
Not sure if its Windows update related. My old Lenovo W540 is working well, but some of my colleagues with the newer P50 have problems. Some of them, not all. All in the same company, updates are managed by IT so the environments should be quite equal.
Might have to do something with AutoDesk Civil 3D. A new P50 is coming our way, we will install FME first, then the other components to check when it starts to fail.
+54
+54Small update: It looks like it is Windows Profile related... When logging on with a fresh user on the defective laptop the problem goes away and the performance is stunning.
+54Small update: It looks like it is Windows Profile related... When logging on with a fresh user on the defective laptop the problem goes away and the performance is stunning.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
