Community AlphaAlpha MUADMINS
DEDeutsch
Anmelden
Auf MuADMINSConfig ScannerZip deiner Dateien hochladen: Rates, Drops, Spots, LimitsÖffnenAuf MuADMINSTriff uns auf DiscordFrag nach Hilfe, zeig, woran du arbeitest, und sprich mit anderen Serverbetreibern über MU.Öffnen

MuADMINS

Lösungen

Kurze Fixes für häufige Probleme mit Server, Client und Website bei MU Online, jeweils mit Quelle und Datum. “Bestätigt” heißt: Die Person, die gefragt hat, hat gesagt, dass der Fix funktioniert hat.

98 Lösungen für “couldn't connect to sql server” · Zurücksetzen

  1. Website

    Website error "Fatal error: Call to undefined function mssql_connect()" (XAMPP 1.7.7, SQL Server 2008, DarksWeb 0.3)

    New XAMPP builds no longer have the mssql_* functions these old sites use. 1. Install XAMPP 1.7.1 (said to be the last one with mssql_*), or add code that defines those functions to the s...

    ✓ Vom Threadersteller bestätigtDarksTeam · 2019-02-07
  2. ToolsWebZen 97d / 99b97d

    MuEditor 2.1 / MuMaker: 'SQL Connection failed' with a 97d+99i server, even when run as administrator

    1. Running the editor as administrator did not help. 2. The editors connect through the ODBC data sources of the server (MuOnline, MuOnlineJoinDB and so on), so these must be registered c...

    ✓ Vom Threadersteller bestätigtDarksTeam · 2016-05-07
  3. ToolsMuEmu / Louis

    MuEditor and MuEditorDeCuenta (account editor) cannot connect to SQL Server on the VPS, both show connection errors at start

    1. Configure both editors with the IP of your VPS, the SQL user sa and its password. 2. Open the SQL Server port (1433 unless you changed it) in the Windows Firewall of the VPS. 3. In SQL...

    ✓ Vom Threadersteller bestätigtCreandoMU · 2023-01-01
  4. ToolsAndere FilesS6

    BeastMaker admin tool: how to set up the SQL connection and the allowed user (and SQL 2000 without "Edit Top 200 Rows")

    1. Run the table script from the release post to create the BeastMaker table (columns BeastMaker_Allowed, BeastMaker_Logs) in the MuOnline database. 2. Add your allowed entry {"YOURNAME":...

    Neufassung der Quelle durch MuADMINSNot verifiedRaGEZONE · 2015-07-14
  5. Tools

    MuMaker: "Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection."

    1. The error means SQL Server only accepts Windows logins, so the sa login that MuMaker uses is refused. 2. Change the SQL Server authentication to SQL Server and Windows Authentication m...

    ✓ Vom Threadersteller bestätigtRaGEZONE · 2008-01-29
  6. Server-Setup0.97d

    97d GameServer on a VPS says 'Failed to connect to SQL Server' although the SQL login, the MuOnline database and the IPs look correct

    The database and the SQL settings were fine; the IP passed to GameServer.exe in its shortcut was the problem. 1. Right-click the GameServer.exe shortcut you start the server with and open...

    ✓ Vom Threadersteller bestätigtTUServerMU · 2021-02-08
  7. ToolsS6

    WebEngine 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...

    ✓ Vom Threadersteller bestätigtRaGEZONE · 2023-10-06
  8. Tools

    Titan Editor: cannot connect to the MU database to create accounts (single MuOnline database)

    1. Open the Titan Editor config. With only one database (MuOnline) both ODBC names point to it: [Connection] ODBC=MuOnline, ODBC_Me=MuOnline, User=sa, Password=yourpass, SQLServer=(local)...

    ✓ Vom Threadersteller bestätigtRaGEZONE · 2013-09-25
  9. Websiteany

    WebEngine 1.0.9 with a remote SQL Server IP fails with 'Could not connect to database (1)', while MuCore connects to the same server without problems.

    1. In the WebEngine installer select the ODBC driver instead of dblib/sqlsrv. 2. Make sure the matching PHP ODBC extension is enabled and port 1433 is reachable. 3. Finish the install.

    ✓ Vom Threadersteller bestätigtRaGEZONE · 2017-09-09
  10. WebsiteS6

    WebEngine 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...

    ✓ Vom Threadersteller bestätigtRaGEZONE · 2023-10-06
  11. WebsiteSeason 6

    WebEngine on web hosting says "Could not connect to database (1)"

    Shared web hosting often blocks outgoing connections to port 1433, the default SQL Server port, so the website cannot reach the database on your VPS even when tools on your own PC can. 1....

    ✓ Vom Threadersteller bestätigtTUServerMU · 2021-02-07
  12. Server-Setup

    JoinServer and DataServer cannot connect to the database although the backup is restored

    These files had the database name MuOnlineS6 in the server configs while the database was restored as MuOnline, so the servers looked for a database that does not exist. 1. In SQL Server...

    ✓ Vom Threadersteller bestätigtTUServerMU · 2018-09-27
  13. Server-SetupIGCNS9

    IGCN S9 E2 repack: DataServer says 'Login failed for user ...' (SQLSTATE 28000) and 'DATA SERVER CANNOT CONNECT TO MSSQL'

    1. The repack DataServer config came with a SQL login that does not exist on your SQL Server (here a random name like D2a78Rtko0), so the login fails. 2. Open the database settings of the...

    ✓ Vom Threadersteller bestätigtRaGEZONE · 2019-07-14
  14. Websiteany

    WebEngine CMS on a web host cannot reach the SQL Server on a VPS: 'Could not connect to database (1)', even after opening port 1433 in the firewall and enabling TCP/IP.

    1. Check the usual items first: inbound rule for TCP 1433 in Windows Defender Firewall on the VPS, TCP/IP enabled in SQL Server Configuration Manager. 2. If it still fails, test whether t...

    ✓ Vom Threadersteller bestätigtRaGEZONE · 2025-02-12
  15. Website

    What does the DmN CMS setup change in the MU database (columns, Character.id, WZ_CONNECT_MEMB) and what can break?

    The DmN CMS 1.2.3 setup does more than create its own tables: 1. It ALTERs the game databases: adds columns from its version files, for example MEMB_INFO Admin, last_login, activated, act...

    Not verifiedVon MuADMINS geschrieben
  16. Server-SetupMSProS2, S3, S6

    What are the MSPro database settings (ODBC, MD5Encryption, DisconnectOnlineAccount) and the update queries?

    MSPro files connect through the ODBC DSN named MuOnline: - JoinServer\JoinServer.ini: JoinServerODBC = MuOnline, CaseSensitive = 0, MD5Encryption = 0, MaxIPLimit = 0, MaxHwIDLimit = 0, Di...

    Not verifiedVon MuADMINS geschrieben
  17. Tools

    MuCore install: "Connection with MuOnline Database Failed" and "Extension php_mssql.dll must be enabled"

    1. MuCore needs a PHP that still has the old php_mssql.dll extension: in php.ini find extension=php_mssql.dll and remove the ; in front of it. 2. If your web server package has no php_mss...

    ✓ Vom Threadersteller bestätigtRaGEZONE · 2011-03-05
  18. Tools

    MuCore 1.08 installer: with the MSSQL connection it cannot get past step 3 (MSSQL 2008 R2, XAMPP 1.7.1)

    1. Use XAMPP 1.7.7 for MuCore 1.08 (XAMPP 1.7.1 with MSSQL 2008 works badly). 2. Install the client DLL that supports your MSSQL version (linked in the reply). 3. Open C:/xampp/php/php.in...

    ✓ Vom Threadersteller bestätigtRaGEZONE · 2016-05-26
  19. ToolsOpenMUS6E3

    OpenMU admin panel: the Setup page says 'Can't connect to the database, probably not created yet' or 'Update required'

    1. Open Setup (/setup). It shows the state of the database. 2. *Can't connect to the database, probably not created yet* or *Not created*: click Create, pick the game version (Season 6 Ep...

    Neufassung der Quelle durch MuADMINSNot verifiedGitHub (MUnique/OpenMU) · 2026-10-26
  20. Tools

    MuMaker 1.13: "Format of the initialization string does not conform to specification starting at index 30" when connecting to SQL

    1. Check that SQL Server has TCP/IP enabled on port 1433 and that port 1433 is allowed in the Windows firewall; check the ODBC source and the MuMaker config. 2. Make sure .NET Framework 3...

    ✓ Vom Threadersteller bestätigtRaGEZONE · 2025-04-30
Kommst du immer noch nicht weiter? Frag den MU-Assistenten MuGPS durchsuchen Auf MUTube suchen

MuADMINS Community Alpha: kostenlos, von der Community gemacht, in aktiver Entwicklung.