This article applies to:
- Marshal Reporting Console
Question:
- How to troubleshoot and fix connectivity issues with MRC and the WebMarshal or MailMarshal database located on another SQL Server
Procedure:
To ensure MRC can connect successfully to your SQL server hosting your MailMarshal or WebMarshal database, you must ensure certain settings are in place on the SQL Server. These are the basic settings that allow MRC to interact with the remote database.
- Check and confirm name resolution and network connectivity between the MRC server and the MailMarshal or WebMarshal SQL server.
- On the MailMarshal or WebMarshal SQL Server, open the SQL Server Configuration Manager.
- Ensure that the TCP/IP protocol is enabled. Verify the port where SQL Server is listening - by default it is port 1433.
- Ensure that the SQL Server Browser service is running.
- After making any changes and before closing SQL Server Configuration Manager, restart the SQL Server Service.
For detailed guidance on the above steps, see article Q11018. The information in this article applies to both MailMarshal and WebMarshal.
Check that you have entered the correct server and instance information for the database in MRC.
- A typical entry for server\instance would be similar to MailMarshalserver01\SQLEXPRESS
Additional step for WebMarshal
Verify that the WebMarshal SQL Server is set to Mixed Mode (SQL authentication and Windows Authentication). (By default the SQL Express instance created by some versions of WebMarshal does not include SQL Authentication.)
- For more information about how to perform this procedure see article Q10142.
- To complete these instructions you will need to connect using SQL Management Studio. You may be able to connect to the WebMarshal SQL server using the installation of SQL Management Studio that is installed with MRC (as part of SQL Express Advanced). You can also download SQL Management Studio Express from Microsoft.
Notes:
For further troubleshooting, see the following articles from Microsoft:
For advanced troubleshooting with SQL, see also: Microsoft KB 328306