|
|
Rank: Member Groups: Member
Joined: 3/28/2007 Posts: 56 Points: 0
|
i keep getting this error sometimes. it doesn't happen always but it so far has no solution has anyone else seen this? edit: the app runs fine on my XP development machine, but when I post it to server I get this error, sometimes it works, sometimes it doesn't, our server is win2k3 Code:Server Error in '/IMAGEEDITOR' Application. --------------------------------------------------------------------------------
The specified module could not be found. (Exception from HRESULT: 0x8007007E) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)] System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0 System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +211 System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +141 System.Reflection.Assembly.Load(String assemblyString) +25 System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +32
[ConfigurationErrorsException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)] System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +596 System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +3479049 System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +46 System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +177 System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +180 System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) +347 System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) +125 System.Web.Compilation.BuildManager.EnsureFirstTimeDirectoryInit(VirtualPath virtualDir) +316 System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode) +208 System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath) +40 System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +54 System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +93 System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +111 System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +54 System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +31 System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +40 System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +139 System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +120 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155
-------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42
|
|
Rank: Member Groups: Member
Joined: 3/28/2007 Posts: 56 Points: 0
|
Found solution! by default VS 2005 does not publish the .lic files when you "Publish Web Site" add the following to your Web.Config file: Code: <configuration> <system.web> <compilation> <buildProviders> <remove extension=".lic"/> <add extension=".lic" type="System.Web.Compilation.ForceCopyBuildProvider"/> </buildProviders> </compilation> </system.web> </configuration>
this ensures that .lic files are brought over when you do a publish. also note that the .lic files are only needed when it tries to compile the app, so if they were missing from the start, you can't add them after its compiled, you'll notice that you can remove them from the bin after a compile, but if the server ever recompiled they would need to be there.
|
|
Rank: Advanced Member Groups: Administration
, Member
Joined: 8/3/2003 Posts: 506 Points: 348
|
Thanks for the information.
Sincerely yours, Dmitry Sevostjanov.
|
|
Rank: Member Groups: Member
Joined: 3/28/2007 Posts: 56 Points: 0
|
I'll be glad when the final release of 2.0 is out with documentation
|
|
Rank: Member Groups: Member
Joined: 3/28/2007 Posts: 56 Points: 0
|
ok.... was still having the same error message, even after .lic files came over on a publish of code.
this time it seems to solve it for sure I had to "add" the tracing enabled node in the web.config file, AFTER it was published.
so, first, publish the code WITHOUT the line in web.config next, after publish is complete, change the web.config file to have the and it works!
my guess is that the project for the Aurigma tools (graphics mill, editor, I don't really know what) must have been a debug build, so the DLLs need the code to run in debug mode, but for some reason, simply adding them doesn't work, it needs to be changed AFTER publishing the code.
I suspect this should not be an issue with a non-debug build of the tool
hope this helps anyone else pulling their hair out as I was.
|
|
 Rank: Advanced Member Groups: Administration
, Member
Joined: 8/2/2003 Posts: 708 Points: 105
|
Perhaps the problem is in Aurigma.PhotoEditor.dll - it sounds it is built with wrong compiler settings. We will check it out, and I fix it in the final version. I hope it is not a big problem to enable trace for this beta as a temporary workaround. If not, please submit case. Sincerely yours, Andrew Simontsev from Aurigma Team
|
|
Rank: Member Groups: Member
Joined: 3/28/2007 Posts: 56 Points: 0
|
I am not sure it is working 100% of the time, this problem seems to be sporatic
It would be nice if you could send me a non-debug compile of the aurigma dlls to use
|
|
 Rank: Advanced Member Groups: Administration
, Member
Joined: 8/2/2003 Posts: 708 Points: 105
|
Also, make sure that the file msvcr71.dll is located in %windows%\system32\ folder. Not sure if it helps in your case, but without this file you will always have "specified module not found" problem. This file can be found on your Windows XP machine (also in system32). Sincerely yours, Andrew Simontsev from Aurigma Team
|
|
Rank: Member Groups: Member
Joined: 3/28/2007 Posts: 56 Points: 0
|
was just going to post that same fix, it works for us.
will the release version of this require that dll on the server? it is my understanding that may be a debug dll, and we wouldn't want that on the server
|
|
Rank: Advanced Member Groups: Administration
, Member
Joined: 8/3/2003 Posts: 506 Points: 348
|
Hello,
This file will be included into installation package and you will not have to copy it by hand.
Sincerely yours, Dmitry Sevostjanov.
|
|
Rank: Member Groups: Member
Joined: 3/28/2007 Posts: 56 Points: 0
|
if this is a debug dll, we wouldn't want it on a production server
|
|
Rank: Advanced Member Groups: Administration
, Member
Joined: 8/3/2003 Posts: 506 Points: 348
|
Hello,
It is not debug library, it is Microsoft Visual C++ Runtime library.
Sincerely yours, Dmitry Sevostjanov.
|
|
|
Guest |