Re: Object Browser

Hey! Thanks very much for all your help.

The only thing that makes me suspicious is that it's happening on not only
my work computer, but my home computer as well.

Another clue: it didn't start happening on either until I installed Office
2007. I'll try out your suggestions and let me know how it goes.

thanks again!

"Mark Pryor" wrote:

On Sat, 21 Apr 2007 11:58:02 -0700, funnybroad wrote:

Hi! Thanks for that.

I have Office 2007 on my home computer, and I have the same problem there as
well. I just got the error window that says: "Microsoft Script Editor has
encountered a problem and needs to close. We are sorry for the
inconvenience."

Then I looked at the Application Event Log and found these two entries:

"Faulting application mse7.exe, version 12.0.4518.1014, stamp 45417460,
faulting module msvcr80.dll, version 8.0.50727.163, stamp 44849dd9, debug? 0,
fault address 0x0001533c. For more information, see Help and Support Center
at http://go.microsoft.com/fwlink/events.asp.";

Faulting application mse7.exe, version 12.0.4518.1014, stamp 45417460,
faulting module msvcr80.dll, version 8.0.50727.163, stamp 44849dd9, debug? 0,
fault address 0x0001533c. For more information, see Help and Support Center
at http://go.microsoft.com/fwlink/events.asp.

AND THEN... when I go to that link and search on the event ids (1000, 1001),
I get search results in just about every language EXCEPT English...

"mr_unreliable" wrote:

hi FunnyBroad,

This is just a wild-a** guess, but it appears that you are
at a spot where the MSE is attempting to present a listing
of COM objects -- and hangs up.

This could happen for (maybe) two possible reasons.

1. For some reason, you registry is screwed-up, and MSE is
getting lost trying to find some object with a bad address,
or maybe an address for something that has been disconnected
(diskette, cd-rom, dvd, flash mem... ). Or since you mentioned
network connection, maybe the object is to be found on a
disconnected server. This might be addressed with a good
"registry cleaner" tool, of which there are many.

2. Or, maybe it is looking at a microsoft object, and attempting
to "do-you-a-favor" by checking to see if there is a newer
version available -- and since microsoft keeps changing its url's
all the time, MSE might be looking for an update in some
obsolete url.

If you want to get really fancy, you can get out your copy of
spy and attempt to see exactly where MSE is getting hung up.

You can call me cynical and/or jaded, but I suspect sending
your system errors to ms will get you nothing - or at best
a correction which will appear in the next system to be
released in five years.

cheers, jw
____________________________________________________________

You got questions? WE GOT ANSWERS!!! ..(but,
no guarantee the answers will be applicable to the questions)




funnybroad wrote:
When I need to edit my VBSCRIPT in Infopath 2007, I do an Alt-Shift-F11, and
Microsoft Script Editor launches.

Ctrl-Alt-J brings up the Object Browser Window.

The problem is that every time I click "customize...", then click "Other
Packages and Libraries", then click "Add...", one of these two things happen:

1. I get an hourglass, and I hear my harddrive start spinning for 30
seconds... then the script editor stops responding, and I have to kill the
process (I've waited up to 15 minutes to let it keep looking for whatever
it's looking for).
- OR -
2. Microsoft Script Editor dies completely, and I get an apology window
from Microsoft and an offer to send them the errors.

The only way around this came from a colleague who said, "disconnect your
workstation from the network." Sure enough, that solves the problem, but it
kind of sucks that I have to do this every time I want to add a new object to
the object browser.

Does anyone know what is going on? Is Microsoft Script Editor trying to
browse the internet for objects or something? How do I configure it so that
it doesn't, and I don't have to disconnect my workstation to add a new object
library?


hello,

JW's suggestion to use spy, or some spy tool, should narrow down which
typelib is corrupted in the registry.

Personally I've troubleshot with regmon (www.sysinternals.com) running in
the background when adding an object with MSE or VB6. When it hangs or
crashes, stop regmon and patiently look to see where it stopped
enumerating.

There is a pretty good chance that running the following WMI script will
mimic the same process if it stops mid way due to corruption.
http://www.tlviewer.org/EnumTypeLib.vbs.txt

be sure to run the above with Cscript so output goes to a console.
Do not use Wscript or you will get tired of dismissing the msg dialog.

--
Mark

.