+1  A: 

The error is not anything to do with processor-specific stuff. It is clearly a missing file that is causing this error. Have you double checked that you have all the required files and assemblies installed on the new dedicated server?

Earlz
A: 

Does anyone of the error information indicate what module could not be found?

If not, verify the deployed bin directory has everything your site has when its working on your test server. Then go through the web.config and make sure all referenced modules are on the target server.

Frank Schwieterman
+2  A: 

First of all, the error you are getting relates to a missing file, hence the FileNotFoundException. However, you are also getting HRESULT 0x8007007E, which points to a missing unmanaged DLL.

Here's how I would tackle this problem:

  1. Step through the code to find where this exception occurs. With that HRESULT, I'm pretty sure you'll find the exception to be on a line where an unmanaged DLL function is called.
  2. Identify what unmanaged DLL you're trying to use.
  3. Check to see that it's there. First, you should check that any ones you are using are in their right places and are referenced correctly. If that is all OK, make sure that any dependencies they themselves have are there, too.

Also, after you complete step 2, we might be able to help you more if you tell us what type of unmanaged code you're using (i.e., what it might require to run, in terms of its own dependencies).

Hope I helped! :)

Maxim Zaslavsky