Unable to connect to Communication Station

Question

Dear All,
We are facing an issue in CRM MSA.
When we are trying to connect to the Communication station via the
Mobile Client Console - Test Adapter connection, we get this error
saying "
Unable to connect to Communication Station
Source: Adapter connection
Suggestions:
Check that network connection to communication station is proper.
Check that the registry entry under
HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MSA\CRMLaptopAdapter\Host points to
correct communication station.
0 Trying to access Communication Station Chmswq13.pp-r07-
chbs.cp.chbs, please wait...
1260 Unable to connect to Communication Station."
1.We already have configured the comm station and all the connection
and services are working fine in the Comm station.
2.We are able to successfully ping the comm station from the laptop
which we are running the mobile client console. Both the machines are
in the same domain.
3.The comm station hostname are also properly maintained in the
HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MSA\CRMLaptopAdapter\Host file.
Can you please help us out with this problem.
Will surely reward points if there are any solutions.
Thanks in advance.
Warm Regards,
Rajeet Mathur.

Answer 1

Hi,
Please apply the following settings st the commstation.
Please follow the steps in the chronological order
1.  Start -> Run -> "DCOMCNFG"
2.  Right click on 'My Computer' and select Properties
3.  Tab: Default Properties
    Check on 'Enable Distributed COM on this computer'
4.  Tab: COM security
    Click on Access Permissions and click on 'Edit default'
       Check for the presence of the groups 'Administrators',
       'Interactive', 'System' and 'Network'
       Grant permissions for 'Local Access' and 'Remote Access'
    Click on Launch and Activation Permissions and click on 'Edit
    default'
       Check for the presence of the groups 'Administrators'
       'Interactive', 'System' and 'Network'
       Grant permissions for Local Launch, Local Activation, Remote
       Launch, Remote Activation
5.  Tab: MSDTC
    Click on the 'Security Configuration' button in the group
    'Transaction Configuration'
    UNcheck Network DTC Access
    UNcheck Enable XA Transactions
6.  Tab: Default Protocols
    Check whether connection oriented TCP/IP is present. If not, please
    add it.
7.  Right click on 'SAP Mobile Transfer 5.0' for SAP CRM 5.0 or 'SAP
    Mobile Transfer' for SAP CRM 4.0 solution. Select properties
8.  Tab: Security
    Select 'Perform access checks only at process level'
      8.  Tab: Security
      Select 'Perform access checks only at process level'
      Set 'Authentication level for calls' to None.
      Set 'Impersonation Level' to Anonymous
  9.  Tab: Activation
      Select 'Server Application'
      Check 'Run Application as NT Service'
  10. Tab: Identity
      For Windows 2003 Server
         Select 'System Account'  and select 'Local System-Complete access
         to local machine'
      For other systems
         Add a new user under the local Administrators group.
         The following should be the properties of the new user
         Password never expires
         Password cannot be changed
         Select 'This user' and add. Provide the user credentials
  11. Tab: Advanced
      Select 'Leave running while idle'
  CommStaion OS
  Microsoft have changed the default security policy since Windows 2003
  Server SP1 and Windows XP SP2. So additional steps mentioned below are
  required for the CommStation to work in case you are using any one of
  the operating systems mentioned above.
  12. Enabling network COM access.
      Please take Start menu-> Control Panel-> Add or Remove Programs.
      Click Add/Remove Windows Components.
         Select Application Server and click Details.
         Check the box next to Enable network COM+ access, and then click OK.
         Click Next to complete the Windows Components wizard.
         Click Finish to close the wizard.
     13. Enabling network DTC access.
         Please take the Start menu-> Control Panel-> Add or Remove Programs.
         Click Add/Remove Windows Components.
         Select Application Server and click Details.
         Check the box next to Enable network DTC access, and then click OK.
         Click Next to complete the Windows Components wizard.
         Click Finish to close the wizard.
     14. Changing the default security policy
         Start -> Control Panel -> Administrative Tools -> Local Security
         Policy -> Local Policies -> Security Options -> Network Access.
         Right click on 'Let Everyone permission apply to anonymous user' and
         select Properties.
         Click on Enabled
     15. A new built-in user group namely 'Distributed COM Users' has been
         included since Windows Server 2003 Service Pack 1 to expedite the
         process of adding users to the DCOM computer restriction settings.
         Adding the required user or user group that would access the
         CommStation to 'Distributed COM Users' would solve the remote
         access, launch and activation related issues from the mobile client.
         This requires that the user or the user group is on the same domain
         as the CommStation. If user from other domains or local clients
         access the CommStation, then the following step should be followed.
     16. Changing the DCOM Access
         Start -> Control Panel -> Administrative Tools -> Local Security
         Policy -> Local Policies -> Security Options -> DCOM
DCOM: Machine Access Restrictions in Security Descriptor Definition
Language (SDDL) setting allows you to specify an Access Control List
in two different ways. You can type in the security descriptor in
Security Descriptor Definition Language (SDDL), or you can choose
users and groups and grant or deny them Local Access and Remote
Access permissions. Existence of this policy, overrides, values in
Machine Access Restriction.
Click on the 'Edit Security' button and grant the user 'Everyone'
the privileges 'Local Access' and 'Remote Access'.
DCOM: Machine Launch Restrictions in Security Descriptor Definition
Language (SDDL) is similar to the above settings. Existence of this
policy, overrides, values in Machine Launch Restriction
Click on the 'Edit Security' button and grant the user 'Everyone'
the privileges 'Local Launch', 'Remote Launch', 'Local Activation'
and 'Remote Activation'.
Best Regards,
Shourav