Error The attempt to connect to the server failed [0xc0045013]

Getting a heap of these errors in the event log
Event Type: Error
Event Source: Enterprise Vault
Event Category: File Placeholder Service
Error The attempt to connect to the server failed [0xc0045013]

Running Enterprise Vault Version: 8.0.1.1560
Any suggestion to quickly sort these errors?
Cheers
rOB
1 Solution

Accepted Solutions
Accepted Solution!

Fixed

It was a host file on the file server with the wrong ip for the Ev server.
Thank you for assitance.
Cheers Rob
9 Replies

Can you log in to the File

Can you log in to the File server as the Vault service account and verify the web app url for EV is in the local intranet zone?
For the best O365 Reporting Solution click here Radar-Reporting

Can you log in to the file server

Yes Tony i can and it was not added to the local internet zone.
So i have added it now.
Cheers Rob

Rob, Did that solve the

Rob,

Did that solve the issue?

Cheers,

For the best O365 Reporting Solution click here Radar-Reporting

Error

No still the same i have even tried rebooting both servers no joy.

When you look at the error

When you look at the error message generated in the event log it should give you a URL. Does this URL point to localhost or the evservers DNS Alias?
This type of issue is either pretty easy to fix or can be an absolute minefield where information is missing, for example, but you need to setup a DTRACE of the retrieval process and see where it is going wrong so I would recommend opening up a support case.

URL

Paul,
The URL points to the DNS Alias.(if this suggests an easy fix that would be nice)

I will setup a dtrace of the retrieval process and see what is going on.

a support case might be the way forward.

Thanks

Robert Can you log onto the

Robert

Can you log onto the Fileserver with the Vault Service Account, grab the mentioned URL, and paste it into Internet Explorer?
Does this work, or is there any error message?

Cheers

Quadrotech - EV Migration and Office 365 Solutions, creators of Archive Shuttle.

No the other way I am afraid.

No the other way I am afraid. If it was localhost then that would have been an issue.

Michael has pointed out another troubleshooting step and also a secondary one would be to see if you can pull the offending item from one of the search applications.

If you can then this would indicate that there is either something malformed within the placeholder or the placeholder service itself.

I am presuming that not all items are exhibiting this behavior which would indicate an issue with the individual placeholder. If you can restore via search and rearchive to recreate the placeholder and see if it is formed properly this time.

After the above it is probably case opening time.
Accepted Solution!

Fixed

It was a host file on the file server with the wrong ip for the Ev server.
Thank you for assitance.
Cheers Rob