NovAlf

Fleet Admiral
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-01-12
11:20
767 views
Faulting application name: nzrWinVNCApp.exe
Hi!
After applying ZCM 17.3 seems to some problems start to arise using Remote Management (RM). During session attempt on Windows 10 (1809) device „Faulting application name: nzrWinVNCApp.exe” appear in log and … device restart might return RM to work again, seems to.
Any ideas?
More thanks, Alar.
After applying ZCM 17.3 seems to some problems start to arise using Remote Management (RM). During session attempt on Windows 10 (1809) device „Faulting application name: nzrWinVNCApp.exe” appear in log and … device restart might return RM to work again, seems to.
Any ideas?
More thanks, Alar.
2 Replies
CRAIGDWILSON

Micro Focus Expert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-01-14
17:34
Is the Target Device actually at 17.3?
There was a known issue in 17.2 (Maybe 17.1) where that process could crash and is fixed in Update 3.
Verify that nzrWinVNCApp.exe actually is the 17.3 version. (That is the specific file updated to fix the issue.)
There was a known issue in 17.2 (Maybe 17.1) where that process could crash and is fixed in Update 3.
Verify that nzrWinVNCApp.exe actually is the 17.3 version. (That is the specific file updated to fix the issue.)
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
NovAlf

Fleet Admiral
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-01-17
14:47
Hi and thanks!
Yes, device(s) is at 17.3 and exe is as 17.3.0.1265. Exception code: 0xc0000005.
More thanks, Alar.
Yes, device(s) is at 17.3 and exe is as 17.3.0.1265. Exception code: 0xc0000005.
More thanks, Alar.