cancel
Showing results for 
Search instead for 
Did you mean: 

Error 500 - Internal Server error on sending DCN

markteichmann
Product and Topic Expert
Product and Topic Expert
0 Kudos

Since the upgrade of our SUP servers to 2.2.2 I cannot send DCNs anymore. Even if I try to send them in my browser I always get error 500 (Internal Server Error). The error exists on our development server and also on my local SUP server. Therefore it looks like a changed setting because of the server upgrade.

I am using the HttpAuthDCNServlet, I am using the same syntax as I used for old version 2.1.3. If I omit any parameters I get status 200, e.g.

http://myserver:8000/dcn/HttpAuthDCNServlet

Do you have any idea what changed after upgrading the servers? I also followed the hints in the document Debugging DCNs but had no trace of the error until now.

My call looks like this:

http://myserver:8000/dcn/HttpAuthDCNServlet?cmd=dcn&domain=test&package=moma4:2.0

Content-Type is application/json, I use Basic Authentication using user@domain with a valid password and POST for submitting.

In the body I have the following:

{   "pkg": "moma4:2.0",

    "messages": [

        {

            "id": "1 ",

            "mbo": "AlmOrder",

            "op": ":upsert",

            "cols": {

                "ORDERID": "000000503115",

                "START_DATE": "2013-02-21",

                "FINISH_DATE": "2013-02-21",

                "EQUIPMENT": "000000000010006698"

            }

        }

    ]

}

Now I could trace the following in the log:

The DCN Request in JSON as POST data is: null

Was there a change in the DCN syntax? I could not find anything regarding a change in the documentation.

Accepted Solutions (1)

Accepted Solutions (1)

markteichmann
Product and Topic Expert
Product and Topic Expert
0 Kudos

The issue was solved by SAP Support. You need a change in the web.xml in order to make this work again.

Ask for CR #734611-1 at SAP Support.

hofmann
Active Contributor
0 Kudos

Can you please share the change needed in the web.xml file so others can apply the fix instantly without waiting for SAP to respond?

markteichmann
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Tobias,

the patch was marked as Private Customer Patch. I don't know if I am allowed to share it in public?

hofmann
Active Contributor
0 Kudos

Well, in that case, I guess not 😞

But is it really just a web.xml change?

markteichmann
Product and Topic Expert
Product and Topic Expert
0 Kudos

Yes. You only need to add the following at the top of the web.xml of the dcn webapp 😉

  <context-param>

    <param-name>com.sybase.server.security.factory</param-name>

    <param-value>com.sybase.sup.server.dcn.DCNSecurityFactory</param-value>

  </context-param>

Cheers,  Mark

Answers (0)