• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1801
  • Last Modified:

The system cannot find the file specified.--error that randomly comes up

Hi Experts,

I'm having trouble with an error that comes up randomly after I have made changes or more specifically overwritten files on my server.
 The first time I recieved this error was after I made an include of an ascx file to all the pages on the site.
At that time everything was working well; however, about two hours later every page I made changes to generated an error. The assembly it is looking for is unknown to me. I simply overwrote the files on the server again and the error went away. Now, two weeks later the error has come back. I rewrote the ascx file and the problem is gone once again. I believe the problem still resides and that it will come back again.
 I know this information is limited but if someone has any idea what is going on I am more tha appreciative.

Thank you,
Jared

Here is the error I am recieving.

Server Error in '/TDGCruises' Application.

--------------------------------------------------------------------------------

The system cannot find the file specified.
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 system cannot find the file specified.

Source Error:

 
Line 1:  <%@ Page Language="VB" ContentType="text/html" ResponseEncoding="iso-8859-1" %>
Line 2:  <%@ Import Namespace="System.Data" %>
Line 3:  <%@ Import Namespace="System.Data.OleDb" %>
 


Source File: C:\Inetpub\wwwroot\TDGCruises\default.aspx    Line: 1

Assembly Load Trace: The following information can be helpful to determine why the assembly 'wwinhohp, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' could not be loaded.

 
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].
 


Stack Trace:

 
[FileNotFoundException: The system cannot find the file specified.]
 
[FileNotFoundException: File or assembly name 'wwinhohp, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null', or one of its dependencies, was not found.]
   ASP.default_aspx.__BuildControlTree(default_aspx __ctrl) in C:\Inetpub\wwwroot\TDGCruises\default.aspx:1
   ASP.default_aspx.FrameworkInitialize() +76
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +94
   System.Web.UI.Page.ProcessRequest(HttpContext context) +27
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +186
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +69
 

 


--------------------------------------------------------------------------------

Version Information: Microsoft .NET Framework Version:2.0.40607.42; ASP.NET Version:2.0.40607.42
0
odobo
Asked:
odobo
  • 3
  • 2
1 Solution
 
raterusCommented:
What is this? "wwinhohp"

It looks like your web.config file is referencing this file, and it's going missing.  If this is a valid file that should be here, I'd check your web server and make sure anti-virus software isn't to blame...
0
 
odoboAuthor Commented:
raterus,

We are not referencing any files other than the database in our web.config and antivirus has not changed for a while so i am fairly certain that this is not the case. Its pretty bare bones

this is the web config

<configuration>
      
      <system.web>                        
          <customErrors mode="Off"/>
                   <compilation debug="true"/>
      </system.web>
      
      <appSettings>
            <add key="MM_CONNECTION_HANDLER_TDGDBConn" value="default_oledb.htm" />
            <add key="MM_CONNECTION_STRING_TDGDBConn" value="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Inetpub\wwwroot\TDGCruises\db\TDGDB.mdb;Persist Security Info=False" />
            <add key="MM_CONNECTION_DATABASETYPE_TDGDBConn" value="OleDb" />
            <add key="MM_CONNECTION_SCHEMA_TDGDBConn" value="" />
            <add key="MM_CONNECTION_CATALOG_TDGDBConn" value="" />
      </appSettings>
</configuration>

0
 
odoboAuthor Commented:
i dont know what "wwinhohp" or where it came from.
jared
0
 
raterusCommented:
might be in machine.config then?
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config

Wherever it is, I'd do an exhaustive search of the name, because whatever it is (or isn't), it's your problem!
0
 
odoboAuthor Commented:
raterus,
no luck, i checked the machine.config and could not be found in there either. I'd post it but it is quite large and pointless.

Do you have any theory to why this reference to a file only exposes itself at random times?
 It is logical that if there is indeed a reference to a file that does not exist that an error will come up every time it is requested. So what this tells me is that this assembly is not being referenced every time. I would think that for that to change something must intervene in the process, but our application is not very complex; we do not have a lot of references to assemblys. Interestingly, once the assembly has been requested within the application, it keeps requesting this assembly appearantly until a physical change has been made to the application.
I have not worked with computers for all that long but this kind of behaivor does not even seem possible to me.

in the meantime i will be performing an extesive search for this.
and yes it is my problem.

thanks.
jared
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now