After up gradation from 12.7 to 17.1, I am facing delay server response issue -
1.when trying to set the role from any role to Employee Role(fig-1)
2.When trying to save ticket .
3.When trying to open score board items (fig-2 Yellow marked items)
Please give me with a proper solution.
What is the patch level are you running right now? If you not implemented any patches, Please go ahead and download the RU01 + RU02 patches from below link - https://support.ca.com/us/product-content/recommended-reading/technical-document-index/ca-service-management-solutions-patches.html.
Let us know the results once you implemented the patches
I have to applied any patches till now. We are using CA SM 17.1 in windows 2012 std server with MS SQL 2014 .Please guide me which patch I have to download and apply and what is the procedure of rollback if these patches dint not worked.
Below are the 2 patches that are required i.e.
Saikat, there are many reasons you would get this delay server response. The first thing comes in my mind is...do you re-customize the customization? Please take a look at
How to address "Delayed Server Response Message" i - CA Knowledge
I have upgraded site modes folder as per below link-
Customization Upgrade Utility - CA Service Management - 17.1 - CA Technologies Documentation .Please guide me what to do.
Trouble-shooting "Delayed server response" on Chan - CA Knowledge
I agree with Chi, that most of the times the earlier customizations cause the issues. That may be the first area to troubleshoot. Looks like you have issues with the employee interface. I am guessing you have htmpl files that have been customized. If that is the case, a good starting point would be to copy the custom employee htmpl files (site/mods/..../employee, and site/mods/.../employee/Employee) to a backup folder and delete the employee custom files. Do a pdm_webcache and then try to check on the issues using the default OOTB files. If the problem goes away, at least you know the issue lies with the custom files. If not, you know something else is the problem.