Hi BT and Everyone who has answered this thread.
I appreciate all the answers and assistance here.
I might try what you sent me, BT.
I have had this problem since day one with Windows Seven, so going
back to a previous restore point is not going to solve this problem. <smile>
I had made some changes to my folder options, which I really regret
doing, and this made the problem worse. I just had my loving Vernon
fix it, I mean the folders problem, and we'll see what happens.
I want you all to know, that even though Window-Eyes kind of checks
out when this happens, it's really not a Window-Eyes problem. System
Access will actually read the message that says "explorer.exe, The
Remote call procedure failled and did not execute." I've memorized
this error. lol.
I actually got Window-Eyes to read this one time, when with System
Access, I couldn't even do anything to stop it. I unloaded SA, and
loaded the loving Window-Eyes, and it actually, for the first time,
read that error message. I couldn't get anything to happen right
until I rebooted my loving computer. <smile>
I was told that Microsoft is suppose to eventually have a fix for
this, but I've yet to see it. I think all my updates are current.
I'm not going to worry about this, as if it gets too bad, I'll just
reboot my loving computer.
My folders are working properly, thanks to my loving Vernon.
Thanks to all of you for the assistance.
I'm loving Window-Eyes, and GW Micro. <smile>
Thanks a bunch.
Blessings,
Pat Ferguson
At 07:36 PM 1/13/2011, you wrote:
Hi!
I also looked it up and Microsoft has had the issues for many
years on there server.
This is a recent error and apparently enabling RPC is needed.
For your server is acting up.
Do what this person did and see if it fixes it.
Also, firewall and such are a part of the problem, but go into
the help menu and enabling RPC and see what can be done.
Bruce
Windows 7 forum: "The remote procedure call failed and did not execute."
by:
jedirock
May 16, 2009 11:59 AM PDT
Post 1 of 2
"The remote procedure call failed and did not execute."
by
jedirock
- May 16, 2009 11:59 AM PDT
I can't seem to open any folder using Explorer in Windows 7 RC
b7100, as it fails
with the above error. This happened after Explorer stopped picking
up metadata on
files, and so I killed and restarted explorer using Task Manager.
Files and folders
on my Desktop still show up, and files still open in their
respective applications,
but folders won't show, as with the error. Happens with any local folder.
I can't find anything on Google. I haven't touched any Explorer
settings, and I'm
not interested in an Explorer alternative. I can restart, but this
has happened once
before, so I'm thinking it'll happen again after a restart. Anyone
have any more
permanent ideas?
Reply
Report offensive post
Email to friend
Total posts: 2 (Showing page 1 of 1)
Thread display preference:
Collapsed
Expanded
Back to Windows 7
Tracked
Track this thread
Post 2 of 2
win7 "The remote procedure call failed and did not execute."
by
GabdaG
- August 28, 2009 1:40 AM PDT
In Reply to:
"The remote procedure call failed and did not execute."
by
jedirock
I had the same issue with w7 7260, i simply used windows help to
search for RPC and
followed the instructions on enabling it. Worked like a charm.
Sent: Thursday, January 13, 2011 6:03 PM
Subject: Re: Window-Eyes and Windows Explorer
Checking this error message on google, it seems many people with no
screen reader, are having this same problem, but found no solution.
I would do a system restore to a time before this problem started.
-----Original Message-----
From: Pat Ferguson [mailto:[email protected]]
Sent: Wednesday, January 12, 2011 7:10 PM
To: [email protected]
Subject: Window-Eyes and Windows Explorer
Hi Everyone,
Normally when Window-Eyes checks out, I know it's a Windows Explorer
problem, also, but this time, for the first time ever, Window-Eyes reads the
error message. Here it is:
explorer.exe: The Remote procedure call failled and did not execute.
No matter what I do, this is happening.
Any suggestions are greatly appreciated.
Thanksmuch.
Pat Ferguson
If you reply to this message it will be delivered to the original sender
only. If your reply would benefit others on the list and your message is
related to GW Micro, then please consider sending your message to
[email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can
manage your list subscription at http://www.gwmicro.com/listserv.
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and your
message is related to GW Micro, then please consider sending your
message to [email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You
can manage your list subscription at http://www.gwmicro.com/listserv.
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and your
message is related to GW Micro, then please consider sending your
message to [email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You
can manage your list subscription at http://www.gwmicro.com/listserv.
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and your
message is related to GW Micro, then please consider sending your
message to [email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You
can manage your list subscription at http://www.gwmicro.com/listserv.
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
