Unable to locate Assembly asdlfkjasdfkljasd

OK, this one is a real head scratcher.

I have a paticuarl application on my beta server that flips out almost every time I modify the source code. It gives me an error saying that the cached assembly doesnt exist. Sounds like a permission issue right But I've checked for all of that... and my other apps work just fine. So I google and find some info on app-pools, so i stick the app in its own app pool. Still.... same problems. I spent an entire day fighitng with this thing... all to no avail.

It is a win 2k3 server with .net 1.1, and 2.0 installed. I have currently ONLY .net 1.1 apps setup in IIS.

Could this be caused by a flaw in my code If so How

This is extremely frustrating because its preventing me from coding :| Someone please save me from my looming deadline!

Answer this question

Unable to locate Assembly asdlfkjasdfkljasd

WRuschhaupt
My bad, misread/interpreted the post. My only suggestion at this point is to try to narrow down why this site causes this behavior. Maybe build a test site, no bells and whistles, publish, verify that it doesn't happen and add components from your site.

I had a web service that would crash due to a serialzation/pre-compilation issue that ASP.Net could not handle. During ASP.Net (under .Net 1.1) precompilation stage, a specific user structure which needed serialization had an internal construct that serialization could not handle would crash it on startup....later fixed in .Net 2...

You may have something similar....
Ankini
More info is needed. What is the application A service or an IIS website, or web service Also does rebooting ever help When do one see this error come up When you install do you do iisreset on the comand line Also with the information post the stack trace. Thanks.
Ned Rise
I feel your issue may be that the older operating system is not playing well with .Net and one may have to live with this wrinkle. Insist to the powers that be to upgrade the server or set a path of upgrade and get your site on it.

Otherwise do you do an iisreset on the command line before accessing the site Does the error happen Thanks/Good luck.
Xadja

This sounds like the security issue on the temp folder, maybe exactly this or at least similar:

http://support.microsoft.com/kb/823196/en-us

Serialization sometimes generates a custom assembly, and this is compiled into the temp folder with a funny-looking name.
jsedlak
I also wanted to mention that I did go into IIS and try switching back and forth from .net 1.1 to 2.0 ... strangely, switching from 1.1 to 2.0 completely locks up the machine, a problem ive never had before, but if I reboot it runs fine. Weird huh

Anyway with both 1.1 or 2.0 I still have the same problem with the "missing assembly".
HellsChicken
startting and stoppign IIS doesnt fix the problem... only 2 things fix it (temporarily)

1. I can wait a while, IE, goto lunch and come back, and its working until of course I update the file again.

2. I can restart the machine.

DuncanP

It is a fairly run of the mill web application for searching through data.

Rebooting seems to fix the problem... but rebooting everytime I update my source code is a down right pain.

The error almost always comes up when I update my source code (though not always).

Just a few minutes ago I got this,

Cannot find the assembly tfu9nhue, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null.

Not to be outdone I logged into the server and ran:
---------------------------------------------------
C:\>dir *tfu9nhue* /s
Volume in drive C has no label.
Volume Serial Number is 8433-48C8

Directory of C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\root\6a14841f\f50bbcb8

09/08/2006 12:05 PM 24,576 tfu9nhue.dll.delete
09/08/2006 12:05 PM 34,304 tfu9nhue.pdb.delete
2 File(s) 58,880 bytes

Total Files Listed:
2 File(s) 58,880 bytes
0 Dir(s) 14,569,046,016 bytes free
---------------------------------------------------

As you can see the files have been appeneded with .delete .. this makes SENSE because the cache dll is no longer relevant since I have updated the source. The question is why the heck is it still looking for it

Here is the stack trace:

tack Trace:

[SerializationException: Cannot find the assembly tfu9nhue, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null.]
  System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly() +101
  System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name) +130
  System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable) +128
  System.Runtime.Serialization.Formatters.Binary.ObjectMap.Create(String name, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable) +54
  System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record) +330
  System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryHeaderEnum binaryHeaderEnum) +71
  System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run() +154
  System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, IMethodCallMessage methodCallMessage) +249
  System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, IMethodCallMessage methodCallMessage) +183
  System.Web.Util.AltSerialization.ReadValueFromStream(BinaryReader reader) +765
  System.Web.SessionState.SessionDictionary.Deserialize(BinaryReader reader) +98
  System.Web.SessionState.StateClientManager.Deserialize(Stream stream, Int32 lockCookie) +133
  System.Web.SessionState.SqlStateClientManager.DoGet(String id, SqlCommand cmd) +1148
  System.Web.SessionState.SqlStateClientManager.GetExclusive(String id) +81
  System.Web.SessionState.SqlStateClientManager.System.Web.SessionState.IStateClientManager.BeginGetExclusive(String id, AsyncCallback cb, Object state) +6
  System.Web.SessionState.SessionStateModule.GetSessionStateItem() +67
  System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData) +274
  System.Web.AsyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +66
  System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +173

Yes, the server has been running fine for months... this is a sudden and unexpected occurance. It also only happens with this one application in so far as I can tell.

Thanks!

martona
Yep; that is what I am doing now, starting over from scratch and trying to find what specifically is causing my woes within the code. Unfortunately that means a long and borring day :| and i think id rather be fishing.
Mitesh Shah923
Older operating system Its windows server 2003.. as i said "2k3"

It happens on 2 other machines as well... I have tested thoroughly. Somethings funky and not getting along with the CLR.
Unable to locate Assembly asdlfkjasdfkljasd

Answer this question