Hi Ujwol,
No I have not tried the smconsole tracing yet, but I just learned something new about this issue which is quite interesting. So with my r12.52 upgrade, I am doing the parallel upgrade method so I am building out brand new servers/VMs and installing the r12.52 and configuring the PS SSO between the new r12.52 PS with the existing r12.0 PS. So far I completed the DEV environment which as only a single policy server. Next I completed the QA environment, which has two policy servers. I am now starting on the production environment which has three policy servers.
This issue with the smconsole not launching while the policy server is running only appeared on the first of the three new PROD r12.52 server. As of this morning I finally decided to skip this first prod server and move to the next server feeling confident that this smconsole issue/mess is specific only to that first PROD server but I guess I am wrong. I completed the second PROD server installation and tested the smconsole behavior and see the same exact issue on this new second PROD server too. There must be something slightly different within the server OS/libraries for these three new PROD servers compared to the DEV and QA servers because this problem only exist on these three new servers.
Here is the really interesting new discovery. I know that if I shut down the policy server then the smconsole will launch just fine but once I start up the policy server then go into the [smhome]/bin and launch smconsole then I get that error message, BUT if I shut down the policy server then launch the smconsole and while the smconsole is open, I then start up the policy server then from that point on I can stop the smconsole and launch it back again anytime I want just as long as the policy server does not stop and then start up again while the smconsole is NOT running. Basically the smconsole needs to launch first before the policy server start up so that the smconsole can register its file somewhere before the policy server starts up to overwrite it.
This is quite strange, but I am hoping that based on this description, folks could chime in with thoughts on possible causes
Regards,