Win 32:ACCESS_VOILATION while import

[Former Member]

Hello Experts,

We have upgraded MDM to 7.1 SP04.

After that all import xml's are going to Archive without any changes in MDM data.

At console > import server log, there is an error saying 'Win 32:ACCESS_VOILATION'.

Any idea about how to solve this error?

[Former Member · Accepted solution]

Hi Shailesh,

Please verify->check your repository it may have either Fatal or Non-fatal errors.

To fix this issue, In console Right click on your unloaded repository>Verify Repository>Repair.

Just check and revert with result.

Regards,

Mandeep Saini

[former_member205403 · Accepted solution]

Hi Shailesh,

I came across this page which details about your Windows error:

http://www.support.tabs3.com/main/R10309.htm

As per explanation, we get Access_Violation error if any thread tries to read from or write to a virtual address for which it does not have the appropriate access.

I agree with Mandeep, and it may be because of Fatal/ Non Fatal errors in the repository. Please check by repairing repository and let us know the result.

BR,

Shiv

[Former Member · Accepted solution]

Hello Mandeep,

Thanks for your reply...

We tried verify > Repair, which shows 0 errors (both fatal & non-fatal) and 0 warnings.

Still the problem is there...

We can able to import record by manually executing map in import manager.

But automatic import via import server moves files from ready to archive without any modification in repository.

And automatic import logs this message of Win 32 error.

- Shaailesh.

[former_member182007 · Accepted solution]

Hi,

Can you validate your User/Role and other security settings. if you are using LDAP environment for Administration, please verify all the user and roles. make sure you are login with right user have sufficient role to access a particular application.

it can be authorization issue. after that also verify and repair the repository.

Hope it help.

Deep

[Former Member · Accepted solution]

Hi Shaileesh,

This issue is fixed in MDM 7.1 SP04 Patch18 (build 7.1.04.144).

Please refer [SAP Note 1477199 - MDIS shutdown caused MDIS to crash with ACCESS_VIOLATION|https://websmp130.sap-ag.de/sap/support/notes/1477199]

Kindly update the status of thread.

Regards,

Mandeep Saini

[Former Member · Accepted solution]

Hello Mandeep,

Thanks for the update.

Well we raised message with SAP.

As per SAP this issue was because of selecting custom port numbers while installing MDM components using SAPInst.

We reinstalled MDM components with default ports, and its working fine now.

[former_member205403 · Accepted solution]

Shailesh,

Thanks a lot for sharing information.

Best regards,

Shiv

[Former Member · Accepted solution]

Here is the reply we got from SAP...

The problem caused apparently due to the
following error:
"The specified value for the Server Listening Port (0) is outside the
range of available listening ports for system use. Please use only
values between 49152 and 65535."
Please refer to MDM 7.1 SP04 release note 1432315 and SAP Note 1359600
which mentions the change in the listening ports.

And here are links mentioned above.

[https://service.sap.com/sap/support/notes/1432315]

[https://service.sap.com/sap/support/notes/1359600]

Thanks Experts for all of your suggestions and replies.