Topic
  • 1 reply
  • Latest Post - ‏2013-07-22T15:34:09Z by tcassid
cc_starter
cc_starter
8 Posts

Pinned topic "CRMAP7007 Error reading local file area registry"

‏2013-07-17T21:48:25Z |

Hi All,

I'm trying to assist a developer who get the below error message when he tries to connect to CCRC.

"CRMAP7007 Error reading local file area registry"

I've no idea abt this error message. Can someone pls help me with this? Thanks in advance.

 

 

 

 

Attachments

  • tcassid
    tcassid
    20 Posts

    Re: "CRMAP7007 Error reading local file area registry"

    ‏2013-07-22T15:34:09Z  

    To get a better idea of why the error is thrown you can look in the workspace log file.  This filre is by default <user home>\.Rational\workspace\.metadata\.log

    You can also launch CTE in debug mode by creating a .options file in the directory that he executable is in.  The content of that file should be as below:

    # -------------- CCRC Tracing Options File -----------------
    # All line preceeded with a # sign are not evaluated.

    # ------Server Tracing-------
    # subsystems available:
    # CCRC - Core general tracing related to CCRC server operations
    # CCWEB- CCWeb(CGI operations)
    # SUM -  UCM specific

    com.ibm.rational.clearcase/server_trace=true
    com.ibm.rational.clearcase/server_trace/subsys=CCRC:CCWEB:SUM
    com.ibm.rational.clearcase/server_trace/level=4

    # ------Client Only Tracing-------
    # Parameters available:
    # HTTP_CLIENT - Tracing specific to HTTP communications
    # CTRC_UI -     Tracing specific to the user interface
    # CTRC_CORE -   For client core tracing

    com.ibm.rational.clearcase/client_trace=true
    com.ibm.rational.clearcase/client_trace/params=HTTP_CLIENT:4 CTRC_UI:3 CTRC_CORE:3

    com.ibm.rational.clearcase/client_trace/output=file
    com.ibm.rational.clearcase/client_trace/file_name=C:/temp/cte_debug.out
    # -------------- END CCRC Tracing Options File -----------------

    With that file created, launch CTE from the command line using the -debug option:
    C:\Program Files\IBM\RationalSDLC\ClearCase\RemoteClient>ctexplorer.exe -debug


    The contents of C:\temp\cte_debug.out should be helpful in determining the cause of the failure.  This is also explained in a bit outdated, yet still relevant technote here: http://www-01.ibm.com/support/docview.wss?uid=swg21234118