cancel
Showing results for 
Search instead for 
Did you mean: 

MDM WebServices Problem while connecting to MDM repository

Former Member
0 Kudos

Hello,

we have installed the Web Services for MDM.

When I test the Services, say the MDMSearchRecords I always get a ERROR status and the Message:

id (String) WS_LogonProblem

severity (String) ERROR

text (String) Problem while connecting to MDM repository: z_Material on server: debmu416.server..... at port: 4000. Maybe the Repository-Information has not been set correctly at the requested query.

status (String) FAIL

The Repository Information I try to connect with is correct (Repository Name, Server Name, Port, data Language and schema Language).

Can you pls tell me where the problem could be?

Points will be generously rewarded!

Best Regards,

Mircea

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member206107
Active Participant
0 Kudos

Are you using the same version of MDM Server, MDM Java APIs and MDM Webservices ?

Former Member
0 Kudos

Hi Arun,

Thanks a lot!

you were right! The WebServices version was too old.

Now I can connect to the Repository in Test mode.

I get some other error Messages, like "Field Material_Number is not defined at Table Products." and "Repository Data is not available in the requested Language ." which isn' right.

Do you have a clue where this could come from?

BR,

Mircea

Former Member
0 Kudos

Hi Mircea,

Can you just check weather Field Material_Number exists in your Repository.

This error comes when field doesnot exists in the main table of the repository.

Field code of the field also should be the same.

Thanks and Regards.

Shruti.

Former Member
0 Kudos

Hi Shruti,

the field is there.

Thanks and regards,

Mircea

Edited by: Mircea Precup on May 27, 2008 12:33 PM

former_member206107
Active Participant
0 Kudos

Can you please check your language setting again and make sure there is a space between the language and the country. For eg., English [US].

If you supply the string as English[US] (No space between English and [US] ) , it throws an error.

Best regards,

Arun prabhu S

Former Member
0 Kudos

Hi Arun,

there is a space between English and [US].

Thanks and BR,

Mircea