Troubleshooting Logging and Reporting

My Reporting Client Cannot Connect to the SQL Server

No Network Connection

The machine running the Reporting client may not have a connection to the SQL server. To see if this is the case:
  1. On your machine running Reporting, open the Windows start menu and type cmd.
  2. Open the Command Prompt.
  3. Type this command, replacing SERVERNAME with your SQL server address: ping SERVERNAME.
  4. Press Enter.
  5. If the response received is Request timed out for the ping attempts, you are unable to connect to the SQL server.

Contact your SQL server administrator to ensure you are properly connected to the network for the SQL server.

Incorrect Database Server Name

If you are not managing the SQL server, contact your SQL server administrator confirm the database server and (if required) instance name. If you are managing the SQL server, you can find this information by completing these steps:

  1. Open SQL Server Configuration Manager on your SQL server.
  2. Click SQL Server Services.
  3. In the object browser, double-click SQL Server.

  4. In the Service tab, the Host Name will be the address for your server. The name will have the instance name in brackets.
  5. In the Reporting application, go to File > Options and check your Server is set using the proper database server and instance name.

Incorrect Login Information

Contact your SQL server administrator for the login information. To enter the login information into Reporting, go to File > Options in the Reporting client. If the Windows user you are currently logged in as is to be used for the connection, check Trusted Connection. Otherwise, uncheck this option and enter in the Username and Password of the SQL user to log in as.

The Reporting Application is Unable to Generate Reports

MSMQ is not Installed

You must ensure Microsoft Message Queue (MSMQ) is installed on your Logging server and workstations which are using Reporting. To see if MSMQ is on your machine, open Services and search for the Message Queuing service. If it is not available, it will need to be installed.

You can see how to install MSMQ for your machine here.

The MSMQ is Full

In the event the Microsoft Message Queue (MSMQ) becomes full, messages are no longer sent for logging. When the MSMQ fills up on a Workstation, this is normally due to an issue with the Workstation connection to the logging server. If this occurs on the logging server, this indicates an issue with the connection from the logging service to the SQL database. To check if this is your issue:

  1. Open Computer Management.
  2. Go to Services and Applications > Message Queuing > System Queues.

  3. Select Transactional Dead-letter messages to view the queue. If the queue appears to be full, complete the remaining steps. Otherwise stop here.
    Note: The below steps will delete any log entries created prior to purging the MSMQ.
  4. Right-click Transactional Dead-letter messages and click All Tasks > Purge.

  5. When prompted to confirm the deletion of queued messages, click Yes.
  6. In Windows, open Services.
  7. Right-click the Message Queuing service and click Restart.

MSMQ is Corrupt

To determine if your MSMQ is corrupt, in Windows open Event Viewer. You may see the below error messages for IPFusion Logging:
  • MessageQueueWriter - ChannelFactory stop failed with error: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
  • An error occurred while sending to the queue: Unrecognized error - 1072824281 (0x00e0027).Ensure that MSMQ is installed and running. If you are sending to a local queue, ensure the queue exists with the required access mode and authentication.

In the event your MSMQ becomes corrupt, you will need to re-enable it in Windows. Complete the below steps for all Runtime Workstations, then the Logging server:

  1. Go to the Windows Start Menu.
  2. Search Turn Windows Features On or Off and press Enter.
  3. Uncheck Microsoft Message Queue (MSMQ) Server.
  4. Click OK and restart the machine.
  5. Go to the Windows Start Menu again.
  6. Search Turn Windows Features On or Off and press Enter.
  7. Check Microsoft Message Queue (MSMQ) Server, then expand it and ensure Microsoft Message Queue (MSMQ) Server Core is checked as well.
  8. Start Runtime.
  9. In the Windows Start Menu, search Computer Management and press Enter.
  10. Go to Services and Applications > Message Queuing > System Queues > Transactional dead-letter messages and check if there are messages in the queue.

If you are able to see messages in your queue, the MSMQ is working properly again.

Receiving "The system cannot find the file specified" Message While Generating a Report

The Reporting client has lost connection to the database during the report generation. Ensure you have a connection to the database, then try generating the report again.