It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×6,001
×3,952

question asked: Oct 11 '16, 6:27 a.m.
question was seen: 2,181 times
last updated: Jan 10 '17, 2:05 a.m.

Related questions

FAQ - How this Forum works

Error after login to CLM (DNG)"An error has occurred while processing a server request. The server returned this error code: 500"

0
David Beange (111●3●59●101) | asked Oct 11 '16, 6:27 a.m.
edited Oct 11 '16, 6:44 a.m.
After logging onto CLM V6.0 server and selecting a DNG project I get the following error and would like some guidance on it's resolution.


An error has occurred while processing a server request. The server returned this error code: 500

When i expand the error details it shows.
ID CRRRW7553E  A message that was received from the server indicates an error with no specific handler.
Unable to load https://n005125.portsmouth.uk.ibm.com:9445/rm/storedquery/GetUpdatedComments status: 500
_6@https://n005125.portsmouth.uk.ibm.com:9445/rm/web/_js/?include=A~&etag=FC73salU3os_en_US&_proxyURL=%2Frm&ss=JW4Zk&locale=en-us:2489:8 _6@https://n005125.portsmouth.uk.ibm.com:9445/rm/web/_js/?include=A~&etag=FC73salU3os_en_US&_proxyURL=%2Frm&ss=JW4Zk&locale=en-us:6187:1 _13@https://n005125.portsmouth.uk.ibm.com:9445/rm/web/_js/?include=A~&etag=FC73salU3os_en_US&_proxyURL=%2Frm&ss=JW4Zk&locale=en-us:6202:1

URL: https://n005125.portsmouth.uk.ibm.com:9445/rm/storedquery/GetUpdatedComments

Error 500: Internal Server Error

vvcConfigUrl must not be null (More info found at entry [6b9b670e7beb6069] in the RM application server log)

Version of tool.

rm version


RM Server Log details -

2016-10-11 10:59:45,991 [WebContainer : 18 @@ 10:59 MBoyle@uk.ibm.com <com.ibm.rdm.web.pages.showProjectDashboard@f264c231-0907-4d6c-810f-8d4d4f708ada> /rm/operations] ERROR m.ibm.rdm.fronting.server.services.RMBridgeService  - Service Error: Unable to resolve expected configuration.
2016-10-11 10:59:46,007 [WebContainer : 18 @@ 10:59 MBoyle@uk.ibm.com <com.ibm.rdm.web.pages.showProjectDashboard@f264c231-0907-4d6c-810f-8d4d4f708ada> /rm/operations] ERROR ibm.rdm.fronting.server.services.RMRestServiceBase  - CRRRS1007E  A problem occurred in the Requirements Management (RM) server: Entry [2212bd2c760b56dd]
com.ibm.rdm.fronting.server.exception.BadRequestException: Propagated exception; original message [Configuration uri must not be null]
    at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:243)
    at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:789)
    at com.ibm.rdm.fronting.server.exception.RRSException.capture(RRSException.java:793)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalServiceExchange.checkError(InternalServiceExchange.java:54)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalServiceExchange.getResponse(InternalServiceExchange.java:37)
    at com.ibm.rdm.fronting.server.rrs.operations.internal.OperationsRestService.doPost(OperationsRestService.java:131)
    at com.ibm.rdm.fronting.server.services.RMRestService.doPostInternal(RMRestService.java:89)
    at com.ibm.rdm.fronting.server.services.RMRestService.runInternalMethod(RMRestService.java:468)
    at com.ibm.rdm.fronting.server.services.RMRestService.handleMethod(RMRestService.java:397)
    at com.ibm.rdm.fronting.server.services.RMRestService.performService(RMRestService.java:333)
    at com.ibm.rdm.fronting.server.services.RMRestServiceBase.service(RMRestServiceBase.java:236)
    at com.ibm.rdm.fronting.server.services.RMBridgeService.service(RMBridgeService.java:131)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
    at com.sun.proxy.$Proxy146.service(Unknown Source)
    at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doRestService(AbstractTeamServerServlet.java:970)
    at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2521)
    at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:2316)
    at com.ibm.team.repository.servlet.AbstractTeamServerServlet.access$0(AbstractTeamServerServlet.java:2301)
    at com.ibm.team.repository.servlet.AbstractTeamServerServlet$1.service(AbstractTeamServerServlet.java:246)
    at com.ibm.team.repository.service.internal.compatibility.auth.DelegatedAuthHandler$1.run(DelegatedAuthHandler.java:250)
    at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleAuthentication(AbstractTeamServerServlet.java:2019)
    at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1769)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
    at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
    at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
    at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
    at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1232)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:781)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:480)
    at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97)
    at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165)
    at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107)
    at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3926)
    at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1007)
    at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:287)
    at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1049)
    at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:643)
    at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
    at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)
Caused by: com.ibm.rdm.fronting.server.exception.BadRequestException: Configuration uri must not be null
    at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:243)
    at com.ibm.rdm.fronting.server.exception.RRSException.newBadRequestParametersException(RRSException.java:125)
    at com.ibm.rdm.fronting.server.exception.RRSException.newBadRequestException(RRSException.java:133)
    at com.ibm.rdm.fronting.server.rrs.operations.internal.CheckPermissions.executeServiceRequest(CheckPermissions.java:105)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalDefaultPartitionerFactory$1ExecuteServiceRequest.call(InternalDefaultPartitionerFactory.java:29)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalDefaultPartitionerFactory$1ExecuteServiceRequest.call(InternalDefaultPartitionerFactory.java:1)
    at com.ibm.rdm.fronting.server.core.spi.DefaultPartitionerFactory$1DefaultExecutor.call(DefaultPartitionerFactory.java:76)
    at com.ibm.rdm.fronting.server.core.spi.DefaultPartitionerFactory$1DefaultExecutor.call(DefaultPartitionerFactory.java:1)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.handleExecutables(InternalCoreServices.java:704)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:402)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.executeRequestSequences(InternalCoreServices.java:1134)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.handleRequestSequences(InternalCoreServices.java:1082)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:357)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:253)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:246)
    at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.bulk(InternalCoreServices.java:232)
    at com.ibm.rdm.fronting.server.core.CoreServices.bulk(CoreServices.java:144)
    at com.ibm.rdm.fronting.server.core.CoreServices.bulk(CoreServices.java:68)
    at com.ibm.rdm.fronting.server.rrs.operations.internal.OperationsRestService.doPost(OperationsRestService.java:123)
    ... 63 more
IServiceRequests
    CheckPermissions.INTERNAL <com.ibm.rrs.team.saveArtifact,null,https://n005125.portsmouth.uk.ibm.com:9445/rm/process/project-areas/_WGXq0HmOEea6OOsTXLjtNA>
    OperationsService.REPORT <com.ibm.rrs.team.saveArtifact,null,https://n005125.portsmouth.uk.ibm.com:9445/rm/process/project-areas/_WGXq0HmOEea6OOsTXLjtNA>
Request
    --Not Provided--
Response
    --Not Provided--



Accepted answer

0
permanent link
Donald Nong (14.5k●4●14) | answered Oct 11 '16, 8:24 p.m.
This looks to be the exact same problem as this one, although I don't know how it was resolved eventually. Do check out Mike's answer there.
https://jazz.net/forum/questions/205309/rtc-6-crrrw7553e-a-message-that-was-received-from-the-server-indicates-an-error-with-no-specific-handler

This means that you can try to apply the latest iFix (newer than 003, which includes Maintenance Item 363620) and see if it resolves the issue.

Alternatively, you can try the solution in this technote.
http://www-01.ibm.com/support/docview.wss?uid=swg21977030
David Beange selected this answer as the correct answer
Comments
David Beange commented Oct 12 '16, 9:37 a.m.

Great, Thanks for the response. We have run the repotools re-index and that has resolved the problem for now. But should it reoccur as is suggested we shall look at deploying the ifix.

Mathieu Defianas commented Jan 09 '17, 10:20 a.m.

Hello,
I have installed the last version 6.0.3 and I have the same problem ... Problem : there is no iFix and the reindex doesn't resolve the problem
Have you got an idea ?

Donald Nong commented Jan 09 '17, 7:30 p.m.

It's likely a new issue and you should open a new post, or contact IBM Support. I see that you also posted to the resolved Maintenance Item 363620, and I doubt that anybody is still tracking it.

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Mathieu Defianas (159●4●28●38) | answered Jan 10 '17, 2:04 a.m.

I have found my problem.
DNG is not compatible with nginx ... I have adapted the reverse proxy configuration following this link :
https://jazz.net/wiki/bin/view/Deployment/ConfiguringNGINXReverseProxy

Your answer

Register or 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.