Hi there...
my situation -> SC exe with 14 support-connections (5501-5514).
For every technican here 2 connections. Everything works fine except the Connection to our new tech. who uses port 13 and 14.
They work on a Terminalserver (same UVNC for all, but different dsm-pluginnames ->plugin is still the same)
e.g.
C:\Programme\UltraVNC\vncviewer.exe -dsmplugin VNC_Single_click1_2.dsm -listen 5501
and
C:\Programme\UltraVNC\vncviewer.exe -dsmplugin VNC_Single_click3_4.dsm -listen 5503
The new tech. has got
C:\Programme\UltraVNC\vncviewer.exe -dsmplugin VNC_Single_click13_14.dsm -listen 5513
under my UserLogin connection works great with his config but he gets also under diffent configs like first example following error messages:
"The plugin cannot be loaded.
Please check its name integrity."
and
"Connection failed - Invalid protocol!
Possible causes, forgotten to select a DSMPlugin..." (Just a result of the first msg I think)
So what's wrong there? He's got the same rights as I have?!
[Topic can be moved to DSMPlugin if it's necessary, but I don't think that's a prob' with the Plugin]
Bassi2k
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/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://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/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://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
DSMPlugin cannot be loaded?
DSMPlugin cannot be loaded?
Last edited by Bassi2k on 2008-02-20 09:34, edited 1 time in total.
Re: DSMPlugin cannot be loaded?
Check and make sure all command parameters are separated with ONE SPACE only, and also there should be NO SPACE appending after the command script.
Re: DSMPlugin cannot be loaded?
I used copy'n'paste to insert command parameters... they are written in a txt-file as an example. I checked the spaces... nothing wrong there.
However SAME commandline i copied from his Linking works under my UserLogin.
However SAME commandline i copied from his Linking works under my UserLogin.
Re: DSMPlugin cannot be loaded?
So the tech. run the viewer script with a link.
Maybe you should also check:
1. Is the starting location of the link also the folder of vncviewer (i.e. C:\Programme\UltraVNC\)? This can be shown at the property of the link.
2. Also at the property of the link, select "Advance", click the box of "Run Under Other User's A/C" (Or wording of similar meaning). Login to the tech's A/C, and run the viewer link, when prompt for the user name, try to use your UserLogin to see what is going on.
3. Also under the tech's UserLogin. If he opens a DOS CMS windows, goto the folder C:\Programme\UltraVNC\, and then type & run the script directly. Check if the error still exist.
Maybe you should also check:
1. Is the starting location of the link also the folder of vncviewer (i.e. C:\Programme\UltraVNC\)? This can be shown at the property of the link.
2. Also at the property of the link, select "Advance", click the box of "Run Under Other User's A/C" (Or wording of similar meaning). Login to the tech's A/C, and run the viewer link, when prompt for the user name, try to use your UserLogin to see what is going on.
3. Also under the tech's UserLogin. If he opens a DOS CMS windows, goto the folder C:\Programme\UltraVNC\, and then type & run the script directly. Check if the error still exist.