LOG: Appbase = file:///C:/Program Files/Microsoft Office/OFFICE11/ LOG: DisplayName = PolarionVbaWS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c289ef827c63313a Running under executable C:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE Der Vorgang wurde erfolgreich beendet.Īssembly manager loaded from: C:\WINDOWS\Microsoft.NET\Framework\v7\mscorwks.dll
#Microsoft word is not working dll missing how to#
Anyone knows how to solve this?įirst log.
It looks to me as if the Calling assembly : īeing a dll as well, does not know where to look for the library named PolarionVbaWS? Why does Word not know where from to load the dll, since it has done it one second before. What I found so far using the Fusion Assembly Binding Log Viewer is, that the library can be found and loaded in the first place and then on a second try fails, which then causes the run time error hex 80131902 mentioned above. Issues such as having access to the installation directory, multiple config files per app etc).īut finally I would already be a happy man if it worked at all. to all of our users installation path(s) (avoiding I would like it better to have the lib do the job of loading the SoapExtension instead of deploying the always same ,, etc. How do I get the COM interop to use the/my SoapExtension "SessionExtension" class in the Office VBA enviroment? The only thing that seems to be missing is the SoapExtension, the rest of the communication work well so far (I always chekced with Wireshark if the the session id was added to the soap header and what was sent forth and back). After doing so, Word does not complain anymore but does not seem to use the SessionExtension class either.
#Microsoft word is not working dll missing code#
Redux": when trying to run the VBA code out of MS Word, Word would exactly tell me which library could not be loaded (Name, culture, key etc). to instanciate the SoapExtension "SessionExtension" programatically the way describled in Mike Bouk's RAM " Programatically Registering SoapExtensions.to use the app.config file of the testapplication, renaming it to and placing it in the winword installation path: result was that Word would issue an run time error hex 80131902.Registry, also the SoapExtension class named "SessionExtension". I regasm'd it with /tlb and /codebase option after which all the classes can be found in the In order to make the library a COM interop library, I used sn.exe to generate a strong name key file that is used by Visual Studio to make the lib strong named.
NET Testapplication built in VS Express 2008. The C# sources where autogenerated from WSDL files and then adapted to VBA (C# long != VBA long, array passing by value and ref issue). The library is build with C# in Visual Studio Express 2008 as a. I have been for a while now trying to get a Web Service dll build in Visual Studio Express 2008 running in MS Word 2003s VBA.