Sunday, June 13, 2010

SQL 2000 to SQL 2008 Upgrade

This time I had faced very strange issue. Setup closed automatically with out any waring or error after setup support file installation. There is no error in event log and setup boot strap folder. I had tried SP1 slipstream but setup throws different error.

So, I had upgraded SQL 2000 to 2005 without any issues and was trying to upgrade SQL 2005 to 2008 but setup closed once support file installation completed.

Setup closed after setup support file so I had installed setup support file from SP1. First we need to extract setup file using below statement.

Extract Command
SQLServer2008SP1-KB968369-x86-ENU.exe /x:T:\SP1

Once extracted, just run support setup file which is located in below mentioned path.


Now setup moved to next step. But middle of the setup I got below error.


The specified local group already exists. (Exception from HRESULT:0x80070563)
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

I just pressed 'Cancel' and continue the setup but setup finished incompletely. I had tried setup repair option but same error.

What is the issue?. Setup was trying to re create the local Windows SQL related groups but failed. I removed below mentioned groups in Windows group.


Restarted the repair activity, now I got the error "No mapping between account names and security IDs was done". Setup was trying to map previously created Local groups to SQL server but failed. Pressed 'Cancel' button and continue the setup. Few times, the error was appeared. Finally upgrade completed successfully. Windows local groups were created automatically.

Friday, June 11, 2010

SSIS Package Issues in SQL 2008

After SQL 2000 to SQL 2008 upgrade in cluster environment, SSIS service didnt install automatically. Upgrade wont install SSIS package while upgrade. It should be installed manually on both node manually. Install standalone SSIS service on both node and set auto start.

As per Microsoft recommendation, SSIS service should not be in cluster resource but we can add resource.

After installation, i had faced the below issues.

Issue 1

failed to retrieve data for this request.

After installation, i had faced issues while trying to connect the SSIS package in cluster environment.

By default, SSIS package is always trying to connect the default instance in the node. I had cluster environment so we need to modify configuration file in SSIS package configuration file.

you may also get below errors

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

The SQL Server specified in Integration Services 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 SQL Server 2008 Books Online.

Login Timeout Expired

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2008, 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]. (MsDtsSvr).


1. Navigate this location \Program Files\Microsoft SQL Server\100\DTS\Binn\
2. Edit MsDtsSrvr.ini.xml in notepad and change server name "." to Cluster name.

< xsd="" xsi="">
<>true < /stopexecutingpackagesonshutdown>
< type="SqlServerFolder">
<>MSDB < /name>
<>ServerName\InstanceName < /servername>
< /folder>
< type="FileSystemFolder">
<>File System < /name>
<>..\Packages < /storepath>
< /folder>
< /toplevelfolders>
< /dtsserviceconfiguration>

3. Save XML file and restart SSIS service

Issue 2
"Connect to SSIS Service on machine failed: Access is denied"

While trying to connect the SSIS package from client machine. I can able to connect the SSIS service in node.

We need to add below steps in Local group policy and windows component service.

1. Add users in Distributed COM local windows Users group
2. Start -> Run -> %windir%\system32\Com\comexp.msc to launch Component Services
or program files -> Administrative tools -> Component Services
3. Expend Component Services\Computers\My Computer\DCOM Config
4. Right click on MsDtsServer node and select properties
5. Navigate Security page menu
6. Click Edit button in “Launch and Activation Permissions” section.
7. Add users and provide all permissions. Press ok to complete.
8. Click Edit button on “Launch Permissions” section
9. Add users and provide all permissions. Press ok to complete.
10. Restart SSIS Service

Wednesday, June 2, 2010

Cluster service failed to start local system account

After windows cluster, the windows cluster service failed to start. Error indicate that cluster service didnt strat on local system account.
Error Message

Could not start the Cluster Service service on Local Computer.
Error 1314: A required privilege is not held by the client.

Solution If we want to run cluster service under domain account or local admin group, service account should be added in below locations.

Open Local Security Policy on Administrator group and configure below locations.

Local Security Policy\Security Settings\Local Policies\User Rights Assignment

* Act as part of the operating system
* Adjust memory quotas for a process
* Back up files and directories
* Increase scheduling priorities
* Log on as a service
* Restore files and directories
* Debug programs
* Impersonate a client after authentication
* Manage auditing and security log

This solution is applicable for windows 2003 server. Refer other version on below link;en-us;Q269229