Location of a list of errors that occur during installation of IBM Rational DOORS and HP Quality Center Integration

Usually problems are seen during installation and configuration of IBM Rational DOORS - HP Quality Center Integration primarily due to access restrictions and security policies that are set on the system. Therefore, you should perform the installation when logged into the system as Local Administrator and not just a user with administrative privileges.

The following is a list of errors that might appear during the installation.

Table of Contents

Errors while running Set Access Permission

This ACL is not in canonical form and therefore cannot be modified while running Set access permission wizard

Error 401 while testing services (SOQ and TDI Services) and Error 404 while testing services

No disk space error even though the destination install directory has enough space

IBM Rational DOORS for HP Quality Center Interface Synchronization timer in Service Manager cannot be started

Error while performing Test connection with DOORS and or Quality Center Integration

Error while creating data connection for DOORS or while testing connection for DOORS - Data provider failed to initialize or QC – Data provider failed to initialize

Errors while installing IAS Admin

Error: Access is denied when trying to access http://servername/AdminToolInstall from any client machine to Integration server.

Error: Unable to login to IAS Admin

---

 

Errors while running Set Access Permission

Error: This ACL is not in canonical form and therefore cannot be modified while running Set access permission wizard

The error message appears as shown below while setting registry permission:


--- Configuring Account Start ---
Using Existing User
Username: 'DOORSQA\IWSUSER'
Adding 'DOORSQA\IWSUSER' to local alias 'IIS_WPG'
Success
Granting 'DOORSQA\IWSUSER' batch logon right
Success
Granting 'DOORSQA\IWSUSER' interactive logon right
Success
--- Configuring Account End ---
--- Configuring Registry Permissions ---
Unable to set permission on SOFTWARE\Classes\CLSID\{31C7DE11-80E2-45F3-98EB-036EE69C862B}:System.InvalidOperationException: This access control list is not in canonical form and therefore cannot be modified.propagationFlags)

Steps to resolve:

1. Ensure that you are installing the integration server on Windows 2003 and NOT on Windows 2007.
   The reported error is a known issue with Windows 2007 server.
    
2. IWSUSER and ASPNET users are not listed in 'Deny logon as batch job' and 'Deny log on as a service' in Local Security Policy.
    
3. Try adding IWSUSER in Local Administrators group.
    
4. Navigate in the Windows registry to
   SOFTWARE\Classes\TypeLib\{6BFEF726-18F6-4D56-9FD5-F15E46A7DA6E}
   • Validate the string is in the registry.
   • If the path is valid, check the permissions for the same and give full permissions to IWSUSER and ASPNET user and restart the server.
      
5. If this is an upgrade from previous version of HP Quality Center Integration, ensure that prior to the upgrade you manually stop the following Windows services:
   • IIS admin
   • DOORS- HP Quality Center Integration Timer Service
     
     After the installation is complete, restart the IIS admin and then run Set Access Permission wizard.

 

---

 

Error 401 while testing services (SOQ and TDI Services) and Error 404 while testing services

The 40x errors occur while running the test with the Set Access Permissions wizard. These errors are mostly due to access restriction.

Steps to resolve:

1. Ensure that IWSUSER and ASPNET have full access to the following folders:
   • C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 and all subdirectories
   • $DOORSHOME and all subdirectories
   • Temp directory
     Note: This is the directory set by the environment variable TEMP.
     
     To check the value, go to My Computer -> Properties -> Advanced -> Environment Variables.
     By default, the value is set to C:\Documents and Settings\<UserName>\Local Settings\Temp and can also be accessed by clicking Start -> Run -> type %TEMP%.
      
2. Add ASPNET user to DCOM objects to have full access.
   • Steps to access DCOM objects:
     1. Click Start -> Run -> type dcomcnfg.
     2. Click Component Services -> Computers -> My Computer -> DCOM Config.
     3. Add ASPNET user to have full access for the following:
        • IBM Rational DOORS for HP Quality Center Interface (Legacy)
        • IBM Rational DOORS for HP Quality Center Interface Synchronizer v3.4
        • Telelogic DOORS
     4. Steps to give full access to ASPNET User:
        1. Right-click on the DCOM object (for example Telelogic DOORS) -> Properties.
        2. Select the Security tab.
        3. Select Customize from Launch and Activation Permissions.
        4. Click Edit.
        5. Add the ASPNET user and give full permission.
           
           Note: Ensure IWSUSER has full permission as well.
           
           Repeat the steps above for the fields Access Permissions and Configuration Permissions
           
           Repeat the steps for other DCOM Objects.
           
           For example: IBM Rational DOORS for HP Quality Center Interface (Legacy) and IBM Rational DOORS for HP Quality Center Interface Synchronizer v3.4.
            
3. Ensure IWSUSER is a member of the following groups:
   • Administrators
   • IIS_WPG
   • QCI_Admin_Console_Users
      
4. Ensure that ASP.NET is set as an Allowed WebService Extension by following the steps below.
   1. Open Internet Information Server (IIS) and expand WebService Extension.
      All the webservice extensions registered are listed.
   2. If you find ASP.NET listed, ensure that the status is set as "Allowed".
   3. If you do not find it, you should register ASP.NET first. For instructions to register ASP.NET, refer to step 5 below.
   4. Add the IWSUSER in the web.config file manually.
      
      Open web.config file from C:\Inetpub\wwwroot\DOORSTDIServices.
      
      The contents are similar to the following:
      
      
      </system.diagnostics>
<system.web>
 <authentication mode="Windows"></authentication>
 <authorization>
  <allow roles="QC-GSB\QCI_Admin_Console_Users"></allow>
  <deny users="*"></deny>
  <deny users="?"></deny>
 </authorization>
 <compilation debug="false">
      
      
      Change the contents to:
      
      
      </system.diagnostics>
<system.web>
 <authentication mode="Windows"></authentication>
 <authorization>
  <allow roles="QC-GSB\QCI_Admin_Console_Users"></allow>
   <allow users ="QC-GSB\IWSUSER"></allow>
  <deny users="*"></deny>
  <deny users="?"></deny>
 </authorization>
 <compilation debug="false">
      
       
   5. Re-Register ASP.NET.
      • Open a command prompt (Start -> Run -> type cmd) and execute following command:
        
        C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 > aspnet_regiis –r
         
   6. After the step above is complete, ASP.NET will be set as Blocked in IIS WebService Extensions. Follow step 4 above to set ASP.NET to Allowed.
       
   7. Ensure that Enable anonymous access and Integrated Windows authentication are enabled for DOORSTDIServices in IIS.
      1. Open IIS Admin.
      2. Go to Web Sites -> Default Web Site -> DOORSTDIServices.
      3. Right-click on DOORSTDIServices -> Properties.
      4. Go to Directory Security tab.
      5. In the Authentication and access control field click Edit.
      6. Ensure that the options Enable Anonymous Access and Integrated Windows authentication are checked.

---

Error: No disk space error even though the destination install directory has enough space

This error can appear if the user is not pointing the installation to default drive for example: C:\.

Installation of DOORS-HP Quality Center Integration creates files in two locations:

1. The location you chose to install the product. This location will primarily have executables and other library files required by the product.
2. Location of the Default Website in IIS. Files created here will be used by the integration webservice.
3. Thus, it is important to ensure that you have sufficient disk space in drives that hosts the above location.
   
   For example, if you choose to install the DOORS- HP Quality Center Integration product on the D: drive due to lack of space on the C: drive; if the Default Website in IIS is pointed to the C: drive, then installation can fail due to the error above.

 

Steps to resolve:

Check if the default website is pointing to C:\

1. Open IIS Admin -> Web Site.
2. Right-click on Default Website -> Properties -> Home directory.
3. Check value for Local path.
   
   If the default website is pointing to C:\, the virtual directories Inetpub and wwwroot will be created and thus will require more space.
    

   Note: There are instances where the default website is pointing to a different drive (for example: E:\) and the files are written to the default location of C:\Inetpub\wwwroot. This might happen if you had the default website path pointing to C:\ at earlier time and it was changed later. In such cases, you can make a backup and then delete the directories C:\Inetpub\wwwroot from C:\ and run the installation again for the desired drive.

This issue was identified as a product defect under APAR PM11531.

Defect Description: Installation writes the files in default drive even though destination folder is changed.

WORKAROUND: Copy and paste the contents from C:\ to the desired destination drive.

---

Error: IBM Rational DOORS for HP Quality Center Interface Synchronization timer in Service Manager cannot be started

The full error message is as follows:

Could not start the DOORS/Quality Center Integration timer service on local computer. Error 1053: The service did not respond to the start or control request in a timely fashion.

The Service Control Manager will generate an event if a service does not respond within the defined timeout period (the default timeout period is 30000 milliseconds).

Steps to resolve:

To resolve this problem, use the Registry Editor to change the default time-out value for all services.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Disclaimer

This solution contains information about modifying the system registry. Before making any modifications to the Microsoft Registry Editor, it is strongly recommended that you make a backup of the existing registry. For more information describing how to back up the registry, refer to Microsoft Knowledge Base article 256986

To change the service timeout period:

1. Click the Start -> Run -> type regedit.
    
2. In the Registry Editor, navigate to the registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
   
   In the details pane, locate the ServicesPipeTimeout entry.
    
3. Right-click and select Modify.
   
   Note: If the ServicesPipeTimeout entry does not exist, you must create it by selecting New on the Edit menu, followed by the DWORD Value. Then type ServicesPipeTimeout, and click Enter.
    
4. Click Decimal, enter the new time-out value in milliseconds, and then click OK.
    
5. Restart the computer.

---

Error while performing Test connection with DOORS and or Quality Center Integration

Error while creating data connection for DOORS or while testing connection for DOORS - Data provider failed to initialize or QC – Data provider failed to initialize

Steps to resolve:

1. Ensure that the user specified in the ‘test connection’ is able to access Rational DOORS while running Rational DOORS as IWSUSER.
   1. Right-click on DOORS client icon and click Run As.
   2. Select The following user and provide the username as IWSUSER (with respective password).
       
2. Ensure that you are able to launch Internet Explorer as IWSUSER.
   • Try to access Quality Center. If you are not able to login to Quality Center when Internet Explorer is launched as IWSUSER, ensure that the Internet Explorer settings for the Administrator matches those of IWSUSER.
   • Try to access Rational DOORS. If you are not able to access Rational DOORS while running as IWSUSER, ensure that IWSUSER has full access to $DOORSHOME and its subdirectories.

---

Errors while installing IAS Admin

Error: Access is denied when trying to access http://servername/AdminToolInstall from any client machine to Integration server.

Steps to resolve:

1. Ensure you have installed Microsoft.NET Framework v2.0 and Microsoft.NET Framework 3.0 on the machine where IAS admin needs to be installed.
2. Ensure that you have full access on C:\Inetpub (where C:\ is the drive where Quality Center Integration Server is installed).
3. Give recursive permission to the user C:\WINDOWS\Microsoft.NET\Framework
4. Run Setup.exe from C:\Inetpub\wwwroot\DOORSTDIServices\OCD folder.

 

---

Error: Unable to login to IAS Admin

The login keeps prompting for user name password again and again and eventually fails.

Steps to resolve:

Ensure that the user name that is being used to login to IAS Admin is a part of QCI_Admin_Console_Users group, which was created for Quality Center Integration users at the time of installation.

This can also happen if web.config file has UTF encoding set to UTF-16.

Note: The web.config file can be found in C:\Inetpub\wwwroot\DOORSTDIServices

To resolve this follow the steps mentioned below:

• 1. Take the backup of the web.config file.
  2. Change the UTF-16 to UTF-8.
  3. Save the file.
  4. Restart the IIS Admin service.
     
     Ensure that the user who is trying to access IAS admin has complete access on C:\Inetub\wwwroot folder and on C:\WINDOWS\Microsoft.NET folder