FAQ  •  Register  •  Login

Interop.SHDocVw.dll could not be loaded

Moderator: MiRai

<<

Mrcocomo

Posts: 1

Joined: Tue May 19, 2015 11:57 pm

Post Wed May 20, 2015 12:23 am

Interop.SHDocVw.dll could not be loaded

Dang I'm having the same exact issue. I'm no pro but, I've been using ISboxer for about three yrs now and same thing happened to me tonight as described in the post. I had just right clicked an "always on" keymap for a character set(which is using the Proform template) and ISboxer window popped up saying it had a script error. Gave me the option to try to continue or to quit the program. I chose quit and now I can't open ISboxer at all with out getting a pop up saying:

[i]SystemIO.FileNotFoundException: Could not load file or assembly
'Interop.SHDocVw, Version=1.1.0.0, Culture=Neutral, PublicKeyToken=null' or one of its dependencies.
The system cannot find the file specified.
FileName:'Interop.SHDocVw, Version=1.1.0.0, Culture=Neutral,PublicKeyToken=null'
at ISBoxer_Toolkit.Controls.MainPropertyTreePanel..ctor()
at ISBoxer_Toolkit.Pages.MainPage..ctor()
at ISBoxer_Tollkit.Mainform.InitializeComponent()
at ISBoxer_Toolkit.MainForm.ctor()
at ISBoxer_Toolkit.Program.Main()

WRN: Assembly binding logging is turned OFF
To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!Enablelog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!Enablelog].

Up to tonight I've never had a problem what so ever with ISBoxer's functionality.
<<

bob

User avatar

League of Extraordinary Multiboxers

Posts: 4653

Joined: Sat Feb 15, 2014 11:14 am

Location: In the dining room, with the lead pipe.

Post Wed May 20, 2015 2:38 am

Re: Need some serious help.

That's not the "exact same issue" because it is not the exact same message.

I suggest going to your InnerSpace install folder (e.g. C:\Program Files (x86)\InnerSpace) and removing/renaming the ISBoxerToolkitProfile.XML file and seeing if that makes a difference. If not, you could also try removing/renaming the ISBoxerToolkitGlobalSettings.XML file too.
<<

lax

User avatar

Site Admin

Posts: 7303

Joined: Tue Nov 17, 2009 9:32 pm

Post Wed May 20, 2015 5:27 am

Re: Interop.SHDocVw.dll could not be loaded

I split this off of the unrelated thread.

I don't think Bob's suggestion is going to help. The error message specifically says that Interop.SHDocVw.dll could not be loaded, because the file could not be found:
SystemIO.FileNotFoundException: Could not load file or assembly
'Interop.SHDocVw
, Version=1.1.0.0, Culture=Neutral, PublicKeyToken=null' or one of its dependencies.
The system cannot find the file specified.


My first suggestion would be to run the ISBoxer installer and let it install into the same location you already have it installed to.
<<

bob

User avatar

League of Extraordinary Multiboxers

Posts: 4653

Joined: Sat Feb 15, 2014 11:14 am

Location: In the dining room, with the lead pipe.

Post Wed May 20, 2015 11:09 am

Re: Interop.SHDocVw.dll could not be loaded

lax wrote:I don't think Bob's suggestion is going to help. The error message specifically says that Interop.SHDocVw.dll could not be loaded, because the file could not be found
Good point. I should have read the message more carefully myself..
Not enough coffee....

Return to General

Who is online

Users browsing this forum: No registered users and 5 guests