04-11-2019 05:58 PM
Ok, loooks like might be another issue.
The issue I replicated when connecting to your db returned error:
The issue you are seeing connecting to any db is error:
04-12-2019 06:07 AM
If the accumulating bugs here and one other place are an accurate indication, the SQL Server component inside the Features Input operator is somewhat troubled compared to its counterparts for Oracle and PostGIS - or at least more vulnerable to failure due to circumstances not yet known. We are actually looking at these issues currently, by coincidence, as we are introducing some unrelated improvements here. If there is any information to share in due course, I'll do so. - Hal
04-14-2019 03:50 PM
Resolution to 'Object reference not set to an instance of an object' was installing 'Microsoft System CLR Types'
Documented in the GeoMedia 2018 update 1 & 2 installation notes.
"In order to use SQL Server from the Features Input and Features Database Output operators of Spatial Modeler, you must download the Microsoft System CLR Types for Microsoft® SQL Server® (2008 R2 and 2014 versions).
Verify that you have administrator privileges on the system where you want to install GeoMedia.
To download the Microsoft System CLR Types for Microsoft® SQL Server® (2008 R2 and 2014 versions), visit the Microsoft download site. For example, for the 2008 R2 version, visit: Microsoft® SQL Server® 2008 R2 Feature Pack download site http://go.microsoft.com/fwlink/?LinkID=188391&clcid=0x409; for the 2014 version, visit: Microsoft® SQL Server® 2014 Feature Pack download site https://www.microsoft.com/en-us/download/details.aspx?id=42295. For GeoMedia 2018, you must install the 32-bit (x86) variant."
Note: Do not need to install the entire feature pack. Download ‘ENU\x86\SQLSysClrTypes.msi’ (and optionally ‘ENU\x64\SQLSysClrTypes.msi’) and install.
The other error subsequently observed 'One of the identified items was in an invalid format' has an existing ticket submitted with resulting bug report.