- The editor setup only lists the database options when it reaches the newer SQL Server instance; with two instances (2008 R2 and 2019) it failed with the DBNETLIB error on the old one.
- What fixed it: move (upgrade) the MU database to the newer instance (SQL Server 2012 or newer; the asker used SQL Server 2019) and point the editor at it.
- The asker used CzF because MuMaker does not support his Season 1.0 files.
CzF MU Editor 1.5: DBNETLIB error at install; it only finds the SQL Server 2019 instance, not the 2008 R2 one with the MU database
Tool: CzF MU Editor 1.5
“Anyway i upgrade the db to sql 2019 and it works now..Thanks”
The topic starter, 2020-07-10 (original words)