Data Services Internal Server Error

[tania_burningham3]

I have install data services onto a netweaver app server instead of tomcat. I have deployed and I am able to see data services in the CMC. However, when I try to logon to dataservices through the url I am getting an internal server error 500. Looking at the default trace it appears I am missing configuration but cannot figure out where. Any help would be appreciated.

#2.0^H#2011 09 06 15:54:08:091#0-600#Error#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#

com.sap.ASJ.web.000137##JavaEE/DataServices#0050569A001E01270000000000002966#2223750000000004#JavaEE/DataServices#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0##D48CEBF0D8CF11E0C6150050569A001E#983644a0d8d211e0afb60050569a001e#983644a0d8d211e0afb60050569a001e#0#Thread[HTTP Worker [@71899727],5,Dedicated_Application_Thread]#Plain##

Cannot process an HTTP request to servlet [action] in [DataServices] web application.

[EXCEPTION]

java.lang.NoClassDefFoundError: com/acta/jcrypto/AwAdminBCMCryptoKey : cannot initialize class because prior initialization attempt failed

at com.acta.admin.AwAdminCMSConnection.setCMSPassword(AwAdminCMSConnection.java:80)

at com.acta.webapp.mdreport.struts.action.Logon.processLogon(Logon.java:246)

at com.acta.webapp.mdreport.struts.action.Logon.doExecute(Logon.java:98)

at com.acta.webapp.mdreport.struts.action.BaseAction.execute(BaseAction.java:409)

at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)

at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)

at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)

at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)

at com.acta.webapp.mdreport.servlet.EscapeFilter.doFilter(EscapeFilter.java:52)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:375)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:203)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:438)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:427)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

[Former Member]

For us, the error only went away after adding the BODS user in the cron.allow file (search DS install guide for unix). But this  only resolved the error in the web page (com/acta/jcrypto/AwAdminBCMCryptoKey : cannot initialize class because prior initialization attempt failed) The BOE scheduler and the BODS scheduler still cannot start the jobs. Probably this had to be done before installation and changing this afterwards will not solve the issue completely.

[Former Member]

Hello Tania,

I am experiencing exactly the same issue. Did you find any solution?

Best regards, Louis

[former_member230867]

Hi,

I am facing the same issue. Any resolution?

Erik.

[former_member230867]

Hi Tania,

we have managed to resolve the issue - in our case we were missing the $LINK_DIR variable in the starting profile for the user which is running the BO DS. We have added the variable manually and we were able to login and work normally in the DS Management Console.

Erik.

[Former Member]

Hi Erik,

What did you specify in the $LINK_DIR variable?

Thanks,

Ainsley

[Former Member]

Ok, I found in the Data Services admin guide what the $LINK_DIR should be set to.

[Former Member]

Hi,

I'm  facing exactly the same problem and I noticed $LINK_DIR variable was already set by installation but I'm still getting 500 internal server error. Any ideas would be appreciated.

Cheers,

Sesh

[Former Member]

I've fixed the issue now...thanks.

[Former Member]

Hi Sesh,

How did ou fix this issue? We have LINK_DIR set but still get the error. thanks

Aaron

[Former Member]

Hi Aaron,

I'd referred the following notes to fix the issue, hope it'll also help resolve yours.

1. SAP Note: 1638675 - HTTP Status 500 - The server encountered an internal error () when trying to logon to Management Console.

2. SAP Note: 1595850 - 500 Internal Server Error on logon to the Management Console - Data Services XI 4.0

Good luck!!

Cheers,

Sesh