Can't load dashboard after migrating to RTC 3.0.1.2

Hi Milan,

I apologize for the poor error message. This error could happen is if the user account you're logged in with does not have the JazzUsers or JazzAdmins repository role or a valid license on the Jazz Team Server. Unlike most other components, all dashboard resources are stored on the JTS so there must be a valid user there as well.

Since you're able to view the Web UI on the RTC server, it sounds like it may be either a user synchronization or configuration problem on the JTS. I recommend logging in to the JTS with the same user and look at your user profile to confirm you have a valid repository role assigned and a valid, non-expired license. If you don't, check the logs for user sync problems and check the JTS config to make sure it's pointing to the correct LDAP server or whatever authentication setup you have. You should probably experience the same problem if you're trying to modify your personal dashboard (you may get a better explanation of the error in this case).

Let me know if this is the problem or not.

Hi Milan,

I apologize for the poor error message. This error could happen is if the user account you're logged in with does not have the JazzUsers or JazzAdmins repository role or a valid license on the Jazz Team Server. Unlike most other components, all dashboard resources are stored on the JTS so there must be a valid user there as well.

Since you're able to view the Web UI on the RTC server, it sounds like it may be either a user synchronization or configuration problem on the JTS. I recommend logging in to the JTS with the same user and look at your user profile to confirm you have a valid repository role assigned and a valid, non-expired license. If you don't, check the logs for user sync problems and check the JTS config to make sure it's pointing to the correct LDAP server or whatever authentication setup you have. You should probably experience the same problem if you're trying to modify your personal dashboard (you may get a better explanation of the error in this case).

Let me know if this is the problem or not.

Hi Curtispd,

First, I will let you know in my jobs which were done before this happeened:

First, I had a JTS 3.0 ifix1 with RTC at win server 2003. Then, I moved it to another machine, restoring all staff from db2 backup. Everything was fine until I tried to reach /jazz application from jts part and reverse. I got message about:

A problem communicating with the Jazz Team Server discovery service has prevented the home menu from loading. Your Jazz Team Server may be configured incorrectly.

Then, I found this post, and followed the steps to solve the problem:

https://jazz.net/forums/viewtopic.php?p=54923

it's last comment, by benjamin I think.

Then, when I passed all the steps, I could communicate from jts part to /jazz and reverse, but I couldn't reach any dashboard anymore. I got the message which I mentioned in first post.

I am JazzAdmin, and I think this doesn't matter and it's not connected with my problem.

I assume that I delete consumer key of dashboard before I exported it and retrieved.

What do you think?
Is this recoverable?

Thanks,
W

Yes it's definitely recoverable - the data is still there it's just not able to get to it. We have to figure out why the JFS storage service is not allowing your user to get the data.

I mentioned the JazzAdmin/JazzUser because the CCM app and JTS can have separate LDAP configurations or may have user synchronization problems that would cause the contributor account copy on CCM to be fine but to be missing or incorrect on the JTS, which would manifest itself. That's why I wanted you to check on the JTS specifically, because that's the server where it's failing.

One other possible reason for the 403 response is that the consumer key doesn't match the storage area. This is a security feature in the storage service that sandboxes component data. If you've deleted the com.ibm.team.dashboard consumer key, it will automatically generate a new one and they will no longer match, and this will happen. The fix here is to recover the old consumer key, as was described by Benjamin in that post you linked.

You may be able to get more details about the 403, such as the reason for it, if you go to your personal dashboard and try to modify it, then expand the details section in the error message. Or, you may need to install Firebug and inspect the 403 response body to see what the message was.

Yes it's definitely recoverable - the data is still there it's just not able to get to it. We have to figure out why the JFS storage service is not allowing your user to get the data.

I mentioned the JazzAdmin/JazzUser because the CCM app and JTS can have separate LDAP configurations or may have user synchronization problems that would cause the contributor account copy on CCM to be fine but to be missing or incorrect on the JTS, which would manifest itself. That's why I wanted you to check on the JTS specifically, because that's the server where it's failing.

One other possible reason for the 403 response is that the consumer key doesn't match the storage area. This is a security feature in the storage service that sandboxes component data. If you've deleted the com.ibm.team.dashboard consumer key, it will automatically generate a new one and they will no longer match, and this will happen. The fix here is to recover the old consumer key, as was described by Benjamin in that post you linked.

You may be able to get more details about the 403, such as the reason for it, if you go to your personal dashboard and try to modify it, then expand the details section in the error message. Or, you may need to install Firebug and inspect the 403 response body to see what the message was.

Hi curtispd,

These are the firebug results error:

return this._insert({domNode:_7,_isButton:true,args:_6},_6.index);
?inclu...0_en_US (line 8037)
GET https://server:9443/jazz/ser...oardRestService/dashboard?projectName=Project

500 Internal Server Error
560ms
ParamsHeadersResponseJSON

{"errorClass":"com.ibm.team.jfs.app.http.HttpInternalServerErrorException","errorCode":500,"errorTraceMarshall":,"errorTrace":,"errorMessage":"Internal Server Error\nUnexpected response code 403 while fetching indexTime resource"}



no element found
_update(_25=true, _26=null, _27=true)?inclu...0_en_US (line 15502)
_setScope(_3b=Object { provider=, scope={...}, focusText=false})?inclu...0_en_US (line 15656)
_parseProviders()?inclu...0_en_US (line 15253)
postCreate()?inclu...0_en_US (line 15202)
create(_f=Object { _bannerSearch=true, defaultProvider=, providers=}, _10=undefined)?inclu...0_en_US (line 1246)
postscript(_d=Object { _bannerSearch=true, defaultProvider=, providers=}, _e=undefined)?inclu...0_en_US (line 1206)
toString()?inclu...0_en_US (line 17)
_createSearchBox()?inclu...0_en_US (line 15997)
(?)()?inclu...0_en_US (line 15978)
toString()?inclu...0_en_US (line 17)
_18()?inclu...0_en_US (line 11666)
_1d()?inclu...0_en_US (line 11736)
onload()?inclu...0_en_US (line 11726)
if(_28&&((this._currentQuery!=this._lastQuery)||_25)){
?inclu...0_en_US (line 15502)


"NetworkError: 500 Internal Server Error - https://server:9443/jazz/service/com.ibm.team.dashboard.common.internal.service.IDashboardRestService/dashboard?projectName=Project"


no element found
no element found
no element found
no element found
Error: Unable to load /jazz/web/dojo/../../service/com.ibm.team.dashboard.common.internal.service.IDashboardRestService/dashboard?projectName=Project status:500
(undefined="")?inclu...0_en_US (line 17)
()?inclu...0_en_US (line 17)
(undefined="100")?inclu...0_en_US (line 17)
(function(){var _1=null;if((_1||(typeo...etTimeout(dojo._loadInit,1000);}})();
?inclu...0_en_US (line 17)


Regards,

Yes it's definitely recoverable - the data is still there it's just not able to get to it. We have to figure out why the JFS storage service is not allowing your user to get the data.

I mentioned the JazzAdmin/JazzUser because the CCM app and JTS can have separate LDAP configurations or may have user synchronization problems that would cause the contributor account copy on CCM to be fine but to be missing or incorrect on the JTS, which would manifest itself. That's why I wanted you to check on the JTS specifically, because that's the server where it's failing.

One other possible reason for the 403 response is that the consumer key doesn't match the storage area. This is a security feature in the storage service that sandboxes component data. If you've deleted the com.ibm.team.dashboard consumer key, it will automatically generate a new one and they will no longer match, and this will happen. The fix here is to recover the old consumer key, as was described by Benjamin in that post you linked.

You may be able to get more details about the 403, such as the reason for it, if you go to your personal dashboard and try to modify it, then expand the details section in the error message. Or, you may need to install Firebug and inspect the 403 response body to see what the message was.

Hi curtispd,

These are the firebug results error:

return this._insert({domNode:_7,_isButton:true,args:_6},_6.index);
?inclu...0_en_US (line 8037)
GET https://server:9443/jazz/ser...oardRestService/dashboard?projectName=Project

500 Internal Server Error
560ms
ParamsHeadersResponseJSON

{"errorClass":"com.ibm.team.jfs.app.http.HttpInternalServerErrorException","errorCode":500,"errorTraceMarshall":,"errorTrace":,"errorMessage":"Internal Server Error\nUnexpected response code 403 while fetching indexTime resource"}



no element found
_update(_25=true, _26=null, _27=true)?inclu...0_en_US (line 15502)
_setScope(_3b=Object { provider=, scope={...}, focusText=false})?inclu...0_en_US (line 15656)
_parseProviders()?inclu...0_en_US (line 15253)
postCreate()?inclu...0_en_US (line 15202)
create(_f=Object { _bannerSearch=true, defaultProvider=, providers=}, _10=undefined)?inclu...0_en_US (line 1246)
postscript(_d=Object { _bannerSearch=true, defaultProvider=, providers=}, _e=undefined)?inclu...0_en_US (line 1206)
toString()?inclu...0_en_US (line 17)
_createSearchBox()?inclu...0_en_US (line 15997)
(?)()?inclu...0_en_US (line 15978)
toString()?inclu...0_en_US (line 17)
_18()?inclu...0_en_US (line 11666)
_1d()?inclu...0_en_US (line 11736)
onload()?inclu...0_en_US (line 11726)
if(_28&&((this._currentQuery!=this._lastQuery)||_25)){
?inclu...0_en_US (line 15502)


"NetworkError: 500 Internal Server Error - https://server:9443/jazz/service/com.ibm.team.dashboard.common.internal.service.IDashboardRestService/dashboard?projectName=Project"


no element found
no element found
no element found
no element found
Error: Unable to load /jazz/web/dojo/../../service/com.ibm.team.dashboard.common.internal.service.IDashboardRestService/dashboard?projectName=Project status:500
(undefined="")?inclu...0_en_US (line 17)
()?inclu...0_en_US (line 17)
(undefined="100")?inclu...0_en_US (line 17)
(function(){var _1=null;if((_1||(typeo...etTimeout(dojo._loadInit,1000);}})();
?inclu...0_en_US (line 17)


Regards,

Hi curtispd,

I solved the problem. I exported all consumers keys, and actually, I had two *.dasboard consumer keys... in exported list, there was a wrong consumer key. I replaced it with real (which was created by RTC), then imported keys again, and dasboards are solved.

I have not errors any more.

Thanks, and regards,

Thanks. I've looked into it a little more and am now fairly convinced it's related to the deletion of the dashboard consumer key. I can reproduce the error by deleting it.

It seems the dashboard consumer key is still not correct. The com.ibm.team.dashboard key must be the same as it was before on your 3.0 ifix1 server. You can see the keys in the JTS's admin UI under Server / Consumers (Inbound) / Authorized Keys section. The goal is to arrive at a single com.ibm.team.dashboard key that has the same value as your old server has. Make sure there aren't multiple keys by this name. If you can still run your old server, I recommend checking the value of the key so that you can tell whether it's right or not.

As for fixing it, you may be able to do it manually by editing the incorrect key or creating a new one by pasting the value from the old server. Or, you may need to repeat the steps for importing the keys for the dashboard key only.

It is also worth noting that the admin UI, since 3.0.1, will now prevent users from deleting these "system" keys in order to prevent such problems in the future. I'm not aware of any reason why they would need to be deleted under normal scenarios.