Could not load file or assembly "stdole"

  • 5 December 2007
  • 2 replies
  • 14 views

Badge +3

Getting this in the event log of the K2 server every time a worklfow is initiated from Sharepoint..  Please help :(


 Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1310
Date:  12/5/2007
Time:  1:30:46 PM
User:  N/A
Computer: HCM23
Description:
Event code: 3008
Event message: A configuration error has occurred.
Event time: 12/5/2007 1:30:46 PM
Event time (UTC): 12/5/2007 7:30:46 PM
Event ID: 1e3d66e7e88f4e8c8be9e4dacc3126bf
Event sequence: 4
Event occurrence: 1
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/1/Root/RuntimeServices-2-128413566463308749
    Trust level: Full
    Application Virtual Path: /RuntimeServices
    Application Path: D:Program FilesK2 BlackpearlWebservicesRuntimeServices
    Machine name: HCM23
 
Process information:
    Process ID: 5436
    Process name: w3wp.exe
    Account name: HCk2admin.prod
 
Exception information:
    Exception type: ConfigurationErrorsException
    Exception message: Could not load file or assembly 'stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (D:Program FilesK2 BlackpearlWebservicesRuntimeServicesweb.config line 37)
 
Request information:
    Request URL: http://hcm23/RunTimeServices/SharePointService.asmx
    Request path: /RunTimeServices/SharePointService.asmx
    User host address: 10.1.5.47
    User: HCMSP.Admin
    Is authenticated: True
    Authentication Type: Negotiate
    Thread account name: HCMk2admin.prod
 
Thread information:
    Thread ID: 6
    Thread account name: HCMk2admin.prod
    Is impersonating: True
    Stack trace:    at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
   at System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai)
   at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
   at System.Web.Compilation.WebDirectoryBatchCompiler..ctor(VirtualDirectory vdir)
   at System.Web.Compilation.BuildManager.BatchCompileWebDirectoryInternal(VirtualDirectory vdir, Boolean ignoreErrors)
   at System.Web.Compilation.BuildManager.BatchCompileWebDirectory(VirtualDirectory vdir, VirtualPath virtualDir, Boolean ignoreErrors)
   at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath)
   at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
   at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
   at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath)
   at System.Web.UI.WebServiceParser.GetCompiledType(String inputFile, HttpContext context)
   at System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler(HttpContext context, String verb, String url, String filePath)
   at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
   at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
 
 
Custom event details:


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


 


2 replies

Badge +9
We had this exact problem, and the solution involved removing the reference to stdole from the web.config located in webservices/runtimeservices under your blackpearl web site's home directory.  This assembly is not actually needed by the product, but tends to get into web.config files by default.  Please let us know if that resolves your problem as well.
Badge +3
Thanks! That fixed it...  Or should I say allowed us to procede onto the next bug/roadblock..  At least now we can start a process though..

Reply