Results being returned to CABI 4.1are being padded with what appears to be a null (last character is an ASCII 0 (Null))

Document ID : KB000067883
Last Modified Date : 24/05/2018
Show Technical Document Details
Issue:

Results being returned to CABI 4.1 are being padded with what appears to be a null. For example, "This is the result" is 18 characters long, but the result from the Data Direct layer indicates 19 characters long, and the last character is an ASCII 0 (Null)

values.png

Environment:

CA Business Intelligence (CABI) 4.1

All Supported Windows Operating Systems

CA Service Desk Manager 14.1

Resolution:

Issue is with the Data Direct ODBC driver between CA Service Desk Manager (CA SDM) and CABI 4.1.

An uninstall and reinstall of the ODBC driver on the CA SDM server usually resolves the issue

1.  Identify the CA SDM hostname being used by the universe. Refer to https://comm.support.ca.com/kb/what-ca-service-desk-manager-ca-sdm-connection-settings-are-preferred-on-the-ca-sdm-cabi-universe/kb000020401 for details

2.  On the CA SDM server identified above, open a command prompt as Administrator (right-click on Command Prompt and select 'Run As Administrator')

3.  Type: 

nxcd bin

oa72_server_uninstall.bat

oa72_client_uninstall.bat

copy C:\Windows\System32\drivers\etc\services C:\Windows\System32\drivers\etc\services_backup

notepad C:\Windows\System32\drivers\etc\services

4.  Towards the bottom of that file, will see couple of lines like below:

OA6_1998519985/tcp# OpenAccess 6 service CA Service Desk Manager ODBC Agent

OA6_1998719987/tcp# OpenAccess 6 service CA Service Desk Manager ODBC Data Access

5.  Comment them out by placing a # character in front of each line, so the result should look like

#OA6_1998519985/tcp# OpenAccess 6 service CA Service Desk Manager ODBC Agent

#OA6_1998719987/tcp# OpenAccess 6 service CA Service Desk Manager ODBC Data Access

6.  Save and close the file.

7.  Back at the command prompt from step#3 above, run below commands

oa72_client_setup.bat

oa72_server_setup.bat

8.  The above two commands should complete successfully without any errors

9.  Ensure that the two CA SDM ODBC services are working by accessing Windows Control Panel -> Services  and verify that the two services are running

CA Service Desk Manager ODBC Data Access

CA Service Desk Manager ODBC Agent

10. Restart CABI's Server Intelligence Agent (SIA) by accessing CABI Server remotely and by launching Central Configuration Manager (CCM) by:

a) Click on Windows Start Menu and type: Central Configuration Manager (CCM)

b) Right-click on CCM and select 'Run as Administrator' option

c) In the CCM window, select the Server Intelligence Agent, right-click and select STOP

d) Refresh the CCM screen by selecting the refresh button

e) Once the status goes to STOPPED, right-click on the Server Intelligence Agent again and select START

11.  Try the CABI reports again and verify that the CABI results are no longer being padded with Null characters