My systems department needs to upgrade the OS on the PAM Server and Service Catalog server. Current Server OS is Win Server 2008. The issue is that the disk was thick provisioned and could not just be extended. I have a C: and E: drive on the server and the apps are installed on E:.
The plan was to create a new disk and copy all the data from E: to new drive and then delete the old E; drive. C: would then be extended to 180GB to accommodate Win Server 2012. The OS would then be upgraded to Win Server 2012 and patched.
Once the server was brought up though, the EEM 184.108.40.206 and PAM 4.2 SP02 App were not functioning at all. Please advise on the best way to proceed.
Hi Yogan.For my (correct) understanding.Originaly, the Catalog software was installed in E:\Program Files\CA\Service Catalog\.....And then you created a new disk, say F:Next you just copied E:\Program Files\CA\Service Catalog\..... to F:\Program Files\CA\Service Catalog\.....Nothing more, nothing less.Please advise. Thanks in advance and kind regards, Louis.
Renamed F: to E: after deleting old E:
I assuming the issue lies with CA EEM not functioning after that server was upgraded as well. The Service Catalog is trying to access the site and prompts for credentials but nothing will be found as CA EEM cannot be accessed.
Are you able to access the EEM UI and login successfully?
I am not able to access the login screen. It comes up with "500internal sponsor error". I have sent the debug level logs to CA Support hopefully it will be of some help in resolving the issue.
What is the Support Case # for reference?
The support case number is 01362151
owned by: Kaveek Jimmy
I have asked Kaveek to engage the EEM Support Team for further assistance.
Good Morning Yogan.Please check on the following, somewhat formal kind of statement:This 'Community' functionality is meant for relatively simple questions&(quick)answers for CA Service Catalog.Looking into this one, it seems/appears that a 'quick answer' can not be made available within this community thread.More likely, 'investigation' and/or 'debugging' is needed to find a possible cause and solution for this.Therefor I need to ask you to consider to open a 'standard' case.Through which you can get standard, full-service and in-depth follow-up by our Support Teams.Thanks in advance for your understanding and kind regards, Louis.
Engaging the EEM team to further assist on this ticket.
Will send you feedback via the ticket as soon as I have a resource and make some headway.