Wel, I didn't really change anything, but when I came back from lunch everything seems to be working fine now. I'm really stumped as to what may have caused this, or what may have fixed it, but I'm glad it's working. Now I've got to install asp.net ajax
1.0 on my server and hope the same thing doesn't happen there...
BTW, I did have the release of asp.net ajax installed - in fact I uninstalled it a couple times and reinstalled it, so I'm pretty sure the installation was successful. Also, I am using the most recent version of AjaxControlToolkit.dll which came out yesterday...
Thanks for all your help, this one, I'm afraid, is a mystery...
The best solution I've found is to delete the TEMPORARY project from the directory: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files. This works a treat, and whenever I crash (which is when I get this error), I can rebuild in minutes -
in fact, it works for any reference, not just the AJAX control toolkit. Hope this helps someone else and saves them from pulling their hair out!
I have almost the same problem, i have VS2005 installed on 3 computers in the office, and 4 days ago one of them stop work with ajax, i tried to remove the folder into Visual Studio 8 that i named AjaxToolkit and again unzipping the AjaxControlToolkit.zip with
the same name, but now i have a builds errors like this:
Warning 9 Resolved file has a bad image, no metadata, or is otherwise inaccessible. Could not load file or assembly 'C:\Archivos de programa\Microsoft Visual Studio 8\AjaxToolkit\SampleWebSite\Bin\AjaxControlToolkit.dll' or one of its dependencies. The
module was expected to contain an assembly manifest. PayUp.Web
When i trid to add the reference in my web project a warning icon shows in the reference Ajaxcontroltoolkit reference, and the propierties dont fill the culture, description, version, etc, and in the others computers the reference ajaxcontroltoolkit's propierties
fill all the fields correctly.
I tried to remove the temporaly files in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 but the error still there and i have tried to unistall the VS05 and the error still there.
Here's what I did to resolve this under VS2008 (its probably very similar under VS2005):
First, on any project where I'm using dlls, I always create a dll folder to hold them. I NEVER rely on the bin folder for references (since that would be cleared out when running a clean operation and most source control programs do not include the bin
file when checking in/out) or on local copies of the dll (c:\ajax\2.0\bin\ajaxcontroltoolkit.dll). Sure, the build operation puts a copy there but thats its job--leave the bin file to the build script. If you ever work on your code somewhere else, publish
it to another machine, or hand it off to someone else; you don't have to worry about whether the new machine has its ajaxcontroltoolkit.dll installed in the same location on its hard drive as yours. As a side note, under the properties -> advanced for the
dll, I have a build action set to content and a copy to output directory set to do not copy
Second, I go into the references, remove any current ajaxcontroltoolkit references (or any other special dlls that I was using and am moving to the dll folder), and add the dll references back in pointing to the copies in my dll folder.
Thirdly, if I'm going to be using something like the ajaxcontroltoolkit on most of my pages, I go ahead and throw the following into the web.config file so I dont have register statements on every page:
Hope this helps, it took me a while to get it right
If this is an intermittent problem for you (ie, it works for a bit after a build and then you get a parser error), try stopping and starting IIS. In my case, the ajaxcontroltoolkit that the build script had placed in the bin folder was being replaced with
an earlier verison of the toolkit. Restarting IIS seems to have fixed this. Since doing this, my version in the bin folder has not reverted to 1.16xxx, it stays a 1.19xxx and I don't have any more frustrating errors.
I too have a website, which emits these errors at random. ASP.NET is a great idea and has worked well for me many years.
It appears, however, that Microsoft is now losing grips of its product, as to which the sporadic nature of this issue can only attest.
It seems that an overall goal of Microsoft is to weave their users/developers into a net, from which it is diffult to migrate.
Now that javascript libraries such as jquery has reached maturity it would seem a good occasion to look for alternatives to the ASP.NET heavyweighter and adopt for more to-the-point methods such as jquery + web services.
You may receive this error if you are running your site with impersonation. Check your web.config impersonation tag and/or the security context that the particular user is running under:
<br /><br />
In my case, the fix was changing the user that was being impersonated on my local machine. I was able to pinpoint it to this issue because the site was working on my local machine with my development web.config, but not with my live web.config,
and this was one of the main differences. I didn't make it as far as determining what specific security access was different between the two users. I tried granting my live web.config impersontated user full access to the bin folder on my local machine to
no avail.
eappell
Member
491 Points
268 Posts
Re: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Access is de...
Jan 25, 2007 01:37 AM|LINK
Wel, I didn't really change anything, but when I came back from lunch everything seems to be working fine now. I'm really stumped as to what may have caused this, or what may have fixed it, but I'm glad it's working. Now I've got to install asp.net ajax 1.0 on my server and hope the same thing doesn't happen there...
BTW, I did have the release of asp.net ajax installed - in fact I uninstalled it a couple times and reinstalled it, so I'm pretty sure the installation was successful. Also, I am using the most recent version of AjaxControlToolkit.dll which came out yesterday...
Thanks for all your help, this one, I'm afraid, is a mystery...
Eddie
Puhfista
Member
137 Points
47 Posts
Re: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Access is de...
Mar 16, 2007 07:40 PM|LINK
hey rb_jlm,
How is it that you make the AjaxControlToolKit copy local?
eappell
Member
491 Points
268 Posts
Re: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Access is de...
Mar 19, 2007 02:46 PM|LINK
I just added a reference to my project, pointed it to the dll and it added it to my bin folder. I don't have it installed in the GAC...
eddie
bishpop999
Member
4 Points
2 Posts
Re: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Access is de...
Jul 13, 2007 05:59 PM|LINK
Adancin
Member
11 Points
4 Posts
Re: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Access is de...
Sep 05, 2007 08:20 PM|LINK
Only grant read and execution permissions to the bin/AjaxControlToolkit.dll file for everyone
skqi
Member
104 Points
27 Posts
Re: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Access is de...
Oct 15, 2007 07:46 AM|LINK
copy to bin folder will do. Check http://dotnetfish.blogspot.com/2007/10/could-not-load-file-or-assembly.html
Billing software
Application Development
inventory software
javikiller
Member
6 Points
4 Posts
Re: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Access is de...
May 21, 2008 11:44 AM|LINK
I have almost the same problem, i have VS2005 installed on 3 computers in the office, and 4 days ago one of them stop work with ajax, i tried to remove the folder into Visual Studio 8 that i named AjaxToolkit and again unzipping the AjaxControlToolkit.zip with the same name, but now i have a builds errors like this:
Warning 9 Resolved file has a bad image, no metadata, or is otherwise inaccessible. Could not load file or assembly 'C:\Archivos de programa\Microsoft Visual Studio 8\AjaxToolkit\SampleWebSite\Bin\AjaxControlToolkit.dll' or one of its dependencies. The module was expected to contain an assembly manifest. PayUp.Web
When i trid to add the reference in my web project a warning icon shows in the reference Ajaxcontroltoolkit reference, and the propierties dont fill the culture, description, version, etc, and in the others computers the reference ajaxcontroltoolkit's propierties fill all the fields correctly.
I tried to remove the temporaly files in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 but the error still there and i have tried to unistall the VS05 and the error still there.
I dont know how to do!!
</div></div>lasstlos
Member
2 Points
1 Post
Re: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Access is de...
Jun 09, 2008 04:46 PM|LINK
Here's what I did to resolve this under VS2008 (its probably very similar under VS2005):
First, on any project where I'm using dlls, I always create a dll folder to hold them. I NEVER rely on the bin folder for references (since that would be cleared out when running a clean operation and most source control programs do not include the bin file when checking in/out) or on local copies of the dll (c:\ajax\2.0\bin\ajaxcontroltoolkit.dll). Sure, the build operation puts a copy there but thats its job--leave the bin file to the build script. If you ever work on your code somewhere else, publish it to another machine, or hand it off to someone else; you don't have to worry about whether the new machine has its ajaxcontroltoolkit.dll installed in the same location on its hard drive as yours. As a side note, under the properties -> advanced for the dll, I have a build action set to content and a copy to output directory set to do not copy
Second, I go into the references, remove any current ajaxcontroltoolkit references (or any other special dlls that I was using and am moving to the dll folder), and add the dll references back in pointing to the copies in my dll folder.
Thirdly, if I'm going to be using something like the ajaxcontroltoolkit on most of my pages, I go ahead and throw the following into the web.config file so I dont have register statements on every page:
<configuration> <system.web> <pages> <controls> <add tagPrefix="cc1" assembly="AjaxControlToolkit" namespace="AjaxControlToolkit"/> </controls> <pages> <compilation> <assemblies> <add assembly="AjaxControlToolkit"/> </assemblies> </compilation> </system.web> </configuration>Hope this helps, it took me a while to get it right
If this is an intermittent problem for you (ie, it works for a bit after a build and then you get a parser error), try stopping and starting IIS. In my case, the ajaxcontroltoolkit that the build script had placed in the bin folder was being replaced with an earlier verison of the toolkit. Restarting IIS seems to have fixed this. Since doing this, my version in the bin folder has not reverted to 1.16xxx, it stays a 1.19xxx and I don't have any more frustrating errors.
awarberg
Member
28 Points
11 Posts
Re: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Access is de...
Sep 03, 2008 06:18 PM|LINK
I too have a website, which emits these errors at random. ASP.NET is a great idea and has worked well for me many years.
It appears, however, that Microsoft is now losing grips of its product, as to which the sporadic nature of this issue can only attest.
It seems that an overall goal of Microsoft is to weave their users/developers into a net, from which it is diffult to migrate.
Now that javascript libraries such as jquery has reached maturity it would seem a good occasion to look for alternatives to the ASP.NET heavyweighter and adopt for more to-the-point methods such as jquery + web services.
Best regards
Andreas
jwfoster
Member
2 Points
1 Post
Re: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Access is de...
Sep 09, 2008 02:57 PM|LINK
<br /><br />
<
identity impersonate="true" userName="UserName" password="Password" /><br /><br />
In my case, the fix was changing the user that was being impersonated on my local machine. I was able to pinpoint it to this issue because the site was working on my local machine with my development web.config, but not with my live web.config, and this was one of the main differences. I didn't make it as far as determining what specific security access was different between the two users. I tried granting my live web.config impersontated user full access to the bin folder on my local machine to no avail.