The Remote Prodecure Call Failed and Did Not Execute
-
Last week I found multiple Domain Controllers OS partitions full, which stopped replication services etc. This happened due to a co-worker installing and running AVG Tuneup--it created a recovery file the size of the rest of the drive. Now when I attempt to access drives or navigate to folders it gives me this error:
I checked the RPC service and it's running. A reboot of the DC did not fix the issue.
-
Yeah, filling up drives, especially drives with databases on them, is not advised.
-
Delete the AVG Tuneup... ewwww
And remove the files it has saved to the drive.
-
The question is how to resolve this issue now
-
@wirestyle22 said in The Remote Prodecure Call Failed and Did Not Execute:
The question is how to resolve this issue now
Install fresh.
-
@DustinB3403 said in The Remote Prodecure Call Failed and Did Not Execute:
Delete the AVG Tuneup... ewwww
And remove the files it has saved to the drive.
I did. I have no idea why someone thought this was a good idea
-
So part of the issue here is it's also a file server. That complicates this issue greatly.
-
@wirestyle22 said in The Remote Prodecure Call Failed and Did Not Execute:
So part of the issue here is it's also a file server. That complicates this issue greatly.
Good time to point out to them why that's not advised and clearly caused issues. Time to start fixing the mistakes rather than bandaiding.
-
@scottalanmiller said in The Remote Prodecure Call Failed and Did Not Execute:
@wirestyle22 said in The Remote Prodecure Call Failed and Did Not Execute:
So part of the issue here is it's also a file server. That complicates this issue greatly.
Good time to point out to them why that's not advised and clearly caused issues. Time to start fixing the mistakes rather than bandaiding.
I actually am getting back from doing that. I have a feeling everything is going to happen at the same time--the summer. We'll see though.
-
So this actually ended up being profile related. When we deleted the profile and then logged back in it fixed the issue
-
@wirestyle22 said in The Remote Prodecure Call Failed and Did Not Execute:
So this actually ended up being profile related. When we deleted the profile and then logged back in it fixed the issue
Whose profile, and that still doesn't explain why there was a 25GB page file.
-
@dafyre said in The Remote Prodecure Call Failed and Did Not Execute:
@wirestyle22 said in The Remote Prodecure Call Failed and Did Not Execute:
So this actually ended up being profile related. When we deleted the profile and then logged back in it fixed the issue
Whose profile, and that still doesn't explain why there was a 25GB page file.
I think the page file is the result of the last company putting an extreme amount of resources into the DC's for some reason but skimping hardcore on the hard drives. The default is 1x the memory, which is a shit ton of memory that it will never use. So I'm going to manually set it to 4GB and call it a day
-
@wirestyle22 said in The Remote Prodecure Call Failed and Did Not Execute:
@dafyre said in The Remote Prodecure Call Failed and Did Not Execute:
@wirestyle22 said in The Remote Prodecure Call Failed and Did Not Execute:
So this actually ended up being profile related. When we deleted the profile and then logged back in it fixed the issue
Whose profile, and that still doesn't explain why there was a 25GB page file.
I think the page file is the result of the last company putting an extreme amount of resources into the DC's for some reason but skimping hardcore on the hard drives. The default is 1x the memory, which is a shit ton of memory that it will never use. So I'm going to manually set it to 4GB and call it a day
Just to reduce the size used? That should work.
Look for unnecessary hibernation files, too.
-
Explorer.exe crashed and is now giving the same error: "The Remote Prodecure Call Failed and Did Not Execute"
