Clarity

Clarity Version 13.3

We are getting following error while saving project in OWB.

'' Unable to Save project CA Clarity PPM\***************. the project you are trying to save does not exist. Use SaveAs instead."

Can anybody have any solution for this.

Thanks in advance.

Ashwin,

Did the Save As work?

Linda

What does the app-ca.log say?

Can you try enabling the logging for OWB as mentioned in the article: TEC468125 - Clarity: How do I enable CA PPM Schedule Connect logging for MSP /OWB troubleshooting?

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec468125.aspx

**********

Clarity: How do I enable CA PPM Schedule Connect logging for MSP /OWB troubleshooting?

Document ID:  TEC468125
Last Modified Date:  5/7/2013
  Show Technical Document Details

Description:

In order to troubleshoot issues with CA PPM Schedule Connect and schedulers OWB or MSP, CA Support may request scheduler logging to be enabled on the local client Windows computer. It will be used to output additional details on the information sent from/to the scheduler when connecting to Clarity.

Solution:

Prior to replicating the error, you will need to set the environment variables below on the workstation that is experiencing the issue:

1. In Windows create a folder, with the following name, for example: C:\schedulerlogs
2. Click the Start button
3. Right click Computer and select Properties
4. In System screen, please select Advanced System settings
5. Click the Environment Variables button
6. Repeat the following for all three variables below: (7a - 7c)
   
   
   1. In the System Variables section choose New
   2. Variable Name will be the value to the LEFT of the = sign below
   3. Variable Value will be the value to the RIGHT of the = sign below
   4. Click OK

1. The three environment variables (please note we are using the folder name we created in 1.)
   
   
   1. SCHED_FORK_OUTPUT = TRUE
   2. SCHED_OUTPUT_FILE = c:\ schedulerlogs \schedLoggingOutput.txt
   3. _schedlogging_ = c:\ schedulerlogs\schedLoggingInput.txt

1. Once done, click OK, and OK to save the changes.
   
   
2. Once these environment variables are set (you can check by typing "set" at the command prompt) open your preferred scheduler (MSP or OWB).
   You may try saving some project back to Clarity in order to verify the logs are created before going further, and then replicate the error. If the logs are not generated, you may want to double check the environmental variables are set correctly, and if everything is fine, restart your workstation before replicating the error.
   
   
3. Reproduce the issue, and once reproduced please send the two files below to Clarity Support as requested:
   
   c:\ schedulerlogs \schedLoggingOutput.txt
   c:\ schedulerlogs\schedLoggingInput.txt

Notes:
The logs could get overwritten while opening projects: you may want to delete the files before replicating the error in order to get only fresh and relevant data.
The Input file will show data fetched by MSP/OWB from the database.
The Output file will show data saved by MSP/OWB back to the database.

**********

Also, check this:

RE: OWB Issue

NJ

If OWB unexpectedly asks for a Save As, you should NOT do so, as it will treat the 'save as' as a save of a NEW project over an existing and try to delete everything that already exists on the project in Clarity before saving the data from your OWB session.  You can lose baselines among other data if this happens.

Save the project locally as an MRP to save your changes and then reopen the plan from Clarity and compare to the RMP.

Usually this happens if you lost the session or someone cleared your project Lock within Clarity.

If you not saving regularly while working in an OWB plan, you can lose the session and OWB doesn't always play nice when it captures a new one.

Jenn