Anonymous_User Absent Member.
Absent Member.
1242 views

desktop app "Filr service not working" after update to 3.4.2

Hello,

we are using desktop management software for software rollout.
So we installed the latest desktop app via
"msiexec.exe /I "MicroFocusFilr-x64-3.4.2.msi" /qn /norestart"
on top the outdated 3.4.0 desktop app.

Some clients now reporting repeatedly above message. You have to manual
stop the "novell filr caching service", uninstall filr desktop app and
reboot.
On Windows 7 you can re-install the msi and all works fine. On Windows
10 the message came again after re-install.

The Event viewer reports this:
Application FilrService.exe
Version of framework: v4.0.30319
The process was terminated due to an unhandled exception.
Exception information: exception code c0000005, ...

additionally an event with id 1000 regarding to filrservice.exe was
created. Wondering: there is version 3.4.1 reported, but we talking
about 3.4.2???

Examining the docs about installation dependencies:
..NET 4.5 and VC2013. X64 versions?

Anyone here with same experiences?

Gotthard


--
Gotthard Anger
Anwenderbetreuung Netzwerkadministration
Landeskirchenamt der EKM
gotthardanger@no-mx.forums.novell.com
https://forums.novell.com/member.php/35038-gotthardanger

Mails an diese Adresse werden nur nach vorheriger Ansage gelesen!
Mails for this address will only be read if you trigger me before.
0 Likes
4 Replies
ingesbraathen Absent Member.
Absent Member.

Re: desktop app "Filr service not working" after update to 3

We got the same experience on some users with the new client, all on Windows 10.
0 Likes
creddyagnal Absent Member.
Absent Member.

Re: desktop app "Filr service not working" after update to 3

Hi Gotthard,

Thanks for reporting the issue.

1) 3.4.2 filr desktop client is dependent on 4.6.2 .NET framework. Since you are using msi installer with no GUI option (/nq), dependent .NET framework is not getting installed. You can try (/qf) option which will pop up a window for installing dependent package in GUI mode (Please go through the msi document).
2) It will be better to use "MicroFocusFilrSetup-x64-3.4.2.exe" file, since it contains .NET framework inbuilt. It is safe to use filr exe file. Just double click on the file and it will install/upgrade seamlessly.


Let us know if you still face the issue. We will help you.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: desktop app "Filr service not working" after update to 3.4.2

Am 13.11.2018 um 06:36 schrieb creddyagnal:
>
> Hi Gotthard,
>
> Thanks for reporting the issue.
>
> 1) 3.4.2 filr desktop client is dependent on 4.6.2 .NET framework. Since
> you are using msi installer with no GUI option (/nq), dependent .NET
> framework is not getting installed. You can try (/qf) option which will
> pop up a window for installing dependent package in GUI mode (Please go
> through the msi document).
> 2) It will be better to use "MicroFocusFilrSetup-x64-3.4.2.exe" file,
> since it contains .NET framework inbuilt. It is safe to use filr exe
> file. Just double click on the file and it will install/upgrade
> seamlessly.

Sorry, the problem is to build an process for upgrade the installation
in silent mode, because the "true" admin doesn´t allow the normal user
installing software.
And as I stated in other post, the exe file doesn´t contain any .net
components. May be the exe has the ability to detect the absence of .net
4.6.2 and can download it.
Further, our workstations have .net 4.6.2 installed, so we must find
other dependencies.

Gotthard




--
Gotthard Anger
Anwenderbetreuung Netzwerkadministration
Landeskirchenamt der EKM
gotthardanger@no-mx.forums.novell.com
https://forums.novell.com/member.php/35038-gotthardanger

Mails an diese Adresse werden nur nach vorheriger Ansage gelesen!
Mails for this address will only be read if you trigger me before.
0 Likes
Highlighted
creddyagnal Absent Member.
Absent Member.

Re: desktop app "Filr service not working" after update to 3

Hi Gotthard,

Thanks for clarifying that your need is to upgrade the Filr client through silent mode install (push install) through push agents.

You are right, Filr exe doesn't contain .Net 4.6.2 components, but it has the mechanism to detect whether it is already installed and if not download and install .Net 4.6.2. We believe silent mode install of Filr client will let .Net 4.6.2 to be installed at first. You may try pushing .Net 4.6.2 to all workstations and then push Filr 3.4.2 client.

However new Filr 3.4.2 desktop client (929) is only dependent on 4.6.2 .NET framework and there are no other dependencies for it. Running exe file will automatically install all dependent packages. Hence it is advised to verify whether client has installed latest .Net 4.6.2 framework or manually install .Net 4.6.2 before upgrading to 3.4.2 desktop client.

We need your help in troubleshooting this issue further. Could you please perform upgrade scenario in separate windows machine manually.
1) Have a Win 10/7 windows machine.
2) Upgrade 3.4.2 client manually.
3) Verify .Net framework version.
4) Verify whether files/folder are getting listed and are accessible.
This helps in understanding what is happening during manual upgrade. Since you have mentioned it’s a silent msi update, we are suspecting .NET framework update is getting skipped.

Note:
How to check the current .Net framework version? Please follow below links.
https://help.bittitan.com/hc/en-us/a...ave-installed-
https://docs.microsoft.com/en-us/dot...-are-installed

Collect following information which will help us in debugging the issue.
1) The current .NET framework version.
2) Event viewer log.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.