Hello. I'm having trouble with my installation of MSDN. Some of the little icons that should appear next to some of the links don't show up, and many of the links don't work. When the links don't work, I get a JScript error "Object does not support this property or method." If I attempt to debug it, it's always a simple, one-line, code block, such as; alink_301.Click()
This is an example of what the missing icons look like. The little box, next to Look here, should be an icon; Send feedback to MSDN. Look here for MSDN Online resources.
But other icons Do show up, as in this case;
Platform SDK: Performance Monitoring
Anyone know how to fix this I've tried uninstalling and reinstalling, to no avail. I'm running Win2000 Pro.
I don't have any answers, but I have seen this twice with different symptoms.
First it was on my corporate Win2000 pro desktop. All the icons in MSDN all went to the small white icons with a dot in the center. This may have been due to a system level change coming from corporate. Re-installation of MSDN did not fix the problem. This machine is as of now permanently compromised for Vb development.
I got a new XP Pro laptop for VB development, and installed MSDN 2001. All links were good. I recently installed VS2005 std edition, and that appears to have been the culprit in compromising MSDN 2001. I still have "See Also" links, but all other header links are greyed out. Hyperlinks within the text are still good.
I also have the same problem with VS6-MSDN. Have also tried un- & re-installing, to no effect. I do also have VS.Net installed. Do we know of fix for this
I have run into this "missing link" problem as well in MSDN versions Oct 2001 and earlier. I recently worked with MS Developer Support to alleviate this issue. Over the course of 2 days we found the proverbial "needle in a haystack" fix. All you have to do is change the following registry setting (Put the following text in a .reg file and run it if you wish):
uninstall HTML Help (workshop), manually delete hh.exe, hh.dat (winnt), hhctrl.ocx, itss.dll, itircl.dll and hha.dll (system32), remove registry-entries [HKLM\SOFTWARE\Classes\CLSID\{ADB880A6-D8FF-11CF-9377-00AA003B7A11}], [HKLM\SOFTWARE\Classes\Internet.HHCtrl\CLSID] and [HKLM\SOFTWARE\Classes\Internet.HHCtrl.1\CLSID] and reinstall HTML Help (workshop)
i’d the same problem (MSDN 10/2001, NT4), i think hhctrl.ocx is wrong registered
Anyone with a bit more experience out there It's not like I can abitrarily upgrade. This is my work machine, and VB6 and MSDN 10/01 are still the corporate standards.
Dave, all I can suggest to you is that you empty your IE cache, then re-open MSDN and try the links again.
Some background: The documentation you are looking at is arranged into many "compiled Help" files, or .CHM files, that are created based on subject matter. There are two main kinds of links in the docs that you are looking at. 1. Simple URL links. A link from a page in one .CHM file that goes to a page in the same .CHM file is a simple URL link. 2. "Associate" links. There are a couple of variants of this one. a. When a link goes from a page in one .CHM file to a page in another .CHM file, we use an associative link, because a simple URL would not always work reliably. A path could be changed, for instance, which would render the hard-coded URL broken. b. One-to-many links are another form of "associative" links. The "See Also" links are an example of this. You click a link that says "See Also", and a list of related pages is displayed in a dialog box. You choose one of the titles from that list, and then that page is displayed.
Items 2a and 2b are the kind of links that are not working for you at this time. A script object is used to make associative links work, and somehow this has been fouled up.
If my suggestion about clearing the IE cache does not succeed for you, the best I can suggest is that you call the Product Support line for further assistance.
Can you please send me the whole Help url so I can figure out which Help files (Hxs) has this issue You can cut and paste the URL from MSDN library URL field which starts as ms-help://MS.MSDNQTR.v80.en
Unfortunately I was not in the team when MSDN Oct 2001 library was built. If its a problem in Oct 2001 library it might already be fixed in latest quarterly library.
Well, I guess my original post wasn't very clear. It's not one page or one library that's giving me trouble. It's all of the pages and libraries that use Javascript for linking. But if it will help, one such page is mk:@MSITStore:C:\Program%20Files\Microsoft%20Visual%20Studio\MSDN\2001OCT\1033\vbenlr98.chm::/HTML/vamscansitable.htm . Since it doesn't have the path fragment you quoted, I copied the entire URL. This one happens to be the Character Sets (0-127) page in the Visual Basic Documentation. It should have two links, See Also and Specifics, at the top of the page, under the title. What I get is this;
Character Set (0 – 127)
If they use basic HTML for links, as in the Platform SDK, it works. Wherever they use an <Object> to execute an "ALink" Command, I just get the little box, as above. They aren't clickable.
(I was wrong about the "icons". They aren't really icons, they're the link objects appearing as the empty boxes with a dot in the center, like the ones above. It's been so long since it worked, I'd forgotten what was supposed to be there. But, why they show up as boxes, I have no idea.)
The sample in my original post is a footer which appears on about half the pages in MSDN, including the Character Set page, but it uses a THIRD method of linking. That's the kind that gives me the error I reported in the original post. At the time, I didn't realize that so many different methods were in use.
Since both methods that fail rely on Javascript, maybe mine is out of sync or something.
Missing Icons and Bad Links in MSDN
Rama Ratnam
First it was on my corporate Win2000 pro desktop. All the icons in MSDN all went to the small white icons with a dot in the center. This may have been due to a system level change coming from corporate. Re-installation of MSDN did not fix the problem. This machine is as of now permanently compromised for Vb development.
I got a new XP Pro laptop for VB development, and installed MSDN 2001. All links were good. I recently installed VS2005 std edition, and that appears to have been the culprit in compromising MSDN 2001. I still have "See Also" links, but all other header links are greyed out. Hyperlinks within the text are still good.
Emptying the IE cache did not help!
A recipe for recovery would be a big help.
---- Dave in NJ
Pogman
Arex
Louisb
I have run into this "missing link" problem as well in MSDN versions Oct 2001 and earlier. I recently worked with MS Developer Support to alleviate this issue. Over the course of 2 days we found the proverbial "needle in a haystack" fix. All you have to do is change the following registry setting (Put the following text in a .reg file and run it if you wish):
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{ADB880A6-D8FF-11CF-9377-00AA003B7A11}]
"Compatibility Flags"=dword:00000000
It's always amazing to me how small -- and invisible -- a fix is to problems like these!
Bri
Stanley.brewer
No, I can't. I don't have those.
That's correct. That's what I'm using.
morningsunshine
Excellent! Thanks Bri!
That was a much needed solution, it's been driving me crazy for 2 weeks now... nice to be able to use my Help Files again!
C.K. Chua
uninstall HTML Help (workshop), manually delete hh.exe, hh.dat (winnt), hhctrl.ocx, itss.dll, itircl.dll and hha.dll (system32), remove registry-entries [HKLM\SOFTWARE\Classes\CLSID\{ADB880A6-D8FF-11CF-9377-00AA003B7A11}], [HKLM\SOFTWARE\Classes\Internet.HHCtrl\CLSID] and [HKLM\SOFTWARE\Classes\Internet.HHCtrl.1\CLSID] and reinstall HTML Help (workshop)
i’d the same problem (MSDN 10/2001, NT4), i think hhctrl.ocx is wrong registered
Jenothan
Peter Gavin
Some background: The documentation you are looking at is arranged into many "compiled Help" files, or .CHM files, that are created based on subject matter. There are two main kinds of links in the docs that you are looking at.
1. Simple URL links. A link from a page in one .CHM file that goes to a page in the same .CHM file is a simple URL link.
2. "Associate" links. There are a couple of variants of this one.
a. When a link goes from a page in one .CHM file to a page in another .CHM file, we use an associative link, because a simple URL would not always work reliably. A path could be changed, for instance, which would render the hard-coded URL broken.
b. One-to-many links are another form of "associative" links. The "See Also" links are an example of this. You click a link that says "See Also", and a list of related pages is displayed in a dialog box. You choose one of the titles from that list, and then that page is displayed.
Items 2a and 2b are the kind of links that are not working for you at this time. A script object is used to make associative links work, and somehow this has been fouled up.
If my suggestion about clearing the IE cache does not succeed for you, the best I can suggest is that you call the Product Support line for further assistance.
madwinchester
Microsoft Developer Network Library Visual Studio CHM Object doesn't support this property or method Internet Explorer
Star Value, Bri. That Was Driving Me Up The Proverbial Wall.
whaveman
Can you please send me the whole Help url so I can figure out which Help files (Hxs) has this issue You can cut and paste the URL from MSDN library URL field which starts as ms-help://MS.MSDNQTR.v80.en
Thanks
Khairun Jamal
MSDN
kopfschuss
Hello again,
Can you please send a URL from latest library for example Visual Studio 2005 or MSDN Quarterly Oct 2005 library
The URL you have sent is from MSDN Oct 2001 library.
Thanks
Khairun
Mark E. Johnson
Unfortunately I was not in the team when MSDN Oct 2001 library was built. If its a problem in Oct 2001 library it might already be fixed in latest quarterly library.
Thanks
Khairun
SeamusJunior44
Character Set (0 – 127)
If they use basic HTML for links, as in the Platform SDK, it works. Wherever they use an <Object> to execute an "ALink" Command, I just get the little box, as above. They aren't clickable.
(I was wrong about the "icons". They aren't really icons, they're the link objects appearing as the empty boxes with a dot in the center, like the ones above. It's been so long since it worked, I'd forgotten what was supposed to be there. But, why they show up as boxes, I have no idea.)
The sample in my original post is a footer which appears on about half the pages in MSDN, including the Character Set page, but it uses a THIRD method of linking. That's the kind that gives me the error I reported in the original post. At the time, I didn't realize that so many different methods were in use.
Since both methods that fail rely on Javascript, maybe mine is out of sync or something.