TITLE: Microsoft SQL Server Management Studio
——————————

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

——————————
ADDITIONAL INFORMATION:

The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic “Configuring the Integration Services Service” in Server 2005 Books Online.

Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)

——————————

Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)

Check the following,

1. Launch SQL Server Configuration Manager
2. Check that the SQL Server Integrated Services is running and that the Log On As account is an Active Directory account with correct permissions.
3. Under SQL Server 2005 Network Configuration make sure Names Pipes is enabled for the SQL instance.

If you have multiple instance then you may need to change the MsDtsSrvr.ini.xml to state the default instance.

The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\ServiceConfigFile specifies the location and name for the configuration file that Integration Services service uses. The default value of the registry key is C:\Program Files\Microsoft SQL Server\90\DTS\Binn\ MsDtsSrvr.ini.xml. You can update the value of the registry key to use a different name and location for the configuration file.

In the configuration file, go to . and replace the . with ServerName\InstanceName

Now secondly if you are using the @query parameter then you need to make sure that you specify the database where you would like the query to run. You can do this by using the @execute_query_database parameter. If you do not do this then you will receive an invalid object name error.

Example:

EXEC msdb.dbo.sp_send_dbmail
@recipients = ‘youremail@domain.com‘,
@subject = ‘Subject‘,
@profile_name = ‘DBMail Profile Account Name‘,
@query = ‘your query‘
@execute_query_database = ‘database you would like to query‘,
@body = ‘your message here or you can leave out if you don’t want anything other then the query in the body‘,
@attach_query_result_as_file = 0 or 1;

Another thing to remember is if you want the query result to be displayed in the body and not as a file attachement then make sure you use the @attach_query_result_as_file parameter and set the value to 0. If you would like to send it as a file attachment then you will need to set the value as 1.

1. Check the Event Log on the Citrix Server
   You should see the following error under the System Log – This computer running MetaFrame Presentation Server will now stop accepting connections. This server is no longer in or could not enter a licensing grace period.
2. Now check the Event Log on your licensing Server
   You should see the following error under the Application Log Error: 9002, Severity: 17, State: 6
   The log file for database ‘CITRIX’ is full. Back up the transaction log for the database to free up some log space.
3. If you do not see the following errors then please visit http://support.citrix.com/article/CTX112408
4. If you do see the errors in your Event Log then you must truncate the inactive transactions in your transaction log and shrink the Citrix transaction log file. The easiest way to do this is to firstly backup your Citrix database log file and then run the following query.
   
   DBCC SHRINKFILE(CITRIX_log, 10)

NOTE: If you get the following message when starting a New Query DB is in single-user mode and there’s already someone connected to the DB.  Then make sure that you have disconnected from the object explorer before clicking on New Query.  So when you first launch SQL Server Management Studio, click cancel when it asks you to Connect to Server.  Then click on New Query, this will ensure that you have not logged on twice in single user mode.

The other error message is “Cannot detach an opened database when the server is in minimally configured mode” when trying to sp_detach_db ‘model’.  Best solution is to launch SQL Server Configuration Manager.  Click on SQL Server 2005 Services.  On the right pane, stop every service except the SQL Server (instance_name).  Also disable the network adapter if you still are getting the error message after stopping all services.

To begin you will need to make sure that you have the following software packages, StoreVault Manager 3.2, SnapDrive 5.0 and SnapManager for SQL 2.11.  If you do not have these packages you can download them from Storevault Support.  Once you have obtained the necessary packages do the following.

NOTE:  You will need to install all packages on the SQL Server that you would like to backup.

1. Install StoreVault Manager 3.2
2. Install SnapDrive 5.0. You may need to install the Windows 2003 Server Hotfix KB931300 – Snapshot volumes do not mount successfully or the volume dismount operation reports an error when you use a Network Appliance storage device with the Windows Server 2003 Virtual Disk Service.Click here to download x64 Version
   Click here to download x86 Version
3. Install SnapManager for SQL 2.11
4. Install ISCSI Software Initiator.  You can download ISCSI Software Initiator from here if you do not have a copy.  Once you have installed the ISCSI Initiator make sure you launch the application and add the ISCSI target and obtain the ISCSI Name, eg. qn.1998-01.com.vmware:vmwareserver01-69g33239.
5. Now launch StoreVault Manager and Log onto the SAN that you would like to create the LUN’s on.
6. Click Create LUN (SAN) and go through the Create LUN Wizard.  Make sure you select MS SQL Database as the LUN Application Type as shown below.
   
   
7. You will also need to add the ISCSI Name of the host and StoreVault will automatically attach the LUN to the host.  Once you complete the Wizard, the LUN will appear under My Computer.
8. Launch SnapManager and follow the Wizard.
9. You will need to migrate all your databases to the newly created LUN’s.  Best practise is to have a seperate LUN for your Databases, Logs and SnapInfo.  Databases that are stored on local disk will not be able to be backed up using SnapManager for SQL.