Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

JavaViewer Errors

Should you have problems with the JavaViewer, here's the place to look for help or report issues
Post Reply
vancedailey
Posts: 5
Joined: 2010-03-02 21:27

JavaViewer Errors

Post by vancedailey »

We are seeing a significant number of errors when using the JavaViewer.
Examples include:
• Network error reset
• Error unknown compression method
• Error: Framebuffer update rectangle too large 2560x2560 at 29696,256)
• Error: incorrect tight palette size: 3
• Error: Invalid stored block lengths
• Error: Network error: could not connect to server: i134504:5901

While its reported to me that these errors have always occurred at some level of frequency its reported that the frequency has increased of late.
We are using release 1.0.6.4. I don't know the exact version of Java on our Windows XP workstations but I know its not very old.

Does anyone have any thoughts as to how we can research these intermittent issues?

One thought we had was to try other options such as turning off compression (the application runs on a high speed wan) and possibly try other parameter settings.

Is there documentation as to what should be passed on the url to control the setting of options?

Thanks,
Vance
redge
1000
1000
Posts: 6797
Joined: 2004-07-03 17:05
Location: Switzerland - Geneva

Re: JavaViewer Errors

Post by redge »

upgrade to 1.0.8.2 and look if better result.
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
vancedailey
Posts: 5
Joined: 2010-03-02 21:27

Re: JavaViewer Errors

Post by vancedailey »

We upgraded a group of Agents to 1.0.8.2 and kept track of their error rate and saw no improvement.

60% of the attempts to view a session resulted in one or more of the following errors:
Incorrect tight pallett size: 3
Unknown compression method
Could not connect to server: i134655:5901
The server at i144106 is taking to long to respond
Invalid stored block lengths
could not connect to server: i134640:5901
Unknown RFB message type 255
Framebuffer update rectangle too large: 2 5184x8209 at (52,30938)
Incorrect tight pallett size: 4
Unknown RFB message type 192
incorrect tight pallett size: 20

Is it possible to launch the regular (i.e. non java) viewer from a browser?
Or will launching an .exe be prohibited for security reasons?

Thanks,
Vance
redge
1000
1000
Posts: 6797
Joined: 2004-07-03 17:05
Location: Switzerland - Geneva

Re: JavaViewer Errors

Post by redge »

did you restart winvnc before new test ?
cache of web browser has been cleared ?
old java have some issue.
not all web browser had been tested. try another one.
big screen had not been tested with java (i think)

work around, try tightvnc 2.0b1
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
vancedailey
Posts: 5
Joined: 2010-03-02 21:27

Re: JavaViewer Errors

Post by vancedailey »

We tried your recommendations (except for using tightvnc) with no luck.

Is it possible to launch the regular viewer (i.e. not the javaviewer) from a browser?

These are PCs in a call center so we have total control over the PCs and what software we have installed.

Thanks,
Vance
B
800
800
Posts: 2338
Joined: 2009-09-09 14:05

Re: JavaViewer Errors

Post by B »

Well sure, you can try to launch the .EXE from the browser, but most browsers will fight you a bit, as you noted.

There's a thread about an ActiveX based viewer, if you're into that sort of thing...

But if you have complete control of the installations, what's wrong with letting them run the vncviewer.exe outside of the browser?
Post Reply