It is likely your choice of folders and how you are redirecting ''everything'' to ''D:Home2''.
When you install QC, it has 2 major steps: 1) Load the Platform (files and ''base'' application files, 2) Configure the installation with the Configuration Wizard.

The first step of installation just copies generic QC11.52 files to the C: application install folder:

*Default = ''C:Program FilesHPHP Application Lifecycle Management 11.52''*

Sometimes people choose to redirect this install to :

*''D:Program FilesHPHP Application Lifecycle Management 11.52''*

The Configuration Wizard then allows you to set the Deploy and Repository path or take defaults, then based on various answers/settings, it repackages the ''application'' with your local settings and ''deploys'' it to the Deployment folder.

Normally we just take all defaults:

*Default Deploy folder = 'C:ProgramDataHPALMwebappsqcbin'
Repository: 'C:ProgramDataHPALMrepositoryqc'*

To avoid utter confusion and issues like you are having, we recommend simple changes like changing c: to d: for Deploy or Repository folder.

Example

*Install: ''D:Program FilesHPHP Application Lifecycle Management 11.52''*

*Deploy: 'D:ProgramDataHPALMwebappsqcbin'*

*Repository: 'D:ProgramDataHPALMrepositoryqc'*

In your case, you could add another ''layer'' to the path (but it might make your paths a little confusing) for example:

*Install: ''D:Home2Program FilesHPHP Application Lifecycle Management 11.52''*

*Deploy: 'D:Home2ProgramDataHPALMwebappsqcbin'*

*Repository: 'D:Home2ProgramDataHPALMrepositoryqc'*

This will make things much easier to find if a support ticket is needed later.

Make sure your user that is using the service is the same as the user currently logged in (windows acct) and that they have R/W rights over C: and D: (and below), and that there is ample disk space on D: (in our example).

Paul