# Error after v5.6 upgrade from v5.5 **URL:** \ **Category:** Logstash\ **Created:** [October 29, 2019, 3:14pm UTC](https://discuss.elastic.co/t/error-after-v5-6-upgrade-from-v5-5/205704 "2019-10-29T15:14:20Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ronaldom](https://avatars.discourse-cdn.com/v4/letter/r/8baadc/32.png) [@ronaldom](https://discuss.elastic.co/u/ronaldom)\ **Post date:** [October 29, 2019, 3:14pm UTC](https://discuss.elastic.co/t/error-after-v5-6-upgrade-from-v5-5/205704/1 "2019-10-29T15:14:21Z")
Hi guys, We just recently upgrade our Elastic Stack from v5.5 to v5.6. We encountered the error below when we tried running logstash to populate the new v5.6 indices. Any idea what's going on here? We already re-installed the input jdbc plugin in logtash. **SAMPLE LOG:** [2019-10-29T15:06:01,970][ERROR][logstash.pipeline] A plugin had an unrecoverable error. Will restart this plugin. Plugin: \"~/sqljdbc\_6.2/enu/mssql-jdbc-6.2.1.jre8.jar", jdbc\_driver\_class=\>"com.microsoft.sqlserver.jdbc.SQLServerDriver", jdbc\_connection\_string=\>"jdbc:sqlserver://;user=;password=;", jdbc\_user=\>"", jdbc\_password=\>, jdbc\_validate\_connection=\>true, jdbc\_validation\_timeout=\>-1, last\_run\_metadata\_path=\>"/etc/logstash/.logstash\_jdbc\_something\_type\_ref\_last\_run", clean\_run=\>true, statement=\>"SELECT \* FROM [dbo]. ", type=\>"somethingtyperef", id=\>"e2d1740c363567586234b229d04384c304dc871c-40", enable\_metric=\>true, codec=\>\"plain\_d3065ef2-da96-4e23-b8e4-9e517e5438d3", enable\_metric=\>true, charset=\>"UTF-8"\>, jdbc\_paging\_enabled=\>false, jdbc\_page\_size=\>100000, jdbc\_pool\_timeout=\>5, sql\_log\_level=\>"info", connection\_retry\_attempts=\>1, connection\_retry\_attempts\_wait\_time=\>0.5, parameters=\>{"sql\_last\_value"=\>1970-01-01 00:00:00 +0000}, use\_column\_value=\>false, tracking\_column\_type=\>"numeric", record\_last\_run=\>true, lowercase\_column\_names=\>true\> Error: com.microsoft.sqlserver.jdbc.SQLServerDriver not loaded. Are you sure you've included the correct jdbc driver in :jdbc\_driver\_library? ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [October 29, 2019, 4:06pm UTC](https://discuss.elastic.co/t/error-after-v5-6-upgrade-from-v5-5/205704/2 "2019-10-29T16:06:45Z")
A workaround for the failure to load the driver might be [this](https://github.com/logstash-plugins/logstash-filter-jdbc_static/issues/47#issuecomment-496606449). Read through the whole thread before implementing. ---
**Author:** ![ronaldom](https://avatars.discourse-cdn.com/v4/letter/r/8baadc/32.png) [@ronaldom](https://discuss.elastic.co/u/ronaldom)\ **Post date:** [October 31, 2019, 2:10pm UTC](https://discuss.elastic.co/t/error-after-v5-6-upgrade-from-v5-5/205704/3 "2019-10-31T14:10:17Z")
Thanks @Badger! Additional information: **CONF** input { jdbc { jdbc\_driver\_library =\> "{JDBC\_DRIVER\_PATH:/home/ubuntu/sqljdbc\_6.2/enu/mssql-jdbc-6.2.1.jre8.jar}" jdbc\_driver\_class =\> "com.microsoft.sqlserver.jdbc.SQLServerDriver" jdbc\_connection\_string =\> "jdbc:sqlserver://server;user=username;password=password;" jdbc\_user =\> "username" jdbc\_password =\> password" jdbc\_validate\_connection =\> true jdbc\_validation\_timeout =\> -1 last\_run\_metadata\_path =\> "{LOGSTASH\_METADATA\_PATH:/etc/logstash}/.logstash\_jdbc\_profile\_last\_run" clean\_run =\> true statement =\> "SELECT \* FROM dbo.Table ORDER BY Id" } } As you can see above, **jdbc\_driver\_library** uses the value of {JDBC\_DRIVER\_PATH} environment variable which is \*\*~/sqljdbc\_6.2/enu/mssql-jdbc-6.2.1.jre8.jar\*\*. This path is not recognized for some reason. The error did not happen again when I removed the {JDBC\_DRIVER\_PATH} env variable in the conf file and hard-coded the path to **/home/ubuntu/sqljdbc\_6.2/enu/mssql-jdbc-6.2.1.jre8.jar**. I will try changing the value of the ${JDBC\_DRIVER\_PATH} to replace **~** with **/home/ubuntu** ---
**Author:** ![ronaldom](https://avatars.discourse-cdn.com/v4/letter/r/8baadc/32.png) [@ronaldom](https://discuss.elastic.co/u/ronaldom)\ **Post date:** [November 7, 2019, 3:48pm UTC](https://discuss.elastic.co/t/error-after-v5-6-upgrade-from-v5-5/205704/4 "2019-11-07T15:48:24Z")
Currently trying to populate the employee index with the below settings: ```auto input { jdbc { jdbc_driver_library => "~/sqljdbc_6.2/enu/mssql-jdbc-6.2.1.jre8.jar" jdbc_driver_class => "com.microsoft.sqlserver.jdbc.SQLServerDriver" jdbc_connection_string => "jdbc:sqlserver://SERVER;user=USER;password=PASSWORD" jdbc_user => "DB_USER" jdbc_password => "DB_PASSWORD" jdbc_validate_connection => true jdbc_validation_timeout => -1 statement => "SELECT * FROM [dbo].Employee ORDER BY ID" type => "employee" } } filter { } output { } ``` NOTE: _filter_ and _output_ sections of the conf file is purposely blank **LINUX COMMAND** ```auto sudo /usr/share/logstash/bin/logstash -f /home/ubuntu/Employee-pipeline.conf --path.settings /etc/logstash/ --path.data /var/lib/logstash_new ``` **RESULT** [![enter image description here](https://us1.discourse-cdn.com/elastic/original/3X/7/4/74d9b6c32b8d94fc2cf88ddd5ea46aafd4072315.png)](https://i.stack.imgur.com/qKw9F.png) Looks like logstash does not know or don't have access to ~/sqljdbc...\*.jar I also confirmed that the _mssql-jdbc-6.2.1.jre8.jar_ exists [![enter image description here](https://us1.discourse-cdn.com/elastic/original/3X/1/1/116fae2c70b6a00b149812fa5c4d0616e2700b5b.png)](https://i.stack.imgur.com/iapLz.png) However, when I changed the path to **/home/ubuntu/sqljdbc\_6.2/enu/mssql-jdbc-6.2.1.jre8.jar** , it runs successfully. So **~/** is the same as **/home/ubuntu** This started to occur after upgrading our Elastic Stack from v5.5 to v5.6. Also, note that this does not occur if we run the same conf file with the logstash service. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 5, 2019, 3:48pm UTC](https://discuss.elastic.co/t/error-after-v5-6-upgrade-from-v5-5/205704/5 "2019-12-05T15:48:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.