DocWiki - User contributions [en]

Reporting Configuration: Configure LDAP/AD

2010-09-17T07:18:43Z

Bhanprak:

== Configure LDAP (Active Directory) for user authentication ==

{| border="1"
|-
! '''Problem Summary'''
| Domain user cannot log in through LDAP server
|-
! '''Error Message'''
| Invalid username or password. Please try again.
|-
! '''Possible Cause'''
| The LDAP parameters are incorrect or incomplete
|-
! '''Recommended Action'''
|Sample parameters:
Host Address for Active Directory Server: 192.168.1.2
port: 389
"Use SSL" is not checked
Host Address for Redundant Active Directory Server:
Manager Distinguished Name: CN=Administrator, CN=Users, DC=myCompany, DC=com
Manager Password: <password for user administrator>
User Search Base: CN=Users, DC=myCompany, DC=com
Attribute for User ID: sAMAccountName

Sample value 2 for Manager Distinguished Name: CN=user1,OU=icm8,OU=UCCE80,OU=Cisco_ICM_domain,DC=UCCE80,DC=cisco,DC=com
Sample value 3 for Manager Distinguished Name: CN=testuser,OU=Employees,OU=Cisco Users,DC=cisco,DC=com

Tip 1: The values of OU could be case sensitive.
Tip 2: The max number of characters for Manager Distinguished Name field cannot exceed 85.

'''Action Plan-1:''' Verify following in CUIC setup
1. Verify the users credentials are correct in Active Directory
2. Verify the user is logging in with the correct Domain pre-pended to their Active Directory username. Verify they have not been locked out in Active Directory for too many failed login attempts.
3. Verify that the Active Directory server configured in OAMP is the same one used by UCCE/ICM. Verify the Manager Distinguished Name has the correct Domain name as that used by the ICM Server: CN=Administrator, CN=users, DC=MYDOMAIN, DC=COM

'''Action Plan-2:''' If Domain user is not able to login to CUIC yet, do the following:

Step-1: In OAMP Active Directory configuration page, check if User Search Base has 'CN=Users' in it. This is needed except incase User Search Base is already CN=Domain Users. Try To login to CUIC with supervisor name prepended with proper domain name
Step-2: If Step-1 doesn’t work, If user is not able to login still, modify to 'CN=Domain Users' in User Search Base and try to login
Step-3: If Step-2 doesn’t work, change following
Attribute for User ID = userPrincipalName
User Search Base search base, modify to = CN=Domain Users
And then try to login to CUIC with user id as testuser@bioscripinc.net (for this to work Ldap should be configured to accept both UserPrincipleName for login)

'''If AD user is still not able to login
'''
1.Login to Active directory using 'Active Directory Explorer by Microsoft' or Softerra LDAP browser
2.Navigate to the AD account name
3.Look for attribute distinguishedName, it would be something like "CN=UserName,DC=Users,DC=CompanyName,DC=COM...."
4.Copy every thing from distinguishedName except CN=UserName to 'User Search Base' element in OAMP Active directory configuration page
5.Make 'User ID Attribute' to userPrincipleName and from LDAP browser findout the userPrincipleName Attibute
Use the same thing to login to CUIC, login name would be like testuser@company.com
6.If user is not able to login to CUIC, then problem might be with Active directory LDAP authentication, then
Make 'User ID Attribute' to samAccountName and from LDAP browser find out the samAccountName Attibute
Use the same thing to login to CUIC, login name would be like 'company\testuser'

|-
! '''Release'''
| Release 8.0(1)
|-
! '''Associated CDETS#/ Similar SRs '''
| 614786193,615387559,614830251, cdets-defectid:CSCth62535 '''
|-
|}
[[Category: Configuration Examples]]

Reporting Configuration: Configure LDAP/AD

2010-09-14T08:02:04Z

Bhanprak: /* Configure LDAP (Active Directory) for user authentication */

== Configure LDAP (Active Directory) for user authentication ==

{| border="1"
|-
! '''Problem Summary'''
| Domain user cannot log in through LDAP server
|-
! '''Error Message'''
| Invalid username or password. Please try again.
|-
! '''Possible Cause'''
| The LDAP parameters are incorrect or incomplete
|-
! '''Recommended Action'''
|Sample parameters:
Host Address for Active Directory Server: 192.168.1.2
port: 389
"Use SSL" is not checked
Host Address for Redundant Active Directory Server:
Manager Distinguished Name: CN=Administrator, CN=Users, DC=myCompany, DC=com
Manager Password: <password for user administrator>
User Search Base: CN=Users, DC=myCompany, DC=com
Attribute for User ID: sAMAccountName

Sample value 2 for Manager Distinguished Name: CN=user1,OU=icm8,OU=UCCE80,OU=Cisco_ICM_domain,DC=UCCE80,DC=cisco,DC=com
Sample value 3 for Manager Distinguished Name: CN=testuser,OU=Employees,OU=Cisco Users,DC=cisco,DC=com

Tip 1: The values of OU could be case sensitive.
Tip 2: The max number of characters for Manager Distinguished Name field cannot exceed 85.

'''Action Plan-1:''' Verify following in CUIC setup
1. Verify the users credentials are correct in Active Directory
2. Verify the user is logging in with the correct Domain pre-pended to their Active Directory username. Verify they have not been locked out in Active Directory for too many failed login attempts.
3. Verify that the Active Directory server configured in OAMP is the same one used by UCCE/ICM. Verify the Manager Distinguished Name has the correct Domain name as that used by the ICM Server: CN=Administrator, CN=users, DC=MYDOMAIN, DC=COM

'''Action Plan-2:''' If Domain user is not able to login to CUIC yet, do the following:

Step-1: In OAMP Active Directory configuration page, check if User Search Base has 'CN=Users' in it. This is needed except incase User Search Base is already CN=Domain Users. Try To login to CUIC with supervisor name prepended with proper domain name
Step-2: If Step-1 doesn’t work, If user is not able to login still, modify to 'CN=Domain Users' in User Search Base and try to login
Step-3: If Step-2 doesn’t work, change following
Attribute for User ID = userPrincipalName
User Search Base search base, modify to = CN=Domain Users
And then try to login to CUIC with user id as testuser@bioscripinc.net (for this to work Ldap should be configured to accept both UserPrincipleName for login)

|-
! '''Release'''
| Release 8.0(1)
|-
! '''Associated CDETS#/ Similar SRs '''
| 615387559 '''
|-
|}
[[Category: Configuration Examples]]

Reporting Configuration: Configure LDAP/AD

2010-09-14T07:59:16Z

Bhanprak: /* Configure LDAP (Active Directory) for user authentication */

== Configure LDAP (Active Directory) for user authentication ==

{| border="1"
|-
! '''Problem Summary'''
| Domain user cannot log in through LDAP server
|-
! '''Error Message'''
| Invalid username or password. Please try again.
|-
! '''Possible Cause'''
| The LDAP parameters are incorrect or incomplete
|-
! '''Recommended Action'''
|Sample parameters:
Host Address for Active Directory Server: 192.168.1.2
port: 389
"Use SSL" is not checked
Host Address for Redundant Active Directory Server:
Manager Distinguished Name: CN=Administrator, CN=Users, DC=myCompany, DC=com
Manager Password: <password for user administrator>
User Search Base: CN=Users, DC=myCompany, DC=com
Attribute for User ID: sAMAccountName

Sample value 2 for Manager Distinguished Name: CN=user1,OU=icm8,OU=UCCE80,OU=Cisco_ICM_domain,DC=UCCE80,DC=cisco,DC=com
Sample value 3 for Manager Distinguished Name: CN=testuser,OU=Employees,OU=Cisco Users,DC=cisco,DC=com

Tip 1: The values of OU could be case sensitive.
Tip 2: The max number of characters for Manager Distinguished Name field cannot exceed 85.

'''Action Plan-1:''' Verify following in CUIC setup
1. Verify the users credentials are correct in Active Directory
2. Verify the user is logging in with the correct Domain pre-pended to their Active Directory username. Verify they have not been locked out in Active Directory for too many failed login attempts.
3. Verify that the Active Directory server configured in OAMP is the same one used by UCCE/ICM. Verify the Manager Distinguished Name has the correct Domain name as that used by the ICM Server: CN=Administrator, CN=users, DC=MYDOMAIN, DC=COM

'''Action Plan-2:''' If Domain user is not able to login to CUIC yet, do the following:

Step-1: In OAMP Active Directory configuration page, check if User Search Base has 'CN=Users' in it. This is needed except incase User Search Base is already CN=Domain Users. Try To login to CUIC with supervisor name prepended with proper domain name
Step-2: If Step-1 doesn’t work, If user is not able to login still, modify to 'CN=Domain Users' in User Search Base and try to login
Step-3: If Step-2 doesn’t work, change following
Attribute for User ID = userPrincipalName
User Search Base search base, modify to = CN=Domain Users
And then try to login to CUIC with user id as testuser@bioscripinc.net (for this to work Ldap should be configured to accept both UserPrincipleName for login)

|-
! '''Release'''
| Release 8.0(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}
[[Category: Configuration Examples]]

Reporting Configuration: Configure LDAP/AD

2010-09-14T07:54:23Z

Bhanprak:

== Configure LDAP (Active Directory) for user authentication ==

{| border="1"
|-
! '''Problem Summary'''
| Domain user cannot log in through LDAP server
|-
! '''Error Message'''
| Invalid username or password. Please try again.
|-
! '''Possible Cause'''
| The LDAP parameters are incorrect or incomplete
|-
! '''Recommended Action'''
|Sample parameters:
Host Address for Active Directory Server: 192.168.1.2
port: 389
"Use SSL" is not checked
Host Address for Redundant Active Directory Server:
Manager Distinguished Name: CN=Administrator, CN=Users, DC=myCompany, DC=com
Manager Password: <password for user administrator>
User Search Base: CN=Users, DC=myCompany, DC=com
Attribute for User ID: sAMAccountName

Sample value 2 for Manager Distinguished Name: CN=user1,OU=icm8,OU=UCCE80,OU=Cisco_ICM_domain,DC=UCCE80,DC=cisco,DC=com
Sample value 3 for Manager Distinguished Name: CN=testuser,OU=Employees,OU=Cisco Users,DC=cisco,DC=com

Tip 1: The values of OU could be case sensitive.
Tip 2: The max number of characters for Manager Distinguished Name field cannot exceed 85.

'''Action Plan-1:''' Verify following in CUIC setup
1. Verify the users credentials are correct in Active Directory
2. Verify the user is logging in with the correct Domain pre-pended to their Active Directory username. Verify they have not been locked out in Active Directory for too many failed login attempts.
3. Verify that the Active Directory server configured in OAMP is the same one used by UCCE/ICM. Verify the Manager Distinguished Name has the correct Domain name as that used by the ICM Server: CN=Administrator, CN=users, DC=MYDOMAIN, DC=COM

'''Action Plan-2:''' If Ldap user is not able to login to CUIC yet, do the following:

Step-1: In OAMP Active Directory configuration page, check if User Search Base has 'CN=Users' in it. This is needed except incase User Search Base is already CN=Domain Users. Try To login to CUIC with supervisor name prepended with proper domain name
Step-2: If Step-1 doesn’t work, If user is not able to login still, modify to 'CN=Domain Users' in User Search Base and try to login
Step-3: If Step-2 doesn’t work, change following
Attribute for User ID = userPrincipalName
User Search Base search base, modify to = CN=Domain Users
And then try to login to CUIC with user id as testuser@bioscripinc.net (for this to work Ldap should be configured to accept both UserPrincipleName for login)

|-
! '''Release'''
| Release 8.0(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}
[[Category: Configuration Examples]]

Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch

2010-09-09T11:58:12Z

Bhanprak: /* Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch */

== Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch==

{| border="1"
|-
! '''Problem Summary'''
| Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch.
|-
! '''Error Message'''
| WARNING: Exception caught: An exception occurred while executing a Transact-SQL statement or batch. (ExecutionFailureException)
WARNING: Trace: at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand)
at CuisConfigTool.Util.SQLUtil.runScript(String script, String address) in n:\bluevue\CuisConfigTool\CuisConfigTool\Util\SQLUtil.cs:line 869
at CuisConfigTool.Archiver.ArchiverConfiguration.setupCommonData() in n:\bluevue\CuisConfigTool\CuisConfigTool\Archiver\ArchiverConfiguration.cs:line 562

|-
! '''Possible Cause'''
| Unified IC CUIS configuration tool must be run as a Windows administrator (mapped
also as a sysadmin security login on the local Archiver SQL Server).

|-
! '''Recommended Action'''
| -> Please go through "Archiver Check List" mentioned in [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/intelligence_suite/intelligence_suite_75/user/guide/isic75ug.pdf Archiver user guide] with due diligence before Archiver Installation/configuration.
-> Check to see if the SQL Server service uses the "local" CuisDBAdmin account prior to running the config tool.
|-
! '''Release'''
| Release 7.5(x)
|-
! '''Reference SR #'''
| 614841109, 611182195
| |-
|}

[[Category:Unified IS, Release 7.5]]

Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch

2010-09-09T11:57:37Z

Bhanprak: /* Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch */

== Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch==

{| border="1"
|-
! '''Problem Summary'''
| Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch.
|-
! '''Error Message'''
| WARNING: Exception caught: An exception occurred while executing a Transact-SQL statement or batch. (ExecutionFailureException)
WARNING: Trace: at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand)
at CuisConfigTool.Util.SQLUtil.runScript(String script, String address) in n:\bluevue\CuisConfigTool\CuisConfigTool\Util\SQLUtil.cs:line 869
at CuisConfigTool.Archiver.ArchiverConfiguration.setupCommonData() in n:\bluevue\CuisConfigTool\CuisConfigTool\Archiver\ArchiverConfiguration.cs:line 562

|-
! '''Possible Cause'''
| Unified IC CUIS configuration tool must be run as a Windows administrator (mapped
also as a sysadmin security login on the local Archiver SQL Server).

|-
! '''Recommended Action'''
| -> Please go through "Archiver Check List" mentioned in [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/intelligence_suite/intelligence_suite_75/user/guide/isic75ug.pdf Archiver user guide] with due diligence before Archiver Installation/configuration.
-> Check to see if the SQL Server service uses the "local" CuisDBAdmin account prior to running the config tool.
|-
! '''Release'''
| Release 7.5(x)
|-
! '''Associated SR #'''
| 614841109, 611182195
| |-
|}

[[Category:Unified IS, Release 7.5]]

Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch

2010-09-09T11:47:59Z

Bhanprak: New page: == Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch== {| border="1" |- ! '''Problem Summary''' | Archiver: Configuration tool failed. ...

== Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch==

{| border="1"
|-
! '''Problem Summary'''
| Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch.
|-
! '''Error Message'''
| WARNING: Exception caught: An exception occurred while executing a Transact-SQL statement or batch. (ExecutionFailureException)
WARNING: Trace: at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand)
at CuisConfigTool.Util.SQLUtil.runScript(String script, String address) in n:\bluevue\CuisConfigTool\CuisConfigTool\Util\SQLUtil.cs:line 869
at CuisConfigTool.Archiver.ArchiverConfiguration.setupCommonData() in n:\bluevue\CuisConfigTool\CuisConfigTool\Archiver\ArchiverConfiguration.cs:line 562

|-
! '''Possible Cause'''
| Unified IC CUIS configuration tool must be run as a Windows administrator (mapped
also as a sysadmin security login on the local Archiver SQL Server). Check to see if the SQL Server service uses the "local"
CuisDBAdmin account prior to running the config tool.

|-
! '''Recommended Action'''
| Please go through "Archiver Check List" mentioned in Archiver user guide with due diligence before Archiver Installation/configuration
|-
! '''Release'''
| Release 7.5(x)
|-
! '''Associated SR #'''
| 614841109, 611182195
| |-
|}

[[Category:Unified IS, Release 7.5]]

Troubleshooting Tips for Unified IS 7.5

2010-09-09T11:27:34Z

Bhanprak: /* Archiver */

'''Back:''' [[Troubleshooting Unified Intelligence Suite]]

'''Add tip:''' [[Create Troubleshooting Tips]]

The following tips were added by Cisco Documentation:

= Archiver=
:* [[Archiver: Data Retrieval]]
:* [[Archiver: Free Space and Emergency Purge]]
:* [[Archiver: How to Point to Another Server]]
:* [[Archiver: Load Archiver Fails]]
:* [[Archiver: LoadArchiver Fails with "Primary key constraint violations"]]
:* [[Archiver: Performance and Memory Space]]
:* [[Archiver: Scheduled Events Do Not Run]]
:* [[Archiver: Configuration tool failed. Exception occurred while executing a transact statement or batch]]

= Configuration=
:* [[Configuration: Configuring IIS Failed]]
:* [[Configuration: Configuring the CUIC Scheduler Service Failed]]
:* [[Configuration: Creating CUIC Database Failed]]
:* [[Configuration: Port 80 Error]]
:* [[Configuration: Server Not Responding to Ping Command]]
:* [[Configuration: Setting Folder Permissions Failed]]
:* [[Configuration: Setting Up Permissions for CUIS SQL Server Login Failed]]

= Installation=
:* [[Installation: SQL Hardening]]

= Licensing=
:* [[Licensing: Exceeded the Number of Licensed Users]]
:* [[Licensing: Error Code in Event Viewer: -1]]
:* [[Licensing: Error Code in Event Viewer: -2]]
:* [[Licensing: Error Code in Event Viewer: -4]]

= Logging In=
:* [[Logging In: Cannot Access CUIS Using IP Address]]
:* [[Logging In: User Cannot log In]]

= Reporting =
:* [[Reporting: Connection Dropped Message]]
:* [[Reporting: Data Source Failover]]
:* [[Reporting: Deleting Users]]
:* [[Reporting: Effect of IIS Recycle on Reports]]
:* [[Reporting: SQL Validation for Unified IC]]
:* [[Reporting: Error while rendering reports]]

= System =
:* [[System: Location of Unified IC Files]]
:* [[System: Purge the CUIC Database]]
:* [[System: Release Notes for Maintenance Releases]]
:* [[System: Retrieve Size for CUIC Database Tables]]
:* [[System: SQL Hardening Failure]]

= Upgrading =
:* [[Upgrading : Scheduler does not start after an upgrade]]

Archiver: LoadArchiver Fails with "Primary key constraint violations"

2010-08-20T13:39:35Z

Bhanprak: New page: {{Template:Required Metadata}} == Archiver: LoadArchiver Fails with "Primary key constraint violations"== {| border="1" |- ! '''Problem Summary''' | "Primary key constraint violations" ...

{{Template:Required Metadata}}
== Archiver: LoadArchiver Fails with "Primary key constraint violations"==

{| border="1"
|-
! '''Problem Summary'''
|
"Primary key constraint violations" when running the LoadArchiver stored procedure.
|-
! '''Error Message'''
| Primary Key Contraint Violations
|-
! '''Possible Cause'''
| (1)CUIS Archiver requires that the HDS and Archiver servers be in same time zone. If these servers are in different time zones, there will be "primary key constraint violations" on various and random tables when running the LoadArchiver stored procedure.

or
(2)The Archiver stored procedure might had archiver.dbo.xp_InsertChildInterval and archiver.dbo.xp_UpsertChildInterval has i.status=2 in sql query (as mentioned in SR 615134909)

|-
! '''Recommended Action'''
| For cause (1) Place the Archiver and HDS servers in the same time zone.

For cause (2) Login to Archiver machine, Open "Sql Server Management Studio" and navigate to below stored procedure in archiver database and change i.status=2 to i.status=2066 in sql query.
Stored Procedure-1: xp_InsertChildInterval
Stored Procedure-2: xp_UpsertChildInterval
|-
! '''Release'''
| Release 7.5(x)
|-
! '''Associated CDETS #/SR'''
| CSCsz99377, SR615134909
|-
|}

[[Category:Unified IS, Release 7.5]]

Troubleshooting Tips for Unified IS 7.5

2010-08-20T13:38:33Z

Bhanprak:

Troubleshooting Tips for Unified IS 7.5

2010-08-20T13:36:33Z

Bhanprak:

Troubleshooting Tips for Unified IS 7.5

2010-08-20T13:29:00Z

Bhanprak:

Archiver: LoadArchiver Issues with Different Server Time Zones

2010-08-20T13:25:23Z

Bhanprak: /* Archiver: LoadArchiver Issues with Different Server Time Zones */