Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

RTC: saving project fails with "invalid UUID"

Hi

I created a new user account and tried to add it to the members of one of our projects. When attempting to save the project it fails with:

Saving project area failed.

invalid UUID [http://schnwa6042:9080/jazz/_MNP7sBalEeKZu-f1CdVM0g]

I've read somewhere that the "_" character in the UUID could be the problem? But obviously I have no influence over the generated UUID...

RTC version is 2.0.0.2 iFix3

Any help is really welcome!

Thanks, Dominique

1

2 votes

Comments

I see the problem now also on the newest update of the supported Firefox ESR Version 10. Update 10.0.10.

Anybody else has the same problem?


Accepted answer

Permanent link

I had last week similar problem with V.3.0.1.4 and reported a defect in jazz.net:

[Work Item 236526]: Saving project area failed on a very new created project

Yesterday I investigate a bit more and saw, I have the problem only with Firefox, not with IE and Chrome.

I'm using FF16.0.1, IE8 and Chrom 22.0.1

I asked some collegues to do the same, and do not see the problem.

If I remember I got the problem about a week ago first time. This is more or less the time when I got the Firefox upgrade from V.15 to V.16. (I know only the FF ESR is supported).

I will downgrade tody my Firefox and test again.

Jared Burns selected this answer as the correct answer

7 votes

Comments

I have now done the tests with Firefox Versions, and it is clear it is the upgrade from Firefox 15 to 16:

- Deinstall Firefox 16.0.1
- Install Firefox ESR 10
- Edit Project Area and add a member
- Save
=> OK!

- Desinstll Firefox ESR 10
- Install Firefox 16.0.1
- Edit Project Area and add a member
- Save
=> ERROR uuid...!

1 vote

Thanks for all of the research and information you've included.

I have seen this happen on FF 16.  There appears to be a bug in the Javascript support somewhere. I can see a variable on the right hand side of an assignment with one value and on the left with a different (invalid) value.

Firefox 16 is not a supported browser and has not been fully tested with RTC. FF 10 ESR is the latest supported version of Firefox.

Martha (Ruby) Andrews

Jazz L3 Developer

I see the problem now also on the newest update of the supported Firefox ESR Version 10. Update 10.0.10.

Anybody else has the same problem?

I retested with several PC's.

Firefox ESR 10.0.10 is WORKING correctly. So ignore my comment above.


8 other answers

Permanent link
Kristen, The fix is not included into 3.0.1.5. You need a hotfix for this version.

0 votes


Permanent link
Kristen, If you would like to have the fix on top of 3.0.1 you can consider opening PMR requesting for hotfix. Please attach also information what is the reason why you cannot upgrade to 4.0.1.

0 votes


Permanent link
The issue has been fixed in CLM 4.0.1.

0 votes

Comments

Are there any plans to include the fix in the RTC 3.0.1.x stream? We're not in a position where we can upgrade to 4.0. 

Thanks, that may be the best option for us. Just to be certain, is the fix included in 3.0.1.5 or would we need a hotfix for that version too?  


Permanent link
Went to FF ERS 10 and working ok now. What a pain.
Thank god i found this post, just wasted a lot of time with this issue.
Let us hope it goes better from now on :-)

0 votes


Permanent link
Same problem encountered with Firefox 16.0.2 while trying to save team & project areas.
Is there any planned issue with those latest versions of Firefox ?

Thanks

Cédric Ferchal

0 votes

Comments

Yes, this is fixed in 4.0.1. See [Work Item 236526]: Saving project area failed on a very new created project

Ruby
Martha (Ruby) Andrews
Jazz L3 Developer

1 vote

Thank you for your answer.

Cédric Ferchal


Permanent link
Thanks for that tip!

I would have never suspected the browser being an issue :-) But I can confirm that with internet explorer 8 it seems to work. Normally I'm using firefox (current versin 16.0.1) and it was with this browser when I detected the problem.

0 votes


Permanent link
We also have reports of this with FF 18

1 vote


Permanent link
I ran into the same error with FF16 downgrading to FF15 corrected the problem

1 vote


Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 343
× 21
× 9

Question asked: Oct 15 '12, 5:02 a.m.

Question was seen: 15,833 times

Last updated: Jan 30 '13, 7:50 a.m.

Confirmation Cancel Confirm