Data Manger error: the system cannot find the file specified.

[Former Member]

Hi,

I am using VPN to connect to MDM repository and get error:

the system cannot find the file specified. Windows sockets error code 2. And forced exit data manager. However I can login the other repository on the MDM server. Can you suggest any way to fix? Thanks!

David

[Former Member · Accepted solution]

Hi,

If it is happening only for specific repository.

Check the following.

1. Make sure the repository u are trying to connect is loaded and running.

2. Check if the repository has any errors.

By right click on the repository and select

"Verify repository->Check".

Thanks and Regards

Subbu

[Former Member · Accepted solution]

Hi Subbu,

Before I tried to log on Data Manager, I checked:

1. repos is up and running

2. I tried to check (no error), repair, re-index

But still have the problem. I also tried to create new ids, it doesn't work either.

Thanks,

David

[Former Member · Accepted solution]

Hi David,

Are you able to access any other repository on the MDM Server thru VPN, except the one with which you are getting the error ?

Thanks and Regards

Subbu

[Former Member · Accepted solution]

Yes, I can access another repos on that server, but all the other repos give me the access error. Any other suggestion?

Message was edited by: David

[Former Member · Accepted solution]

David,

I don't really understand the error that you are getting: "<i>Yes, I can access another repos on that server, but all the other repos give me the access error"</i>". Is there any problem with your VPN?? Try to ping your server from your machine via command prompt and let us know the result.

Regards,

Rajani

[Former Member · Accepted solution]

Hi David,

If you are not able to access all the repositories on the MDM Server <b>thru VPN</b>, then I am sure its a problem with the <b>VP</b>N, not with MDM.

Thanks and regards

Subbu

[Former Member · Accepted solution]

Hi Rajani and subbu

The situtation is:

- I can ping the server and get response back.

- I can access the repository via Import manager.

- I can only access one repostitory on that server, but not other repositories. All those repositories are giving me error message:

the system cannot find the file specified, and sockets error.

Based on these, I doubt I have problem with VPN as I can at least access one of the repository. But I am not sure what kind of socket problem it could be. And the error says: cannot find the file specified. What kind of system file DM is looking for?

Thanks,

David

Message was edited by: David

[Former Member · Accepted solution]

Hi David,

Its strange.

What I could think of is

Does the VPN is blocking the port number on which the other repositories are running ?

Thanks and Regards

Subbu

[Former Member · Accepted solution]

Hi Subbu, but I have no problem to use import manager to access that repository,which gives me problem in Data Manager. Anyway, how do I check if VPN block the port# of that repos?

Thanks,

David

[Former Member · Accepted solution]

David,

Hmmmm!!

I have a question.

Are you using the standard repository or Did you create any new repository and trying to access thru VPN.

Thanks and Regards

Subbu

[Former Member · Accepted solution]

The repos type is normal, was created by admin in local. I was able to access it from Data manager thru VPN a few days ago. But I had this problem for days now.

What do yo mean by a standard repository?

Thanks,

David

[Former Member · Accepted solution]

David,

SAP delivers 5 standard repositories along with the software bundle.

1. Employee

2. Customer

3. Articles

4. Materials

5. Vendors

Thanks and Regards

Subbu

[Former Member · Accepted solution]

David,

Can you try to uninstall and re-install Data Manager and check?

Regards,

Rajani Kumar

[Former Member · Accepted solution]

This repos is a custom repos. Not a SAP standard one, then.

[Former Member · Accepted solution]

Hi Rajani,

I tried to reinstall Data Manager. Not working. I will try it again.

Thanks,

David

[Former Member · Accepted solution]

Removed DM and re-installed DM, still have the same issue.

I tried to reward points to you but can't find the radio buttons any more. Next time I will assign points ASAP. Thanks for helping!

David

Message was edited by: David

[Former Member · Accepted solution]

It really does sound as if you are having a problem with ports. If you are able to connect to even one repository, then the problem is not with the Data Manager.

Here is how you can check:

1) Open the MDM Console, and note the port numbers of the loaded repositories.

2) Now open a Command Prompt window and type the following command:

telnet [mdm server] [repository port]

(you can use either the machine name or IP address for mdm server).

For example:

telnet 10.20.30.40 5500

You should get an empty command-type window with no error messages. This indicates success. You can close the window by clicking on the "X". Try this with the one repository which works in the DM, and then with the other repositories.

Let us know the results,

Walter

[Former Member · Accepted solution]

Hi Walker,

Thanks for your suggestion.

Before I run telnet. I ping the MDM server. Connection is good.

Then I run telnet with ip and port. It shows a strange character(unreadable Ñτô&#9565;), and append it after a few seconds=> Ñτô&#9565;Ñτô&#9565;Ñτô&#9565;Ñτô&#9565;Ñτô&#9565;Ñτô&#9565;Ñτô&#9565;. When I type any key, it disconnect: connection to host lost.

David

[Former Member · Accepted solution]

David,

As Walter and Subbu pointed out, there may be a problem with your ports. If you have access to your server, you can also check the ports that are in use by typing <b>netstat -a</b> (I am assuming that you are using windows box).

Try to change the port assigned to the repository to any other number between 2000 to 9999. Make sure the port number you choose is not in use, as well as port number1 and port number2. Refer to <a href="http://help.sap.com/saphelp_mdmgds55/helpdata/EN/8e/9f9c427055c66ae10000000a155106/frameset.htm">Console documentation</a> for further details.