LS,
I'm using VS2005 C#. I installed VS 2005 SP1 and than I installed Ajax support.
I made my website and on my development PC it works.
On my windows 2003 server (with the windows 2003 SP1 installed) I have no VS (so no VS 2005 SP1), it is just a server.
The older version of my website without Ajax is perfectly accessible through the internet. However when I install my new website (I first did install the Ajax setup.MSI and the ASP.net 2 redistributals were already installed as they were needed for my previous version of the website) my website is no longer accessible, it produces an error.
When I now access my page through the internet from my server I get the following configuration error (in the web.config file):
<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
Should I copy System.Web.Extensions.dll from my development PC to the server (if so where to?)
My guess is that there should be no need to manually copy files, so what is the problem. Is there a different setup to install Ajax support on a Windows 2003 server?
I hope someone has the answer and is willing to help me.
Kind regards
Clemens Linders
I found a thread stating that I needed to copy the System.Web.Extensions.dll's to the bin folder of my project and than publish the website.
So I did and luckily the error above was gone, unluckily I got another error (seems a lot like the first one but the error above originated from the web.config file and this originates from the ASPX file).
I still hope anybody can give me a clue.
The error is (unfortunately partially in dutch, I put a translation between the curly brackets {}):
Serverfout in toepassing /.
Parser-fout {Parser-error}
Beschrijving:Er is een fout opgetreden bij het parseren van een bron die vereist is om aan deze aanvraag te voldoen. Raadpleeg de volgende details van deze parser-fout en pas het bronbestand waar nodig aan. {Description: there was an error ......}Parser-foutbericht:Kan bestand of assembly System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 of een van de afhankelijkheden hiervan niet laden. De manifestdefinitie van de gevonden assembly komt niet overeen met de assembly-verwijzing. (Uitzondering van HRESULT: 0x80131040){Parser-errormessage: Cannot load the file or assembly System.Web.Extensions...or one of it's dependancies. The manifestdefinition of the found assembly doesn't concur (isn't the same) as the referenced assembly}
Fout in bron: {error in source}
Regel 3: <%@dotnet.itags.org. Register Assembly="WebChart" Namespace="WebChart" TagPrefix="Web" %>Regel 4:Regel 5: <%@dotnet.itags.org. Register Assembly="System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"Regel 6: Namespace="System.Web.UI" TagPrefix="asp" %>Regel 7:
Bronbestand:/Default2.aspx Regel:5
Laadtracering van assembly: U kunt de volgende informatie gebruiken om vast te stellen waarom de assembly System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35niet kan worden geladen.
WRSCH: registratie van assembly-bindingen is uitgeschakeld.Als u assembly-bindingsfouten wilt registreren, stelt u de registerwaarde [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) in op 1.Opmerking: er is een prestatiestraf gekoppeld aan de registratie van assembly-bindingsfouten.Als u deze functie wilt uitschakelen, verwijdert u de registerwaarde [HKLM\Software\Microsoft\Fusion!EnableLog].
It is as if it's complaining about a wrong version but I only downloaded ONE version of Ajax and I only have this version on both my development PC as deployment server.
On this site I also found a thread regarding this parser-error. In that thread someone asked if AjaxControlToolkit.dll was installed. I do not have a AjaxControlToolkit.dll (I do have AjaxExtensionsToolbox, but also copying that into the bin-map didn't help). Furthermore the same solution was offered to copy the System.Web.Extensions.dll't to the project's bin folder. Luckily for that person it did the trick for him, but I already did this. Another option that was mentioned is to give the command gacutil -f system.web.extensions.dll. So I copied gacutil to the bin-folder of my server. from CMD (DOS) I executed gacutil -f system.web.extensions.dll
And the result was: system.web.extensions.dll is an invalid option?? (it is in the same bin-folder)
I also downloaded and installed The AjaxControlToolkit. I put the AjaxControlToolKit.dll in the bin-folder of my project, I published the website and still I get this error.
So to repeat in short what I did was:
I installed Ajax both on my developer PC and windows server 2003 deployment pc. I copied system.web.extensions.dll + system.web.extensions.design.dll + AjaxControlToolkit.dll (+ some other dll's) to the bin-folder of my project. I published the website to my server and still I run into problems.
Any ideas?
Kind regards,
Clemens Linders
-------------------------------
Update on my problem (unfortunately it is still there)
As some people in this forum mention that they also have VS installed on their server I installed VS 2005 on my server.
Than I installed the VS80 SP1 update and than I installed Ajax ASP.NET2 version 1.00
I even ran gacutil /i system.web.extensions.dll (also for the design dll)
As my problem persisted I copied the source of my website to this VS and compiled it (the system.web.extensions dll's and the AjaxControlToolkit.dll copied to the bin-folder). Surprisingly enough it did not compile and came up with more or less the same error.
Maybe this will help someone to identify my problem?? Is it an installation issue??
The error I got was:
Error 1 Kan bestand of assembly System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 of een van de afhankelijkheden hiervan niet laden. De manifestdefinitie van de gevonden assembly komt niet overeen met de assembly-verwijzing. (Uitzondering van HRESULT: 0x80131040) C:\Documents and Settings\Administrator\Mijn documenten\Visual Studio 2005\WebSites\RAT\Default2.aspx 5
Translation:
Error 1 cannot load the file or assembly System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 or one of it's dependancies. The manifest of the found assembly doesn't match the assembly reference........
The error points to line 5 of Default2.aspx which is:
<%@dotnet.itags.org.RegisterAssembly="System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
Namespace="System.Web.UI"TagPrefix="asp" %>
It's nice to see that 31 people (at this time) took an interest to look into my problem. I hope that this latest development can give someone a clue as to what actually is causing my problem.
Again thanks.
Clemens Linders
==============================================================================================================================
Finally I can report to you that I have solved my problem (thanks to a tip of my brother).
The error does seem to report that there are two versions of the system.web.extensions.dll. But how I only installed the Ajax asp.net 2 setup I got from the original Ajax website. But than I remembered I also installed VS Orcas Beta 1. And this installed a second version of the system.web.extensions.dll.
I saw in this forum that sometimes people said I looked into my GAC and saw. For newcomers (like myself) let me tell you that if you open c:\windows\assembly that you are actually looking in the GAC. For some people who have the same problem as I did, it is a matter to install the system.web.extensions.dll in the GAC. The way people advise how to do this on this forum is using gacutil /f system.web.extensions.dll (don't forget the design version as well). I found that first I needed to copy the gacutil (which I found after doing a search) in the seem folder as the dll and than still if I used /f I got an error but after doing gacutil /? it seemed far more obvious to do gacutil /i system.web.extenstions.dll (/i for install) which at least worked. My brother also told me that when you open the Assembly folder (or you may call it the GAC), you can add dll's to the gac by simple dragging them to the assembly folder (copy and paste doesn't work). And indeed this is a far easier way of adding dll's to the gac.
But as mentioned this didn't solve my problem. Although I could see that on my server I had the version 1.0.61025.0 installed and on my development system I had 1.0.61025.0 and 2.0.0.0 And than I realised that this 2.0.0.0 version had to come from the Orca Beta version.
I tried to cheat and also installed the 2.0.0.0 (which is 925Kb versus aprox 650Kb for the other version). But that didn't work.
I found that on the web.config file most references to the system.web.extensions.dll were made to 1.0.61025.0 but some were made to 2.0.0.0. Als the aspx file made reference to 2.0.0.0. I changed all these to 1.0.61025 but that didn't help. Suddenly the error on my server chnaged from line 5 to line 1.
When you publish the website a new dll is made by VS. and during publishing a reference is added to line 1 of the aspx file. Because I also had the 2.0.0.0 version of the system.web.extensions.dll in my GAC. A reference to this 2.0.0.0 dll is made in the dll that is created during publishing. I tried to remove this 2.0.0.0 dll by right-clicking it in the windows/assembly folder and choosing remove. But it kept saying it couldn't remove this file. It was being used. So that is when I was sure that this had to come from Orca.
Only when I removed Orcas and repaired VS 2005, my problem was gone.
I did get another problem though, my webservice suddenly sometimes doesn't give a response. I haven't debugged that yet but I found a reply on the interned of someone who also removed Orca and repaired VS 2005 and everything seemed to work accept for websites. Websites and webservices isn't the same but I guess I will remove VS 2005 and re-install it.
Despite that the golden tip didn't come from this forum I would like to thank the people who read this and at least tried.
The reason that I kept updating my problem and finally also mentioned the salution is that I hope that others will benefit.
OR BETTER: don't make the same mistake as I did and don't install a Beta version of VS on the same partition as where you have your VS that you really use
I hope that people will benefit from my mistake and what I have written here.
Goodluck
Clemens Linders
Versiegegevens: Microsoft .NET Framework Versie:2.0.50727.42; ASP.NET Versie:2.0.50727.210
Hi, Clemens Linders
We appreciates that you share the solution so that the answer can be found and used by other community members having similar questions.
Thank you very much,You are so kind:)
Best Regards
No comments:
Post a Comment