I receive a message that Mamut cannot contact the server on a single-user installation
article ID: 2024463
When opening Mamut I receive a message stating that there is no contact with the SQL Server even when Mamut and the SQL Server have been installed on the same machine.
This is caused due to either the SQL service not starting, or Mamut not being allowed to contact the SQL server.
Reason 1: Mamut.ini cannot be edited or is missing information
A new installation of Mamut will create mamut.ini if it's missing. Sometimes the permissions on the file does not allow it to be edited when Mamut launches and tries to connect to the server.
The solution is to delete the file and start Mamut again.
In Windows XP the file is located under C:\Documents and settings\All users\Public Mamut\Mamut.
In Windows 7, Vista and Windows Server 2008 the file is located under C:\Users\Public\Public Mamut\Mamut.
Reason 2: Mamut is not allowed to contact the SQL Server
This is usually caused by Mamut being blocked by a firewall. Go into the firewall settings on the machine and check that mamut.exe and mdatatools.exe files have full access to the Internet. Turn off the firewall and test.
Reason 3: The SQL service failed to start because of the firewall
There may be slightly different reasons for this, but often the firewall blocks access to network protocols.
Go into the firewall settings on the machine and make sure that the sqlservr.exe file has full access.
Reason 4: Mamut cannot find the local SQL Server on a single-user installation
This can occur if there are problems with the network setup in Windows or the computer name in Windows has been changed.
1. Start Windows and browse to C:\Documents and Settings\All Users\Public Mamut\Mamut. In Vista, Windows 7 and Windows Server 2008 the path is C:\Users\Public\Public Mamut\Mamut.
2. Open Mamut.ini and add the line Server=(local) If you have a line with Server=, edit this to point to (local)
3. Close and save Mamut.ini.
Reason 5: The SQL service cannot use the network protocols in Windows.
This can occur if the firewall/antivirus is blocking access to network protocols or there is something wrong with them. If Mamut is only running on one machine, then you can set SQL Server to not use the network.
Follow these steps:
1. Go to Start - Programs - Microsoft SQL Server 2005/2008 R2/2012 - Configuration Tools - SQL Server Configuration Manager.
2. In the window, expand the group SQL Server Network Configuration.
3. Click on Protocols for MAMUT.
4. In right window check that Shared Memory, Named Pipes and TCP/IP are enabled and that VIA is disabled.
5. Right click on TCP/IP, and select Disable.
6. Right click on Named Pipes, and select Disable.
7. Click on SQL Server Services.
8. Right click on SQL Server (MAMUT), and select Start or Restart.
9. Start Windows and browse to C:\Documents and Settings\All Users\Public Mamut\Mamut. In Vista, Windows 7 and Windows Server 2008 the path is C:\Users\Public\Public Mamut\Mamut.
10. Open Mamut.ini and add the line Server=(local)
If you have a line with Server=, edit this to point to (local)
11. Close and save Mamut.ini.
The SQL Server (MAMUT) will now start and Mamut will run.
Query words: contact SQL, connection