1. Verify the SQL Server custom ports value through the SQL Server Configuration Manager.

   By default, SQL Server listens on port 1433, which is also the default communication port for Tealeaf, unless selected differently during installation.

2. If your SQL Server implementation uses dynamic ports, you must sync your Tealeaf solution with them.
3. Verify that the SQL network protocols are enabled through the SQL Configuration Manager.

   By default, SQL Server does not enable TCP and Named Pipes, which are used by Tealeaf.

In rare cases, you might change the size of the model database size in your SQL Server installation from the default value of 50MB. SQL Server Management Studio does not allow databases to be installed below the model database size. For example, if the model database size is set to 250MB, when the Database Manager attempts to install the databases, the installation fails because it is smaller than this minimum limit.

The solution is to do one of the following:

• Reconfigure the model database size in SQL Server Management Studio to 50MB. For more information, consult the documentation that was provided with your SQL Server product.
• Reconfigure the database sizes in Database Manager to be slightly larger than the model database size in SQL Server Management Studio. For the above example, you could set the database size to 260MB.
  Note: Database sizes must be configured through individual file groups for each database.

When the SQL Server starts, a dynamic port is selected. This port is used during operations. During restart, the configured port remains, unless a conflict emerges.

If the ports must remain dynamic, complete the following steps.

1. Start all Tealeaf services.
2. Start the database.
3. Through SQL Server Management Studio, locate the port that the SQL Server uses.

   This port must be populated for each database in the Connection dialog of the Database Manager.

4. In the Database Manager, set the ports for the databases.
   1. From the TDM menu, select Mode > Info/Config > Report Server Configuration.
   2. Populate the ports accordingly. When changes are applied, the registry keys are updated for you.

   On the Report Server, database port numbers are in the following registry keys. You can update these through the Database Manager Connecting screen.

   Product (Database)	Registry Key
   cxImpact (Reports)	Tealeaf Technology > DataStore > Report Server > Port
   cxReveal (Search)	Tealeaf Technology > DataStore > Database > Search > Database Port

   Note: If the SQL Server is forced to choose a new dynamic port, then the new port must be used whenever you access the databases through the Connecting screen in the Database Manager and repopulated in the appropriate registry key through the Database Manager using the above steps.
5. Through the Database Manager, install or upgrade the databases as necessary.

Restore failed for Server <MyServer>

Additional information:System.Data.SqlClient.SqlError: File: 
'C:\Program Files\Microsoft SQL Server\
MSSQL10_50.MSSQLSERVER\MSSQL\DATA\RL_REPORTS.mdf' is claimed by 'DATA'(3) and
'PRIMARY'(1). The WITH MOVE clause can be used to relocate one or more files. 
(Microsoft.SqlServer.Smo)

The above issue is caused by the SQL Server restore procedure that converts all of the Tealeaf database names to RL_REPORT.mdf. This situation is typically caused when the new location has a different directory structure or when the databases are moved to a new version of SQL Server.

The solution is to manually append the file name of each data file to include the Filegroup identifier for the file to the end of the file name.

See the Microsoft Support site for information about the Warning SuperSocket Info warning message.

This message is not an error message. This text is only a warning that SQL Server was not able to register a Service Principal Name (SPN), which indicates that the security mechanism used is Microsoft Windows NT Challenge\Response (NTLM) authentication instead of Kerberos.

CAUSE

The message usually appears because the SQL Server service account is running as a domain user who does not have requisite permissions to register SPNs.

SQL Server blocked access to procedure 'sys.sp_OAGetProperty' of component 
'Ole Automation Procedures' because this component is turned off as part of 
the security configuration for this server. A system administrator can 
enable the use of 'Ole Automation Procedures' by using sp_configure. 
For more information about enabling 'Ole Automation Procedures', 
see "Surface Area Configuration" in SQL Server Books Online.

sys.sp_OAGetProperty is an automation procedure that allows access to system details. Tealeaf uses this stored procedure to acquire details on disk space.

The error message is harmless. However, to avoid confusion, you might want to deny access to pr_ServerDiskSpace, which uses this stored procedure. When access is denied, error messages are reported from pr_ServerDiskSpace, instead of sys.sp_OAGetProperty. Error messages from the latter procedure may suggest possible hacks or malicious software, so unnecessary messages should be suppressed.

To deny access, run the following through SQL Server Management Studio:

use TL_STATISTICS
go
Deny execute on pr_ServerDiskSpace to TLAdmin;
Deny execute on pr_ServerDiskSpace to TLUser;

use TL_visreport
go
Deny execute on pr_ServerDiskSpace to TLAdmin;
Deny execute on pr_ServerDiskSpace to TLUser