guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Couchman <>
Subject Re: MS SQL Extension Broken?
Date Fri, 09 Feb 2018 13:33:49 GMT
On Fri, Feb 9, 2018 at 5:55 AM, sebastian.k <>

> Hi there,
> I've setup guacamole on centos 7.4/rhel with the new MS-SQL extension from
> version 0.9.14.
> The problem is that users get "corrupted". After a fresh install I can
> login
> once or twice with the guacadmin user without problems. But on the third or
> forth login attempt I'm getting. "Unexpected internal error". I logged out
> correctly every time. I also tried installing MS-SQL locally but the
> results
> are the same.
> ...
> It would be great if someone could tell me what I'm doing wrong.
> Is somebody using MS SQL 2016 with latest Guacamole 0.9.14 without any
> trouble?
> Thanks in advance
> Sebastian

It's definitely possible there is an issue with the MS-SQL Extension, but I
have not run into this particular behavior.  I doubt very much that the
user - or at least the user information in the database - is actually
getting corrupted.  It's more likely some sort of connection error between
the extension or JDBC driver and SQL Server.  So, a few questions for you...
- What version of Java are you using?
- What version of Tomcat are you using?
- What make/model/version of the MS-SQL JDBC driver are you using?
- If you restart Tomcat, does the problem go away?
- If you create a new user while you're able to log in, does that user
account work when guacadmin does not?
- Are there any system-level messages - anything in dmesg output, or
/var/log/messages, etc., that indicates any other sort of problem (OOM,
SELinux, etc.)?

Also, if you could, could you configure the Guacamole Client for either
debug or trace logging and post the output (preferably in a PasteBin or
something like that, and not in the e-mail)?  This can be done by creating
a logback.xml file in GUACAMOLE_HOME, and you can find instructions for
what that file needs to contain here:


View raw message