MuADMINS
Solutions
Short fixes for common MU Online server, client and website problems, each with its source and date. “Confirmed” means the person who asked said the fix worked.
0 solutions for “sql server 2008” in Gameplay · Clear
Nothing in Gameplay for these words yet, but they find solutions in other categories and server files (below).
Search all of MuGPS for “sql server 2008” Ask the MU Assistant
More answers for “sql server 2008”
0 in Gameplay, 21 in other categories and server 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
1. 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....
✓ Confirmed by the topic starterRaGEZONE · 2020-07-10DarksTeam 97d+99i on Windows 10 64-bit: servers say they cannot connect to SQL after installing SQL 2008. Editing the ODBC .reg did not help.
1. Uninstall the SQL Server 2008 instance that was installed with Windows authentication only. 2. Reinstall it choosing Mixed Mode and give sa a password. 3. Restore the MuOnline database...
✓ Confirmed by the topic starterTuServerMU · 2018-08-05SQL 2000 will not install on Windows 7, so how do I run DarksTeam 97d files on SQL Server 2008 R2 instead?
1. Install SQL Server 2008 R2 and set a password for sa during setup (do not skip it). 2. Restore the MuOnline database from the files. 3. Open the ODBC admin (32-bit one on 64-bit Window...
✓ Confirmed by the topic starterTuServerMU · 2018-08-06SQL Server 2008 R2 setup crashes and closes while installing support files. Formatting and installing it before .NET did not help.
1. Stop using the repacked or modified installer you downloaded. 2. Download the SQL Server installer directly from Microsoft (a forum moderator linked the official download). 3. Run that...
✓ Confirmed by the topic starterTuServerMU · 2017-09-17MuEmu S4: the server and MuMaker do not see the databases on SQL Server 2008 R2 even with remote connections and TCP/IP enabled.
1. Check how SQL Server was installed: it had been set up as a named instance. 2. The files and MuMaker expect the default instance, reached as (local) or the PC name. 3. Reinstall SQL Se...
✓ Confirmed by the topic starterTuServerMU · 2017-11-11MuEmu S6 DataServer and JoinServer show "Could not connect to database" on SQL 2008 R2 even after renaming MuOnlineS6 to MuOnline. What fixed it?
1. In the DataServer and JoinServer config files make sure the database name is the one you restored (MuOnline, not MuOnlineS6). 2. Delete the old or duplicate MuOnline DSNs and create th...
✓ Confirmed by the topic starterTuServerMU · 2018-06-06WebEngine CMS installer: "Could not connect to database (1)" at the database step with MSSQL Server 2008 (PDO ODBC, XAMPP)
1. In this case the game files connected fine but the WebEngine installer kept failing on the database step, with no error in the SQL logs or the Windows event log. 2. The cause was a con...
✓ Confirmed by the topic starterRaGEZONE · 2023-10-06WebEngine CMS install keeps saying 'Could not connect to database (1)' with SQL Server 2008 and XAMPP (PDO ODBC), even though SSMS connects fine.
1. The thread found a conflict between SQL Server 2008 and WebEngine's connection. 2. Install a newer SQL Server (2012 worked for the topic starter; another user had 2019 working). 3. Res...
✓ Confirmed by the topic starterRaGEZONE · 2023-10-06



