• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 1018 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Conflict between CCS5.3/5.4 and ESSO (Oracle Enterprise Single Sign-on)

Maxpower
Expert 1105 points
Other Parts Discussed in Thread: CCSTUDIO

CCSv 5.3 used to run on my computer so I don't know why it quit working on my computer recently. I tried updating to 5.4 and was finally successful at installing 5.4 after I completely uninstalled 5.3. However, I keep getting a "ccstudio.exe stopped working" message when creating a new workspace.

I checked the Windows Application log and found this:

Faulting application name: ccstudio.exe, version: 0.0.0.0, time stamp: 0x4d87abff
Faulting module name: ssojho.dll, version: 7.0.2.342, time stamp: 0x4e2102af
Exception code: 0xc0000005
Fault offset: 0x00028001
Faulting process id: 0x3c20
Faulting application start time: 0x01ce8d2b35b3815a
Faulting application path: C:\ti\ccsv5\eclipse\ccstudio.exe
Faulting module path: C:\Program Files (x86)\Passlogix\v-GO SSO\Helper\Java\ssojho.dll
Report Id: 772db796-f91e-11e2-861d-b8ac6f0f1e90
 

Notice the bolded text? ESSO is a tool that provides login information so you don't have to re-type your username and password for various enterprise applications.

I can get CCS to run in a new workspace if I, either rename ssojho.dll, or go into the Windows task manager and kill all the processes related to ESSO. Pausing ESSO does not solve the problem.

It seems like once I can get CCS to create a workspace, it will work from then on, even if ESSO is running.

Any ideas as to why?

Is there a fix? Or workaround, other than shutting down ESSO?

Thanks

  • 0
    TI__Genius 15710 points

    Hello, 

    Unfortunately, we can't say that we came across something like this in the past. Could you check if you get any CCS crash logs? see link below for where to look. I am looking for .dmp file or hs_errPID.log files that might provide more clues. 

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#CCS_Diagnostic_Logs

    The main thing that happens different during workspace creation is that a new directory is created. Could there be some permissions/directory creation failure? Would it be possible to try different location for new workspace? 

    Martin

  • 0 in reply to MartinS
    Expert 1105 points

    Martin,

        I followed the directions in the link you provided. I assume you wanted me to enable trace logging.

    I set TI_TRACE_LOGGING to 6 and re-ran CCSv5.4. When I try to create a new workspace, I get the crash, as expected but I am not finding the crach dump file. I am on Windows 7 so it should be in /users/<user-id>/.TI-trace. I do not have that folder. I do have "show hidden files and directories" selected.

    If it is not trace logging, which log do you need?

    I am an administrator on my computer and I am creating a directory from my root drive. CCS will create the .metadata directory that has a log in it but it simply says there was a crash but provides no further information.

    Thanks

  • 0 in reply to Maxpower
    TI__Genius 15710 points

    Sorry, should have mentioned out which logs to look for. I am in interested in Debug Server Dump Files. If you click on Debug Server Dump File and click on View, then Windows Explorer will open at the right place. hs_err*.log files should be in the same directory as well. 

    Martin

  • 0 in reply to MartinS
    Expert 1105 points

    Martin,

       To get to that dialog, I have to opne a workspace that already exists. When creating a new workspace, CCS crashes before I can do anything.

    When I open up an existing workspace and go to the support dialog and click view, the directory it opens is empty. There are no files listed.

    I turned on the Debug Server Log option and gave it the same directory as the Debug Server Dump File. It then creates a file but it doesn't say anything about any issues.

    I still must be misunderstanding what you want me to do.

    Thanks for your help

    Thanks

  • 0 in reply to Maxpower
    TI__Genius 15710 points

    That directory in CCS support dialog is the same per installation/version of CCS, thus it does not matter which workspace you use. .dmp files provide more debugging type information. However, .dmp files are not always generated when CCS crashes. I was hoping that would be the case as it is easier to get more information.  Unfortunately, I am not familiar with Esso and my search on potential causes/issues has not turned up much. New workspace ends up creating a new directory in the filesystem. I am not sure if there are any special permissions that esso enforces on directory creation. The only other thing that I can try to suggest is to use CCS with your system Java Runtime (assuming it is 32-bit). You would need to navigate to CCSInstallRoot\ccsv5\eclipse directory and rename "jre" to something else e.g. "__jre__". If your system Java is 64-bit, then you could try downloading latest 32 bit JRE from Oracle and replacing original jre that CCS installs with version that you downloaded. CCS will not work with a 64-bit JRE. 

    Martin

  • 0 in reply to MartinS
    Expert 1105 points

    Martin,

        Thank you for your contiued help!

    I renamed the jre directory but still had the same crach with CCSv5.4. Everything works with CCSv5.3 on another computer (that also has ESSO) but it is running Windows XP and the computer that is having the problem is running Windows 7.

    I tried to install the update to 5.4 on the XP machine to see if I could determine if this is a 5.3 issue or a Windows 7 specific issue but the upgrade failed.

    I have a workaround for this issue and it only happens when I am creating a new workspace which is not often.

    Thanks again for the help

  • 0 in reply to Maxpower
    TI__Genius 15710 points

    Regarding 5.4 upgrade on XP machine: Would you be able to .zip and attach installation logs? They should be in C:\Program Files\Install Jammer Registry. 

    Regarding the crash: I was thinking that Win7 might be a a 64 bit os, where it's Esso libraries might be 64bit dll's. Based on the screen capture that you provided Esso is loaded by Java processes or maybe all system processes. I know that a 32-bit java environment can't load 64-bit dll's and vice versa, thus maybe it is that incompatibility. WinXP is likely to be a 32bit system. However, it is strange that this crash would be getting triggered only on a new workspace, rather than all the time. 

    Thanks,
    Martin

     

  • 0 in reply to MartinS
    Expert 1105 points

    Martin,

        That is correct. The Winxp machine is 32 bit and the Win 7 machine is 64 bit. I don't remember having this issue with previous versions of CCS on the Win 7 machine but it is possible I never tried to create a new workspace after I was "upgraded" to Win 7.

    I saw the message (during the failed update) to zip up the logs and post them but I didn't because I had this same issue on the Win 7 machine a little while back and I ended up having to uninstall 5.3 and do a full install of 5.4. I chose to upgrade the Win 7 machine because, for some reason, 5.3 would not run anymore and I could not upgrade in place to 5.4. I figure I will do the same thing on the Winxp machine. If that doesn't work, I will post the install logs.

    Thanks