cancel
Showing results for 
Search instead for 
Did you mean: 

MDM Client crashes frequently

Former Member
0 Kudos

We continue to struggle with the import manager and data manager clients crashing. There seems to be no pattern to when it just disappears with no error message or warning.

We are on the latest build 5.5.63.73.

We are on the initial implementation and about to turn over to the business who is lukewarm at best and having the client crashing many times a day will not be popular.

Any help is appreciated. I am going to post an OSS note as this forum does not seem to be monitored by SAP.

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

please check the memory sizing for the machine on which you are using the client,

let us know what is the platform you are on, and in which scenario is it failing, like is it failing at matching, with memory out error

or is it is failing just when import started, test the connection between client m/c and MDM server.

Are you attempting parallel loads?

-Sudhir

Former Member
0 Kudos

Thanks

Windows Server 2003 SP2

32 GB memory

Local database IBM DB2 9.1

Connecting locally via mstsc

We are doing single imports with the source being local Access MDB of just 5000 records. It occurs on execute of import.

Nothing exotic here

Appreciate the help

Former Member
0 Kudos

good to know , it is Windows!

Can you check windows system log to see why the application terminated ?

Good Number os reasons why Import manager can crash,

wonder whats going on with Data Manager.

Former Member
0 Kudos

Hi Lee,

Just a small check.

Please verify that your MDM server build is exactly matching with the GUI build version.

You can go to Data manager->Help->About data Manager.

You will find the version and trhe Build version there.

You can verify with the Build Version of the MDM server that you have mentioned ( Seen in console).

This problem might be due to the Mismatch of the Build Version of the MDM server & the GUI's used.

If found any, please upgrade it and match it correctly.

If not, then do raise an OSS note. Might be a problem with the Latest build.

Hope it helps.

Thanks and Regards

Nitin jain