SOBEK - FAQ and Known Issues
Find all of the known issues and frequently askes questions concerning SOBEK on this page. Maintenance and support is included in our SOBEK service packages. Please check the service packages for the package that suits your specific needs.
Support
The SOBEK support desk is the user’s instantly accessible contact point for all questions and problems concerning the software. The support team answers the majority of questions instantly or takes responsibility that a timely reply is given by one of the other SOBEK team members. All incoming queries on the software packages, current or future performance, are recorded in our issue tracker system. This system is an important instrument in the realization of improvements to the package, the manuals and the Deltares Academy training courses.
Contact support
If you have questions about purchasing the software, please contact our Sales Service team. For any of your software technical questions our Support team is happy to help you.
Known issues
Unsolved in SOBEK 2.16 2D Grid causes simulation to stop without error due to Unix End of Line format
SOBEK requires 2D grids to have Windows End of Line format. Grids that have been created on Linux or with QGIS (for example), will need to be converted to the Windows format. If your GIS software does not provide an option to change this, or if you have received your grid from a third party, you can manually change the format as follows:
- Download and install the free text editor Notepad++
- Open your grid with Notepad++
- In the menu, click on ‘Edit’ – ‘EOL Conversion’ – ‘Windows (CR LF)’
- Save the grid and reopen your SOBEK model
Note: If the option to convert to Windows format is greyed out in Notepad++, your grid already uses the Windows format.
Solved Errors when opening SOBEK output graphs after installing August 2019 Windows Update
After installing the August 2019 Windows Update, opening graphs in ODS_View will show the following error:
Error 5 : Invalid procedure call or argument ( subDoGraph / CommonObjects10 part 14)
This is a known issue with the August 2019 Windows Update, and Microsoft is working on a resolution. This issue affects all supported Windows versions.
We expect a definitive fix to be distributed by Microsoft on the next Patch Tuesday, on September 10th.
Workaround:
- Blocking or uninstalling the August 2019 Windows Update will prevent the issue from occurring.
- Microsoft has provided temporary fixes for some of the affected Windows versions. These temporary fixes are labelled as “Preview” or “Optional” by Microsoft.
Please consult your IT department in decisions relating to (un-)installing Windows updates.
Background info:
List of temporary fixes by Microsoft:
- KB4512534 for Windows 10 Version 1809
- KB4512509 for Windows 10 Version 1803
- KB4512494 for Windows 10 Version 1709
- KB4512495 for Windows 10 Version 1607
- KB4517276 for Windows 10 Version 1507
- KB4517297 for Windows 7 und Windows Server 2008 R2
- KB4517301 for Windows Server 2008 SP2
- KB4517298 for Windows 8.1 und Windows Server 2012 R2
Microsoft describes this known issue as follows:
After installing this update, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an “invalid procedure call error.”
Frequently Asked Questions (FAQ)
Documentation
The software is delivered with a manual, including Getting Started and Tutorials.