Mamut Business Software cannot connect to the server

article ID: 2023494 

 

 

When trying to connect to Mamut Business Software you will not get an immediate response. After a short while, a message will appear stating that Mamut cannot connect to the SQL-Server. The reason may be that the SQL-Server has not been started or that you computer does not have access to it.

--------------------------------------------------------------------------------

Check the following:

1. On the client, check that Mamut is trying to connect to the correct server

Open Mamut.ini on the client.

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.
Check that the line Server= points to the correct server name. This can be found on the server by right clicking on Computer and selecting Properties. It is either directly under Properties or under Computer Name.

If server name is blank, delete Mamut.ini and start Mamut again. This will generate a new file with correct information.

2. Check that the client and server are connected to the same local network in the same workgroup or domain

This can be found on the server by right clicking on Computer and selecting Properties. It is either directly under Properties or under Computer Name.

--------------------------------------------------------------------------------

3. Check the SQL Server

Do the following on the Server computer:

 

Check that the SQL-service is running

1. Go to Start – Programs – Microsoft SQL Server 2005/2008 - Configuration tools - SQL Server Configuration Manager.

2. Select SQL Server Services.

3. Find SQL Server (MAMUT). (If you have not chosen Mamut as an instance, when installing the program, you will find another instance name written in the brackets).

4. Right click on SQL Server (MAMUT) and click Start/Restart.

5. Right click on SQL Browser and click Start/Restart.


Check that the SQL-service has network protocols activated
1. Go to Start – Programs – Microsoft SQL Server 2005/2008 - Configuration tools - SQL Server Configuration Manager.

2. Expand SQL Server Network Configuration and select Protocols for MAMUT.

3. Check that the protocols TCP/IP and Named Pipes are Enabled. If not, right click and select Enable.

4. If a protocol was enabled, restart the SQL-service as described above.

--------------------------------------------------------------------------------

4. Check the firewall

If you use Windows Firewall, you will be able to find it within the Control Panel. If you use a different firewall you need to consult its documentation on how to allow programs through.

A simple test to see if the firewall is at fault is to disable it completely and test Mamut on a client.

The following settings should be available with full permissions on the server:
• Port with the name SQL and the number 1433

• The program sqlservr.exe that is usually installed on the path C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.MAMUT\MSSQL\Binn

• The program sqlbrowser.exe that is usually installed on the path C:\Program Files(x86)\Microsoft SQL Server\90\Shared\

 

The following settings should be available with full permissions on the client

1. Go to the Firewall on the computer. (If you use Windows Firewall go to Start – Control Panel – Windows Firewall. For other Firewalls, follow the instructions in this article 2023477).

2. Add the File Mamut.exe with full permission to the network and to the Internet.

--------------------------------------------------------------------------------

5. Add the Windows user as SQL-administrator on the server

See this article for SQL 2008 and SQL 2012.

--------------------------------------------------------------------------------


6. Test the connection to the SQL-server with ODBC


--------------------------------------------------------------------------------


7. Check the resolve of server name to IP-address

If connection with ODBC fails, check that the server name resolves to the correct IP-address on the client.

Here is how to check it:
1. On the server, click on Start or Start - Run.
2. Type in CMD and press Enter.
3. In the command prompt that opens, type in: IPCONFIG and press Enter.
4. Make a note of the IP-address for the server.
5. On the client, click on Start or Start - Run.
6. Type in CMD and press Enter.
7. In the command prompt that opens, type in: PING <name on the server> and press Enter.
8. Compare the IP-address displayed (what the client thinks it is) to the address noted in step 4  above (what the server knows it is).

If the client and the server shows different IP-address there is a problem with resolving IP-addresses on the network and this must be solved by the network administrator.

 


Query words: server, SQL, connect, connection to server