I have combed the forums here and googled this until I am blue in the face.  I have a strange error and it seems like no else has run across this becuase it involves moving from one server to another.

I wrote some custom modules for a customer.  This server konked out and he moved the webiste to another server.

It seems to have started up and ran fine until one day I flipped RemoteErrors on briefly then got this error (sorry I don't have the exact text, I can't bear to crash his portal again!):

"Error in Application" and what follows is a reference like this:

Can't find C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\root\987b2220\5e42b023\YourCustomThing.dll

Well, there are about 8 of these, so I figure why not just copy all the YourCustomNNNN.dlls from <portal root>/bin/ to the directory above?  I do so, and it works great until the application is restarted and I have to copy these things back to the folder above and things run great for a week or three.

I did a search on the server and noticed that all the YourCustomNNNN.dlls are in the Temporary ASP.NET Files\root but buried one or two levels deeper.  And these buried references do have correct __AssemblyInfo__.ini files that refer to <portal root>/bin/.

Is there a way to convince ASP.NET to dig a little deeper for these DLLs?

Thanks much, this is a strange one to me.

Weezy

Hi Mitch:

Thanks for the response.  They are custom module-related .dlls.  I used the dnnjungle tutorial and have done about 6 of these.  3 are the .dlls for the code-behind and business logic and 3 for the SQLDataProvider.  Nor sure what you mean by "How are you referencing...?"  They all reside in DotNetNuke/bin on the website.  For some of them I had built .zip files and used the DNN module install, some of them I create the module definition "by hand" without using DNN module upload; I just copy the .dlls and pages directly (I have remote access to the server.)

It's almost like the new server decided to create different folders in the ASP.NET/TempFiles area, but the website can't find them there; it is looking in the old spot they were in on the old server, or vice versa; they are put in the old area, but .NET is looking in the new folders.

I suspect this is most unusual because it involves everything being copied to a new server; not too many people are going to have that happen.

Thanks for any help or thoughts.

Weezy